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

{% 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>.
      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="https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FGkPrYPaWmC89PwfPB9JI%2FIMG_9A75C565AF05-1.jpeg?alt=media&amp;token=7e64c17e-f1d6-45e0-9579-62999e888585" 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.

![](https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FdD3j9DU4mDN3xzY66Wqr%2Flogten_1.jpeg?alt=media\&token=8e6c289c-effb-4b17-809c-1e42e2c182d1) ![](https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FP2se7pGMjZwj5uBvYvgw%2Flogten_2.jpeg?alt=media\&token=5ac7f5d0-2e75-45f0-966b-a13f5eaa34b1) ![](https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FYHRyDVTffqCjPDNFEwVt%2Flogten_3.jpeg?alt=media\&token=ea6e09fe-094c-497f-b1f0-70d83599dec1)

</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="https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2F4R5XL8OKfeZxrJ137mJ4%2FcrewLounge.png?alt=media&amp;token=e4513a00-e0b4-4a7a-b637-1bf7bfe37ac0" 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).

![](https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2Fg9Eog07IULGPsOukJkS1%2Fmcc-screen-1.png?alt=media\&token=cc78cd3c-c279-454e-9dad-ec533985a72b) ![](https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FgHHkFBhAhoB7ePOvbPXY%2Fmcc-screen-2.png?alt=media\&token=4c40755c-ca01-459f-95a0-01f3020ca2a3) ![](https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FdRITjdbbbhh2uaOlRp4R%2Fmcc-screen-3.png?alt=media\&token=7e60375c-93bc-4ccd-bec5-ca97146bada0)

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

![](https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FJ30e6i2JGHOy5wL7runS%2FRB%20import_1.jpeg?alt=media\&token=80676831-5847-4d05-b3cf-fd0eb9605820) ![](https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FgSTlDgGXj1ZJ7s9AVY5s%2FRB%20import_2.jpeg?alt=media\&token=2668791d-18e9-4481-9f3f-12439c0817ad) ![](https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FsdkRjr77SZzzWEqDjEiS%2FRB%20import_3.jpeg?alt=media\&token=c0f9a415-01da-459c-a167-686e49054705)

</details>

<details>

<summary>OffBlock</summary>

In the OffBlock app, go to **Menu → Statistics, Reports, Exports** and tap **Total statistics**. Tap the **Export** button in the bottom-right corner, choose **Export as CSV**, then submit the CSV file.

</details>

<details>

<summary>ForeFlight</summary>

In the ForeFlight app, go to **Logbook**, scroll all the way down and tap **MENU → SETTINGS**. Find the **Auto-Export** section, turn it on, and set **Export Options** to **CSV**. Tap **Export Now** and you will receive the CSV file by email. Submit that file — it already contains both your aircraft and your flights.

ForeFlight uses its own aircraft type codes, so after uploading you will be asked to match each one to the correct aircraft type.

**Tip:** if you use ForeFlight alongside Wader, you can forward the CSV attachment ForeFlight emails you straight to **<foreflight@wader.pro>** instead of downloading it and importing it manually.

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

{% 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="https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2F6xGWCQZGf3MhTSjp3Al4%2Faireuropa1.jpeg?alt=media&amp;token=adbb8b1c-74d2-4589-85b8-395fc3c93523" alt="" data-size="original">

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

<img src="https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FJrL4daMvdNR8fTWBTv36%2Faireuropa2.jpeg?alt=media&amp;token=9bc1a01d-b758-472c-8bd8-b4e915ae30e6" 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>🇬🇧 British Airways</summary>

Import your roster from the **iBid** app:

1. Open iBid on your phone and go to your roster for the month
2. Use the **share / print** option and choose **Save as PDF**
3. Submit the saved PDF

The roster doesn't record whether you flew as Captain or First Officer, so during import you'll be asked to **select your function (PIC or SIC)** — the block time is credited to that role for every flight, and the Captain (and any extra Co-Pilot) named in the roster is added to the crew.

Legs you have already flown are imported with their **actual off-block and on-block times**. Legs still to come are imported with their **scheduled times**, so you can import the whole month at once — import the roster again after flying them and those legs are updated with the actual times.

{% hint style="info" %}
Take-offs and landings come from the **Ldg** tick in your roster: a ticked leg is logged with one take-off and one landing, an unticked leg with none. Standby, office days and hotel details are skipped automatically. All times are UTC.
{% 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="https://3440297477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Famix6flPIe1pzcyRPQy5%2Fuploads%2FmwZBCx9R7vpUDHxfq5rj%2FCaptura%20de%20tela%202024-02-24%20224155.jpg?alt=media&amp;token=09b3b667-38c1-4a2a-90de-b22a1100ff17" 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>🌐 PDC CrewConnex</summary>

If your airline uses the PDC CrewConnex crew portal, you can import your roster directly.

Log in to the CrewConnex portal (efyweb3.pdc.com/crewconnex), open the **Roster** page for the month you want, then use your browser's **Print → Save as PDF** to download it and submit it.

The roster doesn't record whether you flew as Captain or First Officer, so during import you'll be asked to **select your function (PIC or SIC)** — the block time is credited to that role for every flight, and the other pilot listed in the roster's Crew column is added as the second crew member.

{% hint style="info" %}
Only actual flights are imported. Off days, standby, and blank duties are skipped automatically. Times are recorded in the time reference shown in your roster's column headers — local by default, or UTC if your roster uses it.
{% endhint %}

</details>

<details>

<summary>🇶🇦 Qatar Airways</summary>

Log in to the Qatar Airways crew system and export your logbook as an **Excel** file, then submit it.

</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>🇸🇪 SAS - Scandinavian Airlines</summary>

Open the **SAS Crew Portal**, go to the **Airside** app, and select **Logbook**. Export it as **CSV**, then submit the file.

</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>🇺🇸 United Airlines</summary>

Log in to the United Airlines crew portal, go to the **Logbook** section, and set your desired date range. Click **Export** to download the **.txt** file, then submit it.

The export doesn't record whether you flew as Captain or First Officer, so during import you'll be asked to **select your function (PIC or SIC)**.

</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>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</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 if <code>timeReference</code> is <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>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>. 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>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>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 will be automatically calculated based on OOOI times</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 %}