FlyNat LogBook Desktop is a standalone Windows application designed for professional drone pilots who need a structured, compliant flight log. It parses raw flight data files directly from your drone — no cloud upload required for the core logbook — and stores everything locally in an encrypted-at-rest SQLite database on your computer.
The app is distributed as a single .exe file built with PyInstaller. Just download and run — no Python installation, no dependencies, no admin rights needed.
C:\Users\[you]\FlyNat\logbook.db. No flight data is sent to any server. The only optional cloud feature is Google Drive sync, which you control.
FLIGHT LOGBOOK
Full searchable table of every flight: date, drone model, duration, location, battery levels, altitude, and personal notes.
STATISTICS DASHBOARD
Summary stats — total hours flown, number of flights, average duration, favourite locations, battery trends.
ADVANCED ANALYTICS
Charts and breakdowns by drone model, month, altitude distribution, and flight duration histogram.
PDF EXPORT
Generate a professional, compliance-ready PDF logbook report. Includes flight map thumbnails, stats, and pilot info — suitable for CAA / CAAI inspection.
GOOGLE DRIVE SYNC
One-click backup of your entire logbook to Google Drive as a JSON file. Readable by the FlyNat mobile app for live viewing on your phone.
MULTI-FORMAT IMPORT
Drag and drop DJI binary logs, DJI CSV exports, Betaflight blackbox files, or generic CSV. The parser handles conversion automatically.
| Format | Description | Fields Extracted | Support |
|---|---|---|---|
| .DAT / .TXT | DJI binary flight log (decoded via dji-log-parser) | Date, duration, GPS path, altitude, battery, drone model | FULL |
| DJI CSV | CSV exported from DJI Flight Hub or DJI Assistant | Date, duration, location, altitude, battery start/end | FULL |
| .BBL / .BFL | Betaflight / Cleanflight blackbox binary | Date, duration, GPS (if available), drone identifier | FULL |
| Flyability Elios 3 | CSV / JSON export from Flyability Inspector — inspection drone logs | Date, duration, location, altitude, flight identifier | FULL |
| Generic CSV | Any CSV with flight data — custom column mapping | Configurable via CSV Mapper tool | MAPPED |
dji-log.exe and handles this automatically.
All flight records are stored in a local SQLite database. No account, no login, no internet connection required to use the logbook.
Database location:
C:\Users\[YourName]\FlyNat\logbook.db
The database contains three tables:
- flights — One row per flight: date, duration, drone model, GPS coordinates, battery start/end, location name, notes, sync status.
- flight_path — GPS path points (latitude, longitude, altitude, sequence) for each flight — used to render map thumbnails in PDF.
- settings — Key-value store for pilot name, Drive token, and app preferences.
FlyNat/ folder from your user profile to an external drive or cloud storage. The .db file is portable and can be moved to any Windows machine running FlyNat.
The PDF export feature generates a professionally formatted logbook report that meets the record-keeping requirements expected by civil aviation authorities, including Israel's CAAI (רשות התעופה האזרחית). Each report includes:
- Cover page — Pilot name, report generation date, summary statistics (total flights, total hours, drones flown).
- Flight table — Every flight in chronological order with date, location, drone model, duration, altitude, battery levels, and notes.
- Map thumbnails — For flights with GPS path data, a map image showing the flight area is embedded per entry.
- Statistics page — Aggregated totals, breakdown by drone model and month.
The Google Drive sync feature lets you upload a snapshot of your entire logbook to your personal Google Drive with one click. This serves two purposes: a cloud backup, and a way for the FlyNat mobile app to read your desktop logbook data.
OAuth 2.0
Drive API
The first time you sync, a browser window opens for Google OAuth authorization. After approving, a token is saved at C:\Users\[you]\.flynat\token.json. Subsequent syncs happen silently with no browser interaction.
- Direction: Desktop → Drive only. The desktop app writes; the mobile app reads. No data flows back to the desktop.
- File: Uploaded as
flynat_logbook.jsonin your Drive root. Overwritten on each sync. - Scope: The app only requests
drive.filepermission — it can only access files it created, not your entire Drive.
Download the .exe
Download FlyNat LogBook.exe from the link above or from the FlyNat home page. No installation wizard — just a single portable executable (~320 MB, all dependencies bundled).
Run the app
Double-click the .exe. Windows SmartScreen may show a warning on first run — click More info → Run anyway. The app creates the FlyNat\ folder in your user profile and initializes the local database automatically.
Enter your pilot name
On first launch, a setup dialog asks for your pilot name. This name appears on exported PDF logbooks and is stored locally — no account needed.
Import your first flight
In the Logbook tab, click Import Flight Log. Select a DJI .DAT, .TXT, or CSV file from your drone or DJI Flight Hub export. The parser automatically extracts flight data and adds it to your logbook.
Export a PDF report (optional)
Click Export PDF in the Logbook toolbar to generate a compliance-ready A4 logbook. The PDF is saved to your Downloads folder.
Sync to Google Drive (optional)
Click Sync to Drive to back up your logbook and make it visible in the FlyNat mobile app. Authorize with Google once — all future syncs are one click.
Export PDF
Live UTM
- Step 1 — Desktop: Import your flight logs from DJI / FPV files, then click Sync to Drive. Your logbook is saved to Google Drive.
- Step 2 — Mobile: Open the FlyNat app and go to your Profile. Your logbook loads automatically from Google Drive — read-only view.
- Live flights: During an active flight, the mobile app streams your GPS to the FlyNat server in real time. This is independent of the logbook — no desktop needed.
- OS: Windows 10 or Windows 11 (64-bit). No macOS or Linux version is currently available.
- Storage: ~350 MB for the executable. Additional space for your logbook database (grows with flight count — typically a few MB).
- Memory: 512 MB RAM minimum. 2 GB recommended for large logbooks with GPS path data.
- Internet: Required only for Google Drive sync and PDF map thumbnails. Core logbook works fully offline.
- No admin rights required: The app writes only to your user profile folder. It does not modify system directories or the registry.
- No installation: Single portable .exe — copy it anywhere, run from USB if needed.