Ahh, Bach! Thanks

 

We really need better better protections for GS assignments, especially for reserves. Woken up at 0200 (30 of us), which I was ok with since I could actually be awarded it. I hit accept and acknowledged it in ARCOS. The trip showed on my schedule and even had the proper PB days placed (50/50 on that usually). Woke up to get ready, and only checked my schedule to look at something else, and the trip was gone. Look back and my schedules says removed because they skipped a SC. To me, them not doing their due diligence and ensuring they checked for reserves available should be the cost of doing business. Maybe then they wouldn't be in such a hurry to send it to so many pilots, especially when you're waking pilots up in the middle of the night.

 

This is on my list of things to fix in the next contract. As a Reg, you would be guaranteed single pay. As a Res, you get nothing.

Therefore I submit we should "Establish Reserve Rotation Guarantee". Once it hits your schedule, you should be guaranteed the pay and/or credit.

 

You're only guaranteed it within 2 hours of report per 23.Q.12, which is the justification they used to remove it. Striking 23.Q.12 would be a great start. Either way, both line and reserves should have the same protections. If it goes out to ARCOS for GS coverage (especially if you start waking people up), it someone should at least get pay/credit for the trip.

 

Harrrrumph!!

 

That is not cool. It's bad enough when it NOOPs but when it's their own mistake and you wake up super early for nothing that hurts!

 

I agree. Once it's on your schedule it should be guaranteed pay/credit. We adjust our lives for trips that are on our schedule.

 

Most AUG RR's that I've done/seen have not gone on timecard or even RR on the monthly schedule. Supposedly they're all "hand reviewed" now and the consensus is that takes 2+ weeks. Some rotations actually DROP in credit (if the RR takes a hard fly trip down to an ADG trip) and all there may or may not be is a vague comment burried in the rotation itself.

This will either be a well oiled machine with a company SME on the case in a week or two, or it will be a "deny deny deny" and get paid 6 months later after you can prove it scenario once we break the April ACE backlog.

Good thing we're playing footsie refunding 0.05% dues.

 

ALPA simplifies all reroute calculations so that 100% of reroutes pay premium.

Pilots: Thanks ALPA for "letting" them pay us less!!

 

The general problem with reroute and how it interacts with the time card is because of ancient technology and the patchwork of reroute rules over the years. DBMS never really caught up, which is why there isn’t a “unified” or even “coherent” display of reroute pay.

Reroute pay for getting back late (23 L8/9) came first, then that is why it has its own little spot on the time card and little RR notations on the schedule display. It’s been around long enough for DBMS to catch up and is kinda automated.

Mid rotation reroute end state (pre-2019) came much later, with a much more painful history of language and grievance settlements. That’s why there is no automation for it, and they have to figure it manually. When they finally get around to paying it, it’s this obscure status code like 4F1R.

The first mistake people make is that reroute pay is just reroute pay. There are different triggers and different pay treatments depending on the exact nature of the reroute. The second is assuming the person explaining it is correct, which while with good intentions, isn’t always the case. The best thing to do is go to the source.

I agree that reroute pay, all reroute pay, should be clearly itemized on the time card. The new L4 language should also facilitate automation.