> 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/aircraft-and-systems/aircraft-systems/multi-function-displays-mfds/hover-mode-hvr.md).

# Hover Mode (HVR)

{% hint style="warning" %}
**Hover Mode is only available starting V1.4.0**
{% endhint %}

This page contains a special view of the Primary Flight Display specific for Hovers. To access the HVR Page, click on the PFD Button (Top left button) of any Multi Function Display in the MV22.

<figure><img src="https://2097992004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPEYB5ha9hkXpOBVaiED0%2Fuploads%2FpbDGqKRbrrnD03E0qqGS%2Fimage.png?alt=media&amp;token=ae3c313e-0dfb-4057-90e9-5d5526081f72" alt=""><figcaption><p>Hover Page</p></figcaption></figure>

1. **Nacelles Indicator:** Indicates the angle of nacelles in degrees. It also visualizes the “Conversion Corridor” <mark style="background-color:green;">(See Performance for more details)</mark>. Upper and lower limits based on airspeed are shown as two red indicators, safe area is in green.
2. **TO CARGO Display:** Will display only if external cargo has been selected. Displays distance and bearing to cargo.&#x20;
3. **Compass Rose**&#x20;
4. **Cargo Position Indicator:** Displays where is the cargo located with respect to aircraft, if external cargo has been selected.&#x20;
5. **Radio Altitude and Vertical Speed Indicator:** Limited to maximum altitude of 500ft and vertical speeds of +500/-500. Beware of VRS Conditions

{% hint style="danger" %}
Vertical speeds inferior to 1500 ft/min that may result in Vortex Ring State (VRS). Avoid the red line when flying at low speeds/high nacelle angles.&#x20;
{% endhint %}

6. **Interm Power:** Green = normal, Yellow = caution, Red = warning, Red Blinking = engine overstress

{% hint style="danger" %}
Engines cannot sustain full throttle for longer than 60 seconds. If Interm Power is blinking, reduce throttle to at least 98% for a few seconds to reduce stress on the engines.
{% endhint %}

7. **Horizontal Speed Indicator and Flight Path Vector Indicator:** This indicator will display the absolute value of the horizontal speed of the aircraft while in hover. The white rotating indicator displays the direction of flight of the aircraft (eg. direction of the speed vector).
8. **Hook Status Display:** Displays the current status of the hook and any loads attached to it. "HOOKED" indicates load has been successfully picked up by the aircraft,  "HOOK BROKE" indicates the sling load has broke due to overstress.
9. **Hook Indications Display:** Displays important information regarding status of the sling loads - such as hover timers, pull up indications, and speed indications.


---

# 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/aircraft-and-systems/aircraft-systems/multi-function-displays-mfds/hover-mode-hvr.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.
