Bring your logbook across

Off Chocks has a dedicated LogTen Pro Import that recognises LogTen's own column names, so in most cases you upload one file and skip straight to confirming your flights.

Check your export first: the free checker reads it with the Off Chocks import code in your browser and shows its flights, hours and currency.

1. Open LogTen on your iPhone, iPad, or Mac and make sure you are in the logbook you want to move.
2. Turn on Zulu (UTC) time in LogTen before you export, so your out, off, on and in times are unambiguous. Off Chocks reads a bare clock time as Zulu by default.
3. In LogTen, open the Reports tab, then Exporters, and choose Export Flights (Tab). It writes every flight with every field LogTen holds, including crew names and tail numbers, to a tab-delimited .txt file. On iPhone or iPad, tap Configure Report, clear any filter, set the full date range and tap Generate. On a Mac, select All Entries in the Logbook tab before you run it.
4. LogTen produces a wide tab-delimited file, often well over a hundred columns, which is normal.
5. Share or save the file with the iOS or Mac share sheet (email it to yourself, or save to Files, iCloud Drive, or Dropbox) so you can open it on the device running Off Chocks.
6. In Off Chocks, go to the Logbook tab, tap Import, and choose the LogTen Pro Import tile, not the CSV / Spreadsheet Import tile. It accepts .csv, .tsv, and .txt.
7. Upload the file. Off Chocks auto-detects LogTen's columns, so once a valid date and a total time are found, the Map Columns step is skipped and you go straight to Confirm.
8. At Confirm, review your flights in a table. Untick any you do not want, override the date format, switch a time column between UTC and local airport time, and check warnings such as unrecognised airport codes. Then run the import. Aircraft and crew named in your flights are created automatically.

Heads up: Exporting from LogTen does not need an active subscription, so you can always get your logbook out. Re-importing the same file later is safe, because Off Chocks detects and skips duplicates. If your LogTen times were in local time rather than Zulu, switch the relevant column from UTC to local airport time at Confirm. The date format default follows your authority (FAA is MM/DD, EASA and CASA are DD/MM), and you can override it at Confirm.

If you keep your logbook in ForeFlight, you can bring it into Off Chocks with one CSV file. The ForeFlight Import reads a standard ForeFlight logbook CSV export and detects its columns automatically, so there is nothing to map by hand.

Check your export first: the free checker reads it with the Off Chocks import code in your browser and shows its flights, hours and currency.

1. Export from ForeFlight Web (plan.foreflight.com) rather than the app. Sign in with your ForeFlight account; the flights you log on your iPad or iPhone sync there automatically.
2. Open Logbook, select the Export tab at the top, then click the blue Export button to download your logbook as a CSV file. (Alternatively, from Logbook, then Settings, turn on Export to Email to have the CSV emailed to your account address.)
3. Get that CSV onto the device running Off Chocks, for example by emailing it to yourself or saving it to Files, iCloud Drive, or Dropbox.
4. In Off Chocks, open the Logbook tab and tap Import.
5. Choose the ForeFlight Import tile.
6. Upload the CSV. The wizard has four steps: Upload, Map Columns, Confirm, and Import. Because a standard ForeFlight export includes the required fields (flight date and total time), the Map Columns step is skipped and you go straight to Confirm.
7. Review the parsed flights at Confirm, untick any you do not want, then run the Import.

Heads up: The ForeFlight Import takes a .csv file, not .tsv or .txt. ForeFlight durations are decimal hours (1.5 means one hour thirty), which is exactly what the import expects, so there is no time conversion to do. Clock times are read as UTC by default, with a switch to local airport time at Confirm. Re-importing the same file is safe, because duplicate rows are detected and skipped.

If your current logbook can produce a CSV file, you can bring it into Off Chocks. Off Chocks fills in a match for each column header it recognises; you check those, match the rest to Off Chocks fields yourself, then confirm and import.

1. Export a CSV from your current app:
   • MyFlightbook: sign in at myflightbook.com, open the Logbook tab, then Download, and choose the CSV download. Times come out as decimal hours, and you can leave the FlightID column in.
   • Garmin Pilot: there is no on-device export, so do this on the web. Sign in at fly.garmin.com, open Logbook, then Setup, then Export to Spreadsheet, and save the CSV.
   • Safelog: sign in at safelogweb.com, open Other Tools, then Data Import and Export, and create an export of your logbook. Set a text qualifier (for example a double quote) first so commas inside remarks do not break the file.
   • ZuluLog: sign in at zululog.com, use the account or backup tools to request a CSV backup, and download it. Review your field settings first so the columns you need are included.
   • Logbook Pro Desktop: open Logbook Pro on your computer, go to File, then Export, and choose Comma Separated Values (.CSV). Export works only in the registered version, then transfer the file to your device.
   • EASA-region apps: CrewLounge and mccPILOTLOG can export a CSV from their logbook tools; use that file with the steps below.
   • Any other app: save or export your data as CSV. If your app only exports its own backup format, open that file in a spreadsheet first and save it as CSV, with a single header row naming each column.
2. In Off Chocks, open the Logbook tab, then Import.
3. Tap CSV / Spreadsheet Import and upload your file (.csv, .tsv, or .txt, up to 25 MB and 50,000 rows). You need a connection, since imports run online.
4. In the Map Columns step, check the matches Off Chocks filled in and match each remaining column to the right Off Chocks field. Every row needs a flight date and a total or block time (a total can be derived from a seat-time column like PIC or SIC if the total column is blank). You can save your mapping as a reusable preset.
5. In the Confirm step, review the parsed flights, tick the ones to import, fix the date order or time zone if needed, then import. Aircraft and crew named in your flights are created automatically.

Heads up: Most apps export times as decimal hours (1.5 means one hour thirty); Off Chocks also reads H:MM (1:30) and H+MM (1+30), so glance at the Confirm totals to be sure nothing looks doubled. Date order varies too: US and FAA-style files lean MM/DD while EASA and CASA files lean DD/MM. Off Chocks auto-detects the order and lets you override it at Confirm, and ISO YYYY-MM-DD is never ambiguous. Re-importing the same file is safe. If an import goes wrong, tap Undo this import on the finish screen, or on the Import page within 30 days, and those flights move to Recently Deleted. If you only have career totals and not per-flight rows, use Balance Forward instead.

If you keep your logbook in Excel, Google Sheets, or Apple Numbers, save it as a CSV file, check the column matches Off Chocks suggests, and match the rest by hand. A little tidying first makes the import clean.

Starting a spreadsheet? Download the free one with FAA, EASA and CASA columns, totals filled in, that imports in one step.

1. Lay the sheet out as one flat table: a single header row at the top, one flight per row, with no blank spacer rows, no merged cells, and no totals row at the bottom.
2. Write dates as YYYY-MM-DD (for example 2026-03-14), and write durations as decimal hours (1.5 means one hour thirty) or as H:MM (1:30). A bare whole number is read as hours, so 2 means two hours and 0.5 means thirty minutes.
3. Format tail numbers and any all-numeric registrations as Text before you type them, so leading zeros are kept. In Excel, set the column format to Text, or type an apostrophe before the value.
4. Export to CSV:
   • Excel (Windows or Mac): File, then Save As, then choose CSV UTF-8 (Comma delimited) (*.csv), then Save. Pick the UTF-8 variant so accented names survive.
   • Google Sheets: File, then Download, then Comma-separated values (.csv). This exports the current tab only, so repeat for each tab.
   • Numbers (Mac): File, then Export To, then CSV. Open Advanced Options to confirm UTF-8 encoding and to combine multiple tables into one file.
   • Numbers (iPhone or iPad): tap the three-dot More menu, then Export, then CSV.
5. In Off Chocks, go to the Logbook tab, then Import, then the CSV / Spreadsheet Import tile. Upload your CSV.
6. In the Map Columns step, check the suggested matches and match each remaining column to an Off Chocks field. Flight Date and Total / Block Time are required; map From, To, PIC, SIC, Night, landings, Aircraft Type, Aircraft Rego, Remarks, and the rest as you have them. Save the mapping as a preset so future imports skip this step.
7. On the Confirm step, review every parsed flight, tick or untick which to import, override the date order (DD/MM versus MM/DD) if detection guessed wrong, and switch bare clock times from Zulu to local airport time if needed. Then run the import.

Heads up: This tile suggests a match only where a column header is a name it knows, ignoring case, spaces and punctuation, so a tidy single-table CSV with plain headers is worth the effort. Excel and Numbers will sometimes turn a duration like 1:40 into a date such as 1-Apr, so write durations as plain decimal hours, and set any column that looks wrong to Text before exporting. Off Chocks skips rows that duplicate flights already in your logbook, so re-importing a corrected file is safe.

Moving a handwritten logbook into Off Chocks usually means one of two things: bringing across your carried-forward totals once, or entering each flight so your dates, routes, and landing currency are exact. Many pilots do both. Use one of the two paths below.

Starting a spreadsheet? Download the free one with FAA, EASA and CASA columns, totals filled in, that imports in one step.

Heads up: When transcribing into a spreadsheet, keep every duration as decimal hours and the registration column formatted as text, because spreadsheets often mangle 1:30 into a time of day and drop leading zeros. Writing dates as ISO YYYY-MM-DD avoids any confusion over date order (the fallback follows your authority: FAA reads MM/DD, EASA and CASA read DD/MM, and you can override it at Confirm).

If you already have a logbook full of history, you do not have to re-type every flight. Balance Forward lets you enter your career totals as opening figures, so your hours land in Off Chocks straight away and you start logging new flights from there.

1. Gather your existing totals first. From your paper logbook or current app, write down your career totals broken down by aircraft type: total time, night, PIC (and PIC night), SIC (and SIC night), Dual (and dual night), Instructor, ICUS, Instrument Actual, Instrument Simulated, Cross-Country, Day Landings, and Night Landings. Note the date your logbook is current to.
2. In Off Chocks, open the Logbook tab and tap Import.
3. Choose the Balance Forward tile. No file is needed; this is manual entry on the device.
4. For each aircraft type you have flown, add an Aircraft Type card and enter its ICAO type code and engine type (single or multi).
5. Fill in that type's career totals from the figures you gathered, entered as plain hour figures.
6. Set the as-of date for the card so the opening totals are dated to the point your logbook was current. New flights you log later add on top of this.
7. If you have simulator hours, use the separate Simulator Time section to add sim cards (device type, type simulated, sim time, instrument time, and an as-of date).
8. Check the running grand total on screen against your logbook totals, clear any improbable-total warning, then save.
9. From here, log new flights individually so your totals and recency build correctly going forward.

Heads up: A Balance Forward is a summary, not a set of dated flights, so it builds your hour totals but does not restore landing, takeoff, or approach recency. Under FAA, EASA, and CASA rules, currency is computed from dated individual flights, so log any recent flights you need for currency individually. Also enter each period once: if you also import the same dates as individual flights, you will double-count your hours, so pick one method per date range.