There is a persistent misconception about what the Pilot Monitoring role requires. It is frequently understood as the easier of the two positions — the pilot who is not flying, who manages the radios, who runs the checklists, who watches. This framing gets it precisely backwards. The PF's job, in one sense, is defined and bounded: fly the aircraft, execute the plan, manage the energy and the flight path. The PM's job is unbounded. It encompasses everything that the PF does not have the bandwidth to attend to — and on a complex sector, that is a great deal.
This behaviour is asking something specific of the PM: not merely to monitor and react, but to think ahead, to monitor effectively, and to provide timely warnings. Each of those three elements is distinct. Each can fail independently. And the failure of any one of them leaves the crew with a gap in its defensive capability that the PF has no way of knowing about.
Thinks Ahead — The PM as the Crew's Forward Observer
A duty day is a sequence of threats arriving at different distances. Some are visible at the briefing stage — the weather building along the route, the notam on the destination runway, the fuel calculation that leaves less margin than you would like. Others emerge in flight — the unexpected reroute, the deteriorating alternate, the traffic conflict that ATC has not yet resolved. The PM who is thinking ahead is not waiting for these threats to arrive. They are working out where the aircraft will be in ten minutes, what the environment will look like when it gets there, and what the crew needs to know before it does.
This is the anticipatory dimension of situational awareness — what Endsley's model calls Level 3, projection: the ability to predict future states based on current information. Most pilots develop Level 1 (perception) and Level 2 (comprehension) to a reasonable standard. Level 3 is where the PM earns their position. The weather radar that is set up, tilted, and interpreted not for the current position but for the position in fifteen minutes. The fuel that is mentally calculated against the revised routing before ATC finishes reading it out. The approach that is considered — not just loaded — before the top of descent.
The PM who is reacting to threats as they arrive is always one step behind the aircraft. Thinking ahead puts them a step in front of it.
Convective weather is one of the most consistently mismanaged threats in commercial aviation, and the PM's role in managing it illustrates this behaviour precisely. Thunderstorms are generally foreseeable — they appear on weather charts at the briefing stage, they develop on the radar during flight, and their avoidance strategies can be planned before they become urgent.
The PM who is thinking ahead has the radar set up correctly — tilt adjusted, gain set, returns being interpreted — well before the crew needs to deviate. They have considered the routing, identified the escape options, and formed a view about the developing picture. When the threat begins to materialise, they are ready to brief the PF on what the radar is showing and what the options are. The PM who notices the return at the same moment as the PF is not monitoring effectively. They are observing reactively — and at that point, the margin for managed avoidance has already narrowed.
Monitors Effectively — Active Not Passive
Monitoring and watching are not the same thing. Watching is passive — the eyes move across the instruments, the information arrives, the brain registers it. Monitoring is active — it involves a mental model of what the instruments should show, a continuous comparison between that model and what they actually show, and an immediate response when the two diverge. The PM who is watching may notice a deviation. The PM who is monitoring will notice it earlier, will have a view about its significance, and will act on it before it becomes a problem for the PF to manage.
Effective monitoring requires a structured scan. Not a random pass across the panel, but a deliberate sequence that covers the parameters that matter in the current phase of flight, in an order that ensures nothing critical is missed. It requires that the PM maintains this scan even when other demands — communications, checklists, ACARS, cabin calls — are competing for attention. And it requires that the PM recognises when their own monitoring has degraded — when workload has pushed the scan into the background — and actively restores it.
Research into automation monitoring has consistently found that vigilance degrades significantly during extended periods of normal operation. The PM who has been managing a high-workload communications exchange, running a non-standard checklist, or dealing with a cabin issue has had their monitoring scan interrupted. The aircraft has continued flying, apparently normally, and the temptation is to assume that nothing has changed.
The disciplined PM does not make that assumption. They re-establish the scan explicitly — checking the parameters they have not scanned, confirming the automation state, verifying the routing — before returning to other tasks. This is not excessive caution. It is the recognition that unmonitored flight is a period during which divergences can accumulate undetected.
Timely Warnings — The Word That Carries the Most Weight
Of the three elements in this behaviour, timely is the one that deserves the most scrutiny. A warning that arrives after the PF has already identified the threat is not a warning — it is confirmation of something already known. A warning that arrives too late for the PF to take effective action is not useful — it is commentary on what is about to go wrong. The value of a PM warning is entirely determined by when it arrives relative to when the PF needs it to act.
This has a practical implication that many pilots do not fully internalise: the PM must be willing to call a threat before they are certain it is a threat. Waiting for full confirmation — waiting until the weather return is unambiguously severe, the altitude deviation is clearly established, the traffic conflict is definitive — means waiting until the PF's options have narrowed. The call that matters is the early one: "Weather building on the left, watch the radar" said with two minutes of decision time remaining is worth ten times the same call made with thirty seconds.
A warning that arrives in time to act on is a tool. A warning that arrives too late is a report.
The PM who calls threats early needs a crew environment in which that is welcomed rather than challenged. A first officer who calls a potential altitude bust when they are not entirely certain, who flags a fuel concern before it is critical, who raises a weather deviation option before the captain has asked — that first officer is doing exactly what this behaviour requires. The captain who receives those calls with engagement rather than dismissal has created the conditions in which early warnings will continue to arrive. The captain who responds with irritation has ensured that the next call will come later, if it comes at all.