Single-Pilot CRM: The Briefing That Matters Happens Before Engine Start

For most of my career, Crew Resource Management was taught as a two-crew discipline: captain and first officer, challenge and response, the sterile cockpit, the callout that catches a wrong selection before it becomes an incident. Then single-pilot operations grew from a niche into a significant part of the industry — and with them came a quiet assumption that CRM somehow does not apply when there is nobody sitting to your right.

It does apply. It simply looks different.

The crew is larger than the cockpit

In single-pilot operations the crew is distributed. It includes the ground handler who knows the aircraft is heavier than the load sheet suggests, the engineer who mentions an intermittent fault, the dispatcher watching a front build on the weather radar, the controller who offers a shortcut. None of them sit in the flight deck. All of them can prevent an error — if they are given the chance.

The problem is that none of them will volunteer it. In a two-crew environment the second pilot has both the duty and the proximity to speak. In single-pilot operations the person who could stop the chain sits outside the aircraft and outside the authority gradient. Making that person useful is a CRM task, and it begins long before the flight.

Brief the people, not just the aircraft

Most single-pilot briefings are technical: fuel, performance, alternates, threats. All necessary. What is often missing is the human half — who is doing what, who is allowed to interrupt, and how.

Three questions turn a pre-flight briefing into a CRM briefing:

1. What is the riskiest part of this flight, in your view? Ask the handler, the engineer, the person who has flown the route twice this week. Their answer is not a decision; it is data you did not have.
2. If you see something that looks wrong, what will you do? Say the answer out loud — tell me, even if I look busy — and make it specific to the situation: the loading, the fuel, the weather, the paperwork.
3. What should not happen without checking with me? Boundaries matter in both directions. A handler who understands the limit is a resource; one who guesses is a risk.

That takes four minutes. Four minutes that change the quality of every interaction that follows.

Authority gradient with nobody to challenge you

A single pilot with a strong personality and thirty years of experience is a formidable operator and a poor safety system. Nothing in the cockpit challenges the decision. The data does not argue. The checklist does not notice that you skipped an item because you have done it a thousand times.

The countermeasure must be deliberate: build the challenge from outside. Some operators require a second opinion before high-risk departures. Some crews make a phone call before a marginal decision. The method matters less than the habit of exposing a decision to another mind before committing to it.

The most dangerous phrase in single-pilot operations is not "watch this". It is "I have done this hundreds of times".

Fatigue is the crew member nobody briefs

Single-pilot flying compresses rest. There is no pilot monitoring to notice the long pause, the repeated read, the slowed checklist flow. Fatigue degrades exactly the faculties you need in order to notice that you are fatigued.

Practical countermeasures:

• Treat the duty period as a resource with a hard limit, not a target.
• Write the decision thresholds down before the flight, while you are fresh: fuel minima, crosswind limits, the point at which you divert rather than continue.
• Keep a personal no-go list that does not require judgement in the moment.

The discipline of exposure

Experience is a poor substitute for a second perspective. When a decision feels obvious, that is usually the moment to expose it to somebody who was not in the room when it formed.

What good looks like

The best single-pilot operators I have worked with share a pattern. They arrive early and talk to people. They ask questions that invite contradiction. They say thank you when somebody brings them a problem. They write down their minima and keep them when they are tired. They treat CRM not as a course they attended but as a way of working with everyone around the aircraft.

That is the standard. Not the absence of a co-pilot — the presence of a crew.