How to import flights from MyFlightBook

If you've been logging on MyFlightBook for a few years, you have a CSV that DaPilot reads natively. The import takes about a minute for a typical airline-pilot logbook. Aircraft, tail numbers, every time field, approaches, and remarks all map cleanly. Duplicate detection makes re-importing safe.

Why this matters

MyFlightBook is the most popular free pilot logbook. Switching apps usually means losing fields, re-typing tails, or accepting that your historical totals will be approximate. DaPilot reads the MyFlightBook CSV format end to end, so the only thing you might lose is anything stored in MyFlightBook's app-specific fields that have no FAA equivalent (those go into remarks).

What you need

Your MyFlightBook account login.
About five minutes for the export plus a minute for the import.
DaPilot installed and signed in.

Export from MyFlightBook

1Sign in to MyFlightBook on the web

Go to myflightbook.com and sign in. The export is on the web side, not in the iOS app. The web side is where MyFlightBook keeps the CSV download.

2Open Logbook → Tools → Download

The exact menu path moves around as MyFlightBook updates. As of early 2026, the path is Logbook → Tools → Download. Pick CSV as the format. Some MyFlightBook accounts also offer "MyFlightBook Native CSV" and a generic CSV; either works.

3Save the file to your iCloud Drive

Save the file somewhere you can pick it up from the iPhone. iCloud Drive is the simplest. The file name is usually myflightbook-export-YYYY-MM-DD.csv.

Import into DaPilot

4Open the import screen

In DaPilot, tap Settings → Import. Pick MyFlightBook CSV as the source. Tap Pick file and navigate to the CSV in iCloud Drive (or wherever you saved it).

5Wait for the parse

DaPilot reads every row and shows a summary: number of flights, number of unique aircraft, date range. If the parser flags any row as malformed, you'll see the row number and the reason. Most of the time the file is clean.

6Confirm the aircraft fleet

DaPilot creates an aircraft entry for every unique tail number in the file. The first time around, you'll see a "New aircraft" list with each tail and the type designator the parser inferred. Confirm the type designators (the parser uses MyFlightBook's TypeName field, which is usually right but occasionally generic). If anything looks wrong, fix the type before saving the import.

7Tap Import

The full import takes about thirty seconds for a thousand-flight logbook. The dashboard refreshes with your historical totals. Currency cards recompute from the most recent 90 days of imported flights.

What gets imported

Date, route (departure and destination airports)
Aircraft tail number and type designator
Total time, PIC, SIC, dual received, CFI given
Cross-country, night, simulated instrument, actual instrument
Day landings, night landings (full-stop and T&G if MyFlightBook stored them as separate fields)
Approaches (count, with names if available)
Holds, intercepting and tracking
Block out / off / on / in times if you logged them
Remarks
Sign-off / endorsements as a remarks line (DaPilot does not currently model endorsements as a separate type)

What does not import

Image attachments (photos of paper logbook pages, IFR clearance screenshots, etc.) stay in MyFlightBook.
App-specific fields like custom property tags (MyFlightBook's "Property" system) become a remarks line.
Flight Duty Periods and rest periods (these are DaPilot's Airline Mode model and have no MyFlightBook equivalent).

Duplicate detection

If you re-import the same file, DaPilot detects duplicates by the combination of date + route + total time. The route is the full route string (e.g. "KMRY-KSFO"); total time must match exactly. Same row twice, second one is skipped. This means you can:

Re-import after editing flights in MyFlightBook (only the new and changed rows are processed)
Recover from an interrupted import by running it again
Append a partial export (only rows since your last DaPilot date) without doing the full file

The dedupe is exact-match, so if you change the tail format between MyFlightBook and DaPilot the dupes won't be caught. Stick with one tail format throughout.

Common pitfalls

Exporting only a date range. MyFlightBook lets you filter the export. If you filter to the last month and import, you only get a month. Pull the full history once.
Mixing MyFlightBook native and FAR-style CSV exports. Pick one format and stick with it; mixing creates inconsistent column headers across imports.
Editing flights in both MyFlightBook and DaPilot in parallel. Pick one as the source of truth before you switch.
Importing without checking the aircraft type designators. MyFlightBook stores generic types for some aircraft (e.g., 'Cessna 172' instead of 'C172'). Fix the designators in the New aircraft list before tapping Import or your fleet rolls up wrong.
Re-importing a file with edited flights and expecting the edits to land. Dedupe will skip those rows. Edit in DaPilot directly after the initial import.

After the import

Spot-check three things:

Total time on the dashboard matches your MyFlightBook total. If you find a 0.1-hour drift, it's almost always a single row with a decimal-format mismatch; search and fix.
Recent currency cards match what MyFlightBook showed yesterday.
One specific recent flight to make sure the time fields are in the right slots (PIC vs SIC vs dual).

If anything is off, edit. There's no penalty for editing imported flights. After you're confident the import is clean, you can switch your day-to-day logging to DaPilot and stop opening MyFlightBook.

Switching workflows

Some pilots run both apps in parallel for a month while they get comfortable with DaPilot. That works, but be intentional about which one is the source of truth so you don't end up reconciling. The simplest approach: do your daily logging in DaPilot, and re-export from MyFlightBook only if you find a historical row missing.

Last updated April 27, 2026 · 5 min read