Definition
Pilot Flying (PF) and Pilot Monitoring (PM) define the role split that drives every multi-crew operation. The PF manipulates the flight controls and makes the active flying decisions; the PM handles radios, checklists, system management, performance calculations, and — critically — independent verification of the PF's actions. The two roles are explicitly assigned for each flight or each phase, often swapped on rotation so both pilots maintain currency in both roles.
The PF/PM terminology replaced the older "Pilot Not Flying" (PNF) language in the late 2000s for a deliberate reason. "Not flying" framed the supporting pilot as passive, which subtly encouraged passive behavior — exactly the failure mode that contributed to controlled-flight-into-terrain and other monitoring-failure accidents. "Pilot Monitoring" reframes the role as an active, accountable function: the PM is supposed to call deviations, challenge questionable decisions, and intervene when standards are breached. This is the operational expression of Crew Resource Management (CRM) and threat-and-error management (TEM) doctrine.
PF/PM is distinct from Pilot in Command (PIC). PIC is the legal authority for the flight, regardless of who is currently flying. A captain can be the PIC and the PM simultaneously while a first officer flies as PF; the captain's command authority is unchanged. Logging conventions differ — under EASA, PIC, PICUS, P1, P2, and PF time are tracked as separate columns where applicable — and getting these conventions right is essential to a logbook that withstands airline scrutiny.
Why It Matters for Flight Schools
PF/PM discipline is one of the strongest predictors of safe multi-crew operations. The accident record is full of cases where a competent PF made a mistake the PM saw coming, but didn't call it out — or made a mistake the PM didn't see because they were buried in non-monitoring tasks. Operators with strong PF/PM standardization define exactly which callouts are required, when checklists run, and what "sterile cockpit" means below 10,000 feet. Operators without that standardization rely on each crew to invent it, with predictable variance.
For training organizations transitioning students from single-pilot to multi-crew operations, PF/PM is the heart of the Multi-Crew Cooperation (MCC) and Airline Pilot Standard MCC (APS-MCC) curricula. Students arriving from single-pilot training have to learn an entirely new operational mode — and instructors have to assess monitoring discipline as rigorously as flying skill, which is harder because monitoring failures are often invisible until something else goes wrong.
How Aviatize Handles This
Aviatize's training management module separates PF and PM tracking for multi-crew lessons, supporting the MCC and APS-MCC standards where each student must complete a defined number of hours in each role. The lesson plan and post-lesson debrief capture not just airborne performance but PM-specific competencies — checklist discipline, deviation calls, threat anticipation — so monitoring weakness is visible to instructors rather than hidden behind "the flight went fine."
For logbook integrity, Aviatize supports the parallel logging of PIC, PICUS, P1, P2, PF, and PM time in the columns each licensing authority requires. A cadet completing an integrated ATPL in an EASA jurisdiction produces a logbook that maps cleanly to the airline employer's expectations, without the after-the-fact reconstruction that broken record-keeping forces.