> 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-microsoft-c-17-globemaster-iii/the-aircraft/cockpit-displays/plan-position-indicator.md).
# Plan Position Indicator
{% hint style="warning" %}
Please note that starting on Version Number V1.1.15, aggressive performance optimizations have been made, including limiting pages on PFD and MFDs, and mirroring both copilot's FMCs. More information here: [NOTAMs](/miltech-simulations-microsoft-c-17-globemaster-iii/product-details/notams.md)
{% endhint %}
PPI Page
1. **Heading indicator**
2. **TAWS/WX/TCAS Indicator:** TAWS is controlled by the RDR button on the MCP. TCAS is by default always TA/RA
3. **Aircraft Position Indicator:** The position of traffic will be displayed in reference to the position of the Aircraft Indicator
4. **Range Lever:** As per selected on the MCP
5. **Navigation/Waypoint Information**
6. **Screen Brightness Selector:** Cycles through display OFF/Night (Low Brightness Mode) and Day (High Brightness Mode).
7. **Multi-Function Display Selector:** Cycles through the different pages available on the MFD.
---
# 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-microsoft-c-17-globemaster-iii/the-aircraft/cockpit-displays/plan-position-indicator.md?ask=&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.
