Choose the current flight phase
The normal document sequence is: Preflight → Before start → Pushback → Engine start → Before taxi → Takeoff → Climb and cruise → Descent → Approach → Selected landing procedure → After landing → Shutdown → Secure. In the original checklist, engine start occupies sections 16–18 and before taxi starts at section 19. Use Engine start — part 1 and Before taxi — part 1 to find the procedures. When recording progress, obtain the actual section and item identifiers from the live checklist. The phase sequence organizes procedures. It does not authorize movement, establish a clearance, define a landing-continuation procedure, or evaluate a condition. Go-around is selected when required; it is not the routine successor to completion of a landing checklist. Use only one landing branch. For an initialized in-flight or turnaround scenario, verify the actual initial condition before selecting the applicable phase. Do not execute an earlier ground procedure in flight merely to obtain a complete historical checklist.Conditions
The checklist does not evaluate conditions or activate itself automatically. Establish each condition before its dependent action. The source records express this ascondition_policy="not_evaluated" and automatic_activation=False.
N2 is engine core speed as a percentage of its reference speed. VR is the rotation speed; VSI is the vertical speed indicator; FAF is the final approach fix. AGL means above ground level.
No numerical stability tolerance, observation interval, timeout or abnormal-start limit is supplied by the engine-start amendment. Obtain applicable values from the assigned supplement; do not derive them from the 25% and 56% event thresholds.
Moving to the next section does not satisfy that section’s conditions. Engine-start part 1 transitions to part 2; part 2 transitions to part 3. Part 3 has no explicit source transition. Before-taxi selection is a phase decision after engine-start completion and applicable readiness verification.
Monitor conditions as they occur
Retain document and item order in procedure records. Within an ordered action group, perform the stated sequence. Monitor time- and state-dependent events while other work proceeds. The climb/cruise source lists the 10,000-ft group before the transition-altitude group. Where the assigned transition altitude occurs earlier, use the authorized event schedule; do not delay transition-altitude monitoring until 10,000 ft. Retain the original item identities and recorded source order.Record progress and completion
Create a separate phase instance for each approach, go-around or repeated procedure. Retain the active checklist revision, section ID, item ID, source requirement, observations, decisions, action/operation reference and verification outcome. Do not reuse a previous approach’s completion evidence. Local record states arepending, waiting_for_gate, needs_input, blocked, acting, verifying, verified, failed and excluded_by_explicit_scenario_rule. These are local record terms, not server operation status values. Source MANUAL evaluation remains unchanged.
A condition that is temporarily false requires waiting, not automatic exclusion. An inapplicable branch or explicitly excluded scenario item requires a documented decision. An unknown condition remains unresolved. Notes retain NOT_APPLICABLE evaluation without being counted as physically verified checks.
Before closing a section, account for every item. Enter the next section only when its prerequisites apply. If a required indication is absent, report the item and retain the active control or handover function. Do not manufacture completion by issuing a command, resetting an annunciator, substituting an unrelated observation, or silently skipping the item.