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

# Shutdown — part 1

> Shutdown — part 1: 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

Begin shutdown in the assigned parked condition. Set the parking brake and establish the required electrical supply before moving engine start levers to CUTOFF.

The checklist requires fuel pump switches OFF without a listed APU exception. Engine bleed ON is a switch-selection requirement, not an indication that a stopped engine supplies air. Account for the assigned APU and electrical/air configuration.

With Airside Services active, anti-collision OFF can initiate deboarding and cargo unloading.

## Secure

Select the secure procedure when required after shutdown. Its four checks are IRS OFF, emergency-exit lights OFF, window heat OFF and packs OFF. A battery-OFF or mandatory APU-OFF step is not included. Record the actual end condition; secure-checklist completion alone does not establish cold-and-dark.

### 1. Parking brake — **Set**

Set the parking brake using the configured brake procedure. Verify the brake is set.

> **Checks and evidence**
>
> **Expected response:** Set
>
> **Verification:** Observe the requested brake state, and for ground-handler control obtain the actual handler instruction.

### 2. Electrical power — **Set**

Use an approved electrical-panel subprocedure, confirming the intended source and bus configuration.

> **Checks and evidence**
>
> **Expected response:** Set
>
> **Verification:** Require the applicable switch, source and on-bus indications.

### 3. Engine start levers — **Cutoff**

Set both engine start levers to CUTOFF. The start levers control fuel admission; they are separate from the rotary engine start switches.

> **Checks and evidence**
>
> **Expected response:** CUTOFF
>
> **Verification:** Read back the lever positions and the phase-appropriate engine outcome.

### 4. Fasten belts — **Off**

Set the fasten-belts sign to OFF at the supplied shutdown step and confirm the sign/switch state.

> **Checks and evidence**
>
> **Expected response:** OFF
>
> **Verification:** Require a valid OFF state.

### 5. Anti-collision light — **Off**

Set the beacon/anti-collision light OFF at this shutdown step and verify the result.

> **Checks and evidence**
>
> **Expected response:** OFF
>
> **Verification:** Confirm OFF and preserve the shutdown context.

### 6. Fuel pump switches — **Off**

Establish the supplied shutdown response OFF for the fuel-pump switches, reading each current state before any toggle.

> **Checks and evidence**
>
> **Expected response:** OFF
>
> **Verification:** Confirm the required OFF position for each applicable pump using validated state decoding.

### 7. CAB/UTIL — **As needed**

Resolve and apply the required cabin/utility power selection.

> **Checks and evidence**
>
> **Expected response:** As needed
>
> **Verification:** Observe the actual CAB/UTIL switch state.

### 8. IFE/PASS SEAT — **As needed**

Resolve and apply the required in-flight-entertainment/passenger-seat power selection.

> **Checks and evidence**
>
> **Expected response:** As needed
>
> **Verification:** Observe the actual IFE/PASS SEAT switch state.

### 9. Wing anti-ice — **Off**

For an explicit OFF, establish OFF. For As needed, first resolve the mission’s icing decision using an approved policy; do not infer it from temperature alone.

> **Checks and evidence**
>
> **Expected response:** OFF
>
> **Verification:** Verify the selected switch state and the relevant valve/annunciator outcome under a the applicable decoder.

## Continue after this procedure

Continue to [Shutdown — part 2](https://www.narev.ai/docs/irl-gym/aircraft/procedures/shutdown-2.md). The checklist adds no condition between these parts; the next part’s individual step conditions still apply.


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