4.25.26 – Contract Implementation Update #58: Rescheduling in ECS

Saturday, April 25, 2026

Contract Implementation Update #58
Rescheduling in ECS

The first Rescheduling items coming to ECS for notification are expected in May.

There are no changes to Rescheduling other than how you are notified of your Reschedule. Rescheduling requirements and timelines are not changing, and this does not replace first-party contact where required in the CBA.

The first notifications to be implemented will include:

• Disruptions after report but prior to origination (CBA 10.J.3.d)
• Disruptions after origination (CBA 10.J.4.c)

Additional information on Rescheduling can be found on the APFA website and in CBA Section 10.J.

Notification of Repair Changes for the following CBA sections:

CBA 10.J.3.d (Disruption after report but prior to origination)

When a Flight Attendant experiences a disruption after report but prior to origination (CBA 10.J.3.d), Crew Scheduling has either four (4) hours after report time or three (3) hours after the disruption, whichever is later, to notify the Flight Attendant of their sequence repair. During this timeframe, a Flight Attendant must remain contactable. The notification of repair will now come via ECS instead of a phone call.

CBA 10.J.4.c (Disruption after origination)

When a Flight Attendant experiences a disruption after origination of their sequence (CBA 10.J.4.c), Crew Tracking has three (3) hours after the disruption is known to notify the Flight Attendant of the sequence repair. During this timeframe, a Flight Attendant must remain contactable. The notification of repair will now come via ECS instead of a phone call.

How it looks

When you experience a disruption to your sequence, you will receive an ECS notification. You will be provided with:

• The sequence affected
• How long you must remain contactable
• The disruption type
• Which flight leg was disrupted
• The start time of the disruption
• When your repair window ends
• Sequence Base Time (SBT): Time displayed in the time zone of the base where the sequence originated.

When the sequence is repaired, or your repair window ends, you will receive a second message. If your sequence is repaired, the message will include:

• The disruption type
• Repaired sequence details, including
  • Upcoming flight numbers
  • Date of flights
  • Departure times
  • City pairs
  • Position
  • ‘dhd’ if the leg is a Deadhead
  • Duty days are separated by a break

• Status of your sequence (Repaired or released pending repair).

If your repair window ends prior to Crew Scheduling / Tracking repairing your sequence, you will receive a message detailing:

• Status of being released from either your duty day or your sequence
• If released from your sequence, a reminder for Reserves of remaining obligation on available days.

Reminder: If Crew Scheduling does not Reschedule you within your repair window when your originating flight segment is disrupted after report but prior to origination (CBA 10.J.3.d), you will be released from your sequence and have no further obligation to the sequence.

More information regarding these ECS updates and the official launch date will be communicated next week.

In Unity,

Ashleigh Harbison
LAX

Hunter Meredith
PHL

Mike Sosa
DFW

Contact the CIC