An operator can license de-identified flight data it collects for itself, but most airline flight data sits inside a safety programme that pilots agreed to for safety use only. Read that agreement first. Simulator session logs and training records are usually easier, because the training centre creates them, yet they name trainees and must be stripped. Cockpit voice recordings stay out. A pilot's logbook belongs to the pilot.
- Flight data collected under an FAA-approved FOQA programme is governed by the operator's agreement with its pilots.
- De-identified means no flight, date or crew can be worked out, not only that names are gone.
- Simulator and training-centre records are the operator's own, but each one is about a named trainee.
- Cockpit voice recordings are kept for accident investigation and are not a licensing asset.
Can an operator license flight data to AI companies?
Yes for some of it. The operator controls the data its aircraft and training devices produce, but three things limit what can leave: the pilot agreement behind the flight data programme, contracts with the aircraft maker and lessor, and the fact that most records point to a named crew.
The table sorts the usual records. This page is general information, not legal advice. Your own programme documents, labour agreements and contracts decide.
| Record | Who controls it | Can it be licensed? |
|---|---|---|
| Routine flight data from quick access recorders (FOQA or flight data monitoring) | The operator, under its approved programme and pilot agreement | Only if the agreement allows use outside safety, and only de-identified |
| Mandatory flight data recorder contents | The operator, for a short retention period | Little to license. The recorder holds the most recent hours only |
| Cockpit voice recordings | The operator, for accident investigation | No |
| Simulator session logs and instructor grading | The training centre or the operator's training department | Often, after trainee and instructor names are removed |
| Crew qualification and training records | The certificate holder | Only as de-identified, aggregated training histories |
| Pilot logbooks | The individual pilot | Not by the operator |
| Engine and system health data sent to the maker | Shared under the maker's service contract | Read the contract. The maker often holds rights in the processed data |
What is the difference between operational flight data and simulator sessions?
Operational flight data is what a real aircraft recorded on a real flight. Simulator data is what a training device recorded while a crew practised. The first is tied to a safety programme and a flight that can be traced. The second is created by the training organisation for its own purposes.
US rules define a FOQA programme as "an FAA-approved program for the routine collection and analysis of digital flight data gathered during aircraft operations" (14 CFR 13.401). The mandatory recorder is a different thing. An operator must keep its recorded data only "until the airplane has been operated for at least 25 hours" (14 CFR 121.344), so the crash recorder is not an archive. The years of history sit in the FOQA or flight data monitoring system.
A simulator is defined by what it copies: a full flight simulator is "a replica of a specific type; or make, model, and series aircraft cockpit" (14 CFR 1.1). Its session logs record a crew handling an engine failure, a rejected take-off or a windshear escape. Real flights almost never contain those events. That is why training-device sessions are worth describing separately.
Do pilot agreements restrict licensing flight data?
Usually yes. Flight data programmes run on a promise to crews that the data is used for safety and that individuals are protected. A licence to an outside party is a new use, so the pilot group normally has to agree to it.
The FAA's guidance shows how central that promise is. Its checklist for a programme plan asks whether "a copy of an agreement with the pilot association (if applicable) for FOQA data usage" is attached. It describes a "gatekeeper" as the person "who can link FOQA data to an individual flight or crewmember" and says "the gatekeeper is normally a member of the pilot association" (FAA AC 120-82).
The regulation adds a protection that depends on the programme staying what it is: "the Administrator will not use an operator's FOQA data or aggregate FOQA data in an enforcement action against that operator or its employees" when the data comes from an approved programme (14 CFR 13.401). Before any outside use, ask your safety department and counsel whether it could affect the programme's approval or the trust it rests on.
Are simulator sessions and training records easier to license?
Often, yes. No safety-programme agreement covers them in most organisations, and the training centre created them. The limits are the people in them and the contracts around the device.
A US training centre must keep a record for each trainee that includes "the trainee's performance on each lesson and the name of the instructor providing instruction" and "the date and result of each end-of-course practical test" (14 CFR 142.73). An airline must "maintain current records of each crewmember" covering "proficiency and route checks, airplane and route qualifications, training" (14 CFR 121.683). These are personnel records about named people. They can be licensed only as de-identified training histories, and employment law or a labour agreement may still say no.
Check two contracts. The simulator runs on a data package licensed from the aircraft maker, and the device maker's software may restrict export of session data. Third-party trainees are customers: a training services agreement often says their records are confidential to the customer airline.
Who owns flight data: the operator, the aircraft maker or the pilot?
No single rule answers it. In practice the operator holds the raw data its aircraft record, the maker holds rights under its service contracts, a lessor may have rights under the lease, and the pilot owns a personal logbook.
The pilot's logbook is the clear case. The duty to log falls on the person: "each person must document and record the following time in a manner acceptable to the Administrator" (14 CFR 61.51). An operator cannot license its pilots' logbooks. A pilot could offer their own, but one logbook is a small record.
For everything else, read the contracts in this order: the pilot agreement for the flight data programme, the engine and airframe health-monitoring agreements, the aircraft lease, and the simulator data licence. Each can limit use of data the operator physically holds.
How do you remove crew and tail identifiers, and is crew consent needed?
Remove everything that lets someone work out the flight: tail number, flight number, exact date and time, city pair and crew codes. Names alone are not enough. Where the data stays linkable to a person, consent or agreement from the crew is the safer basis.
The FAA's own definition sets the bar: de-identified data is "data from which any identifying elements that could be used to associate them with a particular flight, date, or flightcrew has been removed" (FAA AC 120-82). A flight can be re-identified from public tracking data if the date, route and aircraft type survive.
Crew based in Europe add data protection law. Personal data is "any information relating to an identified or identifiable natural person", including a person who can be identified "indirectly" (GDPR, Article 4). A flight data file keyed to a roster is personal data about the two pilots. The de-identification guide explains the general method.
- Replace tail numbers with stable codes per aircraft, so a fleet can still be studied.
- Shift dates by a random offset per aircraft and round times.
- Replace airports with a class (runway length, elevation band, approach type) unless the buyer needs the location and the pilot group agrees.
- Drop crew identifiers and any free-text remarks.
- Keep the logical frame layout, the data map that says what each recorded parameter is.
Can cockpit voice recordings be included?
No. Treat cockpit audio as outside any licence. It exists for accident investigation and is protected by law and by every pilot agreement.
The US rule says recorded cockpit information "is used to assist in determining the cause of accidents or occurrences" and that "the Administrator does not use the record in any civil penalty or certificate action" (14 CFR 121.359). The investigating board "may not disclose publicly any part of a cockpit voice or video recorder recording" except the parts of a transcript it decides are relevant (49 U.S.C. 1114).
What are flight data and simulator records worth?
No public source gives a price for this kind of record, so this page does not quote one. Value depends on how much of the archive can lawfully leave and how well it is described.
The likely users are developers of models that predict maintenance needs, assist pilots, grade training or simulate flight. Flight data becomes more useful when it can be joined to what was done to the aircraft afterwards. See the guide to aircraft maintenance records.
| Raises the value | Lowers the value |
|---|---|
| Several years of continuous data across a fleet | A few months, or gaps after a system change |
| The parameter map for each aircraft configuration | Raw binary files with no decoding information |
| Events already detected and labelled by the analysis system | Unprocessed data only |
| Simulator sessions with instructor grading attached | Session logs with no outcome |
| A link to maintenance actions on the same aircraft code | Flight data that cannot be joined to anything |
| Written agreement of the pilot group | An unresolved question over programme terms |
Example: inventory for a regional operator with a training centre
A fictional operator flies 30 turboprops and runs two full flight simulators. Its safety manager and head of training fill in one page. The figures are invented to show the method.
| Record | Volume | Rights position | Decision |
|---|---|---|---|
| FOQA flight data | 6 years, about 210,000 flights | Pilot agreement limits use to safety | Out until the pilot association agrees in writing |
| Detected event library | 48,000 events | Same agreement | Out for the same reason |
| Simulator session logs, own crews | 9 years, 31,000 sessions | Company records; no clause on outside use | In, de-identified, after notice to the pilot group |
| Simulator sessions, customer airlines | 12,000 sessions | Confidential under training contracts | Out unless each customer agrees |
| Instructor grading sheets | Linked to own-crew sessions | Personnel records | In as scores only, with no names and no remarks |
| Cockpit voice recordings | Not archived | Protected | Out |
| Maintenance records | 9 years | Company records | In, joined on the aircraft code |
Fictional example. The first conversation is about simulator sessions and maintenance history, while the pilot association considers the flight data question.
Common mistakes operators make
Most come from treating flight data as ordinary company data.
- Offering FOQA data without reading the pilot agreement the programme was approved with.
- Removing names and leaving tail number, date and route in place.
- Assuming the mandatory flight recorder holds an archive.
- Including customer airlines' simulator sessions without their agreement.
- Shipping raw recorder files without the parameter map.
- Forgetting the simulator data package licence and the engine maker's data terms.
- Treating a pilot's personal logbook as a company record.
Flight and training records as a data asset
An operator that has flown the same fleet for years holds something a simulator cannot generate: how real aircraft and real crews behaved, flight after flight, and how trainees handled failures that rarely happen in service. Whether any of it can be licensed depends on agreements the operator already has.
Origin works with buyers and helps an operator describe what could lawfully leave, find out what it could be worth and decide whether to go further. Nothing is exported at the start. A repair station or maintenance organisation holds a different part of the same picture. Origin Data Partners is an independent data partner that helps companies get their data bought. A buyer may pay Origin when a deal closes.
Does your company hold records like these? See what your data is worth.
Common questions
Can you sell flight data to AI companies?
An operator can license de-identified flight data it controls. Data collected under an FAA-approved FOQA programme is governed by the operator's agreement with its pilots, which usually limits use to safety. Get the pilot group's written agreement first.
Can you sell flight simulator data to AI companies?
Often. Session logs and grading belong to the training organisation that created them. Remove trainee and instructor names, leave out customer airlines' sessions unless they agree, and check the simulator data package licence.
Can you sell pilot logbooks to AI companies?
An operator cannot, because a logbook is the pilot's own record under 14 CFR 61.51. A pilot could offer their own, but one logbook is a small record. Operators hold crew training and qualification records instead, which are personnel records.
Who owns flight data from an aircraft?
No single rule decides. The operator holds the raw data, the pilot agreement limits how programme data is used, the engine or airframe maker may hold rights under a service contract, and a lessor may have rights under the lease.
What are flight data worth to an AI buyer?
No public source gives a price. Value rises with years of continuous fleet data, the parameter map, labelled events and a link to maintenance history. It falls where rights are unresolved or files cannot be decoded.
Is crew consent needed to license flight data?
Where data can be linked to a flight or crew member, agreement from the pilot group is the practical requirement, and European data protection law treats such data as personal. Properly de-identified data removes the link to a flight, date and crew.
Sources and further reading
- 14 CFR 13.401: Flight Operational Quality Assurance Program, prohibition against use of data for enforcement purposes
- FAA Advisory Circular 120-82: Flight Operational Quality Assurance (PDF)
- 14 CFR 121.344: digital flight data recorders for transport category airplanes
- 14 CFR 121.359: cockpit voice recorders
- 49 U.S.C. 1114: disclosure, availability and use of information (National Transportation Safety Board)
- 14 CFR 142.73: training center recordkeeping requirements
- 14 CFR 121.683: crewmember and dispatcher record
- 14 CFR 61.51: pilot logbooks
- 14 CFR 1.1: general definitions (flight simulation training device, full flight simulator)
- Regulation (EU) 2016/679 (GDPR): Articles 4, 5 and 9
