Airline Pilot Central Forums

Airline Pilot Central Forums (https://www.airlinepilotforums.com/)
-   Cargo (https://www.airlinepilotforums.com/cargo/)
-   -   FDX - 757 Disputed Pairings - Nov '14 (https://www.airlinepilotforums.com/cargo/84559-fdx-757-disputed-pairings-nov-14-a.html)

DLax85 10-20-2014 03:14 AM

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

MaxKts 10-20-2014 04:40 AM


Originally Posted by DLax85 (Post 1749641)
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

I understand how the dispute process works - what I don't understand is why this sequence was OK for SEP - OCT but is now disputed for NOV. Plus the layover is always shorter due to waiting in SYR for MEM flight to come through and the ramp is really slow!

FDXLAG 10-20-2014 04:45 AM


Originally Posted by MaxKts (Post 1749655)
I understand how the dispute process works - what I don't understand is why this sequence was OK for SEP - OCT but is now disputed for NOV. Plus the layover is always shorter due to waiting in SYR for MEM flight to come through and the ramp is really slow!

The sig emails are all on the sig notes. They are always responsive to my inquiries.

Overnitefr8 10-20-2014 05:49 AM


Originally Posted by MaxKts (Post 1749655)
I understand how the dispute process works - what I don't understand is why this sequence was OK for SEP - OCT but is now disputed for NOV. Plus the layover is always shorter due to waiting in SYR for MEM flight to come through and the ramp is really slow!

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.

MaxKts 10-20-2014 06:15 AM


Originally Posted by Overnitefr8 (Post 1749675)
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.

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!

DLax85 10-20-2014 06:57 AM


Originally Posted by MaxKts (Post 1749691)
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!

"Last month"...as in Sep?

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

appDude 10-20-2014 09:46 AM

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 :)

Overnitefr8 10-20-2014 02:08 PM


Originally Posted by MaxKts (Post 1749691)
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!

October it is only BTV-SYR-EWR-SYR-BTV with layovers in BTV and EWR

MaxKts 10-20-2014 03:34 PM


Originally Posted by DLax85 (Post 1749714)
"Last month"...as in Sep?

In the 757 bidpack?

What was the trip # or line #?

Prngs 140/07, 144/14 and 146/22 all in Sep bidpack.



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
SYR is never on time! You wait on the MEM flight and then wait on the ramp because everything else is more important than you getting to BTV. :mad:

MaxKts 10-20-2014 03:36 PM

Heard from a friend that the SIG knew about the pairing but did not dispute in Sep because they had other issues to worry about. :mad:


All times are GMT -8. The time now is 09:12 AM.


User Alert System provided by Advanced User Tagging v3.3.0 (Lite) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Website Copyright ©2000 - 2017 MH Sub I, LLC dba Internet Brands