> 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/stratoware-miltech-simulations-bo105/aircraft-and-systems/cockpit-layout.md).

# Cockpit Layout

Description and location of all cockpit switches, gauges, instruments, and controls.

<figure><img src="https://2080447739-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FghproFq72NBcurEIBla8%2Fuploads%2Fw2xM9Cm2t4SBHebkUqAH%2Fwide_cockpit.png?alt=media&amp;token=a975be82-8f07-4889-b74e-5b88c172c55d" alt=""><figcaption></figcaption></figure>

1. **Overhead Console**: refer to [Overhead Panel](/stratoware-miltech-simulations-bo105/aircraft-and-systems/cockpit-layout/overhead-panel.md).
2. **OAT Indicator**: Features one pointer, which indicates   &#x20;on two scales with centigrade (°C) and Fahrenheit graduations (°F).&#x20;
3. **Power Control Levers**: Responsible for independent engine power control. 3 state levers: OFF, IDLE, and FLY. Refer to [Overhead Panel](/stratoware-miltech-simulations-bo105/aircraft-and-systems/cockpit-layout/overhead-panel.md) for more information.
4. **Standby Magnetic Compass**: Displays heading in degrees.
5. **Instrument Panel**: refer to [Instrument Panel](/stratoware-miltech-simulations-bo105/aircraft-and-systems/cockpit-layout/instrument-panel.md).
6. **Switch Panel**: refer to [Switch Panel](/stratoware-miltech-simulations-bo105/aircraft-and-systems/cockpit-layout/switch-panel.md).
7. **Center Console**: refer to [Center Console](/stratoware-miltech-simulations-bo105/aircraft-and-systems/cockpit-layout/center-console.md).
8. **Pilot Collective Lever**: Shared control used to adjust the pitch of all main rotor blades simultaneously, controlling vertical lift.
9. **Pilot Seat**
10. **Copilot Seat**

<figure><img src="https://2080447739-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FghproFq72NBcurEIBla8%2Fuploads%2FB89iiHgkFFpPzdTwH7Lx%2Fprimary_controls.png?alt=media&amp;token=057afd11-197b-4c4f-a826-1d8a1706912b" alt=""><figcaption></figcaption></figure>

11. **Pilot's Cyclic Stick**: Primary flight control used to command pitch and roll by tilting the rotor disc. Controls forward, aft, and lateral movement of the aircraft.
12. **Pilot's Tail Rotor/Directional Pedals**: Control the pitch of the tail rotor blades to manage yaw (nose direction) and counteract main rotor torque.
13. **Direct Vision Window**
14. **Map Pocket**

<figure><img src="https://2080447739-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FghproFq72NBcurEIBla8%2Fuploads%2Fdqh05nxd5DhvV0W8XOWJ%2Funderseat.png?alt=media&amp;token=86ab5838-a839-4fbc-abaa-6ebba972ae7c" alt=""><figcaption></figcaption></figure>

15. **Rotorbrake**: Used to decelerate and stop the main rotor following engine shutdown, reducing blade rotation time.


---

# 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/stratoware-miltech-simulations-bo105/aircraft-and-systems/cockpit-layout.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.
