> 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/onboarding/importing-your-previous-logbooks.md).

# Importing Your Previous Logbooks

{% hint style="info" icon="star" %}
This a PRO feature. Subscribe [here](https://logbook.waderaviation.com/import).
{% endhint %}

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

1. **Check supported formats** below — find your logbook app or airline system
2. **Follow the instructions** for your format to export the correct file
3. **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.
4. **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.
5. 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*

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

***

## Supported Formats

### Electronic Logbooks

<details>

<summary>LogTen Pro</summary>

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.

<img src="/files/44g8Txi9sc90qiSIFEkF" alt="" data-size="original">

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.

![](/files/hduQJSNGJfo8zkFbvPlc) ![](/files/e4FUGcWCKxVcTG9kBV5p) ![](/files/Evt0ujYUAjAT3YLLru1F)

</details>

<details>

<summary>mcc / crewLounge PILOTLOG</summary>

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

<img src="/files/sqZPwd9fBdfmkC3s6FkX" alt="" data-size="original">

**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).

![](/files/1WVj9ZzoTX3r2yDTLLgT) ![](/files/gAKDg58wLG2ORjNUyKob) ![](/files/8cZgXKqDHvTfUPzKtV4C)

</details>

<details>

<summary>RB Logbook</summary>

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.

![](/files/j3fyW6R1nnQgmpc2vnb7) ![](/files/POJm5QUyigh7Bw95efZv) ![](/files/y4YF14iVFBI6WRlMe6AM)

</details>

<details>

<summary>Others</summary>

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

</details>

***

### Airline Systems

<details>

<summary>🌐 AIMS / eCrew</summary>

**AIMS eCrew (Legacy)**

1. Log in to AIMS eCrew in your browser
2. 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**

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

</details>

<details>

<summary>🇧🇷 ANAC (SACI)</summary>

1. Log in to the ANAC system at [sistemas.anac.gov.br/SACI](https://sistemas.anac.gov.br/SACI/)
2. In the left menu, select **CIV → Declaração de Experiência de Voo**
3. 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.).

{% hint style="warning" %}
Make sure to upload the original (unaltered) file.
{% endhint %}

</details>

<details>

<summary>🇷🇺 Aviabit</summary>

Export your logbook from Aviabit in **CSV** format.

{% hint style="warning" %}
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](#standard-spreadsheet) to fill in any gaps before submitting.
{% endhint %}

</details>

<details>

<summary>🇪🇸 Air Europa</summary>

Go to your **Casillero Digital** app and tap **Logbook**:

<img src="/files/XWqX08SJnZBXGcu6Tluo" alt="" data-size="original">

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

<img src="/files/AXHGpdCP8S58pahXvrn2" alt="" data-size="original">

You will receive the file in your corporate email.

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

</details>

<details>

<summary>🇦🇪 Air Arabia</summary>

Log in to the Air Arabia **Cesar web portal** and generate the **Electronic Log Book** file in Excel (.xls) format.

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

</details>

<details>

<summary>🇧🇷 Azul Linhas Aéreas</summary>

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

{% hint style="info" %}
Azul Conecta uses a different format that is currently not supported. In that case, the [standard spreadsheet](#standard-spreadsheet) is the best option.
{% endhint %}

</details>

<details>

<summary>🇦🇪 Emirates</summary>

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

Submit the downloaded Excel file.

</details>

<details>

<summary>🇧🇷 GOL Linhas Aéreas</summary>

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.

<img src="/files/6AJox0AoKjyiu6cWAk8L" alt="" data-size="original">

{% hint style="warning" %}
The consolidated file from the roster ("ESCALA") **cannot** be used — it does not include mandatory logbook information such as aircraft registration.
{% endhint %}

</details>

<details>

<summary>🇧🇷 LATAM Airlines Brasil</summary>

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

{% hint style="info" %}
LATAM Cargo uses a different format that is currently not supported. In that case, the [standard spreadsheet](#standard-spreadsheet) is the best option.
{% endhint %}

</details>

<details>

<summary>🇲🇻 Trans Maldivian Airways</summary>

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

{% hint style="warning" %}
Make sure to upload the original (unaltered) file.
{% endhint %}

</details>

<details>

<summary>Others</summary>

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.

</details>

***

## Standard Spreadsheet

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

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

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

| Field                     | Status                                           | Description                                                                                                                                                 |
| ------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `flightDate`              | <mark style="color:red;">(required)</mark>       | Date of the flight in `YYYY-MM-DD` format (e.g. `2023-06-15`)                                                                                               |
| `aircraftIata`            | <mark style="color:orange;">(recommended)</mark> | IATA aircraft type code (e.g. `738` for Boeing 737-800)                                                                                                     |
| `aircraftIcao`            | <mark style="color:orange;">(recommended)</mark> | ICAO aircraft type code (e.g. `B738`). At least one of `aircraftIata` or `aircraftIcao` should be provided                                                  |
| `flightNumber`            | <mark style="color:yellow;">(optional)</mark>    | Flight number (e.g. `LA1234`). Do not include the airline prefix if it is already in the field                                                              |
| `aircraftTailnumber`      | <mark style="color:orange;">(recommended)</mark> | Aircraft registration / tail number (e.g. `PT-MSY`). Used to identify the specific aircraft                                                                 |
| `depAirport`              | <mark style="color:red;">(required)</mark>       | ICAO or IATA code of the departure airport (e.g. `SBGR` or `GRU`)                                                                                           |
| `arrAirport`              | <mark style="color:red;">(required)</mark>       | ICAO or IATA code of the arrival airport (e.g. `SBSP` or `CGH`)                                                                                             |
| `timeReference`           | <mark style="color:red;">(required)</mark>       | Timezone reference for all time fields. Use `UTC` for Zulu time, or a UTC offset such as `UTC-3` or `UTC+1`                                                 |
| `baseAirport`             | <mark style="color:yellow;">(optional)</mark>    | ICAO or IATA code of your home base airport. Used to calculate cross-country time if not provided separately                                                |
| `startTime`               | <mark style="color:orange;">(recommended)</mark> | Block-off time (chocks removed / pushback) in `HH:MM` format                                                                                                |
| `takeoffTime`             | <mark style="color:orange;">(recommended)</mark> | Wheels-off time in `HH:MM` format                                                                                                                           |
| `landingTime`             | <mark style="color:orange;">(recommended)</mark> | Wheels-on time in `HH:MM` format                                                                                                                            |
| `parkingTime`             | <mark style="color:orange;">(recommended)</mark> | Block-on time (chocks in / engines off) in `HH:MM` format                                                                                                   |
| `totalTime`               | <mark style="color:red;">(required)</mark>       | Total flight time (block-to-block) in decimal hours (e.g. `1.5`) or `HH:MM` format (e.g. `1:30`)                                                            |
| `stickTime`               | <mark style="color:yellow;">(optional)</mark>    | Time at the controls (airborne time) in decimal hours or `HH:MM`                                                                                            |
| `nightTime`               | <mark style="color:yellow;">(optional)</mark>    | Night flying time in decimal hours or `HH:MM`                                                                                                               |
| `actualInstrumentTime`    | <mark style="color:yellow;">(optional)</mark>    | Actual IMC time in decimal hours or `HH:MM`                                                                                                                 |
| `simulatedInstrumentTime` | <mark style="color:yellow;">(optional)</mark>    | Simulated instrument time (hood / foggles) in decimal hours or `HH:MM`                                                                                      |
| `crossCountryTime`        | <mark style="color:yellow;">(optional)</mark>    | Cross-country time in decimal hours or `HH:MM`. If omitted, Wader will calculate it automatically based on `baseAirport`                                    |
| `takeoffs`                | <mark style="color:yellow;">(optional)</mark>    | Total number of takeoffs (day + night). If omitted, defaults to `1`                                                                                         |
| `landings`                | <mark style="color:yellow;">(optional)</mark>    | Total number of landings (day + night). If omitted, defaults to `1`                                                                                         |
| `dayTakeoffs`             | <mark style="color:yellow;">(optional)</mark>    | Number of daytime takeoffs                                                                                                                                  |
| `nightTakeoffs`           | <mark style="color:yellow;">(optional)</mark>    | Number of night takeoffs                                                                                                                                    |
| `dayLandings`             | <mark style="color:yellow;">(optional)</mark>    | Number of daytime landings                                                                                                                                  |
| `nightLandings`           | <mark style="color:yellow;">(optional)</mark>    | Number of night landings                                                                                                                                    |
| `approachType`            | <mark style="color:yellow;">(optional)</mark>    | Type of instrument approach flown (e.g. `ILS`, `RNAV`, `VOR`, `NDB`). Use one value per flight; if multiple approaches were flown, use the most significant |
| `function`                | <mark style="color:red;">(required)</mark>       | Pilot function / role. Accepted values: `PIC`, `SIC`, `FO`, `Relief`, `Instructor`, `Student`, `Examiner`, `Deadhead`, `Observer`                           |
| `ifrTime`                 | <mark style="color:yellow;">(optional)</mark>    | Total IFR time in decimal hours or `HH:MM`                                                                                                                  |
| `multiPilot`              | <mark style="color:yellow;">(optional)</mark>    | Multi-crew / multi-pilot time in decimal hours or `HH:MM`                                                                                                   |
| `pilotName1`              | <mark style="color:orange;">(recommended)</mark> | Full name of the other crew member in the primary crew position (e.g. Captain if you are FO). Used for logbook crew records                                 |
| `pilotName2`              | <mark style="color:yellow;">(optional)</mark>    | Full name of an additional crew member                                                                                                                      |
| `pilotName3`              | <mark style="color:yellow;">(optional)</mark>    | Full name of an additional crew member                                                                                                                      |
| `pilotName4`              | <mark style="color:yellow;">(optional)</mark>    | Full name of an additional crew member                                                                                                                      |
| `remarks`                 | <mark style="color:yellow;">(optional)</mark>    | Free-text remarks or notes for the flight entry                                                                                                             |
| `isSimulator`             | <mark style="color:yellow;">(optional)</mark>    | Set to `true` if this entry is a simulator session rather than an actual flight. Defaults to `false`                                                        |
| `qualificationLevel`      | <mark style="color:yellow;">(optional)</mark>    | Simulator qualification level, if applicable (e.g. `FFS`, `FTD`, `FNPT`). Only relevant when `isSimulator` is `true`                                        |