DaPilot

How to import flights from LogTen Pro

If you've been logging on LogTen Pro for years, the export comes out of LogTen for Mac and lands in DaPilot in about a minute. Aircraft, tails, every time field, landings, holds, and remarks all map over. The duplicate check uses the same rule as the MyFlightBook and ForeFlight paths, so if you've already imported some of these flights from another logbook the matching rows are skipped automatically.

Why this matters

LogTen Pro is the desktop logbook many Part 121 and 135 pilots have used for a decade or more. The catch with switching is that LogTen exports a tab-separated text file with column names from its internal data model (flight_flightDate, flight_totalTime, etc.) and not every other app reads that natively. DaPilot does. You don't have to convert anything in Excel first.

What you need

  1. LogTen Pro on either Mac, iPad, or iPhone (any one of them, whichever holds your master logbook).
  2. About five minutes for the export plus a minute for the import.
  3. DaPilot installed on your iPhone and signed in.

Export from LogTen Pro

1Open LogTen Pro on the device that has your full logbook

If you sync LogTen across Mac, iPad, and iPhone, give the device you're exporting from a few seconds to pull the latest entries before you start. Pick whichever one is most convenient. The export menu and the file format are the same on all three.

2Reports → Exporters → Flights

Open Reports → Exporters and pick the Flights tab. LogTen ships a few presets; the Export Flights preset is the one DaPilot reads. If you've renamed columns in a custom preset, switch back to the default for this export. You can switch back to your custom one afterward.

3Save or share the file

LogTen produces a tab-separated .txt file. On Mac, save it to iCloud Drive or anywhere your iPhone can reach. On iPad or iPhone, use the share sheet to send it to Files (iCloud Drive), AirDrop it to your other device, or email it to yourself. DaPilot reads the tab-separated file directly, so you do not need to open it in Excel or Numbers and re-save as CSV.

Import into DaPilot

4Open the import screen

In DaPilot, tap Settings → Import. Pick the LogTen .txt file from iCloud Drive (or wherever you saved it). DaPilot auto-detects the LogTen format from the column headers, so you don't need to tell it which app the file came from.

5Wait for the parse

DaPilot reads every row and shows a summary: number of flights imported, number of aircraft created, and any duplicates skipped. If a row has a malformed date, you'll see the row number and the reason. Most LogTen exports are clean.

6Confirm the aircraft fleet

DaPilot creates an aircraft entry for every unique tail in the file. LogTen exports a type code (e.g. B738, C172) but does not include the make/model split, complex/high-performance/TAA flags, or tailwheel status in the default preset. Open each new aircraft in DaPilot and confirm those flags before you start logging fresh flights, otherwise endorsement-currency math may be off.

What gets imported

  • Date, departure, destination, route
  • Tail number and type code (mapped to ICAO type and make/model)
  • Total time, PIC, SIC, dual received, dual given (mapped to CFI given)
  • Cross-country, night, IFR (actual + simulated when split)
  • Day landings and night landings
  • Full-stop landings (allocated to night first when both are present)
  • Approach count when your preset includes it
  • Holds
  • Block out, takeoff, landing, and block in times if you logged them
  • Remarks (with the LogTen flight number prepended when present)

What does not import

  • Per-approach detail (LogTen stores each approach as a separate child entity; the count comes through, the per-approach type does not in v1).
  • Aircraft equipment flags (complex, high-performance, TAA, tailwheel). LogTen's default export doesn't include them; confirm per-aircraft in DaPilot.
  • Custom field values renamed via a non-default preset. Use the default Export Flights preset.
  • Endorsement images and PDFs attached inside LogTen.

Duplicate detection

DaPilot dedupes by the combination of date + route + total time. This rule is the same for MyFlightBook, ForeFlight, and LogTen imports, which means you can safely import from more than one source: a flight you already brought in from MyFlightBook will be skipped when the LogTen export reaches it. Re-running the same LogTen file is also safe.

The dedupe is exact-match. If your route format differs between apps (one uses KSFO-KLAX, the other uses KSFO KLAX), the matcher will not collapse them. Pick one format and stick with it.

After the import

Spot-check three things:

  1. Total time on the dashboard matches the total LogTen showed yesterday. A small drift is usually one row with a decimal mismatch; search and fix.
  2. Recent currency cards match LogTen's recency view.
  3. One specific recent flight to confirm the time fields landed in the right slots (PIC vs SIC vs dual).

If anything is off, edit the flight directly in DaPilot. There is no penalty for editing imported flights.

Switching workflows

If you want to keep LogTen open as a safety net for a few weeks, that's fine. Just decide up front which app is the source of truth so you don't end up reconciling. The simplest cutover: do daily logging in DaPilot from a fixed date, and only return to LogTen if a historical row is missing.

· 5 min read