FDX - 757 Disputed Pairings - Nov '14
#1
FDX - 757 Disputed Pairings - Nov '14
It's been a while, but unfortunately Disputed Pairings are back in the 757 MEM Bidpack as we enter Peak.
Please put Safety First, and support your PSIT & SIG:
Straight from the SIG Notes:
#103 / 10NOV
#105 / 17NOV
#120 / 10, 17 NOV
#124 / 24NOV
#302 / 04, 05, 06, 11, 12, 13, 18, 19, 20, 25, 26 NOV
#346 / 10, 17 NOV
BFM-QRO, pairing 302, is a previously disputed pairing that has reappeared in November. We are continuing to dispute this pairing design based on risks associated with operating two legs critical into a high CFIT/minimal ATC international
destination.
TV-SYR-EWR-FLL, disputed pairings 103/105/120/124/346 contain an 11+01 layover before an 11+18 3 leg night duty period
Thanks,
In Safety...and Unity,
DLax
Please put Safety First, and support your PSIT & SIG:
Straight from the SIG Notes:
#103 / 10NOV
#105 / 17NOV
#120 / 10, 17 NOV
#124 / 24NOV
#302 / 04, 05, 06, 11, 12, 13, 18, 19, 20, 25, 26 NOV
#346 / 10, 17 NOV
BFM-QRO, pairing 302, is a previously disputed pairing that has reappeared in November. We are continuing to dispute this pairing design based on risks associated with operating two legs critical into a high CFIT/minimal ATC international
destination.
TV-SYR-EWR-FLL, disputed pairings 103/105/120/124/346 contain an 11+01 layover before an 11+18 3 leg night duty period
Thanks,
In Safety...and Unity,
DLax
#2
Part Time Employee
Joined APC: Jul 2006
Position: Dispersing Green House Gasses on a Global Basis
Posts: 1,918
It's been a while, but unfortunately Disputed Pairings are back in the 757 MEM Bidpack as we enter Peak.
Please put Safety First, and support your PSIT & SIG:
Straight from the SIG Notes:
#103 / 10NOV
#105 / 17NOV
#120 / 10, 17 NOV
#124 / 24NOV
#302 / 04, 05, 06, 11, 12, 13, 18, 19, 20, 25, 26 NOV
#346 / 10, 17 NOV
BFM-QRO, pairing 302, is a previously disputed pairing that has reappeared in November. We are continuing to dispute this pairing design based on risks associated with operating two legs critical into a high CFIT/minimal ATC international
destination.
BTV-SYR-EWR-FLL, disputed pairings 103/105/120/124/346 contain an 11+01 layover before an 11+18 3 leg night duty period
Thanks,
In Safety...and Unity,
DLax
Please put Safety First, and support your PSIT & SIG:
Straight from the SIG Notes:
#103 / 10NOV
#105 / 17NOV
#120 / 10, 17 NOV
#124 / 24NOV
#302 / 04, 05, 06, 11, 12, 13, 18, 19, 20, 25, 26 NOV
#346 / 10, 17 NOV
BFM-QRO, pairing 302, is a previously disputed pairing that has reappeared in November. We are continuing to dispute this pairing design based on risks associated with operating two legs critical into a high CFIT/minimal ATC international
destination.
BTV-SYR-EWR-FLL, disputed pairings 103/105/120/124/346 contain an 11+01 layover before an 11+18 3 leg night duty period
Thanks,
In Safety...and Unity,
DLax
#3
Gets Weekends Off
Joined APC: Nov 2006
Position: 767 FO
Posts: 8,047
The sig emails are all on the sig notes. They are always responsive to my inquiries.
#4
What I see as the difference is an additional hub turn to FLL once a week rather laying over in EWR. So it isn't the same trip.
#5
Part Time Employee
Joined APC: Jul 2006
Position: Dispersing Green House Gasses on a Global Basis
Posts: 1,918
I flew BTV-SYR-EWR-FLL last month without a layover in EWR! It was a bidpack pairing not a revision. The only difference in NOV is with the seasonally adjusted times you don't rate a hotel during the turn now - turn went from 4:08 to 4:00. A hotel on a hub turn is not a layover!
#6
I flew BTV-SYR-EWR-FLL last month without a layover in EWR! It was a bidpack pairing not a revision. The only difference in NOV is with the seasonally adjusted times you don't rate a hotel during the turn now - turn went from 4:08 to 4:00. A hotel on a hub turn is not a layover!
In the 757 bidpack?
What was the trip # or line #?
The SIG notes seem to reference a shorter layover time prior to a long duty period.
Did the trips you flew consistently stay on schedule?
Thx
#7
And again, your best visibility of disputed pairings as you look at open time:
FxCal, BidX, MagixWebFX
Using one of these tools will help you stay clear of an inadvertent pickup of a disputed pairing.
appDude
... although of course my recommendation is FxCal
FxCal, BidX, MagixWebFX
Using one of these tools will help you stay clear of an inadvertent pickup of a disputed pairing.
appDude
... although of course my recommendation is FxCal
#8
I flew BTV-SYR-EWR-FLL last month without a layover in EWR! It was a bidpack pairing not a revision. The only difference in NOV is with the seasonally adjusted times you don't rate a hotel during the turn now - turn went from 4:08 to 4:00. A hotel on a hub turn is not a layover!
#9
Part Time Employee
Joined APC: Jul 2006
Position: Dispersing Green House Gasses on a Global Basis
Posts: 1,918
The SIG notes seem to reference a shorter layover time prior to a long duty period.
Did the trips you flew consistently stay on schedule?
Thx
Did the trips you flew consistently stay on schedule?
Thx
Thread
Thread Starter
Forum
Replies
Last Post