Importing your previous logbooks
You can import your previous logbooks into WADER and consolidate all your flight experience in one place.
Updated Policy – Effective May 2025 Imports are now available through a one-time payment for listed formats, or PRO support for other cases.
Alternatively, instead of importing all previous flights individually, you can simply enter your total past experience using the Previous Experience function inside the app.
Once you are set as a new Wader user, you might want to bring your flights that are logged in a different logbook or provided by your airline or flight school system.
We offer importing services for the formats listed below through a one-time payment. If your data comes from a different format not listed below, it may require additional processing under our PRO support service. In that case, contact us for more information!
How to Request an Import
1. Prepare your file: make sure your file is in one of the supported formats listed above.
If you’re using a custom format, you can either:
Transpose your data to our spreadsheet template, or
Request import via our PRO Support service.
2. Contact us: mail your file to help@waderaviation.com and include your Wader user code, so we can locate your account. We’ll review your file and let you know if it’s ready for import or if adjustments are needed — and how long the process is expected to take.
⏱️ Import times may vary depending on file complexity and support workload.
3. Payment
For supported formats, imports are available through a one-time payment.
For custom or unsupported formats, imports are handled through PRO Support, which includes personalized assistance.
⚠️ Important Imports are processed AS IS, based on the data you provide — please review your file carefully before sending it. If there are errors or missing information, you will need to correct them manually in the app after import. Since Wader does not support batch editing, this can be time-consuming — so it’s strongly recommended to make sure your file is clean and complete before submitting it.
Supported Formats
Electronic Logbooks
Airline systems
Standard Spreadsheet
If you have your hours logged in an unsupported format, you can transpose your records to our template in CSV below and send it to us.
Make sure to follow the following filling instructions, otherwise the import cannot be completed!
flightDate
(required)
Enter the date of flight.
All records must follow the same format.
aircraftIata
(preferred over ICAO)
If you fly an airliner, the IATA code is preferred over the ICAO code. Some aircraft variants share the same ICAO code but have different IATA codes. Click here to search for your aircraft code.
aircraftIcao
(required if no IATA)
If the aircraft doesn't have an IATA code, enter the ICAO code. Make sure you use the actual ICAO code and not the type rating. Click here to search for your aircraft code.
For generic aircraft types, you may use ASEL (single-engine), AMEL (multi-engine) or GLID (glider/sailplane).
flightNumber
(optional)
Enter the flight number.
aircraftTailnumber
(required)
Enter the complete aircraft registration including the hifen (-), as applicable.
Optional - For simulator sessions, enter the simulator registration code.
depAirport
(required)
Flights only - Enter the departure airport IATA or ICAO code.
arrAirport
(required)
Flights only - Enter the arrival airport IATA or ICAO code.
timeReference
(required)
Enter the reference of your times. Valid options: UTC, LOCAL or BASE.
baseAirport
(optional)
In case your times are in 'BASE' reference, inform what is the airport base (IATA or ICAO code).
startTime
(preferred over totalTime)
Enter the out of gate time of flight or simulator session start time, using the format: hh:mm.
Alternatively use the totalTime field. In that case, note that your startTime in the app will be set to 00:00.
takeoffTime
(optional)
Enter the takeoff (off ground) time of flight, using the format: hh:mm.
landingTime
(optional)
Enter the landing (on ground) time of flight, using the format: hh:mm.
parkingTime
(preferred over totalTime)
Enter the in the gate time of flight or simulator session end time, using the format: hh:mm.
Alternatively use the totalTime field. In that case, note that your parkingTime in the app will be calculated based on totalTime - startTime.
totalTime (required if no start and parking/end times)
Enter the total time of your flight or simulator session, using the format hh:mm, instead of start and parking/end times.
Note that, in such cases, startingTime is set to 00:00 and parkingTime is set to totalTime - startingTime.
stickTime
(optional)
For augmented crews, enter time you occupied a seat in the flight deck, using the format hh:mm. If left blank it will be considered 100% of total time.
nightTime
(optional)
Enter night time, using the format hh:mm. If left blank, it will be calculated automatically based on startup and parking times.
actualInstrumentTime
(optional)
Enter the flight time under actual Instrument Meteorological Conditions (IMC), using the format hh:mm. Alternatively, enter TRUE to consider 100% of total time, or enter FALSE (or leave blank) to consider it 00:00.
simulatedInstrumentTime
(optional)
Enter the flight time under simulated IMC (under the hood), using the format hh:mm. Alternatively, enter TRUE to consider 100% of total time, or enter FALSE (or leave blank) to consider it 00:00.
crossCountryTime
(optional)
Enter cross-country time using the format hh:mm. Alternatively, enter TRUE to consider 100% of total time, or enter FALSE (or leave blank) to consider it 00:00.
takeoffs (optional)
Enter total number of takeoffs.
Alternatively, use the dayTakeoffs and nightTakeoffs.
landings (optional)
Enter total number of landings.
Alternatively, use the dayLandings and nightLandings.
dayTakeoffs
(optional)
Enter the number of takeoffs during day time. If left blank, it is automatically calculated based on startup and parking times
nightTakeoffs
(optional)
Enter the number of takeoffs during night time. If left blank, it is automatically calculated based on startup and parking times.
dayLandings
(optional)
Enter the number of landings during day time. If left blank, it is automatically calculated based on startup and parking times.
nightLandings (optional)
Enter the number of landings during night time. If left blank, it is automatically calculated based on startup and parking times.
approachType
(optional)
Enter approach type. Valid options: ILS CAT II/III, ILS CAT I, RNP-AR, RNP, GLS, LPV, LOC, VOR, NDB or VISUAL
function (required)
Enter your onboard function. Valid options:
Flight: PIC, SIC, Examiner, Instructor, Dual, SPIC or PICUS
Simulator: Trainer or Trainee
ifrTime (optional)
Enter IFR time using the format hh:mm. Alternatively, enter TRUE to consider 100% of total time, or enter FALSE (or leave blank) to consider it 00:00.
multiPilot (required)
Enter TRUE for multi-pilot operations, or enter FALSE (or leave blank) for single-pilot.
pilotName1 (recommended)
PIC (flight) or Trainer (simulator) name. Use SELF if that's you.
Note: PIC name is a minimum required information for some logbooks, so if left blank, a dash ("-") may appear in EASA logbook, for instance.
pilotName2
pilotName3
pilotName4 (optional)
Use SELF if that's you.
remarks (optional)
Use it for notes that will be printed in your logbook Remarks and Endorsements column. You may use it to save your Training Type (for simulator sessions), for instance.
isSimulator (required)
Indicate if that record is a Simulator session. Valid options: TRUE or FALSE.
qualificationLevel (optional)
For simulator sessions only.
Use it to indicate the simulator qualification level.
Valid options: FFS, FTD, FNPT, AATD, BATD, BITD, PCATD.
Check here for definitions of each qualification level.
FAQ
Q: Can I still import my previous logbook? A: Yes! You can import it through a one-time payment if your file is from one of our supported formats. If your file is more customized, it can be imported through our PRO support service.
Q: What if I don’t want to import every flight individually? A: You can simply enter your total previous flight experience directly in the app using the Previous Experience function. It’s a quick and easy alternative.
Q: How do I start the import? A: Email your file to help@waderaviation.com and include your Wader user code so we can locate your account.
Q: Will Wader fix errors or missing data in my file during import? A: No. Imports are processed AS IS, based on the information you submit. Please review your file carefully before sending it.
Last updated
Was this helpful?