LRD-MEM flight, departure time amended and scheduled delayed for one hour with original airport stby period of 30 minutes not changed, resulting in a break in the arpt stby period to the scheduled new depart time of two hours plus ten minutes ................. Then I noticed that after trip was over, the entire arpt stby duty period was changed to show that we did one hour plus ten minutes as arpt stby, so as not to show any break in the arpt stby duty period to the new scheduled delayed depart time.
Was this done correctly or should there have been another arpt stby duty period tacked on the pairing as another revision to the pairing ? Reason I ask this way, our weak CBA has allowed the Company to NOT pay us for any bid pack designated sweep flights, under the section of disruptions unless another duty period is added to the pairing. Should I have called and pressed to have another arpt stby duty period added to this pairing, once Company had revised our departure time to one hour later and there was a break in the arpt stby duty period to the scheduled revised departure time ???
Company is getting away with making us show for scheduled airport standby periods and holding us longer at the ramps to satisfy their requirements of a later departure time.

 

If I'm following you correctly, it sounds like they had they early show built into the pairing, and just delayed your departure. I learned the hard way that a SHARPT before a sweep flight is NOT an airport standby, it's just reflecting the start of duty. If it showed an STARPT, then it would be an airport standby. Seems trivial, but it's not. Unless scheduling released you for a full crew rest and then brought you back out, then you were still on one continuous duty period, regardless of the gap between the end of the SHARPT leg in the pairing and the departure time of the flight, so no extra duty period pay. Kind of like on a hub-turn. It may be two seperate pairings, but it's all one duty period from the time you showed in the field until you finish at your final destination. Kind of weird how they did they did the rebuild on your pairing after they delayed your departure, but unfortunately in your case, it's just a situation where your departure was pushed back and you got back to MEM late. I'm guessing it didn't get you back into MEM late enough to affect any rigs based on TAFB, so if it was a scheduled sweep flight, I don't think you'll get anything.

 

KDEN, this is exactly what happened to us and it also occured the same way a week before. Basically, it looked real strange to have us scheduled like this. I am miffed that we cannot get anything "extra pay", because as long as this kind of thing is listed in the bidpack as SWEEP, all the pay stuff disappears.
I don't understand why we would have given that one to the Company so easy, makes me very suspicious about the rest of the CBA ............................

 

Agree --- it's all one duty period and given it's a designated sweep flight no disruption pay earned.

Now, if the STBY period was added after the trip was initially built (i.e. they revised your pairing, brought you in early and added the STBY period where it didn't previously exist), then I believe you would get xtra compensation.

But that, of course, is a different scenario.

 

I don't think we gave that one to the company. This is one of those "that's the way we've always done it" things. Been doing it that way long before any contract existed. All that aside, I would still be very suspicious about the rest of the CBA.

I'm still looking for all the hidden money

Hopefully, this next time around EVERYONE will actually READ the contract before voting in favor of it