FDX - July08 Disputed Pairings
#1
FDX - July08 Disputed Pairings
ALPA's founders chose "Schedule with Safety" as our motto. The SIG/PSIT is Scheduling for OUR Safety !!
Support them in upholding the standard -- Do not fly disputed pairings!
Remind those you know who fly disputed pairs, either by force or by choice, to fill out a Critique Sheet on their experiences (or email/call the SIG) so they have ammunition for the disputed pairs resolution process.
Posted in the ALPA FDX MEC Message Line dated Jun 5, 2008:
===== Message Line Contents ==========
July Disputed Pairings:
727: None
A300 HKG: None
A300 MEM: #277, #307
A300 SFS: None
DC-10: None
MD-11 ANC: #86, #87, #88, #89, #90, #109, #2056, #2057, #2058, #2059, #2060
MD-11 LAX: None
MD-11 MEM: #188, #189, #267
===== End Message Line Contents ==========
Disputed Pairings Links (VIPS access required):
A300 MEM
#277/15 Jul
#277/22 Jul
#307/11 Jul
#307/18 Jul
MD11 ANC
#86/04 Jul
#87/05 Jul
#87/12 Jul
#87/26 Jul
#88/11 Jul
#89/18 Jul
#90/25 Jul
#109/09 Jul
#2056/04 Jul
#2056/25 Jul
#2057/05 Jul
#2058/11 Jul
#2058/18 Jul
#2059/12 Jul
#2060/26 Jul
MD11 MEM
#188/08 Jul
#188/15 Jul
#188/22 Jul
#189/09 Jul
#189/16 Jul
#189/23 Jul
#267/19 Jul
Reminder: These pairings should not be available in any bid pack lines and should not be assigned to any secondary lines without a specific request, by pairing number, from the crewmember to do so.
The MagicWebFX Automatic Disputed Pairs file is ready for download; check the "Update before download" box in the Open Time module (available in free and paid versions).
Support them in upholding the standard -- Do not fly disputed pairings!
Remind those you know who fly disputed pairs, either by force or by choice, to fill out a Critique Sheet on their experiences (or email/call the SIG) so they have ammunition for the disputed pairs resolution process.
Posted in the ALPA FDX MEC Message Line dated Jun 5, 2008:
===== Message Line Contents ==========
July Disputed Pairings:
727: None
A300 HKG: None
A300 MEM: #277, #307
A300 SFS: None
DC-10: None
MD-11 ANC: #86, #87, #88, #89, #90, #109, #2056, #2057, #2058, #2059, #2060
MD-11 LAX: None
MD-11 MEM: #188, #189, #267
===== End Message Line Contents ==========
Disputed Pairings Links (VIPS access required):
A300 MEM
#277/15 Jul
#277/22 Jul
#307/11 Jul
#307/18 Jul
MD11 ANC
#86/04 Jul
#87/05 Jul
#87/12 Jul
#87/26 Jul
#88/11 Jul
#89/18 Jul
#90/25 Jul
#109/09 Jul
#2056/04 Jul
#2056/25 Jul
#2057/05 Jul
#2058/11 Jul
#2058/18 Jul
#2059/12 Jul
#2060/26 Jul
MD11 MEM
#188/08 Jul
#188/15 Jul
#188/22 Jul
#189/09 Jul
#189/16 Jul
#189/23 Jul
#267/19 Jul
Reminder: These pairings should not be available in any bid pack lines and should not be assigned to any secondary lines without a specific request, by pairing number, from the crewmember to do so.
The MagicWebFX Automatic Disputed Pairs file is ready for download; check the "Update before download" box in the Open Time module (available in free and paid versions).
#5
I missed the SIG notes. Why is PR 188/189 (MD11) disputed?
The SIG also wants comments on pairings not disputed. I flew one and my friend flew it a month later... an afternoon launch MEM-OAK, nearly 30 hours off at the Fisherman's Wharf. AM launch OAK-ANC, with 15 hours off. ANC-MEM the same evening as you arrived. The last leg is the killer. Can't keep your eyes open.
And, no chance to visit F Street!!!!!!
The SIG also wants comments on pairings not disputed. I flew one and my friend flew it a month later... an afternoon launch MEM-OAK, nearly 30 hours off at the Fisherman's Wharf. AM launch OAK-ANC, with 15 hours off. ANC-MEM the same evening as you arrived. The last leg is the killer. Can't keep your eyes open.
And, no chance to visit F Street!!!!!!
#6
Notes to Follow
Relax, It's FedEx . You haven't missed anything, because the SIG Notes haven't been released yet. The M.O. for the last few months has been to release the pairing numbers at the same time as the bidpacks via a Message Line Email; then follow-up with the Notes the next week-- after Mgt gets done editing them.
#7
#9
Line Holder
Joined APC: Jul 2006
Position: MD11FO
Posts: 47
Several council members have inquired about the status of the ANC-NRT-NGO DP submitted per the SIG Dispute Track.
C.B.A. Section 25.BB.G. reads as follows:
Final Resolution of Scheduling Disputes: VP/MEC Chairman Track
The MEC Chairman may elect to notify the Vice President, Flight Operations that he is invoking the VP/MEC Chairman track regarding a particular SIG dispute. The notification shall be in writing and shall state the unresolved concerns/problems and the Association’s position. Upon receipt, the Vice President, Flight Operations shall promptly have the stated unresolved concerns/problems investigated, including a review of the process undertaken thus far regarding the dispute. After at least one bid period of flying data is gathered on the disputed pairing, the Vice President, Flight Operations shall meet with the MEC Chairman at a mutually acceptable date and time to review the results of the investigation and discuss options for dealing with the unresolved concerns/problems. Following the meeting, the Vice President, Flight Operations shall advise the MEC Chairman in writing of what actions, if any, the Company shall take to address the presented concerns.
Urgent Notice
Ladies and Gentlemen,
We apologize for delivering this message to you in this manner; however, minutes before publishing the monthly Council 79 Open Time DP Reminder, we were notified that the Vice President, Flight Operations has determined that the ANC-NRT-NGO sequence is not disputable. This means there are no DPs for the remainder of June and none for July. In order to expedite publication of this council email before the release of Open Time today, we will leave the original message (but for the DP listing) as is, in order to avoid going to the back of the queue for the communications, legal and MEC review.
I guess negotiations just started 2 years early...
C.B.A. Section 25.BB.G. reads as follows:
Final Resolution of Scheduling Disputes: VP/MEC Chairman Track
The MEC Chairman may elect to notify the Vice President, Flight Operations that he is invoking the VP/MEC Chairman track regarding a particular SIG dispute. The notification shall be in writing and shall state the unresolved concerns/problems and the Association’s position. Upon receipt, the Vice President, Flight Operations shall promptly have the stated unresolved concerns/problems investigated, including a review of the process undertaken thus far regarding the dispute. After at least one bid period of flying data is gathered on the disputed pairing, the Vice President, Flight Operations shall meet with the MEC Chairman at a mutually acceptable date and time to review the results of the investigation and discuss options for dealing with the unresolved concerns/problems. Following the meeting, the Vice President, Flight Operations shall advise the MEC Chairman in writing of what actions, if any, the Company shall take to address the presented concerns.
Urgent Notice
Ladies and Gentlemen,
We apologize for delivering this message to you in this manner; however, minutes before publishing the monthly Council 79 Open Time DP Reminder, we were notified that the Vice President, Flight Operations has determined that the ANC-NRT-NGO sequence is not disputable. This means there are no DPs for the remainder of June and none for July. In order to expedite publication of this council email before the release of Open Time today, we will leave the original message (but for the DP listing) as is, in order to avoid going to the back of the queue for the communications, legal and MEC review.
I guess negotiations just started 2 years early...
#10
Watch out. ANC Trip 109 on 9 Jul should still be listed as disputed. It doesn't have the ANC-NRT-NGO sequence in it.
It was "Disputed for rest issues. The one and only reset happens too late in this pairing to be effective. It has a night departure, multiple body clocks swaps and short layovers before the reset."
It was "Disputed for rest issues. The one and only reset happens too late in this pairing to be effective. It has a night departure, multiple body clocks swaps and short layovers before the reset."
Thread
Thread Starter
Forum
Replies
Last Post