> 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-mh60/product-information/included-sceneries.md).

# Included Sceneries

As usual in recent Miltech Simulations releases, we include **4 detailed mini-sceneries** with the aircraft, each tailored for mission-oriented operations:

**KLDR – San Diego Coast Guard Air Station (USA)**\
A busy USCG facility located along the San Diego waterfront, supporting maritime patrol, SAR, and border operations.

**LEPM - Peñón de Vélez de la Gomera Helipad (Spain)**\
A remote outpost on the Mediterranean coast, suited for Strait of Gibraltar patrols, anti-submarine warfare missions, and confined landing practice with the MH-60R.

**KCGK – Kodiak Coast Guard Air Station (USA)**\
One of the largest Coast Guard bases in the United States, situated in the rugged terrain of Kodiak Island, Alaska, and home to long-range SAR and patrol missions.

**YGAD – Garden Island Naval Base (Australia)**\
A key Royal Australian Navy installation near Perth, optimized for MH60R operations, including ASW, training, and fleet support.

All these locations feature helipads (for Ready to Fly start) and "Parking Spots" (for Cold and Dark Start).


---

# 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-mh60/product-information/included-sceneries.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.