"Do not pair" (DNP) lists — informal or semi-formal mechanisms by which flight crew members flag interpersonal incompatibilities with specific colleagues — represent a largely opaque but operationally significant layer of airline crew scheduling culture. At major carriers, these lists typically exist within crew scheduling software or as notations accessible to base managers and crew coordinators, and they are generally triggered by a crewmember formally requesting not to be paired with a specific individual, sometimes following a reported conflict, a safety concern, or a hostile cockpit environment. The threshold for honoring such a request varies widely by carrier, union contract language, and the severity of the underlying complaint. A single DNP request between two pilots is common and routinely accommodated through the normal trip trade and reassignment process with minimal administrative scrutiny.
The consequences escalate substantially when a single pilot accumulates DNP requests from multiple crewmembers. At that point, the pattern transitions from a scheduling inconvenience to a potential CRM (Crew Resource Management) and airmanship concern that warrants management attention. Chief pilots, base managers, or director-of-operations equivalents at Part 121 carriers are typically the first to identify the pattern, often because crew scheduling surfaces it as a logistical problem — pairing the individual becomes operationally difficult when a growing percentage of the base has flagged them. Once elevated, the response generally follows a tiered progression: an informal counseling session first, then formal documentation, then mandatory CRM recurrent training or a simulator evaluation focused on cockpit interpersonal dynamics, and ultimately disciplinary action up to and including termination if the behavior continues or if the underlying complaints involve safety-relevant conduct.
Union contracts play a decisive role in shaping how these situations are handled at Part 121 airlines. Most ALPA-represented carriers require progressive discipline and afford the accused pilot due process rights, including representation during any investigatory or disciplinary meeting. Pilots have successfully grieved and overturned terminations rooted in pattern DNP complaints when management failed to follow contractual procedures. At non-union carriers, management discretion is broader, and the bar for administrative action is correspondingly lower. The distinction between a personality conflict and a safety concern is critical — a pilot documented as creating a hostile or intimidating cockpit environment may face action under the carrier's Safety Management System (SMS) framework, which carries different procedural protections than a standard HR matter.
For corporate and Part 135 operators, the dynamic differs in scale but not in substance. In a small flight department with two or three pilots, a single irreconcilable interpersonal conflict can be existential for the department's operations. Director of aviation positions at Part 91K and 135 operators often handle these situations directly and informally, and the absence of a union contract means the path from documented complaint to termination can be significantly shorter. The FAA does not maintain a "do not pair" registry, and such conflicts do not independently appear on a pilot's record unless they produce a formal enforcement action, a termination that surfaces in a background check, or a negative reference that affects future employment — the last of which is the most practically significant career risk for the individual involved.
The broader implication for working pilots is that cockpit interpersonal conduct is increasingly being treated as a competency rather than a personality quirk. ICAO's competency-based training frameworks and the FAA's Advanced Qualification Program (AQP) both formally include CRM and interpersonal effectiveness as evaluable standards. A pilot who accumulates DNP requests is, in effect, generating documented evidence of a recurring deficiency in one of those competencies — and in an era where SMS programs require carriers to treat behavioral patterns as safety data, the institutional tolerance for ignoring such patterns has narrowed considerably compared to prior decades.