> 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/system-functions-syst.md).
# System Functions (SYST)
Most functions on the SYST page are not simulated, and therefore INOP (crossed with a green mark)
* **Blade Fold/Wing Stow (BFWS):** One of the unique features of the Osprey is its capability of folding the wings, propellers and stowing the aircraft in a reduced space. This is particularly important when operating to/from Vessels and Carriers. BFWS procedures are fully modeled in our rendition of the Osprey.
* **NOTE: Simulated Aircraft Geometry remains the same when the wings are folded or unfolded. Crash Detection must be Off for this feature to work well in tight spaces.**
Figure: SYST/BFWS Page
1. **FLIGHT READY:** Command to start the unfolding/unstowing process (when aircraft is Folded and Stowed OR Folded Horizontally)
2. **FULL STOW:** Command to start the Folding and Stowing process (when aircraft is FLIGHT READY)
3. **ROTOR LOCK:** Command to lock rotors. Cannot be activated if props are rotating.
4. **FOLD HORIZONTAL:** Command for horizontal blade folding without fully stowing the wings. (when aircraft is FLIGHT READY).
5. **Checklist:** Arrow marks items that have been completed automatically. See Normal Procedures on BFWS 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/multi-function-displays-mfds/system-functions-syst.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.
