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

# Approach

> Approach: conditions, actions and checks for the Boeing 737-800.

Use this procedure to prepare for the selected approach. Confirm each required aircraft state before acknowledging the corresponding checklist item.

## General

Apply the ground proximity warning system (GPWS) flap inhibit only when a flaps-15 landing is required. The fixed landing-light condition is **At or above 10,000 ft**, as stated by the checklist. At transition level, apply the assigned altimeter setting.

After approach preparation, use exactly one landing procedure: ILS, IAN or VNAV. Establish the applicable landing-continuation and missed-approach instructions before proceeding.

### 1. If flaps 15 landing needed: Ground proximity flap — **Flap inhibit**

**Condition:** If flaps 15 landing needed.

If the planned landing requires flaps 15, select flap inhibit and verify the switch and guard states. A temporary flaps-15 setting during approach configuration does not establish this condition.

> **Checks and evidence**
>
> **When:** If flaps 15 landing needed.
>
> **Expected response:** Flap inhibit
>
> **Verification:** Require the intended inhibit/guard state and record why the conditional item applies.
>
> **Earlier source wording:** Apply flap inhibit only when the source condition “If flaps 15 landing needed” has been explicitly established.
>
> Use the operating instruction above where it corrects or clarifies this earlier wording.

### 2. At or above 10,000 ft: Fixed landing light — **On**

**Condition:** At or above 10,000 ft.

When the stated condition is satisfied, select the applicable landing lights ON. Verify the installed lights required by this item.

> **Checks and evidence**
>
> **When:** At or above 10,000 ft.
>
> **Expected response:** ON
>
> **Verification:** Confirm the intended fixed lights, not merely an aggregate or partially populated indication.

### 3. Passenger sign — **As needed**

Resolve the required seat-belt and no-smoking/chime selections from mission context and installed configuration.

> **Checks and evidence**
>
> **Expected response:** As needed
>
> **Verification:** Verify the actual requested signs/switch states.

### 4. At transition level: Altimeter — **Set**

**Condition:** At transition level.

At transition level, set the assigned local altimeter setting. Verify the pressure-reference mode and indicated setting.

> **Checks and evidence**
>
> **When:** At transition level.
>
> **Expected response:** Set
>
> **Verification:** Confirm standard/local mode and each required side/standby cross-check.

### 5. Update RNP — **As needed**

Check the required navigation performance (RNP) for the selected arrival or approach against the displayed navigation-performance information.

> **Checks and evidence**
>
> **Expected response:** As needed
>
> **Verification:** Require the applicable displayed RNP and navigation-performance evidence on the correct pages.
>
> **Earlier source wording:** Verify the approach/arrival RNP requirement using mission data and displayed navigation-performance information.
>
> Use the operating instruction above where it corrects or clarifies this earlier wording.

## Select the landing procedure

After approach preparation, choose the one procedure that matches the assigned approach:

| Assigned approach | Continue with |
| - | - |
| Instrument landing system (ILS) | [ILS landing](https://www.narev.ai/docs/irl-gym/aircraft/procedures/ils-landing-1.md) |
| Integrated approach navigation (IAN) | [IAN landing](https://www.narev.ai/docs/irl-gym/aircraft/procedures/ian-landing-1.md) |
| Vertical navigation (VNAV) | [VNAV landing](https://www.narev.ai/docs/irl-gym/aircraft/procedures/vnav-landing-1.md) |

Do not execute multiple landing branches for the same approach. If a go-around is initiated from an applicable landing branch, transfer to [Go-around](https://www.narev.ai/docs/irl-gym/aircraft/procedures/go-around.md).


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