> 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/setup/safety-features/high-wind-failsafe-trigger.md). # High Wind Failsafe Trigger This section covers the High Wind Failsafe Trigger settings.
The **High Wind Failsafe Trigger** is a safety feature that activates when the vehicle detects wind speeds exceeding 14 m/s. When triggered, it initiates a predefined action, such as returning to home or landing, to prevent the vehicle from being adversely affected by high winds. **Default Failsafe Action:** Return Failsafe detection can trigger one of the following actions.
DisabledNo action (the failsafe will be ignored).
Return modeThe vehicle will enter Return mode and fly directly to the designated landing location at the set return altitude, then land.
Land mode*The vehicle will enter Land mode and land immediately.
(**\***only available in AMC's Advanced Mode) --- # 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/setup/safety-features/high-wind-failsafe-trigger.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.