DaPilot

How to import flights from ForeFlight Logbook

ForeFlight is what most US-based GA pilots use for charts and weather, and many use its built-in logbook too. Switching the logbook side of your life to DaPilot is a one-shot CSV import, plus an optional decision about which app stays your daily logger going forward.

Why this matters

If your logbook is in ForeFlight, your flights live in ForeFlight's cloud. Switching to DaPilot does not require you to abandon ForeFlight as an EFB; it just means DaPilot becomes the logbook of record. The CSV import preserves every FAA field, so your hour totals, currency, and historical record show up on the DaPilot dashboard intact.

What you need

  1. Your ForeFlight account access (same email used in the iOS app).
  2. About ten minutes total: five for the export, five for the import and review.
  3. DaPilot installed and signed in.

Export from ForeFlight

ForeFlight's logbook export is one of those features that's not in the iPad app. You do it from the web side.

1Sign in at plan.foreflight.com

Open plan.foreflight.com in a browser and sign in with the same Apple ID or email you use on the iPad. The web logbook lives at plan.foreflight.com/logbook.

2Open Logbook → Reports → Export

The export option is under Logbook → Reports → Export Flights as of early 2026. ForeFlight occasionally renames menu items; if the path moves, look for "Export" or "Download" inside the Logbook section.

3Pick CSV and the full date range

ForeFlight offers PDF and CSV exports. Pick CSV for DaPilot. Set the date range to "All flights" so the export includes your full history. Smaller ranges are fine if you only want a slice.

4Download the file

ForeFlight emails you the file or makes it available for download in the browser depending on which export path you used. Save it somewhere you can pick it up on the iPhone (iCloud Drive is the simplest).

Import into DaPilot

5Open the import screen

In DaPilot, tap Settings → Import. Pick ForeFlight CSV as the source. Tap Pick file and navigate to the file you downloaded.

6Confirm aircraft and fleet

ForeFlight stores aircraft a bit differently than MyFlightBook. The CSV has a separate aircraft block and a flights block; DaPilot reads both and creates the fleet first, then the flights.

You'll see a list of aircraft with type designators. ForeFlight type designators are usually accurate. Confirm the list and tap Continue.

7Tap Import

The import processes flights in chronological order. A typical 5,000-flight ForeFlight history takes about 45 seconds. The dashboard refreshes once the import is done.

What gets imported

  • Date, route, aircraft tail and type
  • Total time and every FAR 61.51 time category (PIC, SIC, dual, CFI)
  • Cross-country, night, simulated instrument, actual instrument
  • Day landings, night landings, full-stop and T&G separately
  • Approaches with names (ForeFlight stores approach names by default)
  • Holds, intercepting and tracking
  • Block out / off / on / in times if you logged them
  • Remarks (ForeFlight calls this "Notes")
  • ForeFlight's track-log-derived flights become regular flights with a "Track log" tag in remarks

What does not import

  • Photos and attachments. ForeFlight stores receipts and approach plate screenshots; those stay there.
  • Endorsements. ForeFlight has a separate endorsements model that DaPilot does not yet match. Endorsement records become a remarks line on the affected flight.
  • Flight Duty Periods. ForeFlight does not model FDPs; if you fly Part 121 and were tracking duty in a separate spreadsheet, you'll need to add that data manually in Airline Mode after the import.

Re-importing

Heads up: unlike the MyFlightBook importer, the ForeFlight importer does not currently dedupe on re-import. If you re-import the same ForeFlight CSV twice, you will end up with duplicate flights. Pick MyFlightBook or ForeFlight as your primary source and stick with it. If you have already imported a ForeFlight CSV and need to re-pull data, edit the source file to keep only the new rows before importing again.

ForeFlight's CSV format includes a per-flight unique ID. DaPilot does not key on that ID, so editing a flight in ForeFlight after a previous import will not propagate to DaPilot.

After the import

Spot-check the same three things as the MyFlightBook import:

  1. Dashboard total matches ForeFlight Reports total.
  2. Recent currency cards match what ForeFlight showed.
  3. One recent multi-leg day to confirm each leg is its own row.

ForeFlight users sometimes have very granular track-log-derived rows (a single 1.5-hour flight imported as five 0.3-hour rows because the track log was paused). The import preserves whatever ForeFlight had. If you want to consolidate those into a single row in DaPilot, do it manually after the import.

What about exporting back to ForeFlight?

DaPilot exports a MyFlightBook-compatible CSV. ForeFlight does not have a public CSV import format as of 2026, so going back the other way is not a clean round-trip. If you need data in ForeFlight after switching, export from DaPilot and use ForeFlight's "Add flight from spreadsheet" tool, which accepts a structured CSV with explicit column mappings. It's a manual step.

If round-tripping with ForeFlight is a hard requirement, MyFlightBook and LogTen Pro have better two-way compatibility today.

· 5 min read