ProLogbooks
Default language
Flights

Import flights from file

The file import workflow brings flight rows from a CSV, TSV, or Excel file into the current logbook. Use it when the flights already exist in another system, in a spreadsheet, or in a file exported from this workspace.

How file import works

The import process keeps the source file separate from your saved flights until you review it. Work through these steps in order so the final import adds only clean, intentional records.

Upload your file

Choose the CSV, TSV, TXT, or XLSX file that contains the flight rows you want to bring into the current logbook.

Map the columns

Match each source column to the correct logbook field, and leave extra provider columns ignored when they are not needed.

Review the preview

Check staged rows, fix airport or registration warnings, and open a row for detailed editing when a value needs more attention.

Import the records

Import only the selected rows or the full preview after the data looks correct, then confirm the new flights in My Flights.

Start from the correct logbook and upload page

The import belongs to the currently selected logbook. Before you upload anything, confirm that the workspace is pointing to the logbook that should receive the flights.

You can open this workflow from the Import from file button on Add flight. The upload page accepts CSV, TSV, and XLSX files and shows the selected file before you continue.

Start from the correct logbook and upload page
  1. Confirm that the correct logbook is selected in the workspace.
  2. Open Import from file from Add flight.
  3. Choose the source file that contains your flight rows.
  4. Upload the file and wait for the detected columns and row count to appear.

Prepare the file format before upload

A CSV file is a plain-text spreadsheet file where each line is one row and each value is separated by a delimiter, usually a comma. CSV does not keep spreadsheet formatting, colors, formulas, or merged cells; it only carries the text values that should become import columns.

The importer accepts CSV, TSV, TXT, and XLSX files. If another logbook provider gives you an older XLS file, open it in a spreadsheet app and save it as XLSX or CSV before uploading. If the provider exports several formats, choose CSV or XLSX when available.

The first row should be a header row with clear column names. The rows below it should contain the flight records. Column names do not need to match this logbook exactly, because you will map them on the next page, but names such as Date, From, To, Aircraft, Registration, Total time, PIC, Co-pilot, Remarks, and Route are easier to review.

Prepare the file format before upload
  • Comma-separated CSV can look like "Date","From","To","Aircraft","Total time" followed by "2026-06-06","CYUL","CYYZ","C172","1.4". Quotes are useful when a value contains a comma, quotation mark, or extra spaces.
  • Semicolon-separated CSV can look like Date;From;To;Aircraft;Total time followed by 2026-06-06;CYUL;CYYZ;C172;1.4. This is common when a computer uses comma as a decimal separator.
  • TSV uses tab characters between values. XLSX is a normal Excel workbook; keep the import data on the first worksheet and avoid merged headers.
  • Do not mix delimiters in the same file. Use one style consistently: commas, semicolons, tabs, or pipe characters.

Know what a provider export may contain

Files exported from another logbook system often include more columns than this logbook needs. That is normal. You can ignore provider-specific columns during mapping as long as the flight data you want to keep is present and readable.

Typical useful columns include the flight date, departure and arrival airports, aircraft type, aircraft registration, departure and arrival times, total time, pilot role or PIC time, night time, IFR time, approaches, landings, route, and remarks. Attachments are usually not included in CSV exports and may need to be added later from the preview edit page or after import.

Know what a provider export may contain
  1. Export from the provider using CSV or XLSX if those choices are available.
  2. Open the file once and confirm the first row contains column names.
  3. Check that each flight is on its own row.
  4. Confirm airports, dates, and time values are readable before uploading.
  5. Keep a copy of the original provider export until the imported flights have been reviewed.

Review the detected columns and map each one

After upload, the page shows every detected source column and tries to preselect matching logbook fields. Review those choices carefully instead of assuming the automatic mapping is always correct.

Ignored columns are acceptable when the source file contains information you do not want to store. The key fields for preview are the flight date, departure airport, arrival airport, and total flight time.

Review the detected columns and map each one
  1. Read the source column names from left to right.
  2. Confirm that each important column is mapped to the correct logbook field.
  3. Leave unused columns on Ignored instead of forcing a weak match.
  4. Check the required fields before continuing to preview.
  • Use explicit labels such as Departure airport and Arrival airport as your guide when mapping.
  • If the file came from this workspace, many export headers should already map automatically.

Prepare the preview and resolve anything still blocked

Prepare preview moves the mapped rows into a staged review page. This is where you confirm the rows before they become normal saved flights.

If a registration or airport still needs attention, the preview shows warning badges and yellow cells. Resolve those items directly in the preview so the imported rows are clean before final import.

When one preview row needs a fuller correction, open its edit page. That page lets you adjust the flight fields in the normal form layout before you return to the staged preview.

Prepare the preview and resolve anything still blocked
  1. Select Prepare preview after the mapping looks correct.
  2. Read the count and warning badges at the top of the preview page.
  3. Click any yellow registration or airport cell and resolve it before importing.
  4. Open the preview row edit page when the row needs broader corrections than a single yellow cell.
  5. Use Replace file if you need to go back to the upload and mapping step with another source file.

Use the preview edit page to attach files before import

The preview edit page uses the same flight form as a normal flight entry, so you can review the staged values in a calmer layout before final import.

If your current plan includes file uploads, the Flight files card also appears there. Add the supporting files you want to carry into the final saved flight, then save the preview row and return to the staged list.

Use the preview edit page to attach files before import
  1. Open the preview row you want to review in detail.
  2. Correct any fields that still need work.
  3. Use the Flight files card near the end of the form if you need to attach files before import.
  4. Save the preview row and return to the preview list.
  5. Import only after the preview row and its attached files look correct.

Reference the available import fields

The column-mapping list can propose the destination fields below. The field key is the internal value used by the importer, and the label is what you see in the mapping dropdown.

Map the required fields first, then add the optional time, route, approach, landing, or specialty fields only when your source file contains reliable values for them.

Field key Mapping label Explanation
flight_date Flight date Stores the flight date for the imported row.
aircraft_type Aircraft type Stores the aircraft type or model used for the flight.
aircraft_registration Aircraft registration Stores the aircraft registration used for the flight.
pic_name Pilot-in-command name Stores the pilot-in-command name for the flight.
copilot_name Co-pilot / student / passenger Stores the co-pilot, student, or passenger name for the flight.
departure_airport Departure airport Stores the airport code or ident used for Departure airport.
departure_lat Departure latitude Stores the decimal latitude used for Departure latitude.
departure_long Departure longitude Stores the decimal longitude used for Departure longitude.
departure_time Departure time Stores the local clock time used for Departure time in HH:MM format.
departure_utc Departure UTC time Stores the UTC date and time used for Departure UTC time.
departure_timezone Departure timezone Stores the IANA timezone name used for Departure timezone.
arrival_airport Arrival airport Stores the airport code or ident used for Arrival airport.
arrival_lat Arrival latitude Stores the decimal latitude used for Arrival latitude.
arrival_long Arrival longitude Stores the decimal longitude used for Arrival longitude.
arrival_time Arrival time Stores the local clock time used for Arrival time in HH:MM format.
arrival_utc Arrival UTC time Stores the UTC date and time used for Arrival UTC time.
arrival_timezone Arrival timezone Stores the IANA timezone name used for Arrival timezone.
route_via Route / via Stores the intermediate route, via points, or routing notes for the flight.
block_time_minutes Total flight time Stores the duration credited to Total flight time.
day_minutes Day Stores the duration credited to Day.
pic_time_minutes PIC Stores the duration credited to PIC.
sic_time_minutes Co-Pilot Stores the duration credited to Co-Pilot.
night_minutes Night Stores the duration credited to Night.
ifr_minutes Ifr Stores the duration credited to Ifr.
ifr_actual_minutes IFR Actual Stores the duration credited to IFR Actual.
ifr_hood_minutes IFR Hood Stores the duration credited to IFR Hood.
ifr_simulated_minutes Sim. Instr. Stores the duration credited to Sim. Instr..
simulator_minutes FSTD Time Stores the duration credited to FSTD Time.
ground_trainer_minutes Ground Trainer Stores the duration credited to Ground Trainer.
single_pilot_se_minutes SP SE Stores the duration credited to SP SE.
single_pilot_me_minutes SP ME Stores the duration credited to SP ME.
multi_pilot_time_minutes MP Stores the duration credited to MP.
dual_received_minutes Dual Stores the duration credited to Dual.
instruction_given_minutes FI Stores the duration credited to FI.
flight_rules Rules Stores the flight rules value, such as VFR or IFR, for the row.
fstd_date Fstd Date Stores the simulator or FSTD session date when that session is imported separately from the flight date.
fstd_type FSTD Type Stores the simulator, FSTD, or training device type linked to the row.
single_engine_day_dual_minutes SE Day Dual Stores the duration credited to SE Day Dual.
single_engine_day_pic_minutes SE Day PIC Stores the duration credited to SE Day PIC.
single_engine_day_copilot_minutes SE Day Co-Pilot Stores the duration credited to SE Day Co-Pilot.
single_engine_night_dual_minutes SE Night Dual Stores the duration credited to SE Night Dual.
single_engine_night_pic_minutes SE Night PIC Stores the duration credited to SE Night PIC.
single_engine_night_copilot_minutes SE Night Co-Pilot Stores the duration credited to SE Night Co-Pilot.
multi_engine_day_dual_minutes ME Day Dual Stores the duration credited to ME Day Dual.
multi_engine_day_pic_minutes ME Day PIC Stores the duration credited to ME Day PIC.
multi_engine_day_copilot_minutes ME Day Co-Pilot Stores the duration credited to ME Day Co-Pilot.
multi_engine_night_dual_minutes ME Night Dual Stores the duration credited to ME Night Dual.
multi_engine_night_pic_minutes ME Night PIC Stores the duration credited to ME Night PIC.
multi_engine_night_copilot_minutes ME Night Co-Pilot Stores the duration credited to ME Night Co-Pilot.
cross_country_day_dual_minutes XC Day Dual Stores the duration credited to XC Day Dual.
cross_country_day_pic_minutes XC Day PIC Stores the duration credited to XC Day PIC.
cross_country_day_copilot_minutes XC Day Co-Pilot Stores the duration credited to XC Day Co-Pilot.
cross_country_night_dual_minutes XC Night Dual Stores the duration credited to XC Night Dual.
cross_country_night_pic_minutes XC Night PIC Stores the duration credited to XC Night PIC.
cross_country_night_copilot_minutes XC Night Co-Pilot Stores the duration credited to XC Night Co-Pilot.
faa_cross_country_minutes Cross Country Stores the duration credited to Cross Country.
instrument_approaches_count No. Instr. Appr. Stores the numeric count used for No. Instr. Appr..
approach_types Approach Type Stores the approach type names or abbreviations recorded for the flight.
takeoffs_day TO Day Stores the numeric count used for TO Day.
landings_day LDG Day Stores the numeric count used for LDG Day.
takeoffs_night TO Night Stores the numeric count used for TO Night.
landings_night LDG Night Stores the numeric count used for LDG Night.
floats_minutes Floats Stores the duration credited to Floats.
tailwheel_minutes Tailwheel Stores the duration credited to Tailwheel.
helicopter_minutes Helicopter Stores the duration credited to Helicopter.
turbine_minutes Turbine Stores the duration credited to Turbine.
glass_cockpit_minutes Glass Stores the duration credited to Glass.
remarks Exercises / Remarks Stores free-text remarks, notes, or comments for the flight.

Import only the rows you want to keep

When the preview looks correct, import either the selected rows or the full preview. Imported rows move into My Flights and stop being part of the staged preview.

This last step should be a confirmation step, not the first time you notice data problems. A careful preview usually saves more time than fixing saved flights later.

Import only the rows you want to keep
  1. Select the rows you want if you only plan to import part of the preview.
  2. Use Import selection for the checked rows, or Import to bring in the whole preview.
  3. Wait for the confirmation dialog and status message.
  4. Open My Flights afterwards to confirm that the imported flights are now part of the saved logbook.

If something goes wrong

  • If every column stays on Ignored, confirm that the file contains a real header row and not only raw data rows.
  • If Prepare preview stays blocked, review whether date, departure airport, arrival airport, and total flight time are all mapped.
  • If yellow airport or registration warnings remain in preview, resolve them before assuming the import is ready.
  • If you uploaded the wrong file, use Replace file and start the workflow again with the correct source.
Previous: Use Air Carrier Lookup
Next: Use My Flights