> 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/introduction.md).

# Introduction

Thank you for purchasing the Miltech Simulations MH60, in partnership with Blackbird Simulations.

At Miltech Simulations, we remain committed to pushing the boundaries of what’s possible in Microsoft Flight Simulator. Following the success of our CH47D and other military platforms, we now present our most advanced rotary-wing project to date: the legendary MH60, brought to life after over a year of intensive development.

The Miltech Simulations MH60 is a multi-role, maritime helicopter capable of performing a wide variety of missions, from anti-submarine warfare and search-and-rescue, to medevac and special operations support. With advanced mission systems, modular configurations, and a highly detailed 3D model, the MH60 delivers a new level of features depth and realism to the sim.

This product is the result of a close collaboration with Blackbird Simulations, a renowned name in the flight simulation industry. Combining Blackbird’s world-class visual modeling with our own expertise in systems programming and mission integration, the MH60 sets a new standard for helicopter simulation.

We are proud to share this ambitious project with the community, and we hope it becomes a core part of your sim experience.

Miltech Simulations & Blackbird Simulations.


---

# 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/introduction.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.
