> 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/totals.md).
# Understanding Your Totals
## How totals are calculated
Wader counts all **valid (complete) flights** toward your totals. It does not infer or estimate missing values. Every flight that is counted is fully defined — all required fields have been filled in.
If a flight is missing any required information, it is saved but excluded from totals until it is completed.
***
## What makes a flight valid
The following fields are required for a flight to be counted:
| Field | Notes |
| -------------------------- | ------------------------- |
| Flight date | |
| Departure time (OUT) | |
| Arrival time (IN) | |
| Departure airport | |
| Arrival airport | |
| Aircraft type | |
| Tail number (registration) | |
| Pilot role (Function) | |
| PIC name | Required under EASA rules |
***
## Incomplete flights (gray vs. green)
Flights in your logbook are colour-coded based on their status:
* **Gray** — the flight is saved but incomplete. It is missing one or more required fields and is **not counted** in your totals or included in exports.
* **Green** — the flight is complete. All required fields are filled in and the flight **is counted** in your totals.
Once you fill in all required fields on an incomplete flight, it turns green and is counted immediately.
***
## How to find and fix incomplete flights
**Option A — Use the filter:**
Open the filter panel in your logbook and select **Show incomplete logs only**. This filters your logbook to show only the flights that still need attention.
**Option B — Open an individual flight:**
Open any flight and scroll down to the **Flight Times** summary section. You will see a **Pending Items** list showing exactly which fields are still missing.
Open an incomplete flight to see which required fields are missing
Work through each incomplete flight, fill in the missing fields, and save. Once all flights are green, your totals will reflect your complete logbook.
***
## Why your export may differ from the Dashboard
Your Dashboard shows all complete flights with no filters applied. When you export, you configure filters — and those filters can cause the PDF total to differ from what you see in the Dashboard.
### Date range or aircraft filter
When exporting, you select a specific date range and one or more aircraft types. If those filters exclude some flights, the PDF total will be lower than your Dashboard total.
### Previous experience toggle
The **Add previous experience** toggle in the export settings includes or excludes your previous experience totals. If it is off, those hours will not appear in the PDF.
### Relief time deduction
If **Deduct relief time** is enabled in export settings, your PDF will show lower totals than your Dashboard, which always shows gross time.
***
## Matching the Dashboard exactly
{% hint style="info" %}
To get a PDF that matches your Dashboard total exactly: select all aircraft, use the full date range, enable **Add previous experience**, and leave **Deduct relief time** off.
{% endhint %}
***
## Why totals may differ from other logbook systems
Different logbook systems handle missing data differently. Some systems count partial flights or infer missing values (such as estimating flight time from schedule data). Wader requires complete data for every counted flight, which ensures accuracy and consistency with regulatory requirements.
If your Wader totals differ from another system, it is likely that:
* The other system is counting flights that Wader considers incomplete.
* The other system is applying different rules for what counts as a valid entry.
The fix is the same either way: complete all flights in Wader so they show as green.
---
# 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/reference/totals.md?ask=&goal=
```
`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.