> 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/primary-flight-data-pfd.md).
# Primary Flight Data (PFD)
This page contains all the basic aircraft instrumentation and information necessary to fly the MV-22B.
Figure: Primary Flight Data
1. **Nacelles Indicator:** Indicates the angle of nacelles in degrees. It also visualizes the “Conversion Corridor” (See Performance for more details). Upper and lower limits based on airspeed are shown as two red indicators, safe area is in green.
2. **Indicated Airspeed** (Knots)
3. **Altitude Indicator** (Feet)
4. **Vertical Speed Indicator** (Feet/min): A warning red line appears below 60 knots IAS.
{% 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.
{% endhint %}
5. **Radio Altimeter:** Activates at an altitude between 1-5000ft (min altitude can be set in the CDU)
6. **Artificial Horizon**
7. **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 %}
8. **Heading/Compass Indicator**
9. **VOR/Waypoint Information:** Bearing, distance, estimated time arrival.
10. **Autopilot Active Data**: (not visible on screenshot)
---
# 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/primary-flight-data-pfd.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.
