> 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/standby-instruments.md). # Standby Instruments The Standby Flight Instruments provide essential flight and system information when the normal CDU and/or the MFDs become inoperative.

1. **Standby System Indicators:** Include nacelle position, fuel quantity, Nr (Proprotor rpm), Np (Power turbine rpm), Engine Torque, Flaps Indication, etc. 2. **Data Selector Switch:** Switches the data feed from the Flight Computer 1, 2 or BIT. INOP. 3. **Brightness Knob** 4. **Standby Primary Flight Display:** Includes altitude, airspeed, vertical speed, TCAS, artificial horizon, etc. 5. **BARO Adjust Switches:** Increase or Decrease barometric pressure to adjust altimeters. Adjusting the BARO through this switch will also adjust the altimeters on the PFD. BARO Pressure can also be inputted through the CDU. See CDU Menu 2 for more information --- # 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/standby-instruments.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.