> 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/quick-start/logbook/logging-flights/logging-a-flight.md).

# Logging a Flight

This page walks you through creating a new flight entry from start to finish.

## Step-by-step

### 1. Open a new flight

Tap the **+** button and select Flight to open a blank flight form.

### 2. Set the date

The date defaults to today. Tap it to change it if you are logging a past or future flight.

### 3. Select your aircraft

Enter the tail number and the ICAO aircraft type code (for example, B738 or A320). Tap **Use last aircraft** to repeat the tail number and type from your previous flight — useful for pilots who fly the same aircraft regularly.

### 4. Set your crew

Select the total number of pilots (1–4), then enter each pilot's name. Click the search icon next to a pilot position to autocomplete it from your previous entries. Tap **Use last crew** to repeat the same crew as your previous flight.

### 5. Enter airports

Enter the departure airport in the **FROM** field and the arrival airport in the **TO** field using IATA or ICAO codes. Wader automatically looks up the airport details.

### 6. Enter times (UTC)

Fill in the four block times, all in UTC:

| Field   | Meaning                                     |
| ------- | ------------------------------------------- |
| **OUT** | Off-block — when the aircraft starts moving |
| **OFF** | Takeoff — wheels up                         |
| **ON**  | Landing — wheels down                       |
| **IN**  | On-block — aircraft parked                  |

OUT and IN are the only required times. OFF and ON are optional but recommended for accurate totals and to automatically fill the your takeoffs and landings as day or night.

### 7. Fill in logbook details

Select your **function** (PIC, SIC, etc.), **flight rules** (IFR, VFR, or mixed), **flight conditions** and **cross country**. If this was a multi-pilot operation, enable the **Multi-Pilot** toggle.

### 8. Add remarks

Use the **Remarks** field for endorsements, special procedures, or any notes you want recorded in your logbook.

### 9. Save

Tap **Save**. Your flight is now in your logbook.

***

{% hint style="info" %}
**Speed up daily logging with preferences.** Your preferences auto-fill most fields — set them once in Settings and you will rarely need to re-enter them. See [Preferences](/account-and-settings/preferences.md).
{% endhint %}

{% hint style="info" %}
**You do not need to complete every field in one go.** Save with the fields you already know/have and finish the entry later. Flights with missing required fields appear gray in your logbook list and are not included in totals until all required fields are filled. See [Flight Validation](/reference/flight-validation.md).
{% endhint %}

For a detailed explanation of every field, see [Flight Form Reference](/quick-start/logbook/logging-flights/flight-form-reference.md). To auto-fill flight details from an OFP PDF, see [Importing an OFP](/quick-start/logbook/logging-flights/importing-an-ofp.md).


---

# 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, and the optional `goal` query parameter:

```
GET https://support.waderaviation.com/quick-start/logbook/logging-flights/logging-a-flight.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.