> 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

{% hint style="info" icon="star" %}
**One‑Time Import** is no longer available.

Today, importing previous logbooks is included with **Wader PRO**, which also gives you automated, unlimited imports. 

We’ve recently reduced the PRO price to make it more accessible, so it’s easier than ever to bring your entire flight history into Wader and keep it up-to-date. 

Subscribe [here](https://logbook.waderaviation.com/import) to get started.
{% 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 web app:** access the web app ([https://logbook.waderaviation.com/](https://logbook.waderaviation.com/admin)) and go to **Import** in the lateral menu. Select the file source and upload the file.
   2. **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>.&#x20;
      2. If your airline uses AIMS/eCrew, you may also send it to <aims@wader.pro>.
5. Your file is processed **automatically** and you are notified by email once it is completed.

{% hint style="info" %}
If your airline report is not covered yet, hit us via the web app "Send Feedback" and our team will take a look to add it!
{% 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.

<img src="/files/hduQJSNGJfo8zkFbvPlc" alt="" data-size="original"> <img src="/files/e4FUGcWCKxVcTG9kBV5p" alt="" data-size="original"> <img src="/files/Evt0ujYUAjAT3YLLru1F" alt="" data-size="original">

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

<img src="/files/1WVj9ZzoTX3r2yDTLLgT" alt="" data-size="original"> <img src="/files/gAKDg58wLG2ORjNUyKob" alt="" data-size="original"> <img src="/files/8cZgXKqDHvTfUPzKtV4C" alt="" data-size="original">

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

<img src="/files/aSbuziEKLe11ibt7OBjD" alt="" data-size="original"> <img src="/files/yFp7xMmcNms6w7C1xQ7M" alt="" data-size="original"> <img src="/files/fi6MjEJMLjQ7CVM6b0qY" alt="" data-size="original">

</details>

<details>

<summary>Others</summary>

If you have your hours in a digital logbook not listed above, you may still transpose your records to our [standard spreadsheet template](#standard-spreadsheet).

</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.).&#x20;

{% 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** 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>🇮🇪 Ryanair</summary>

Ryanair EFB flight reports are emailed to you after each flight. Just forward them to **<ryanair@wader.pro>** from the email address registered in your Wader account. You can also add your company email as a secondary email to make this easier by going to our web app at <https://logbook.waderaviation.com/profile>

</details>

<details>

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

Go to the **RAMIS system** and export your flights in Excel format.&#x20;

{% 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 web app "Send Feedback" 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 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>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>)</td></tr><tr><td><code>aircraftIata</code></td><td><mark style="color:orange;">(recommended)</mark></td><td>IATA aircraft type code (e.g. <code>738</code> for Boeing 737-800)</td></tr><tr><td><code>aircraftIcao</code></td><td><mark style="color:red;">(required if IATA code not provided)</mark></td><td>ICAO aircraft type code (e.g. <code>B738</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>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>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>)</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>)</td></tr><tr><td><code>timeReference</code></td><td><mark style="color:red;">(required)</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.</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 it informed <code>timeReference</code> as  <code>BASE</code> </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>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> format (e.g. <code>1:30</code>)</td></tr><tr><td><code>stickTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Time at the controls (airborne time) in <code>HH:MM</code> . If <strong>blank</strong>, it will be considered 100% of total time. </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>. If <strong>blank</strong>, it will be automatically calculated based on OOOI times.</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></td></tr><tr><td><code>simulatedInstrumentTime</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Simulated instrument time (hood / foggles) in decimal hours or <code>HH:MM</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>.</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>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>. If simulator: <code>Trainee</code>, <code>Trainer</code> </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></td></tr><tr><td><code>multiPilot</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Multi-pilot time in <code>HH:MM</code></td></tr><tr><td><code>pilotName1</code></td><td><mark style="color:orange;">(recommended)</mark></td><td>Set as <code>SELF</code> if you are the Pilot in Command. Otherwise, add the full name of the other crew member in the primary crew position. <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>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>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>qualificationLevel</code></td><td><mark style="color:yellow;">(optional)</mark></td><td>Simulator qualification level, 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></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.waderaviation.com/importing-your-data/from-another-logbook.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.