Do you have your flight data in a digital format that does not match any of our predefined import options? You can still upload your entire flight history using one of the following methods:
Use Our Custom CSV Template (Recommended)
Copy your flight records into our CSV template and upload the completed file. This is the easiest and most reliable way to import your data, as the template already contains all required columns in the correct format.
Use Your Own CSV File
You can also upload your existing CSV file, provided it contains all required flight data fields.
If your file uses different column names or a different structure than our template, a column mapping screen will appear during the import process. This allows you to match each column from your file to the corresponding field in FLYLOG.io.
⚠️ Please note that all required columns listed below must be present in your file. Missing required data may prevent the import from being completed successfully.
If you are importing flight records exported from systems such as AIMS eCrew or other crew or airline scheduling systems, please check the Airline Pilots guide. To import your previous experience from another digital logbook, please refer to the Migrate from eLogbook.
Custom Template
➡️ HERE DOWNLOAD TEMPLATE FILE ⬅️
Download the template file.
Fill in your flight records using the required columns listed below.
Save or export the file as CSV format.
Upload the file in Import → Bulk Data Import.
The template can be opened and edited using Microsoft Excel, Apple Numbers, Google Sheets, or other spreadsheet applications.
💡 Pro Tip: Use standard ICAO type designators as your aircraft type codes for best results.
Using Your Own File
If your file already follows the same structure and column names as our template, the import will proceed automatically.
If the structure or column names differ, the system will display a column mapping table. During this step, you can assign each column from your file to the appropriate FLYLOG.io field.
To ensure a successful import:
Your file must be in CSV format.
All required columns listed below must be present.
Each required column must be mapped to the correct FLYLOG.io field.
Date and time values should be provided in a consistent format.
💡 Tip: Using our template eliminates the need for column mapping and significantly reduces the risk of import errors.
Required Columns
In the table below, you can find columns that MUST* be present in CSV file. If you are using your own file, RENAME your columns to exactly match the columns in our template.
Column name | Description |
|---|---|
*DATE | Date of flight (yyyy-MM-dd or dd/MM/yyyy) |
*DEPARTURE_AIRPORT | Departure place |
*ARRIVAL_AIRPORT | Arrival place |
*AIRCRAFT_TYPE | ICAO type designator of aircraft |
*AIRCRAFT_REGISTRATION | Aircraft registration/tail |
*DURATION_BLOCK | Total block time (HH:mm or HH:mm:ss or decimal) |
*LDGS_DAY | Day landings |
LDGS_NIGHT | Night landings |
TIME_BLOCK_START | Block start time (HH:mm or HH:mm:ss) |
TIME_BLOCK_END | Block end time (HH:mm or HH:mm:ss) |
DURATION_PIC | Pilot In Command time (HH:mm or HH:mm:ss or decimal) |
DURATION_PICUS | Pilot under Supervision time (HH:mm or HH:mm:ss or decimal) |
DURATION_SIC | Second in Command/Co-pilot/FO time (HH:mm or HH:mm:ss or decimal) |
DURATION_DUAL | DUAL received time (HH:mm or HH:mm:ss or decimal) |
DURATION_INSTRUCTOR | DUAL given (HH:mm or HH:mm:ss or decimal) |
DURATION_NIGHT | Night time (HH:mm or HH:mm:ss or decimal) |
DURATION_IFR | IFR time (HH:mm or HH:mm:ss or decimal) |
DURATION_IFR_ACTUAL | IMC time (HH:mm or HH:mm:ss or decimal) |
DURATION_IFR_SIMULATED | HOOD time (HH:mm or HH:mm:ss or decimal) |
DURATION_XC | Cross Country time (HH:mm/HH:mm:ss or decimal) |
DURATION_MULTI_PILOT | Multi-pilot time (HH:mm or HH:mm:ss or decimal) |
DURATION_SIMULATOR | Simulator time (HH:mm or HH:mm:ss or decimal) |
SIMULATOR_TYPE | Type of simulator |
REMARKS | Remarks and endorsements (visible in official export) |
PERSONAL_NOTE | Private remark (not visible in official export) |
APPROACH_TYPE | Approach type (VISUAL, VOR, ILS, ILS_CAT3, …) |
APPROACH_NR | Nr of approaches |
TAGS | Multiple tags can be separated by space |
NAME_PIC | Name of PIC (Instructor) - use “SELF” for yourself as Pilot In Command |
NAME_COPILOT | Name of Copilot - for multi-pilot and multi-crew-coordination flights (MCC) |
NAME_PICUS | Name of Pilot in Command under Supervision |
NAME_STUDENT | Name of your Student - if you performed the flight as instructor |
TAKEOFFS_DAY | Day takeoffs |
TAKEOFFS_NIGHT | Night takeoffs |
TIME_TAKEOFF | Takeoff time - actual departure time (HH:mm or HH:mm:ss) |
TIME_LANDING | Landing time - actual arrival time (HH:mm or HH:mm:ss) |
FLIGHT_NUMBER | Scheduled flight number (#FR1234) |
ROUTE | Route of flight. For multi-leg flights. |
Troubleshooting
If your import fails:
Ensure your file is saved in CSV format.
Verify that all required columns are present in the file.
Check that date and time values use a valid and consistent format.
Review the column mapping screen and make sure all required fields are mapped correctly.
Confirm that the data in each column matches the expected field type (for example, dates in date fields and flight times in time fields).
If the problem persists, send us your file to support@flylog.io - our team will assist you.
