> For the complete documentation index, see [llms.txt](https://docs.deltaquad.com/gov/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deltaquad.com/gov/flight/quick-takeoff/land-approach.md).

# Land Approach

This section outlines the steps involved in planning the Land Approach.

1. To plan a **Quick Takeoff**, the **DeltaQuad Evo** must be connected to the **GCS**.
2. Position the vehicle at the desired takeoff location.
3. Ensure the **nose** of the vehicle is **pointed into** the **wind**.
4. In the **Fly View**, click on the **Takeoff** command.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/1ELHvxgTwztjwpjFn8Qs/Fly%20View.webp" alt="" width="300"><figcaption></figcaption></figure>

## Land Approach Settings

1. An **Octagon** is positioned around the vehicle, divided into 8 red sectors called **Pizza Slices**.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/FoU93lsxqDPEvPn6Ew9h/image.png" alt=""><figcaption></figcaption></figure>

2. The first step is to assign the **sectors** where the vehicle can **loiter**, **transition**, and **land**. This is done by clicking on the relevant **sectors**. These sectors must be free of **obstacles**, and since the vehicle should take off and transition into the **wind**, **sectors** behind the vehicle should be selected. The vehicle will place the Loiter Down Orbit within the dedicated green area

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/W6ivCV1Fu0nfh32Czwnc/QT%202.webp" alt=""><figcaption></figcaption></figure>

3. Grab the **vertex** at the top of the **octagon** and move it around for more **granular control**.

{% hint style="warning" %}
The vehicle places the **Loiter Down Orbit** within the dedicated **Approach Zones (green)** so the vehicle can transition and land into the wind. If this is not possible, the vehicle will choose a **Loiter Down Orbit** as close as possible to this direction, given the limitations of the selected sectors.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/HGSyAGMT01fRi4vdzXfk/QT%203.webp" alt=""><figcaption></figcaption></figure>

4. Set the altitude for the **Back Transition** using the **Altitude Slider** on the right side of the screen. The **Altitude Frame** is **HGT**, Height (Heights are referenced to the takeoff location).

{% hint style="warning" %}
The minimum **Back Transition/Landing Altitude** to which the vehicle descends must be set at least **25 meters** above the highest obstacles in the landing area. For example, if the tallest tree in the landing area is **10 meters** high, the **Landing Altitude** must be set to at least **35 meters**.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/ClfJUGv6YtcdHY6k0uQQ/QT%204.webp" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/QRAlFq2wQTVN4m8hCzZW/Loiter%20landing.webp" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
When using the **Quick Takeoff**, only the **Orbit Land Pattern** is available as a landing option. A **Straight Land Pattern** is not available.
{% endhint %}

5. **Hold** **to Confirm** the settings for the **Land Approaches**.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/Fpk4tiudoFW1zqhiCAPg/QT%205.webp" alt=""><figcaption></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.deltaquad.com/gov/flight/quick-takeoff/land-approach.md?ask=<question>&goal=<user_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.
