> 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/aircraft-and-systems/aircraft-systems/electrical-system.md).

# Electrical System

The electrical system of the MH60 is designed to provide reliable power to all essential aircraft systems, including avionics, flight controls, sensors, and mission equipment. It consists of two **main AC generators**, each driven by one of the aircraft’s engines, and a third **APU generator** that provides power during ground operations or engine start.

Each generator feeds into a **primary power bus**, which supplies power to critical systems. These buses are connected through power distribution relays and circuit breakers to the avionics and systems. Circuit breakers are not modeled in MSFS.

A **battery** provides power to essential flight instruments during startup, and in case of generator failure. A ground power unit can be connected for startup as well.

The electrical system is managed from the Electrical Panel, located on the overhead panel. More information: [Overhead Panel](/miltech-simulations-mh60/aircraft-and-systems/overview-cockpit/overhead-panel.md)


---

# 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/aircraft-and-systems/aircraft-systems/electrical-system.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.