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

# Climb and cruise

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

Use this procedure when its prerequisites apply. Confirm each required aircraft state before acknowledging the corresponding checklist item.

## General

Monitor the 10,000-ft, transition-altitude and pre-top-of-descent conditions separately. Use the assigned event schedule while retaining checklist item identity and document order. Do not defer an earlier transition-altitude event until the later 10,000-ft event.

Verify STANDARD mode, its pressure setting and the required independent altimeter agreement. Before top of descent, make the required arrival-route modification and verify RNP for the arrival.

Maintain the assigned continuous flight, navigation and fuel monitoring throughout climb and cruise.

### 1. At or above 10,000 ft: Landing lights — **Off**

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

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

> **Checks and evidence**
>
> **When:** At or above 10,000 ft.
>
> **Expected response:** OFF
>
> **Verification:** Verify the required lights are off using the correct reading shape and variant.

### 2. At or above 10,000 ft: Passenger sign — **As needed**

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

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

> **Checks and evidence**
>
> **When:** At or above 10,000 ft.
>
> **Expected response:** As needed
>
> **Verification:** Verify the actual requested signs/switch states.

### 3. At transition altitude: Altimeter — **Set standard**

**Condition:** At transition altitude.

At transition altitude, set STANDARD. Verify the pressure-reference mode and indicated setting.

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

### 4. At transition altitude: Altimeter crosscheck — **Verify**

**Condition:** At transition altitude.

Perform an independent altimeter comparison with assigned tolerances.

> **Checks and evidence**
>
> **When:** At transition altitude.
>
> **Expected response:** Verify
>
> **Verification:** Compare the applicable captain/FO/standby values and reference modes.

### 5. Before top of descent: MOD route for arrival — **As needed**

**Condition:** Before top of descent.

Prepare any required arrival-route modification from the approved arrival plan, review it on the CDU and execute only the intended change.

> **Checks and evidence**
>
> **When:** Before top of descent.
>
> **Expected response:** As needed
>
> **Verification:** Confirm the intended route/arrival fields and absence of unintended modifications.

### 6. Before top of descent: RNP for arrival — **Verify**

**Condition:** Before top of descent.

Verify the approach/arrival RNP requirement using mission data and displayed navigation-performance information.

> **Checks and evidence**
>
> **When:** Before top of descent.
>
> **Expected response:** Verify
>
> **Verification:** Require the applicable displayed RNP and navigation-performance evidence on the correct pages.

## Continue after this procedure

No explicit source transition is declared. Select the next applicable procedure after the required completion and entry conditions are established.


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