Importing Your Previous Logbooks

Transfer your complete flight history from other logbook apps or airline systems into Wader.

This a PRO feature. Subscribe here.

Wader PRO users can bring their complete flight history from another app or airline system in a few clicks.

This page lists which formats are currently supported and how to get your file ready.

How the import works

Check supported formats below — find your logbook app or airline system
Follow the instructions for your format to export the correct file
Subscribe to PRO to have access to the Import Logbook feature within the app or to be able to use the auto-upload by email.
Submit your file through your preferred method.
1. Via mobile app: go to More → Import Logbook, select the file source and upload the file.
2. Via web app: go to Import in the lateral menu, select the file source and upload the file.
3. Via email: forward the file to [airline]@wader.pro using your email associated with your Wader account.
  1. You may use IATA, ICAO or airline name, and the system will properly identify it). Example: ad@wader.pro, azu@wader.pro or azul@wader.pro.
  2. If you are unable to find yours, hit us via the in-app Support Hub and our team will help you.
Your file is processed automatically* and you are notified by email once it is completed.

*Some formats may still be handled manually by our team, while automation is not completely implemented, but are processed within 2 business days

Imports are processed as-is based on the data you provide. Please review your file carefully before submitting — errors or missing information will need to be corrected manually in the app after import.

Supported Formats

Electronic Logbooks

LogTen Pro

Before exporting, make sure your settings are correct: go to Account → Settings → Display Options, set Time Format to Hours:Minutes, and confirm that Use Zulu (UTC) Time is enabled.

Then go to the Reports tab of your LogTen application (available in both mobile and desktop), select Exporters, and generate the Export Flights (Tab) report. Make sure to select this report — not the Dynamic Export Flights.

mcc / crewLounge PILOTLOG

myCrewLounge portal: Go to your profile and select the option to export your database records from PILOTLOG as CSV and JSON files.

Old mccPILOTLOG desktop app: Go to the Query tab, define a date range (or leave it blank), and click Search. Select the option to Export Data and save the report as CSV (or Excel if CSV is not available).

RB Logbook

Go to the More tab in RB Logbook, select Import & Export Data, and look for Export to CSV. Define the period you want to import and generate all available report types: Flights, Aircraft, and People. We need all three files.

Others

If you have your hours in a digital logbook not listed above, you can transpose your records to our standard spreadsheet template or contact our PRO support team via the app, so we can evaluate including it.

Airline Systems

🌐 AIMS / eCrew

AIMS eCrew (Legacy)

Log in to AIMS eCrew in your browser
On the Pilot LogBook report page, select your dates and click Export as CSV
- If that button is not available, right-click the report and use Save Target As to save as an HTM file

AIMS-v2 eCrew

Log in to AIMS eCrew in your browser
Go to Reports → My Logbook, select your dates, and click Go
From the File Export menu, select CSV

🇧🇷 ANAC (SACI)

Log in to the ANAC system at sistemas.anac.gov.br/SACI
In the left menu, select CIV → Declaração de Experiência de Voo
At the bottom of the page, find the export option

This generates an .xlt file that can be opened with any spreadsheet application (Excel, Google Sheets, etc.).

Make sure to upload the original (unaltered) file.

🇷🇺 Aviabit

Export your logbook from Aviabit in CSV format.

Make sure the exported file includes Block ON and Block OFF times — these are essential for a proper import. If your file is missing this data or contains inconsistencies (such as Instrument Time exceeding total Duty Time), consider transferring your data to our standard spreadsheet template to fill in any gaps before submitting.

🇪🇸 Air Europa

Go to your Casillero Digital app and tap Logbook:

Set the date range and select export format "Recommended for Logten Pro X":

You will receive the file in your corporate email.

If you opt to use the auto-upload via email, note that forwarding from Apple Mail, the CSV file may be embedded in the email body instead of attached and the import will not work. Use Gmail or Outlook instead to forward it to ensure the attachment is preserved.

🇦🇪 Air Arabia

Air Arabia's system sometimes links the wrong aircraft type to a tail number. Our import process automatically corrects this using the aircraft registration. If you spot any remaining issues after import, let us know.

🇧🇷 Azul Linhas Aéreas

Request your logbook by opening a Service Now request with Azul. Once you receive it, submit the CSV (preferred) or the PDF file.

Azul Conecta uses a different format that is currently not supported. In that case, the standard spreadsheet is the best option.

🇦🇪 Emirates

Log in to the EK portal
Go to All Apps → Flight Time Report
Load the period you want to import
Click the Download Spreadsheet button (top-right corner of the table)

Submit the downloaded Excel file.

🇧🇷 GOL Linhas Aéreas

Get your monthly reports from CrewLink: go to the portal, select FT Record in the side menu, select the desired month, and click Generate Report. Download each monthly report and submit them all.

The consolidated file from the roster ("ESCALA") cannot be used — it does not include mandatory logbook information such as aircraft registration.

🇧🇷 LATAM Airlines Brasil

LATAM may provide you with a PDF logbook directly. Just make sure it is the original file, and not a regenerated printed PDF (which may not be readable).

LATAM Cargo uses a different format that is currently not supported. In that case, the standard spreadsheet is the best option.

🇲🇻 Trans Maldivian Airways

Go to the RAMIS system and export your flights in Excel format.

Make sure to upload the original (unaltered) file.

Others

If your airline system provides you with all required logbook information in a different format, submit a request via the in-app Support Hub and the team will evaluate whether it can be imported.

Standard Spreadsheet

If your format is not listed above, you can transpose your records into our template:

Follow the field specifications below exactly — incomplete or incorrectly formatted files cannot be imported.

Field

Status

Description

isSimulator

(optional)

Set to true if this entry is a simulator session rather than an actual flight. Defaults to false

flightDate

(required)

Date of the flight in YYYY-MM-DD format (e.g. 2023-06-15). DD/MM/YYYY is also accepted

timeReference

(required)

Timezone reference for all time fields. Use UTC for Zulu time, LOCAL for local time or BASE for time relative to the home base airport

baseAirport

(optional)

ICAO or IATA code of your home base airport. Required if timeReference is BASE

startTime

(recommended)

Block-off time (chocks removed / pushback) in HH:MM format. If blank, it will be defaulted to 00:00

takeoffTime

(optional)

Wheels-off time in HH:MM format

landingTime

(optional)

Wheels-on time in HH:MM format

parkingTime

(recommended)

Block-on time (chocks in / engines off) in HH:MM format. If blank, it will be determined based on startTime and totalTime

flightNumber

(optional)

Flight number (e.g. LA1234)

depAirport

(required)

ICAO or IATA code of the departure airport (e.g. SBGR or GRU). Leave blank for simulator sessions

arrAirport

(required)

ICAO or IATA code of the arrival airport (e.g. SBSP or CGH). Leave blank for simulator sessions

aircraftTailnumber

(required)

Aircraft registration / tail number (e.g. PT-MSY). Mandatory logbook entry

aircraftType

(required)

IATA or ICAO aircraft type code (e.g. B738 or 738). The legacy column names aircraftIcao and aircraftIata are still accepted

simType

(optional)

Simulator device type, if applicable (e.g. FFS, FTD, FNPT, AATD, BATD, BITD, PCATD). Only relevant when isSimulator is true. The legacy column name qualificationLevel is still accepted

function

(required)

Pilot function / role. Accepted values: PIC, SIC, PICUS, SPIC, Dual, Instructor, Examiner. If simulator: Trainee, Trainer

pilotName1

(recommended)

Set as SELF if you are the Pilot in Command. Otherwise, add the full name of the other crew member in the primary crew position. Mandatory for EASA logbook.

pilotName2

(optional)

SELF or the full name of the other crew member

pilotName3

(optional)

SELF or the full name of the other crew member

pilotName4

(optional)

SELF or the full name of the other crew member

totalTime

(required if start and parking times not provided)

Total flight time (block-to-block) in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90)

picTime

(optional)

Time as Pilot in Command in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90). See the note below on how these override function

sicTime

(optional)

Time as Second in Command in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90)

soloTime

(optional)

Solo time in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90)

dualTime

(optional)

Dual instruction received in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90)

picusTime

(optional)

Time as Pilot in Command Under Supervision in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90)

spicTime

(optional)

Time as Student Pilot in Command in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90)

examinerTime

(optional)

Time acting as Examiner in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90)

instructorTime

(optional)

Time acting as Instructor in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90)

simTraineeTime

(optional)

Simulator session time as trainee in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90). Only relevant when isSimulator is true

simTrainerTime

(optional)

Simulator session time as instructor or examiner in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90). Only relevant when isSimulator is true

crossCountryTime

(optional)

Cross-country time in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90). You can also enter true for the entire flight or false for none

actualInstrumentTime

(optional)

Actual IMC time in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90). You can also enter true for the entire flight or false for none

simulatedInstrumentTime

(optional)

Simulated instrument time (hood / foggles) in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90). You can also enter true for the entire flight or false for none

reliefTime

(optional)

Time not at the controls on an augmented crew in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90). The legacy stickTime column (time at the controls) is still accepted

ifrTime

(optional)

Total IFR time in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90). You can also enter true for the entire flight or false for none. Values longer than totalTime are capped to it

nightTime

(optional)

Night flying time in HH:MM (e.g. 1:30), decimal hours (1.5), or whole minutes (90). If blank, it will be automatically calculated based on OOOI times

takeoffs

(optional)

Total number of takeoffs (day + night)

landings

(optional)

Total number of landings (day + night)

dayTakeoffs

(optional)

Number of daytime takeoffs. If omitted, it will be calculated based on takeoffs and OOOI times

nightTakeoffs

(optional)

Number of night takeoffs. If omitted, it will be calculated based on takeoffs and OOOI times

dayLandings

(optional)

Number of daytime landings. If omitted, it will be calculated based on landings and OOOI times

nightLandings

(optional)

Number of night landings. If omitted, it will be calculated based on landings and OOOI times

approachType

(optional)

Type of instrument approach flown. Accepted values: ILS CAT II/III, ILS CAT I, RNP-AR, RNP, GLS, LPV, LOC, VOR, NDB, or VISUAL. Use one value per flight; if multiple approaches were flown, use the most significant

remarks

(optional)

Free-text remarks or notes for the flight entry

multiPilot

(optional)

true if the flight was operated by a multi-pilot crew, false if single-pilot. A multi-pilot time is also accepted: anything above zero is read as true, and zero as false. If blank, the flight is recorded as multi-pilot

depNotes

(optional)

Free-text notes about the departure

depProcedure

(optional)

Departure procedure (SID) flown

depTransition

(optional)

Departure transition flown

arrNotes

(optional)

Free-text notes about the arrival

arrProcedure

(optional)

Arrival procedure (STAR) flown

arrTransition

(optional)

Arrival transition flown

A logbook you exported from Wader can be imported straight back. The export uses these same column names, so you can export, edit in a spreadsheet, and re-import. Three things are not restored, because Wader stores them as links to other records and the export writes their display text: the multi-engine flag, departure and arrival runways, and threats. Previous-experience rows in an export are also skipped — previous experience is recorded separately in your profile.

Pilot function times. If you leave picTime, sicTime, dualTime, picusTime, spicTime, instructorTime and examinerTime blank, the whole block time is credited to whatever you put in function. If you fill any of them in, those values are used instead — useful for an augmented crew, or when a flight is split between two roles.

Duration format. Any duration column accepts HH:MM (1:30), decimal hours (1.5), or whole minutes (90). A value written with : is never ambiguous. For bare numbers, Wader decides once per file: files exported from Wader are read as minutes, everything else as decimal hours.

In the columns that accept true / false — ifrTime, actualInstrumentTime, simulatedInstrumentTime, crossCountryTime and multiPilot — a bare 1 is read as true and a bare 0 as false, never as a duration. To log one hour, write 1:00.

Last updated 20 days ago