> 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/swipe-actions.md).

# Swipe Actions

Flight cards in the Logbook support swipe gestures that let you take quick actions without opening a flight. This is especially useful when logging a busy day of flying with multiple legs.

<figure><img src="/files/J5ePrGPSNdngPUy8zi8a" alt="Swipe actions on a flight card" width="200"><figcaption><p>Swipe right to reveal Duplicate, Next Flight, and Return Flight shortcuts</p></figcaption></figure>

***

## Swipe Left — Delete

Swipe a flight card **to the left** to reveal the **Delete** button (shown in red).

Tap **Delete** to confirm. The deletion is **permanent and cannot be undone**, so make sure you're removing the right flight before confirming.

{% hint style="danger" %}
Deleted flights cannot be recovered. If you have cloud sync enabled, the deletion will propagate to all your devices.
{% endhint %}

***

## Swipe Right — Quick Create Actions

Swipe a flight card **to the right** to reveal three buttons for quickly creating new flights based on the selected one:

### Duplicate

Creates an exact copy of the flight with **all fields pre-filled** — same aircraft, same airports, same crew, same times.

Use this when you need to log an identical or nearly identical flight. You can then open the duplicate and adjust any fields that differ.

### Next Flight

Creates a new flight using the **same aircraft, crew, and general setup**, but with all time fields left empty.

The departure airport is pre-set to the arrival airport of the original flight, so the new leg picks up exactly where the last one left off.

This is ideal for logging back-to-back legs on a multi-sector day without re-entering aircraft and crew details every time.

### Return Flight

Creates a new flight with the **departure and arrival airports reversed** — the aircraft and crew details are carried over from the original flight, but time fields are left empty.

Use this for the return leg of an out-and-back routing.

***

## Notes & Tips

{% hint style="info" %}
The **Next Flight** and **Return Flight** actions are not available for simulator sessions. Simulators do not follow the same point-to-point routing logic as real flights.
{% endhint %}

**Tip:** For a multi-leg day, log your first flight fully, then use **Next Flight** on each completed leg to pre-populate the next one. This keeps your aircraft, crew, and setup consistent across all legs and cuts data entry to just the time fields.


---

# 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/quick-start/logbook/swipe-actions.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.