> 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-microsoft-c-17-globemaster-iii/the-aircraft/cargo-and-loadmaster.md).

# Cargo and Loadmaster

&#x20;Located on the Front of the cargo bay, to the right side of the cockpit stairs. The Loadmaster typically manages cargo operations. This station is equipped with controls and monitoring systems for the loading and unloading process, ensuring cargo is distributed properly and safely. It usually includes displays or instruments for weight distribution, cargo restraint systems, and communication tools to stay in contact with the flight crew and ground personnel. The Loadmaster ensures that cargo is properly secured, and balanced for the flight, and that it adheres to aircraft limitations for safe operation. Here you will find a laptop computer that can be used to load cargo and fuel into the aircraft.&#x20;

<figure><img src="https://1650965077-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQKfDyGFzEE2oA1hDuyJ%2Fuploads%2FWD1P5xp1jtWaqnaWc0xP%2Fimage.png?alt=media&amp;token=a44ab9ce-c25a-4007-819b-ef43708dd957" alt=""><figcaption><p>Loadmaster Station Panel</p></figcaption></figure>

1. **Loadmaster Lights:** Controls Cargo Bay flood lights, LM Panel lights, LM Desktop Lamp, etc. Some Lighting Knobs/switches may be INOP as they do not apply to simulation.
2. **Chute/Rails Control Switches:** INOP, not simulated.
3. **System Status Lights:** Display the status of Hyd 2 and Hyd 3 systems, as well as Electrical Power system. These are important for door and ramp operation, as the ramp and cargo door cannot operate without Hydraulic Pressure or Electrical Power,
4. **Cargo Door and Cargo Ramp Pushbuttons**
5. **Aerial Delivery System Panel:** INOP, not simulated
6. **Ramp Blowdown / Drogue Panel:** INOP, not simulated
7. **PA/Communications Panel**
8. **FED/Smoke Detection Panel:** INOP, not simulated
9. **Environment Panel:** Control Exhaust Fans and Cargo Bay Heater. Cargo Compt temperature selector and temperature displays INOP.
10. **Door Status Lights**

Additionally, the Loadmaster Station has access to the Electronic Flight Bag displayed as a laptop. The touchscreen provides an easy-to-use interface to interact with the aircraft attachments, doors and payloads. We have also added a little homage to our early days in Flight Simulation ;)&#x20;

For more information, read the EFB Section of this manual.&#x20;

<figure><img src="https://1650965077-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQKfDyGFzEE2oA1hDuyJ%2Fuploads%2FcjoQPoKCIzPanMBL4diq%2Fimage.png?alt=media&amp;token=ec2dab8d-42a0-49ea-8847-dcd3d111a487" alt=""><figcaption><p>Loadmaster EFB</p></figcaption></figure>


---

# 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-microsoft-c-17-globemaster-iii/the-aircraft/cargo-and-loadmaster.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.
