> 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-ch47d/product-guides/other-procedures/mission-procedures.md).

# Mission Procedures

{% hint style="warning" %}

* **Crash detection must be OFF** for Missions to load correctly, as Crashes may interfere with our loading scripts. 
* **Beware of sling load limitations** - must fly at maximum 120kts and avoid violent maneuvers when carrying external loads.
  {% endhint %}

### Accessing Missions

1. Launch a flight with the CH47D at any airport in the world. 
2. Turn on the EFB screen by pressing the **HOME** Button
3. Navigate to the **MISSION** page

<figure><img src="https://1335574643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU34X0omCjZJSDMQclhSX%2Fuploads%2FOS1aYgGyAYoU7nRXp0Eo%2Fimage.png?alt=media&amp;token=bd12bfc3-f84f-42ff-8066-752b9e6bc7e0" alt="" width="375"><figcaption><p>Mission Page</p></figcaption></figure>

4. Select any mission from the list.
5. Wait a few minutes for the mission to load completely. The aircraft will be automatically relocated to the start location and all required mission objects will be loaded.

### Included Missions

[Missions](/miltech-simulations-ch47d/aircraft-and-systems/missions.md) List


---

# 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-ch47d/product-guides/other-procedures/mission-procedures.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.