> For the complete documentation index, see [llms.txt](https://docs.flightsim-studio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flightsim-studio.com/tecnam-p2006t-analog/special-features/key-bindings.md).

# Key Bindings

### Key Bindings <a href="#key-bindings" id="key-bindings"></a>

The aircraft uses default MSFS key bindings wherever possible. All others need to be linked to LVARs. They are present from v1.0.3 onwards.

| Description             | LVAR                                         | Range                |
| ----------------------- | -------------------------------------------- | -------------------- |
| Carb heat lever left    | FSS\_P2006T\_BINDING\_CARB\_HEAT\_LEVER\_1   | 0-1                  |
| Carb heat lever right   | FSS\_P2006T\_BINDING\_CARB\_HEAT\_LEVER\_2   | 0-1                  |
| Engine choke left       | FSS\_P2006T\_BINDING\_ENGINE\_CHOKE\_1       | 0=off 1=on           |
| Engine choke right      | FSS\_P2006T\_BINDING\_ENGINE\_CHOKE\_2       | 0=off 1=on           |
| CWS yoke button         | FSS\_P2006T\_BINDING\_YOKE\_CWS              | 0=released 1=pressed |
| Backup battery cover    | FSS\_P2006T\_BINDING\_BACKUP\_BATTERY\_COVER | 0=closed 1=lifted    |
| Master battery switch   | FSS\_P2006T\_BINDING\_MASTER\_BATTERY        | 0=off 1=on           |
| Pitot heat switch       | FSS\_P2006T\_BINDING\_PITOT\_HEAT            | 0=off 1=on           |
| Autopilot master switch | FSS\_P2006T\_BINDING\_AP\_MASTER\_SWITCH     | 0=off 1=on           |
| Avionics LH switch      | FSS\_P2006T\_BINDING\_AVIONICS\_LH\_SWITCH   | 0=off 1=on           |
| Avionics RH switch      | FSS\_P2006T\_BINDING\_AVIONICS\_RH\_SWITCH   | 0=off 1=on           |
| Crossbus LH switch      | FSS\_P2006T\_BINDING\_CROSSBUS\_LH\_SWITCH   | 0=off 1=on           |
| Crossbus RH switch      | FSS\_P2006T\_BINDING\_CROSSBUS\_RH\_SWITCH   | 0=off 1=on           |
| Starter LH button       | FSS\_P2006T\_BINDING\_STARTER\_LH\_BUTTON    | 0=off 1=on           |
| Starter RH button       | FSS\_P2006T\_BINDING\_STARTER\_RH\_BUTTON    | 0=off 1=on           |
| Toe brake left          | <p>FSS\_P2006T\_BINDING\_BRAKE\_LEFT<br></p> | 0-1                  |
| Toe brake right         | FSS\_P2006T\_BINDING\_BRAKE\_RIGHT           | 0-1                  |

**Axis & Ohs Scripts**

We provide scripts to assign all our LVARs directly to buttons without having to know RPN. You can download them here:

{% file src="/files/Ro0wN1ULyVyjricVMisz" %}
(right click -> Save as)
{% endfile %}

Import into A\&O via *Scripting -> Import Scripts* (only works if the simulator is not running).

The carb heat axes have to be configured manually. Just create an axis configuration and set the LVAR as variable. The value range must then be defined from 0 (min) to 1 (max).

![](https://cdn.document360.io/417c2d4d-fdb8-4d4d-b11d-011fe445d776/Images/Documentation/image-1686566582538.png)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flightsim-studio.com/tecnam-p2006t-analog/special-features/key-bindings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
