> 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/planning-a-mission.md).

# Planning a Mission

This chapter covers the key aspects of mission planning.

{% hint style="success" %}
The DeltaQuad Evo is designed for autonomous flight, accomplished through the planning and execution of missions. Missions can be planned using the Ground Control Station and can be created and sent directly to the vehicle, loaded from existing mission plans, or saved for future use. The following sections provide an overview of the fundamental steps involved in planning a mission for the DeltaQuad Evo.
{% endhint %}

## Chapter Index:

* [Preparing a Mission Plan](/gov/flight/planning-a-mission/preparing-a-mission-plan.md)
* [Best Practice and Tips](/gov/flight/planning-a-mission/best-practices-and-tips.md)
* [Mission Start ](/gov/flight/planning-a-mission/mission-start-action.md)[Action](/gov/flight/planning-a-mission/mission-start-action.md)
* [Set Intermediate Waypoints](/gov/flight/planning-a-mission/set-intermediate-waypoints.md)
  * [Survey Pattern](/gov/flight/planning-a-mission/set-intermediate-waypoints/survey-pattern.md)
  * [Corridor Scan](/gov/flight/planning-a-mission/set-intermediate-waypoints/corridor-scan.md)
* [Mission End Action](/gov/flight/planning-a-mission/mission-end-action.md)


---

# 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/planning-a-mission.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.