Two Cultures, One Seniority List
You are the newly hired director of aviation for a company that acquired a competitor 14 months ago. The combined department has 14 pilots, 6 aircraft, and bases 900 miles apart. Seniority was merged by date of hire, which displaced two former captains; one of them, a former chief pilot of the acquired company, now flies as an FO and has become openly critical on the flight deck - second-guessing the captain's decisions on two recent flights and refusing to complete a checklist item “until we discuss it on the ground.” Two captains have asked not to be paired with him. In the last four months three pilots resigned (replacement cost roughly $85,000 each), and an anonymous survey shows a 31-point drop in “I would recommend this department” since the merger. The two pilot groups still run separate group chats that mock the other side. The chief pilot wants to terminate the FO for insubordination; HR wants a documented improvement plan. Your boss, the CFO, asks why this matters and what it will cost.
1. Diagnose what is actually happening. Separate the conduct issue from the integration issue, and name the safety risk.
Read the worked answer
Three distinct problems are tangled together:
- A conduct issue. Refusing a checklist item in flight and undermining the captain is not a culture complaint; it is a threat-and-error-management failure and a legitimate insubordination matter. It must be addressed on its own facts, promptly, with a clear standard - and it is separable from whether the seniority merge was fair.
- An integration failure. Seniority merged by date of hire with no status-protection, no communication plan, and no effort to rebuild identity across two bases. Two displaced captains, separate group chats, and a 31-point drop are textbook merger integration symptoms: loss of status, perceived procedural injustice, and in-group/out-group formation. People do not resist the change; they resist the loss.
- A psychological-safety problem. If a captain cannot raise a concern without being mocked, you will lose the near-miss reports that are your only warning system in a 14-pilot department.
Safety risk: degraded CRM, checklist non-compliance, and crew pairing avoidance - all precursors in approach-and-landing and engine-out events. Business risk: three resignations at $85,000 replacement cost is roughly $255,000, plus lost productivity, plus the cost of a captain who will not speak up. That is the answer for the CFO.
2. Design a 90-day plan. What do you do first, and how do you handle the FO and the pairing refusals?
Read the worked answer
Days 1–14 (stabilize):
- Meet the FO privately, with HR present. Be specific about the two flight-deck events, state the standard (a crewmember raises concerns, but does not withhold a checklist action or override the captain), and issue a written performance improvement plan with defined, observable expectations and a review date. Termination is defensible only after the standard has been stated and documented - and the file is stronger if you say it first.
- Handle the pairing requests honestly: you will not promise permanent avoidance, because that institutionalizes the split; you will manage pairings for a short, defined period while the behavior is corrected.
- Brief all captains on the standard for intervening and on the reporting channel for cockpit conflict.
Days 15–45 (integrate):
- A facilitated joint session with both pilot groups, both bases, on what the merger changed and what it did not. Publish a seniority and upgrade-path explainer so the rules are visible rather than rumored.
- Cross-base pairing where practical, and one common communication channel with a single set of standards; do not let two group chats define the culture.
- Standardize SOPs and checklists across the fleet so nobody can claim “that is not how we did it.”
Days 46–90 (sustain): skip-level conversations, a quarterly all-pilots call, and visible action on the top three survey items. Communicate what you changed and what you did not, with reasons.
3. What do you tell the CFO, and how will you measure whether this is working?
Read the worked answer
To the CFO, in his language: flight departments do not fail from bad airplanes, they fail from crews that will not speak up. The conduct issue is a checklist-compliance risk in a two-crew cockpit; the retention issue is $255,000 of direct replacement cost plus schedule disruption and lost client confidence; the integration issue is the multiplier on both. Frame the spend - facilitation, one joint session, a standardization pass - as a fraction of one resignation.
Measures, tracked quarterly and reported on one page:
- Voluntary turnover and intent-to-stay (single survey question, tracked over time).
- Survey score on “I would recommend this department,” plus a psychological-safety item (“I can raise a concern without fear”).
- Safety reporting rate - an increase is good early; a collapse is a warning.
- Crew pairing requests and refusals (should trend to zero).
- Checklist and SOP compliance observed on line checks.
- Time-to-upgrade transparency: the percentage of pilots who can correctly state their position and upgrade path.
Review the FO's improvement plan at 30 and 60 days and act on the documented record either way. What you must not do is let the integration problem excuse the conduct problem, or let the conduct problem become the excuse for not fixing the integration.