> For the complete documentation index, see [llms.txt](https://support.waderaviation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.waderaviation.com/importing-your-data/from-another-logbook.md).

# Importing Your Previous Logbooks

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

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

{% hint style="success" icon="gift" %}
**Importing from another logbook app is free.** Moving your logbook from another digital logbook app 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.
{% endhint %}

## How the import works

1. **Open Import.**
   * **In the app:** go to **More → Import Logbook**.
   * **On the web:** open the [web app](https://logbook.waderaviation.com/import) 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.** It is processed **automatically**, and you are notified by email when it is done.

{% hint style="info" %}
**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.
{% endhint %}

### 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](https://logbook.waderaviation.com/profile).

### Good to know

* **Re-importing is safe.** A flight that is already in your logbook is updated, not duplicated. See [Updating Your Records via Import](/importing-your-data/updating-your-records-via-import.md).

***

## 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.

{% hint style="info" %}
Importing the Wader spreadsheet template is part of **Wader PRO**.
{% endhint %}

{% file src="/files/s3vvvwJn1vL5psFiI8jW" %}
Download spreadsheet template
{% endfile %}

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

<table><thead><tr><th width="227.328125">Field</th><th width="181.11328125">Status</th><th>Description</th></tr></thead><tbody><tr><td><code>isSimulator</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Set to <code>true</code> if this entry is a simulator session rather than an actual flight. Defaults to <code>false</code></td></tr><tr><td><code>flightDate</code></td><td><mark style="color:red;">(required)</mark></td><td>Date of the flight in <code>YYYY-MM-DD</code> format (e.g. <code>2023-06-15</code>). <code>DD/MM/YYYY</code> is also accepted. Use one date format for the whole file</td></tr><tr><td><code>timeReference</code></td><td><mark style="color:orange;">(recommended)</mark></td><td>Timezone reference for all time fields. Use <code>UTC</code> for Zulu time, <code>LOCAL</code> for local time or <code>BASE</code> for time relative to the home base airport. <strong>One value for the whole file:</strong> it is read from the first flight row. If blank, <code>UTC</code> is used</td></tr><tr><td><code>baseAirport</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>ICAO or IATA code of your home base airport. Required if <code>timeReference</code> is <code>BASE</code>. Like <code>timeReference</code>, it is read from the first flight row</td></tr><tr><td><code>startTime</code></td><td><mark style="color:orange;">(recommended)</mark></td><td>Block-off time (chocks removed / pushback) in <code>HH:MM</code> format. If <strong>blank</strong>, it will be defaulted to <code>00:00</code></td></tr><tr><td><code>takeoffTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Wheels-off time in <code>HH:MM</code> format</td></tr><tr><td><code>landingTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Wheels-on time in <code>HH:MM</code> format</td></tr><tr><td><code>parkingTime</code></td><td><mark style="color:orange;">(recommended)</mark></td><td>Block-on time (chocks in / engines off) in <code>HH:MM</code> format. If <strong>blank</strong>, it will be determined based on <code>startTime</code> and <code>totalTime</code></td></tr><tr><td><code>flightNumber</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Flight number (e.g. <code>LA1234</code>)</td></tr><tr><td><code>depAirport</code></td><td><mark style="color:red;">(required)</mark></td><td>ICAO or IATA code of the departure airport (e.g. <code>SBGR</code> or <code>GRU</code>). Leave blank for simulator sessions</td></tr><tr><td><code>arrAirport</code></td><td><mark style="color:red;">(required)</mark></td><td>ICAO or IATA code of the arrival airport (e.g. <code>SBSP</code> or <code>CGH</code>). Leave blank for simulator sessions</td></tr><tr><td><code>aircraftTailnumber</code></td><td><mark style="color:red;">(required)</mark></td><td>Aircraft registration / tail number (e.g. <code>PT-MSY</code>). Mandatory logbook entry</td></tr><tr><td><code>aircraftType</code></td><td><mark style="color:red;">(required)</mark></td><td>IATA or ICAO aircraft type code (e.g. <code>B738</code> or <code>738</code>). The legacy column names <code>aircraftIcao</code> and <code>aircraftIata</code> are still accepted</td></tr><tr><td><code>simType</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Simulator device type, if applicable (e.g. <code>FFS</code>, <code>FTD</code>, <code>FNPT</code>, <code>AATD</code>, <code>BATD</code>, <code>BITD</code>, <code>PCATD</code>). Only relevant when <code>isSimulator</code> is <code>true</code>. The legacy column name <code>qualificationLevel</code> is still accepted</td></tr><tr><td><code>function</code></td><td><mark style="color:red;">(required)</mark></td><td>Pilot function / role. Accepted values: <code>PIC</code>, <code>SIC</code>, <code>PICUS</code>, <code>SPIC</code>, <code>Dual</code>, <code>Instructor</code>, <code>Examiner</code>. <code>Instructor</code> and <code>Examiner</code> also count the time as PIC. If simulator: <code>Trainee</code>, <code>Trainer</code></td></tr><tr><td><code>pilotName1</code></td><td><mark style="color:orange;">(recommended)</mark></td><td>Name of the Pilot in Command. Use <code>SELF</code> if that was you. <strong>If blank, it is recorded as <code>SELF</code></strong>, so when you were not the PIC, enter the PIC's full name. <strong>Mandatory for EASA logbook.</strong></td></tr><tr><td><code>pilotName2</code></td><td><mark style="color:yellow;">(optional)</mark></td><td><code>SELF</code> or the full name of the other crew member</td></tr><tr><td><code>pilotName3</code></td><td><mark style="color:yellow;">(optional)</mark></td><td><code>SELF</code> or the full name of the other crew member</td></tr><tr><td><code>pilotName4</code></td><td><mark style="color:yellow;">(optional)</mark></td><td><code>SELF</code> or the full name of the other crew member</td></tr><tr><td><code>totalCrew</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Number of pilots in the crew. If blank: <code>1</code> when the flight has <code>soloTime</code>, <code>4</code> when it has <code>reliefTime</code>, otherwise <code>2</code></td></tr><tr><td><code>totalTime</code></td><td><mark style="color:red;">(required if start and parking times not provided)</mark></td><td>Total flight time (block-to-block) in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>)</td></tr><tr><td><code>picTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Time as Pilot in Command in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>). See the note below on how these override <code>function</code></td></tr><tr><td><code>sicTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Time as Second in Command in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>)</td></tr><tr><td><code>soloTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Solo time in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>)</td></tr><tr><td><code>dualTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Dual instruction received in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>)</td></tr><tr><td><code>picusTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Time as Pilot in Command Under Supervision in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>)</td></tr><tr><td><code>spicTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Time as Student Pilot in Command in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>)</td></tr><tr><td><code>examinerTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Time acting as Examiner in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>)</td></tr><tr><td><code>instructorTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Time acting as Instructor in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>)</td></tr><tr><td><code>simTraineeTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Simulator session time as trainee in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>). Only relevant when <code>isSimulator</code> is <code>true</code></td></tr><tr><td><code>simTrainerTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Simulator session time as instructor or examiner in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>). Only relevant when <code>isSimulator</code> is <code>true</code></td></tr><tr><td><code>crossCountryTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Cross-country time in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>). You can also enter <code>true</code> for the entire flight or <code>false</code> for none</td></tr><tr><td><code>actualInstrumentTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Actual IMC time in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>). You can also enter <code>true</code> for the entire flight or <code>false</code> for none</td></tr><tr><td><code>simulatedInstrumentTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Simulated instrument time (hood / foggles) in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>). You can also enter <code>true</code> for the entire flight or <code>false</code> for none</td></tr><tr><td><code>reliefTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Time not at the controls on an augmented crew in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>). The legacy <code>stickTime</code> column (time <strong>at</strong> the controls) is still accepted</td></tr><tr><td><code>ifrTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Total IFR time in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>). You can also enter <code>true</code> for the entire flight or <code>false</code> for none. Values longer than <code>totalTime</code> are capped to it</td></tr><tr><td><code>nightTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Night flying time in <code>HH:MM</code> (e.g. <code>1:30</code>), decimal hours (<code>1.5</code>), or whole minutes (<code>90</code>). If <strong>blank</strong>, it is calculated automatically from <code>startTime</code> and <code>parkingTime</code>. It is not calculated when only <code>totalTime</code> is given</td></tr><tr><td><code>takeoffs</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Total number of takeoffs (day + night)</td></tr><tr><td><code>landings</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Total number of landings (day + night)</td></tr><tr><td><code>dayTakeoffs</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Number of daytime takeoffs. If omitted, it will be calculated based on takeoffs and OOOI times</td></tr><tr><td><code>nightTakeoffs</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Number of night takeoffs. If omitted, it will be calculated based on takeoffs and OOOI times</td></tr><tr><td><code>dayLandings</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Number of daytime landings. If omitted, it will be calculated based on landings and OOOI times</td></tr><tr><td><code>nightLandings</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Number of night landings. If omitted, it will be calculated based on landings and OOOI times</td></tr><tr><td><code>approachType</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Type of instrument approach flown. Accepted values: <code>ILS CAT II/III</code>, <code>ILS CAT I</code>, <code>RNP-AR</code>, <code>RNP</code>, <code>GLS</code>, <code>LPV</code>, <code>LOC</code>, <code>VOR</code>, <code>NDB</code>, or <code>VISUAL</code>. Use one value per flight; if multiple approaches were flown, use the most significant</td></tr><tr><td><code>remarks</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Free-text remarks or notes for the flight entry</td></tr><tr><td><code>multiPilot</code></td><td><mark style="color:yellow;">(optional)</mark></td><td><code>true</code> if the flight was operated by a multi-pilot crew, <code>false</code> if single-pilot. A multi-pilot time is also accepted: anything above zero is read as <code>true</code>, and zero as <code>false</code>. If <strong>blank</strong>, the flight is recorded as multi-pilot</td></tr><tr><td><code>depNotes</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Free-text notes about the departure</td></tr><tr><td><code>depProcedure</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Departure procedure (SID) flown</td></tr><tr><td><code>depTransition</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Departure transition flown</td></tr><tr><td><code>arrNotes</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Free-text notes about the arrival</td></tr><tr><td><code>arrProcedure</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Arrival procedure (STAR) flown</td></tr><tr><td><code>arrTransition</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Arrival transition flown</td></tr></tbody></table>

{% hint style="info" %}
**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.
{% endhint %}

{% hint style="info" %}
**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.
{% endhint %}

{% hint style="info" %}
**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.
{% endhint %}

{% hint style="warning" %}
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`.
{% endhint %}