> 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/searching-and-filtering.md).
# Searching & Filtering
Find specific flights quickly using search and filter tools.
When your logbook grows to hundreds or thousands of flights, finding a specific entry quickly matters. Wader gives you two tools for this: **Search** and **Filter**.
***
## Search
Tap the **magnifying glass icon** in the top bar of the Logbook screen to open the search bar.
You can search flights by any of the following:
| Search term | Examples |
| ----------------- | --------------------------------------------------- |
| **Airport** | ICAO code (`EGLL`) or IATA code (`LHR`) |
| **Pilot name** | First or last name of any crew member on the flight |
| **Flight number** | `BA456`, `UA101` |
| **Tail number** | Aircraft registration, e.g. `G-EUOE` |
| **Aircraft type** | Type designator, e.g. `A320`, `B738` |
| **Remarks** | Any text recorded in the remarks field |
Results update as you type. Tap a result to open that flight.
{% hint style="warning" %}
Search may not work correctly with **special characters** (accented letters, diacritics, non-Latin scripts). For best results, use standard Latin characters — for example, search `Zurich` rather than `Zürich`.
{% endhint %}
Search flights by airport, pilot, tail number, aircraft type, or remarks
***
## Filter
Filter by flight type, completion status, or date range
Tap the **filter icon** in the top bar to open the filter panel. Filters let you narrow the flight list to a specific subset of entries.
Available filters:
| Filter | What it shows |
| ------------------------------- | ---------------------------------------------------------- |
| **Incomplete logs only toggle** | Only flights that are missing required fields (gray cards) |
| **Flight toggle** | Show/Hide flights from the list |
| **Simulator toggle** | Show/Hide sim sessions from the list |
| **Date range** | Flights within a specific start and end date |
### Combining Filters
Filters can be combined. For example, you can filter for **real flights only** within a **specific date range** at the same time.
### Active Filter Indicator
When one or more filters are active, a visual indicator appears on the filter icon to remind you that the list is not showing all flights.
### Clearing Filters
Tap **Reset** inside the filter panel to clear all active filters and return to the full flight list.
***
## Tips
{% hint style="success" %}
Use the **Incomplete flights only** filter to quickly surface any gray (incomplete) logbook entries. This is a great way to do a regular logbook audit and make sure all your flights are counted toward your totals.
{% endhint %}
**Tip:** Combine **Simulator sessions only** with a date range filter to quickly review your simulator currency for a specific period.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.waderaviation.com/quick-start/logbook/searching-and-filtering.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
