SOPs, checklists and the dispatch boundary

Why do a procedure and a checklist serve different purposes?

Distinguish the procedure, flow, checklist and monitoring roles, including how an interruption can leave an action unverified.

Understand the mechanism

A standard operating procedure defines who does what, when, with which call-outs and monitoring. A checklist provides a deliberate verification or action sequence under the operator’s system. Reading a checklist does not physically place a switch in the required position. Conversely, completing a familiar flow does not prove that the critical items were correctly achieved. The two layers address different failure modes: task execution and independent detection of omissions or errors.

Normal, abnormal and emergency procedures have different triggers and time priorities. Some aircraft procedures specify immediate actions before reference to the checklist; others do not. A generic course cannot select those actions for every type. The training objective is to recognise the trigger, preserve aircraft control, allocate duties and use the applicable aircraft procedure. An improvised mixture of two aircraft checklists can lose the assumptions that made either one valid.

Apply the evidence

Interruption creates a state problem: an item may be unstarted, completed, checked or uncertain. A deliberate resumption method prevents uncertainty being converted into a silent assumption. Cross-checking should compare the actual indication or configuration with the required condition. A challenge-and-response exchange becomes weak if both pilots answer from memory while looking elsewhere. Automation does not remove the need to establish which aircraft state actually exists.

Worked case · synthetic training operation

During a synthetic departure preparation, a radio call interrupts a checklist after one pilot moves a control but before the response is confirmed. On resumption the crew use the operator’s interruption/restart method and verify the actual indication. They do not infer completion from the remembered hand movement. The model allows “action performed”, “verified” and “interrupted” to vary independently: only the verified state closes the item. This explains why an additional confirmation can prevent an error even when nobody has forgotten the intended setting.

Why does an MEL entry contain more than a repair interval?

Assess an MEL dispatch case using its conditions, required procedures, repair interval and actual equipment state together.

Understand the mechanism

The master minimum equipment list is the type-level basis from which an operator’s minimum equipment list is developed and approved as applicable. An MEL defines dispatch conditions with specified inoperative equipment. It is not a general declaration that a broken system is harmless. Required conditions may include remaining operative equipment, operational limitations, maintenance actions, crew procedures and placards. The exact item and its applicability must match the actual defect.

A repair interval controls how long a permitted defect may remain deferred under its conditions. It does not erase the conditions or create a universal right to depart. Some defects are outside the MEL’s relief. Multiple individually permitted defects may interact, especially where they remove shared redundancy or impose incompatible procedures. A previous flight with the defect does not establish that the next route, weather or aircraft configuration satisfies the same conditions.

Apply the evidence

The MEL is principally a dispatch tool. A failure occurring after departure is handled through the relevant in-flight procedures and decision process, rather than treating a dispatch repair interval as an in-flight instruction. A configuration deviation list concerns specified external configuration deviations and their conditions; it is not interchangeable with an equipment-defect entry. Keep defect identity, dispatch permission, actual procedures and continuing airworthiness actions distinct.

Worked case · synthetic training operation

A fictional MEL permits one navigation receiver inoperative only when the other receiver is operative and the route does not require the unavailable capability. Maintenance completes the required action, but the planned arrival now requires that capability. The defect remains technically deferred; dispatch on this route is not established. Changing to a supported route may resolve the operational condition. The decision model changes the remaining receiver and route requirement separately, showing why a valid date in the technical log cannot replace an equipment-capability check.

Can you explain and apply the mechanism?

Four original questions. Work from the stated facts, then compare your reasoning with the explanation.