> 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-transition.md). # During Transition The following should be monitored when the vehicle transitions from vertical flight to horizontal flight. After reaching transition altitude, the vehicle will commence the transition to fixed-wing flight. The pusher motor will engage 5 meters below the target altitude (switching from quadcopter to fixed-wing). It will transition in the direction planned for takeoff, but wind can affect the direction, especially if the vehicle is not positioned with its nose directly into the wind. The vehicle will engage high thrust using its pusher motor until it reaches the target airspeed. After this period, it should navigate towards the hold pattern or first waypoint. **If any malfunction occurs with the airspeed sensor, the vehicle will abort the transition after a timeout of 25 seconds. During this period, the vehicle can cover a long distance at the transition altitude. LAND mode must be engaged before the vehicle is at risk of colliding with any obstacles.** ### **No Forward Motion** Operator Action: **LAND** If the vehicle is not moving forward or is drifting with the wind and does not seem to transition towards fixed-wing, there is likely a problem with the pusher motor or propeller. The operator should review the propeller configuration as described in the manual. ### **Flying Backward** Operator Action: **LAND** If the vehicle starts flying backward with increasing speed, the pusher propeller is likely mounted in the wrong direction. The transition should be aborted, and the pusher motor should be inspected. --- # 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-transition.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.