Importing Your Previous Logbooks

Bring your complete flight history into Wader from another logbook app or from your airline’s crew system.

Tip

Importing from another logbook app is FREE. Moving your logbook from another digital logbook app (such as LogTen, ForeFlight, CrewLounge or OffBlock) costs nothing, on any plan.

Importing from an airline crew system or from the Wader spreadsheet template is part of Wader PRO. These sources show a PRO tag in the source list.

How the import works

1. Open Import.
   • In the app: open the Logbook tab, tap the ☰ menu at the top right and choose Import hours. The Import logbook screen opens.
   • On the web: open the web app and select Import in the side menu.
2. Choose your source. Search for your logbook app or your airline.
3. Follow the export steps shown for that source. The steps live in the app, so they are always up to date for every source we support.
4. Upload your file and tap Submit import request. Files can be up to 20 MB. Your file is processed automatically, and you are notified by email when it is done.

On the web, before anything is saved you see Check your import: a summary of your flights, simulator sessions and totals, how your aircraft matched, and any airports to check. Answer anything Wader could not match, then tap Import N records. Nothing is saved until you do, and Cancel import saves nothing. If you chose the wrong source for your file, Wader offers to switch. Your import history shows Not finished or Cancelled for imports you did not complete.

Note

If the web shows Bringing your whole logbook to Wader?, use Import to bring your flights in rather than adding them one by one.

Note

Airline not supported yet? Search for it in the source list anyway. If we cannot import it yet, you can request it from there, and our team will check what your crew system can export.

Sending your file by email

You can also forward your file to [airline]@wader.pro from the email address on your Wader account:

• You can use the airline’s IATA code, ICAO code or name, and the system identifies it. For example: ad@wader.pro, azu@wader.pro or azul@wader.pro.
• If your airline uses AIMS / eCrew, you can also send it to aims@wader.pro.
• To send from your work email, add it as a secondary email in your profile.

Good to know

• Importing again updates. A flight that is already in your logbook is updated, not duplicated. See Fixing or Updating an Import.

---

Standard Spreadsheet

If your logbook app or airline is not in the source list, you can copy your records into our template and import that file.

Note

Importing the Wader spreadsheet template is part of Wader PRO.

Download spreadsheet template

Follow the field specifications below exactly — incomplete or incorrectly formatted files may be imported with errors.

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. Use one date format for the whole file
timeReference	(recommended)	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. One value for the whole file: it is read from the first flight row. If blank, UTC is used
baseAirport	(optional)	ICAO or IATA code of your home base airport. Required if timeReference is BASE. Like timeReference, it is read from the first flight row
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
etd	(optional)	Estimated or scheduled departure time (off-block) in HH:MM format. Columns named ETD, EOBT or STD are also accepted. It follows timeReference. A row with etd and no block times is saved as a planned flight (see the note below)
eta	(optional)	Estimated or scheduled arrival time (on-block) in HH:MM format. Columns named ETA or STA are also accepted. It follows timeReference
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. Instructor and Examiner also count the time as PIC. If simulator: Trainee, Trainer
pilotName1	(recommended)	Name of the Pilot in Command. Use SELF if that was you. If blank, it is recorded as SELF, so when you were not the PIC, enter the PIC's full name. 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
totalCrew	(optional)	Number of pilots in the crew. If blank: 1 when the flight has soloTime, 4 when it has reliefTime, otherwise 2
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 is calculated automatically from startTime and parkingTime. It is not calculated when only totalTime is given
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

Note

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: the multi-engine flag, departure and arrival runways, and threats. Previous-experience rows in an export are imported too: they go back to the previous experience in your profile, and rows you already have are not added twice.

Note

Planned flights. A flight row with etd (and eta if you have it) but no startTime, parkingTime or totalTime is saved as a planned flight, like a roster duty you have not flown yet. Later, import the same flight again with its real times: Wader completes the planned flight and does not add a second one. Simulator rows always need times.

Simulator sessions. Every simulator session you import is saved with the role Trainer or Trainee, never PIC or Co-pilot. Your totals do not change. This applies to new imports only: to change an older session, open it and edit it by hand.

Note

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.

Note

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.

Caution

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.