> ## Documentation Index
> Fetch the complete documentation index at: https://www.narev.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Cockpit interface operation

> Cockpit interface operation for the Boeing 737-800 simulator.

In procedure text, MCP means the aircraft Mode Control Panel. Tool instructions refer to Model Context Protocol. A capability status is a static implementation assessment; use live discovery/observations for current availability.

## Find a procedure

Use `search_docs` to find an aircraft procedure, airport, runway or chart. Read a result with `read_docs`, or follow a known documentation path directly. The [manual directory](https://www.narev.ai/docs/irl-gym/aircraft/manual) lists every procedure in reading order, with readable procedure names.

Use `list_checklist_categories` and `read_checklist` to select the active checklist section and obtain its execution and item IDs. Search the procedure name to find its detailed guidance. Reading documentation does not execute controls or mark progress.

For example, read the first engine-start procedure:

```json theme={null}
{"path": "irl-gym/aircraft/procedures/engine-start-1"}
```

## Controls, readings and operations

Call `list_groups` to discover cockpit group IDs. Call `list_readings` with an optional `group` to discover reading IDs. Use `read_reading` with `reading_id` for one indication, or `read_group` with `group` for related indications. `read_flight_deck_indications` summarizes flight-deck indications. `get_function_states` accepts an optional `group` and reports cockpit control states.

Controls are exposed through aircraft-specific `cockpit_*` tools. Each call accepts an `action`, plus `value` or `text` when required by that action. Use the tool's advertised action descriptions for valid positions, units, ranges, and optional press durations. Arguments are flat objects, without `path`, `query`, or `body` wrappers.

Action results contain `verified`, `before`, `after`, and `detail`. Verification means the specified control change was observed; it does not establish that a checklist requirement or flight maneuver succeeded. Read the relevant indications after acting. If a call's outcome is unclear, inspect the control state before retrying a toggle or held press.

Raw dataref search, reads, writes, and arbitrary simulator commands are not exposed by the pilot MCP. Use named cockpit controls and readings. Report missing controls or indications through `report_issue`.

## Engage both autopilot channels

A short press of the second CMD button changes channels: selecting CMD B with CMD A engaged disengages CMD A, and vice versa. A dual-channel approach requires the held press of the second button with APP armed.

Call `cockpit_mcp_and_autopilot` with `action: "cmd-b-hold"` when CMD A is already engaged, or `action: "cmd-a-hold"` when CMD B was engaged first. The default hold is three seconds; the optional `value` supplies seconds, up to ten. The source guidance records that two seconds did not engage the second channel.

Use the held press once, then check both `mcp-and-autopilot.cmd-a` and `mcp-and-autopilot.cmd-b`. The buttons toggle, so inspect the result before any further press. Follow [ILS autoland and rollout](https://www.narev.ai/docs/irl-gym/aircraft/autoflight/ils-autoland-and-rollout.md) for the required capture, armed modes and landing continuation. Two CMD lights alone do not verify the complete landing sequence.

## Execution discipline

Resolve the source item, its condition and assigned target before submitting an action. Read before toggling, and observe the result. Inspect unknown outcomes before retrying. Verify required aircraft outcomes independently of action verification. HOLD durations are bounded but release attempts are not proof of release after process/network failure. A lost observation does not release the agent from maintaining the assigned control or handover function. No general continuous-flight or landing policy is supplied by this interface.

Use pilot-visible evidence to assess the aircraft. Discover the current pilot tool schemas and action descriptions through `tools/list`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.