> For the complete documentation index, see [llms.txt](https://docs.deltaquad.com/sth/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/sth/flight/planning-a-mission.md).
# Planning a mission
The DeltaQuad EVO has been designed to fly autonomously, this is achieved by planning and executing missions. Missions are set through the Ground Control Station. They can be created and sent to the vehicle directly, loaded from an existing mission plan, or saved to a mission plan. This section covers the basics of planning a mission for the DeltaQuad EVO.
The operator can plan a takeoff and landing from the Fly View by selecting sectors that are free of obstacles at the approach altitude.
The DeltaQuad will take off and transition to aerodynamic mode into a set direction and orbit until new commands are given.
How to take off and land using Fly View will be discussed thoroughly in a later section of this manual.
{% hint style="info" %}
In certain situations where launch and landing sites pose significant restrictions and obstacles, utilizing the Takeoff and Approach functionalities in Fly View becomes impractical. In such instances, it is advisable to employ the Plan View for comprehensive mission planning.
{% endhint %}
---
# 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://docs.deltaquad.com/sth/flight/planning-a-mission.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.