> 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/aircraft-and-systems/missions/rescue-missions.md).

# Rescue Missions

{% hint style="warning" %}
**Crash detection must be OFF** for Missions to load correctly, as Crashes may interfere with our loading scripts. 
{% endhint %}

### **MISSION 1: ALASKA ROADSIDE RESCUE**

An infrastructure expansion project in a remote area of Alaska has resulted in an accident. A large-scale fire engulfed the equipment and vehicles. Fortunately, workers were able to extinguish the fires and suffered only minor injuries. Alaska State Troopers are on site, but the treacherous terrain makes traditional rescue efforts of those injured nearly impossible. A CH47D from Brayant Army Airfield has been dispatched to the scene.

Distance to Target: 75nm

Expected Duration: 75 minutes

<details>

<summary>MISSION INSTRUCTIONS</summary>

* **LAUNCH MISSION**
* **Takeoff** from Brayant Army Airfield, heading **towards waypoint WAPRU.** Use the Handheld GPS (EFB Config Tab) to enter the flight plan.
* Locate the accident zone. Find a good area to land
* **Load** the Injured Patients to your aircraft on the EFB - Load Tab.
* Return to Brayant Army Airfield for patient treatment.

</details>


---

# 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/aircraft-and-systems/missions/rescue-missions.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.