That would be a plain violation of the new provision. Under the current CBA, a double crew may be scheduled when “the Company anticipates that such crew may be required." The TA replaces that language with three specific paths to get an additional pilot or pilots on the flight. The Company may only schedule 3-pilot or 4-pilot augmentation under these defined circumstances:
- Extended Block/Duty: When the Company reasonably anticipates a requirement due to extended block or duty time limitations (e.g., historical data showing a flight frequently exceeds block limits). While similar to our current CBA’s rationale for a double crew, this provision adds a “reasonable” qualifier to “anticipates” and further provides that the anticipation that added crew may be required is not open-ended, but is limited to “due to extended block or duty time.”
- Safety: For the "sole purpose of safety," but only when specifically directed by the VP of Flight Operations or the DO.
- SIG Approval: On an individual trip or pairing when approved by the Scheduling Improvement Group (SIG).
If the Company attempted to assign a pilot as an augmented crew member simply to move the pilot to avoid the cost of a commercial deadhead, that would be a plain violation of the provision, and challenged with objective data (such as FRMG sleep studies or safety audits), historical DHs, etc.
Other Points:
- SIG Approval: The SIG has requested, and the company has granted the request, to have an RFO on legs with block times less than 7+35. DARTs from pilots relaying that certain legs we fly are onerous have led to additional crew members being added even with the block times slightly under the 7+35 and 12+00 thresholds.
- Per FOM 2.45 and a grievance settlement, the Company may only schedule one standard crew (CAP and FO) on a flight. RFO pilots must be scheduled on a separate non-standard crew pairing. For example, CRS may not build a pairing that had an RF2 for the first leg to avoid a DH and then have the pilot fill the CA position for the rest of the trip. The trip may only be CA or RF2. It is possible that the CA trip with a front-end DH could be operationally revised to operate and operate as a RF2 for the first leg. In this case, the scheduled DH bank would be retained, and the pilot would be due Crew Disruption Pay and Front-End DH deletion pay.