# AirData Integration: Automatic Flight Log Sync
### The Manual Logging Problem
Operators using AirData for compliance records, maintenance tracking, and pilot analytics have been doing the same routine for every flight: open the flight logs page in FlytBase, download each log file, switch to AirData, upload it, fill in the pilot and aircraft details, save. For a fleet running multiple flights a day across multiple pilots, this becomes a meaningful daily tax — and any flight that gets skipped means a gap in the compliance record.
The AirData Flink eliminates that workflow. As soon as a drone lands, FlytBase syncs the flight log to AirData automatically. The flight appears in your AirData dashboard with the correct pilot already attributed, ready for analysis, maintenance triggers, and audit reports.
If you're not already familiar with AirData, it's a flight log management and fleet analytics platform widely used for regulatory compliance, maintenance scheduling, pilot performance, and battery health tracking. More at[ airdata.com](https://airdata.com/).
***
### How the Automatic Sync Works
Every flight conducted through FlytBase generates a flight log on landing — this happens regardless of how the flight was initiated. Docked drone flights, non-docked drone flights, scheduled missions, manually triggered flights, alarm-triggered responses, Go To Location flights — all of them produce a log.
With the AirData Flink connected, that log is pushed to AirData immediately after landing. The flight appears in your AirData account attributed to the pilot who flew it, with no manual upload step.
For attribution to work, FlytBase needs to know which AirData pilot corresponds to each FlytBase user. That's what pilot mapping handles.
***
### Pilot Mapping
Each pilot in AirData has a unique AirData Pilot Token. Inside the AirData Flink configuration in FlytBase, there's a pilot mapping tab where you link each FlytBase user to their AirData Pilot Token.
Once a pilot is mapped, every future flight by that pilot syncs automatically with the correct attribution.
If a pilot isn't mapped when they fly: the auto-sync for that flight will fail. The flight log still exists in FlytBase, and once you add the mapping, you can manually push that flight to AirData using the workflow below. Auto-sync does not retry historical flights after a mapping is added.
***
### Manual Sync from Flight Logs
For flights that didn't sync automatically — usually because the pilot wasn't mapped yet — you can push them to AirData from the flight logs page.
Step 1: Open the flight logs page and select the flight you want to sync.
Step 2: Click Share to Flink.
Step 3: In the share dialog, select AirData from the available Flinks.
Step 4: Confirm the sync. The flight is pushed to AirData with the mapped pilot's attribution.
If the pilot for that flight still isn't mapped, the manual sync will also fail — map the pilot first, then retry.
***
### Flight Coverage
Auto-sync runs for any flight that produces a flight log in FlytBase. This includes:
* Docked drone flights (Dock 1, Dock 2, Dock 3)
* Non-docked drone flights
* Scheduled missions
* Manually triggered missions
* Alarm-triggered response flights
* Go To Location flights
If a flight log is generated, it syncs.
***
### Setting Up the Integration
Setup is a two-step process.
1. Open the AirData Flink in your FlytBase organization settings and toggle it on
2. Open the pilot mapping tab and add AirData Pilot Tokens for your pilots
Once enabled and mapped, auto-sync runs in the background for every subsequent flight. Most teams set this up once and operate in fire-and-forget mode from then on.
***
### Hardware Compatibility
The integration operates on flight logs, which are produced by all FlytBase-connected drones:
* Dock 1, Dock 2, Dock 3
* Non-docked drones registered with FlytBase
No firmware requirements or hardware-specific constraints.
***
### Availability
Available now for all FlytBase organizations. Toggle the AirData Flink on under your organization's Flinks settings and add pilot mappings to start syncing.
An active AirData account is required. You'll need each pilot's AirData Pilot Token to complete pilot mapping — these are available within each pilot's profile in AirData.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://releases.flytbase.com/april-2026/airdata-integration-automatic-flight-log-sync.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.