> 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/executing-and-monitoring-a-mission/emergency-procedures/during-the-landing-sequence.md). # During the Landing Sequence The following should be monitored during the landing sequence. Depending on the mission plan or flight mode, the Evo can perform a straight-line, loiter-down, or manual landing. When the Evo is executing a landing sequence, it will significantly lower the altitude. **Special care must be taken during the descent stage to avoid collision with obstacles.** When a collision seems imminent, the pilot must take control of the drone and increase altitude either by switching to a manual control mode and pulling the pitch stick down (nose up) or by repositioning the vehicle and increasing altitude. In such an occurrence, it is advised to either change the mission plan and execute an **RTL** after the change or land the vehicle manually. ### **Unstable Descent** Operator Action: **None** If the vehicle becomes unstable during landing, the landing speed, as indicated in the **Safety** features, is likely set too high. ### **No Auto Disarm After Touchdown** Operator Action: **DISARM (Emergency Action -> SHUTDOWN)** The DeltaQuad Evo should disarm automatically 5 to 10 seconds after touchdown. If the vehicle does not disarm automatically, the disarm command (Shutdown) should be sent. This command can be sent by selecting Emergency Actions - Shutdown. The reason for this could be related to landing on a significantly uneven surface or slope. It can also indicate that the sensors need calibration. ### Landing gear legs do not deploy Operator Action: **None or reposition above soft ground** If one of the landing gear legs does not deploy during descent, do not interfere, as the DeltaQuad Evo is designed to balance itself on the ground even with only three legs deployed. If two legs or more do not deploy during descent, position the vehicle above soft ground (NUDGING), such as grass, and avoid hard ground, such as concrete. {% hint style="warning" %} After an incident or crash wait **10 minutes** as the battery may become unstable. Take pictures of the vehicle from every direction. Try to document the crash and crash site as thoroughly as possible. {% 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 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/executing-and-monitoring-a-mission/emergency-procedures/during-the-landing-sequence.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.