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

# General information

> How to use the Boeing 737-800 simulator checklist and verify each step.

This manual explains how to operate the Boeing 737-800 in the X-Plane 12 simulator and verify each checklist step.

## Find the guidance you need

The [flight manual directory](https://www.narev.ai/docs/irl-gym/aircraft/manual) groups the instructions by flight phase and reference topic. Start with your current phase, then open its checklist. For the arrival scenario, use [Land at Canberra from 25 NM final](https://www.narev.ai/docs/irl-gym/aircraft/examples/canberra-landing.md).

The checklist has 38 stages, containing 234 checks and three notes. Each item includes instructions and the evidence needed to verify completion.

## Simulator scope

These instructions apply to the Boeing 737-800 simulator. Check the active scenario and aircraft configuration before starting a procedure.

This is an independently prepared simulator manual, not a Boeing-issued or approved publication.

## Which instructions govern the procedure

Follow the checklist’s required settings, sequence and verification steps. Aircraft-system descriptions explain those steps; they do not change the requirements.

The [cockpit interface guide](https://www.narev.ai/docs/irl-gym/aircraft/manual/cockpit-interface.md) explains how to find the available controls and readings. Availability of an action does not authorize its use. A fire-extinguisher, alternate-flap or manual-gear action is not a normal-procedure step unless the applicable procedure requires it.

Operating conventions in this chapter, [Cockpit Interface Operation](https://www.narev.ai/docs/irl-gym/aircraft/manual/cockpit-interface.md), and [Procedure Sequence and Completion](https://www.narev.ai/docs/irl-gym/aircraft/manual/procedure-sequence.md) govern agent execution and records. They do not add aircraft checklist entries. The terms **approved**, **authorized** and **assigned** refer to the simulator operator's mission instructions and configured operating supplements, not manufacturer or regulatory approval.

## How to read a procedure

Each checklist item states what to do and what to observe afterward. Open its **Checks and evidence** section for conditions and required observations. Record what you observed before marking the item complete.

**Set / select / move:** Establish the required state and verify the result. Do not move a control already in the required state unless the procedure calls for a transition, such as OFF, then NAV.

**Verify / check:** Observe the specified indication or condition. Do not substitute a state-changing command for an observation. A verification item does not authorize manipulating the system to obtain a favorable indication.

**Announce:** Transmit the required callout through the assigned crew or ground communication channel. Recording text in a local log does not, by itself, constitute transmission.

**As needed / as directed / as scheduled:** Obtain the applicable mission decision, target or schedule before changing the aircraft configuration. Do not assume a standard value that is absent from the procedure.

**Note:** Retain and acknowledge the instruction or source note. A note is not a physical check and does not authorize a cockpit action.

Control and indication references are lookup references. They may identify alternatives or supporting indications. They are not a list of commands to execute in sequence.

## Operating limits

Establish the loaded aircraft identity, active configuration, applicable procedure, required mission data and usable communication/control channels before beginning a phase. Use only resolved public identifiers and the applicable action schemas.

An operation is complete only when its result is known. A checklist item is complete only when its required condition has been verified. Operation completion alone does not satisfy an aircraft-state check.

Treat unavailable, invalid, stale, hidden or undecoded information as **unknown**. Unknown is not OFF, zero, extinguished, safe or complete. An authorized exclusion must remain an exclusion; do not report it as a verified check.

Do not enter an unsupported phase. If a required observation or instruction becomes unavailable during an active phase, retain aircraft control through the assigned control or handover procedure and report the affected item. Stopping checklist progression does not mean releasing control of a moving aircraft.

Apply only the procedures supplied for the active situation. Do not construct omitted panel flows, landing continuation or non-normal procedures from an action catalog or general memory.


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