10.03.25 – Contract and Scheduling Reminders

Contract and Scheduling Reminders

Friday, October 3, 2025

The APFA Contract and Scheduling Departments have seen an alarming uptick in three types of scheduling issues that are contract violations:

• Tagging (adding additional flying after the completion of a sequence) – Non-compliance with CBA 10.J and 12.O.
• 8.5 hours of uninterrupted crew base rest for Reserves.
• Using incorrect/unpaid removal codes rather than the correct paid removal code.

Tagging

“Tagging” is defined as adding flying to the end of a scheduled sequence. The CBA language does not allow the company to add flying to the end of a sequence in order to cover open segments or trips.

We have seen several cases of tagging occur in the past few months. Per our CBA, Flight Attendants are released to rest once their scheduled flying is complete. Unlike other airlines, we do not have an obligation to recheck our schedule or call crew scheduling at the end of a trip to ask to be released. 

Here are some examples of tagging:

Example 1:

• Crew was originally scheduled to work a CLT-MSP-CLT turn.
• Upon return to CLT, an Inflight Manager meets their flight and instructs them that they have been “rescheduled” to work CLT-STL, layover and DH STL-CLT the next morning.

Example 2:

• Crew has one leg back to base on day 3 of a 3-day trip:  TUL-DFW
• Scheduling calls and tells them they are being “rescheduled” to fly a turn when they arrive back in DFW, adding DFW-AUS-DFW.

Tagging of Lineholders is not compliant with the rescheduling language in CBA 10.J.1.a, 10.J.1.c, 10.J.7, and Priority of Trip Assignment in CBA 12.O.

Legal and available inbound Reserves may be given additional flying per CBA 12.O.3, if the company has first completed the steps outlined in 12.O.1 and 12.O.2.

Reserve Crew Base Rest

• CBA 12.E.4: This language allows a Reserve to have 8.5 hours of uninterrupted rest following an assignment. During this rest period, Crew Scheduling should only be calling if there is an operational need to notify you of a schedule change to your next flying assignment. They should not be calling to give you an assignment for later that day or the next day, or if there is a change to your next sequence that is not operationally necessary.
• While you are not obligated to answer the call, if you do answer and the interruption to your 8.5 hours rest was not operationally necessary, please contact your APFA Base Representatives to file a NOD for the contractual violation.

Crew Scheduling’s Use of Incorrect Removal Codes

• When removing sequences from Flight Attendant schedules, crew schedulers/trackers are using incorrect and unpaid codes rather than the correct paid codes. One of the most common occurrences of this is for trips that should be removed with a paid FI code. This is a removal due to going FAR illegal and is pay protected. Instead, the schedulers are using a code 15 removal, which is unpaid. Here’s where to find the removal codes on your HI1 (click images to enlarge):

Pictured above: HI1 with the incorrect removal code (15) which removed the pay from the Flight Attendant’s schedule.

Pictured above:  HI1 with the correct removal code (FI) with pay corrected.

Using incorrect, unpaid removal codes violates multiple provisions including CBA 10.J.10 and 10.K.1.a.

Need more information on DECS Add/ Removal Codes?

APFA has a tool for checking DECS Add/Removal Codes on the APFA website. To access the tool, click on Resources at the top of the APFA landing page and then click DECS Add/Removal Code. Input the desired code and press enter. The description of the code will be displayed (see image below; click to enlarge).

If you believe a trip was removed with the incorrect code, first file a Direct Connect. If denied, contact an APFA Rep for assistance, or complete the APFA Pay Discrepancy form at APFA.org.

In Solidarity,

Jeff Petersen
APFA National Contract Chair
[email protected]

Marti McMillan
APFA National Scheduling Chair
[email protected]