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

> Shutdown — part 3: 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. Transponder — **Stby**

Set code and mode from the mission/clearance, then verify both. Code and mode are separate requirements.

> **Checks and evidence**
>
> **Expected response:** STBY
>
> **Verification:** Read back the actual code and mode; for explicit TA/RA or STBY select that named mode.

### 2. APU switch — **As needed**

Resolve the required APU state for this phase from the mission’s electrical/air plan, then use a validated APU switch procedure.

> **Checks and evidence**
>
> **Expected response:** As needed
>
> **Verification:** Verify selector and APU availability/outcome, not just EGT.

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