> For the complete documentation index, see [llms.txt](https://docs.miltechsimulations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miltechsimulations.com/miltech-simulations-mv-22b-tiltrotor/product-guides/other-procedures/single-engine-operations-engine-failure.md).

# Single-Engine Operations (Engine Failure)

In the event of a Single-Engine Failure, the Osprey can maintain regular flight with degraded performance, via the gearbox driving both proprotors. This is fully simulated on this aircraft product, and it occurs automatically upon loss of one engine.

When flying with a single engine running, the pilot must never perform a VTOL Landing. Landing is exclusively restricted to STOL. Under single-engine conditions, it is recommended to keep a cruise speed of 170 Knots at an altitude of 16,000ft. Beware of overstressing the engine (keep engine indications in Green)

Follow STOL checklist, and adjust nacelle angle, speed and thrust as required.


---

# 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.miltechsimulations.com/miltech-simulations-mv-22b-tiltrotor/product-guides/other-procedures/single-engine-operations-engine-failure.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.