The Procedure You Do
Every Flight Isn't the Test

Some procedures do not require conscious retrieval. The after-start flow, the pre-departure checks, the approach briefing structure — these are procedures performed so frequently that they have become part of the furniture of flight. Their execution is largely habitual, their sequence internalised, their content recalled without conscious retrieval. That automaticity is valuable. It frees cognitive resource for the things that actually require it.

But applies relevant procedural knowledge is not describing that. It is not assessing the pilot's ability to execute the routines. It is assessing something considerably more demanding: the ability to identify which procedure applies to a situation that does not arise every flight, to locate it accurately within a system of manuals that spans multiple volumes, to understand it well enough to apply it correctly under conditions that may be the first time this particular configuration has been encountered on the line, and to do all of that with appropriate crew involvement and the honesty to acknowledge the limits of individual recall.

The word that carries the weight in this behaviour is not procedural. It is relevant.

The Two Categories of Procedure

Every operation has two categories of procedure, and they make very different demands on the crew. The first is the high-frequency category — the procedures done on every flight, or nearly so. Ground handling flows, standard departure profiles, noise abatement procedures for the routes flown regularly, approach categories, standard callouts. These are maintained by repetition. The risk in this category is not ignorance but complacency — the assumption of correctness that comes with familiarity and occasionally conceals a deviation that has crept in over time.

The second category is different in almost every respect. De-icing in a season when it is rarely required. Crosswind technique at the limits of the demonstrated crosswind component, encountered once in a season if at all. Ground air cart connection on a stand with no fixed services. Contaminated runway performance on an operation that almost never sees contaminated runways. These are the procedures that live in the manual rather than in memory, that require active retrieval rather than habitual execution, and that carry the specific risk of false confidence — the feeling of knowing a procedure that is actually only partially remembered.

It is in this second category that the competency is actually being tested. A pilot who executes every high-frequency procedure flawlessly but proceeds from uncertain memory on an infrequent one — rather than checking, asking, or deferring — is not demonstrating procedural knowledge. They are demonstrating its limits while concealing them.

Knowing Where to Look

One of the most underrated procedural skills is manual navigation. Modern operations involve multiple documents — the Flight Crew Operating Manual, the Flight Crew Training Manual, the Operations Manual, company supplements, route-specific guidance, performance documentation. Knowing which of these contains the procedure for a given situation, and being able to locate it efficiently under the time pressure of an active operation, is a practical skill that is rarely discussed and never assessed in isolation — but that makes or breaks the ability to apply relevant procedural knowledge in the situations where it matters most.

The pilot who can navigate to any infrequent procedure in thirty seconds is in a materially different position from the one who knows it exists somewhere in the documentation but cannot locate it reliably under pressure. The difference is not seniority. It is familiarity with the structure of the documentation — built through deliberate engagement with the manuals rather than passive exposure during training events.

Humility as a Procedural Skill

There is a cultural pressure in aviation toward the appearance of knowing. Uncertainty can feel like a liability in an environment where competence is the primary currency of professional credibility. That pressure operates most powerfully in exactly the situations where acknowledging uncertainty is most important — the infrequent procedure, the configuration not seen for months, the crosswind technique that has always been within comfortable limits until today.

The pilot who says, before connecting the ground air cart on an unfamiliar stand, "let me check the procedure" is not demonstrating inadequacy. They are demonstrating a more sophisticated form of competence than the one who proceeds from partial memory and happens to get it right. The outcome in a given instance is not the measure of the behaviour. The behaviour is the measure.

Accepting that not everything is remembered accurately — and acting on that acceptance before it becomes consequential — is one of the specific expressions of humility that procedural knowledge demands. It is also one of the most consistently undervalued. Pilots who never check because they never need to are not necessarily more capable. They are often simply more fortunate, or operating in a sufficiently narrow envelope that the situations requiring infrequent procedures have not arisen recently enough to reveal the gap.

The Crew as a Procedural Resource

Applying relevant procedural knowledge is not a solo activity, and treating it as one is a significant error. The crew is a resource in exactly these situations — the ones where individual memory is uncertain, where the procedure is infrequent, where the manual needs to be retrieved and read against time pressure. The colleague who flew the route last month may have the crosswind technique fresher in their recall. The First Officer who recently completed type conversion may have the APU start sequence more accurately retained than the Captain who qualified three years ago. The handling agent who deals with the ground air cart connection on every turnaround has a currency the crew almost certainly does not.

Delegating the manual search to the crew member with their hands free, inviting input from the colleague with more recent exposure, deferring to the ground engineer on a question of ground servicing procedure — these are not admissions of inadequacy. They are the correct use of available resource. And recognising which resource to use in which situation is itself an expression of the competency.

The crew member who insists on individual authority over a procedure they are uncertain about, when a better-informed resource is available, is not protecting the operation. They are exposing it.

Briefing as Procedural Activation

One of the most effective mechanisms for applying relevant procedural knowledge correctly is also one of the most commonly abbreviated: the briefing of infrequent procedures before they are required. A crosswind that is going to be at the limit of demonstrated performance is known before the approach. A de-icing requirement is identified during dispatch. An APU that is unserviceable, requiring the ground air cart, is notified in the technical log. In each of these cases the information arrives before the procedure is required — which means there is time to retrieve it, read it, discuss it, and agree the execution before the workload is active.

The crew that uses that time is applying relevant procedural knowledge in the most effective way available to them. The crew that notes the requirement and proceeds to the gate without reference to the procedure is deferring the retrieval to a point where workload, time pressure, and the operational context make it harder to do well. The brief is not a formality here. It is the mechanism by which procedural knowledge that was passive becomes active — checked, confirmed, and shared between the crew before it is needed.