> 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/reference/flight-validation.md).

# Flight Validation

In Wader, a flight must have all required fields filled in to be considered **complete**. Incomplete flights appear in **gray** in your logbook and are:

* Not counted in your Dashboard totals
* Not included in exported PDF logbooks

## Required fields

A flight is complete only when **all** of the following are filled in:

| Field                 | Notes                            |
| --------------------- | -------------------------------- |
| Flight date           |                                  |
| Departure airport     | ICAO code                        |
| Arrival airport       | ICAO code                        |
| Departure time (OUT)  |                                  |
| Arrival time (IN)     |                                  |
| Aircraft type         | ICAO type code                   |
| Tail number           |                                  |
| Pilot role (Function) | PIC, SIC, etc.                   |
| PIC name              | Required for EASA logbook format |

## How to fix incomplete flights

1. Tap the gray flight to open it.
2. Look for the **pending items** indicator — it lists the missing fields.
3. Fill in the required fields.
4. Save — the flight will return to normal color and be counted in your totals.

**Tip**: Use the **"Incomplete flights only"** filter in the Logbook to quickly find all gray entries at once.

<figure><img src="/files/vYsB6dN9wikJkkIxmbWd" alt="Pending items on a flight"><figcaption><p>Open an incomplete flight to see which fields are missing</p></figcaption></figure>


---

# 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/reference/flight-validation.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.