Docs › Data

Import Logbook

Import flights from other pilot logbook apps via CSV or TSV files.

Supported Formats#

AppFile TypeSeparatorTime Format
ForeFlightCSVCommaDecimal hours
LogTen ProTSVTabMinutes
MyFlightbookCSVCommaDecimal hours
CrewLounge PilotLogCSVSemicolon or CommaDecimal hours or HH:MM
mccPILOTLOGCSVSemicolon or CommaDecimal hours or HH:MM
RosterBusterCSVCommaMinutes
SIEPACSVCommaHH:MM
Flylog.ioCSVComma or SemicolonDecimal hours or HH:MM
Aviation Pilot LogbookCSVSemicolonHH:MM
CSV (Manual)Any CSVAuto-detectedAuto-detected

How to Import#

  1. Select your logbook format from the format grid
  2. Review the export instructions that appear below (how to export from your source app)
  3. Tap Choose file and select your exported CSV or TSV file
  4. A preview is displayed showing:
    • Total flight count
    • Date range covered
    • New aircraft found
    • Duplicate flights detected
  5. Choose a duplicate handling strategy:
    • Skip (default) – keep existing flights, ignore duplicates
    • Replace – overwrite existing flights with imported data
    • Import all – import everything, including duplicates
  6. Tap Import to proceed

How to Export from Your Source App#

ForeFlight#

  • On iPad: More → Logbook → tap the share icon → Export CSV
  • On web: plan.foreflight.com → Logbook → Export
  • The exported file contains two tables (Aircraft + Flights) — no extra configuration needed
  • All time values are in decimal hours. Approach types, crew names (Person1-6) and custom fields are imported automatically

LogTen Pro#

  • Open LogTen Pro → Reports → Exporters → select "Export Flights (Tab)"
  • Do NOT use "Dynamic Export" — it may omit columns
  • The file is tab-separated (.txt), not CSV
  • Make sure to include all available columns in your export settings
  • Crew names and approach types are imported if present in the export

MyFlightbook#

  • Go to myflightbook.com → sign in → Import/Export → Export → CSV
  • The Route field contains departure + intermediate stops + arrival separated by spaces
  • Check all optional columns for a complete export

CrewLounge PilotLog / mccPILOTLOG#

  • Open the CrewLounge PilotLog or mccPILOTLOG app → Settings → Export → CSV
  • Both semicolon and comma separators are supported (case-insensitive header matching)
  • Both decimal hours and HH:MM time formats are auto-detected (v2 support)
  • Export ALL available fields for best results
  • Aircraft type, operator, crew, runways and approach types are imported

RosterBuster#

  • Open RosterBuster app → Logbook → Export → choose Flights CSV
  • Optionally, also export the Aircraft CSV file separately
  • After the flights file is loaded, you can add the aircraft file to enrich type info
  • Crew (PIC, SIC, FO, SO, Instructor, Purser, Relief, up to 10 Cabin Crew, up to 10 Other) are imported into the Crew field
  • Approaches (up to 6), holds, solo time, cross-country, simulated instrument (hooded IFR) time are imported
  • De-icing, autoland, route, and PF/PM flags are captured when present

SIEPA#

  • From the SIEPA school portal, export your logbook as CSV
  • Multi-page files with repeated headers are handled automatically
  • Total/subtotal rows are ignored. Dates are in DD/MM/YYYY format
  • Simulator-only rows (no flight date but a sim date) are imported as SIMULATOR sessions

Flylog.io#

  • Go to flylog.io → sign in → Settings or Export section → download CSV
  • Both the old format (comma-separated, decimal hours) and the new format (semicolon-separated, HH:MM durations) are supported automatically
  • Columns: date, departure/arrival airports, aircraft type and registration, block time, PIC/SIC time, night, IFR, multi-pilot, takeoffs/landings (day and night), PIC name

Aviation Pilot Logbook#

  • Open the Aviation Pilot Logbook app → Settings → Export → CSV Export
  • Crew list, approach type, runways, and PF/PM are imported
  • Aircraft type, registration, and position (PIC/SIC/Dual/Instructor) are mapped automatically

CSV (Manual)#

For any CSV file not matching the formats above, use the CSV (Manual) option:

  1. Select the file – separator (comma, semicolon, tab) is auto-detected
  2. Preview – shows the first 5 rows with column count and row count
  3. Column mapping – for each CSV column, select the corresponding FlightLog field from a dropdown grouped by category (Core, Aircraft, Times, Duration, Crew, Counts, Ops, Notes)
  4. Format detection – date and duration formats are auto-detected with manual override
  5. Mapping saved – your column mapping is remembered for next time

Duplicate Detection#

Flights are matched by the combination of date + departure airport + arrival airport. When duplicates are found, you can choose one of three strategies:

  • Skip (default) – keep existing flights, ignore duplicates
  • Replace – overwrite existing flights with imported data
  • Import all – import everything, including duplicates

Automatic Flight Enrichment#

When the airport database is available, imported flights are automatically enriched with:

  • Coordinates and city names – from the airport database
  • Great-circle distance – calculated from departure and arrival coordinates
  • Ground speed estimation – derived from distance and block time
  • Night time flag – computed based on departure/arrival coordinates, date, and times
  • Timezone-aware timestamps – all times are generated with proper UTC offsets based on airport timezone data
  • Cross-country flag – imported from CrewLounge, MyFlightbook, LogTen Pro, RosterBuster, and CSV when present
  • Hooded IFR flag – simulated instrument / hooded IFR time imported from CrewLounge, MyFlightbook, LogTen Pro, RosterBuster, and CSV
  • Session type detection – single-pilot, single-engine flights without a flight number are classified as General Aviation
  • Fuel kg→t auto-conversion – fuel values in kilograms are automatically converted to tonnes across all importers
  • Airline code derivation – the airline ICAO/IATA code is derived from the flight number when not explicitly provided
  • Missing times backfill – when scheduled or actual times are missing, they are inferred from available data (scheduled↔real, off/on times default to out/in times)

Can't find what you need? Open the helpdesk or write to support@flightlog.io.