Scheduling Committee

For assistance, contact our Scheduling Committee at  You can find a list of Committee Members on your Local Council Committees page.  For your convenience, a list of Committee Chairs and links to the Local Committee lists are below.

The Scheduling Committee makes sure that the company follows all contractual obligations that are outlined in our Collective Bargaining Agreement (CBA).

  • Makes sure that all pairings constructed by Crew Planning are legal.
  • Works with Crew Planning on line construction on a monthly basis.
  • Provides help and assistant to Flight Attendants who think that their CBA has been broken.
  • Discuss any scheduling problems or concerns with management
  • Files Complaint Resolution Forms (CRF) are filed in a timely manner for all contractual violations
  • Makes sure that Non-Notification of Delay (NND) brought to the Committee’s attention are filed bimonthly.
  • Moves all denied CRF and NND to Grievance should it warrant one being filed.

The Scheduling Committee is available to help you with:

  • Scheduling questions regarding possible contractual violations
  • The best way to contact the scheduling committee is via email at However, if you feel your CBA has been violated please open a ticket on the Support Center for better tracking.


Scheduling Committee

The committee is composed of volunteer members interested in representing the best interest of the members.

Qualifications include:

  • Good organization and communication skills
  • Excellent knowledge of scheduling-related sections of the CBA
  • Adherence to committee policies, procedures, and standards of ethical conduct
  • Be a member in good standing with the AFA
  • Ability to remain in good standing with the company
  • Willingness to do ongoing committee work on a volunteer basis
  • Check emails at least once every 24 hours
  • Log into the Support Center to monitor activity once every 72 hours
  • Return phone calls and text messages within 24 hours
  • File necessary CRF and NNDs within the 30-day timeline as outlined in the CBA

Scheduling Committee FAQs

Your AFA team receives many inquiries on how the monthly lines are built by the Scheduling Committee.  While many Flight Attendants believe that we have a say on how the pairings are built, that is false.  Each month Crew Planning builds the pairings and sends them to the AFA Scheduling Committee for review.  While we are reviewing, we are looking for Contract Violations and FAR Violations. If none of these are found, then the pairings are legal and will be placed into the pot for your Scheduling Committee to use to build the lines you see in the bid packet.

The line build occurs each month at headquarters in Miramar.  The dates that the build occurs varies each month, but if at all possible it’s done on the 28th and 29th of each month.  For example, on the 28th and 29th of January, we will be building the lines for March.  

When your Scheduling Committee members sit down to build the lines, we are given guidelines by Crew Planning to follow. These guidelines will tell us how many lines we are able to build for each base and the average line credit for each base.  These guidelines must be followed, however, we do have a little leeway.  Some months we are able to build 2 or 3 extra lines if the reserve coverage for that month is good.  

As the line building starts for each base, we first start with turn lines, then redeye lines and 2-day lines and so on.  After we finish with all true lines such as all 3-day pairing lines, we are left with a mix of pairings.  We will then place the remaining mix of pairings onto lines so we can reach the desired amount of lines for that base.  

Once we reach the number of lines the company wants for each base, we are left with open time.   At this point, we must place these pairings onto the lines already built to reduce open time down to less than 100 hours. When we begin to place these open pairings onto the lines, it will, unfortunately, make a line that is consistent, not so consistent. 

Let’s go back to the pairings, as mentioned earlier, the AFA has no say as to how the pairings are built, we just need to make sure the pairings are legal. Now, let’s take DFW for example if you are DFW based you will notice the number of turn lines has decreased.  One factor in that is, our flying in DFW has decreased as well.  If Crew Plan was to make more turns out of DFW, they would not be able to get Flight Attendants out of the base to operate other flying.  

Each month when your AFA Scheduling Committee meets with Crew Plan, we suggest what we would like to see with the next month pairings.  While it is not a guarantee they will take our advice we are always hopeful they will. 

If you would like to reference the Contract on how pairings are built please refer to Section 8.D and how the bid lines are built please refer to Section 8.E

We hope this will clear up some confusion on how your lines are built each month.  Please remember you are always welcome to reach out to your AFA Scheduling Committee at

Step-by-Step Guide to Monthly Bidding: Bidding on FLiCA

Step-by-Step Guide to Annual Vacation Bidding: Vacation Bidding

Many times blocked days occur when a more senior person has tried to drop a trip and was denied while the reserve grid was black or red. The reserve grid changes with each drop, swap, or add. Therefore, it may be black or red for a time while senior requests are being processed, then turn back to green as more junior DOT adds are approved. The processing of daily open time (DOT) requests must follow seniority order and cannot back-track to approve a senior drop request that was denied, even after more junior requests make it possible to approve them. For this reason, once the availability has changed it will not allow a less senior person drop a trip if a drop has already been denied to a more senior person. This creates a blocked day, so by the time DOT opens the next day it may still be green to allow those senior requests to go through then.

What does it mean when you receive this message as a denial reason for your DOT request?

FLiCA was designed to process all DOT requests automatically. It only stops and asks for clarification if it gets confused by a complicated request. Initially when FLiCA was implemented at Spirit, to make sure all settings worked properly the processing was done manually. For many reasons, this method remained unchanged and to this day most requests are still processed under the supervision of a Crew Scheduler.

If the DOT process in FLiCA is interrupted or paused for some reason (e.g. Scheduler gets busy with a call), and then restarted later where it was left off, the system is not built to keep a memory of what it has done with a given trip in the previous session (approved or denied) before the interruption. So when it tries to process a trip that is not available anymore because it was awarded to a senior FA in the earlier session, it will deny the request with the reason “Not Available in Opentime Pot”.

Roughly 1% of the time this denial code can mean something else, such as, the trip was removed from DOT before it closed for the day, or the trip was canceled before DOT processing, etc.

It is always a good idea to note who was on the trip before you submitted your request. This way if you get this denial code you can always check either via Flica or Crew Trac who has been added to the trip.

With the implementation of the new CBA, the company is now allowed to pull trips from the Opentime Pot as early as 2000 LT, two (2) days prior to the trip’s start date and assign them to a Flight Attendant in Time Recoverable (TAJ) status.

Since the pairing is then removed after you submitted the request, but before DOT is processed, FLiCA does not know what denial reason to give. For this reason, it will give a “Not Available” denial reason.

If you have doubts about the denial reason given, feel free to file a ticket for the given request, and a Scheduling Representative will be able to track what happened to the pairing and whether the CBA was followed.

Per Section 11.E.2, you will be pay protected for the hours you have left in your vacation bank. The remainder of the pairing credit will be dropped unpaid.  When this occurs, you may see a Sick Unpaid (SCU) code pop up on your schedule.  There is no need to worry if you see this code, at this time SCU is the only code scheduling has to use when a pairing is dropped, and you don’t have sufficient float vacation to cover the entire pairing. When the SCU code is used, for this reason, it will not make you accumulate points under the PRP policy.

The company is under obligation to notify us of a delay greater of 90 minutes. Here are some facts about NNDs.

• The delay of 90 minutes or more must be posted at least 30 minutes prior to your report time.

•  When out of base, scheduling must only notify one of the working Flight Attendants of the change in report time.  That Flight Attendant is then required to notify the rest of the crew.

• If one of the working Flight Attendants contacts scheduling to have the report time changed and scheduling changes the report time, then notification has been made.

MEC Scheduling Committee





Took Office: July 1, 2017
Term End: June 30, 2020

“I’ve been with Spirit Airlines for just over five years. Of those five years, I have volunteered on the Scheduling Committee for just over 4 years. I joined the committee to help the members with the many contractual violations we deal with on a daily basis. Back in May of 2017, I got the great opportunity of being elected MEC Scheduling Chair. Since then I have been working closely with management to limit contractual violations and disputes.”

Took Office: July 1, 2017
Term End: June 30, 2020

“I’m here to help.”

Close Menu