FlybyKnite

And I would have to politely agree with KAFTKTA. Yes-- unlike some, the union has my email address and I receive all those emails, plus the Jetflyer and even read the DP posts here too. And the one thing they all have in common is that I'm just looking at numbers, and not specifics of the pairings. The SIG tells me why they disputed it, but that doesn't help me distinguish that pairing from the others. Not making excuses for the lazy, but there has to be an easier way.

Agreed, the company is certainly not going to help us. They certainly aren't going to spend programming $$ to change a few rotating pairing labels. The SIG doesn't publish the pairings (confidentiality?) and the company can change the dates.

So, I am left not knowing how many of these pairings there are (4 of the #3050) or which dates (5,12,19,& 26Apr). At least with that info, I could go look at the pairing and see why the SIG disputed it. But even knowing that doesn't mean I won't pickup, VTO or CIC request one by mistake. I needed a way to download open time, find and tag those disputed pairings with a big flag so that I could "see and avoid" them. I find this one works for me, because it really sticks out in a text file:

#-#-#-#-#- DISPUTED PAIRING -#-#-#-#-#- DISPUTED PAIRING -#-#-#-#-#-
Trip 564 MEM 11 26APR07
#-#-#-#-#- DISPUTED PAIRING -#-#-#-#-#- DISPUTED PAIRING -#-#-#-#-#-

So I created a small software solution that works for me and a few other folks. The open time and mainframe download modules are fraternally Free—forever, because, I don't want anybody to have an excuse for flying a disputed pairing. If interested, Goto magicwebfx[dot]net. The Contract formatted as a Help File [MEC-approved] is also there and fraternally Free, because, hyperlinks make life easier.

.

TonyC

I have to disagree with you on this point. The SIG letter indeed names the Pairings by number, and explains the problems with the pairings.

For example, in the April SIG Letter we read two sections. First, from the "Definitive List" of Disputed Pairings:

MD11 MEM: #564, #3050 are disputed because both these pairings push the second duty day envelope at 13+09. The crew has to clear customs and immigration in SJU; the 60 minute turn time is simply not realistic. The history of this pairing we were given is unclear as to whether the same crew flew it outbound from SJU each time;even still it went over schedule more then 50% of the time. This pairing will consistently go over the scheduled duty time limit.The suggested fix is to lay the crews over in SJU.

Second, in the MD11/MD10 MEM Section:

We initially disputed nine pairings this month, six survived the resolution process: #12, 116, 118, 119, 564 and 3050. Please read the disputed pairing section for the rational.

Disputed pairings #116, 118, and 119 deserve special mention. The problem sequence is SFS-HKG-ALA. The crew alerts in SFS at 0130lcl, and flies to HGK. They sit in HGK for almost two hours (with an aircraft change) and fly to ALA. Twelve hours after alert in SFS - and 1330lcl on their body clocks - they are shooting an approach to one of our most problematic airports: language and divert issues en-route, QFE and metric altimetry issues in mountainous terrain. Starting next month the company committed to limit this duty period to one leg HKG-ALA.

The company agreed to fix pairings #30 and #406 as dispute resolutions. They were not built on lines and will be revised prior to the secondary line process. The issue was the live leg deadhead IND/ORD/MEM, with a 3+59 drool time in ORD at 3am. The ORD passenger terminal is not open at 3am and it is inappropriate to stay at the Ramp until the flight show time. The solution was to lay the crew over in ORD before the deadhead. They will be available in the secondary line process.

It only takes a few minutes to read the pertinent information and digest it. If I were offered a Draft Trip that involved a quick turn through SJU, I think I'd know enough from reading that to check into the Disputed Pairing issue a little more closely before accepting the assignment.


It's not like there's a long list. There's a neat place in your ALPA Calendar to write down the Pairing Numbers when you read the SIG letter. There are lots of ways to track it, and not many excuses for not.




It sounds like your software "fix" might work on a home computer, but does it work on the computers in AOC, or the ramp offices? Don't get me wrong, I'm not knockin' it, because every little bit helps. I'm just curious.



.

md11phlyer

[quote=FlybyKnite;145499]And I would have to politely agree with KAFTKTA. Yes-- unlike some, the union has my email address and I receive all those emails, plus the Jetflyer and even read the DP posts here too. And the one thing they all have in common is that I'm just looking at numbers, and not specifics of the pairings. The SIG tells me why they disputed it, but that doesn't help me distinguish that pairing from the others. Not making excuses for the lazy, but there has to be an easier way.

Sorry, Tony C beat me to it. But I must say, isn't that exaxtly what the SIG is doing when they tell you why they disputed it? They are specifically identifying the onerous segments that distinguish that pairing from the others.

Phlyer

FlybyKnite

Ouch!

Yes, the SIG and the pairing reviewers (real unsung heroes) do a great job of identifying the onerous segments and publishing the results. I erred in making my publishing comment-- the actual pairings aren't in the notes email but are in the bid pack. I meant that I just don't think a lot of guys are industrious enough to go through the bid pack to eyeball and digest the pairings before open time comes out (especially guys using Fastbid- I'm guilty most months).

And you are correct, it is a personal computer solution (ala magicdisk for the web), so it indeed does not help you in the AOC or on the ramps which means you still need to have your DP List in hand before making trades.

Jim wanted to see the pairings when doing his bid and Fastbid was born. I wanted to download open time and flag disputed pairs and do a couple other things. Bottom line: It is still a basic recognition problem, and if I can help one guy "see and avoid" a DP it makes the whole effort worth while.


.

Purple F/O

Some of those ALPA e-mails have safety updates and links to safety issues that we need to be aware of. I'm not sure I'd feel comfortable flying with an F/O who doesn't get those safety updates.

nightfreight

Looks like the MD-11 Fo that picked up two disputed pairings has dropped both of them. One pairing (564 26Apr) was in open time for about 5 minutes this morning before some other dude picked it up.......

Tuck

Listen I could care less to everyone's excuses. There's an easy way to avoid DPs and the only way we can make sure some lazy people do it, is to discourage them when they take a DP. We should absolutely be posting names here, everywhere. Does someone really have sympathy for these guys?

Deuce130

I'm still going through training on the Bus so having to avoid DP's is a relatively new thing for me. This thread has been eye-opening, to say the least, and I'll be sure to diligently track the DPs in my handy ALPA calender, just inside the front cover on the gold pages. I'll also make sure my ALPA emails don't get routed to my junk folder and get to my inbox. I'll also make sure that I spread the word to my buds if I see them indiscriminately picking up trips in open time that may be DPs and remind them to at least check the status before picking them up. As far as posting people's names on this particular message board, I can't back that. No, I don't have sympathy for them but, as in the case of the F/O "outed" in this thread, the main issue was education, not just being an A-hole. Unless a guy would be willing to also post his own name in the post (which I also don't think is a good idea) then I don't think anyone else should be named, especially when it's liable to have unforeseen consequences. A more direct approach would be to email the guy, or call him personally if you can get his number, and ask him point blank if he realizes that he's picked up a DP. If someone's not willing to do that, then they probably shouldn't post his name here. Besides, it just doesn't sound right to post real names.

FDXLAG

All but 3 of the backseat 727 DP taken for the rest of the month.

FLMD11CAPT

There is an ANC first year F/O who not only repeatedly picks up DP's but then brags about how well they fit his/her schedule. Then e-mails the SIG to berate them about how wrong they are about the trips being disputed.Talk about being "out of the loop". Many attempts have been made at "professional advice'. This case will be tough to solve........