FDX - 727 Disputed Pairings for Nov
11-11-2011, 06:10 PM
#82
Gets Weekends Off
Joined APC: Nov 2006
Position: 767 FO
Posts: 8,047
Originally Posted by matty
Add the braided belt with the jeans hiked 10 inches above you're waist and I'll guarantee you are former USAF! 
http://bmj2k.files.wordpress.com/2010/01/fred-mertz.jpg
11-11-2011, 09:22 PM
#83
Gets Weekends Off
Joined APC: Jan 2008
Posts: 1,193
Originally Posted by Unknown Rider
Do you fly on the back side of the clock?
Originally Posted by DLax85
This isn't your std trip bruddah.
Show at 1:30 in the morning...you are supposed to be ready to go to sleep only 3 hrs later...but not really, because when you show for a trip the company may legally change it to another...and you are responsible for being able to go to max duty time for that second trip.
Now, when they don't change the trip you need to be sleepy 3 hrs after you showed, because you need to be well rested for the 2 legs @ over 5+30 block that's coming your way that afternoon/evening....it's got foreign controllers, high terrain and a non-precision approach...then back to MEM for a hub turn.
(OBTW, those sleep rooms are not guarunteed in Memphis --- they don't have enough for everyone --- yeah, they know it --- and they've got some plans to correct it though
)
Bottom-line: Your company's minimum rules may work for your type of flying, but that doesn't mean they are safe elsewhere.
Show at 1:30 in the morning...you are supposed to be ready to go to sleep only 3 hrs later...but not really, because when you show for a trip the company may legally change it to another...and you are responsible for being able to go to max duty time for that second trip.
Now, when they don't change the trip you need to be sleepy 3 hrs after you showed, because you need to be well rested for the 2 legs @ over 5+30 block that's coming your way that afternoon/evening....it's got foreign controllers, high terrain and a non-precision approach...then back to MEM for a hub turn.
(OBTW, those sleep rooms are not guarunteed in Memphis --- they don't have enough for everyone --- yeah, they know it --- and they've got some plans to correct it though
)Bottom-line: Your company's minimum rules may work for your type of flying, but that doesn't mean they are safe elsewhere.
Carry on.
11-12-2011, 04:42 AM
#84
Gets Weekends Off
Joined APC: Jan 2006
Posts: 394
Originally Posted by FDXLAG
Here I am in Grand Forks. The ladies loved the look.
http://bmj2k.files.wordpress.com/2010/01/fred-mertz.jpg
http://bmj2k.files.wordpress.com/2010/01/fred-mertz.jpg
11-20-2011, 10:21 AM
#85
Gets Weekends Off
Thread Starter
Joined APC: Jul 2007
Position: Gear Monkey
Posts: 3,191
Not hearing any good feedback on this pairing from crews that have flown it ....and am seeing a few more of these trips fall back into Open Time for Nov. 
That's right --- you can legally pick-up a DP and you can legally drop 'em!
It's a choice ---- let's all make the right one!
Now looking ahead into Dec --- the company, unfortunately, would still like to put this in our bidpack permanently, on a regular line, with an even shorter layover.... but our PSIT is doing their best by saying No.
With the Dec View/Add Window opening up soon, let's continue to educate the crew force on which 727 trips are disputed and why.
Simply put it's: Safety....Safety....Safety.
But to quote the PSIT in the recent SIG notes:
Disputes: Pairing #21/#26 – QRO. Critical launch followed by a short rest before a difficult international out and back to high altitude airport. This pairing was disputed in November, and will remain disputed. We have consistently pointed out that critical to day transitions are fatiguing. Given the length and destination of the second duty period, with a showtime in the afternoon WOCL, we feel strongly that this pairing design should be changed.
...and
Our BFM-QRO dispute continues this month. Pilot scheduling has the crew launching to BFM in critical, getting a near minimum rest, then launching in the afternoon for a PM out and back BFM-QRO-MEM. Given this is an international, 6200 foot elevation, mountainous airport the PSIT has decided to dispute the pairing construction. After the dispute was initiated last month, the layover in BFM was further shortened by 30 minutes (60 minutes in week #3 of December), making the pairing even more objectionable to the PSIT.
What message are our collective actions sending crew scheduling and the PSIT this holiday season?
That's right --- you can legally pick-up a DP and you can legally drop 'em!
It's a choice ---- let's all make the right one!
Now looking ahead into Dec --- the company, unfortunately, would still like to put this in our bidpack permanently, on a regular line, with an even shorter layover.... but our PSIT is doing their best by saying No.
With the Dec View/Add Window opening up soon, let's continue to educate the crew force on which 727 trips are disputed and why.
Simply put it's: Safety....Safety....Safety.
But to quote the PSIT in the recent SIG notes:
Disputes: Pairing #21/#26 – QRO. Critical launch followed by a short rest before a difficult international out and back to high altitude airport. This pairing was disputed in November, and will remain disputed. We have consistently pointed out that critical to day transitions are fatiguing. Given the length and destination of the second duty period, with a showtime in the afternoon WOCL, we feel strongly that this pairing design should be changed.
...and
Our BFM-QRO dispute continues this month. Pilot scheduling has the crew launching to BFM in critical, getting a near minimum rest, then launching in the afternoon for a PM out and back BFM-QRO-MEM. Given this is an international, 6200 foot elevation, mountainous airport the PSIT has decided to dispute the pairing construction. After the dispute was initiated last month, the layover in BFM was further shortened by 30 minutes (60 minutes in week #3 of December), making the pairing even more objectionable to the PSIT.
What message are our collective actions sending crew scheduling and the PSIT this holiday season?
Thread
Thread Starter
Forum
Replies
Last Post
