Calculating Reroute
 

1- How many times can one be rerouted when RES but on a GS? These were all on X days.

2- I was on a 2 day GS, 15:45 original credit. Day 2 was operate to ATL, then DH home. Instead when I got to ATL I was rerouted to operate a flight to BHM with an overnight. Day 3 was supposed to be operate back to ATL, then DH home on a flight w/ a 41 min layover. On the way to the airport my schedule showed a reroute again. I was supposed to operate to ATL, then fly a turn (both way) to VPS, then DH home. I acknowledge that change. But then that reroute (#2) was pulled from my schedule and instead I was booked on a different DH that was 1 hour after the first DH flight later so technically another re-route. Again, all 3 days were X days.

I don't think they have credited my pay correctly. I see RRPY on my time card, and then an L9 line below it. I want to make sure I'm credited correctly for all of this mess.


Day 2 Scheduled GS
STL - ATL
ATL - DTW (DH)

Reroute Day 2
STL - ATL
ATL - BHM


Day 3 Scheduled Reroute
BHM- ATL
ATL - DTW (DH) (flight A)

Day 3 Reroute given on day 3 and pulled
BHM - ATL
ATL - VPS
VPS-ATL
ATL - DTW (DH)

Day 3 final reroute
BHM - ATL
ATL - DTW (DH) (flight b, 1.25 hours after flight A)

They can reroute you (after the first leg) all they want (basically). For calculating the pay, you only compare your original rotation with the final rotation when you block in.

Anything on day 2 pays 50% of Block + Minutes Under. Every leg on day 3 pays 100%, plus any trip credit also pays 100%.

Any reroute that you receive but don't actually operate is irrelevant. All that matters is what your final rotation as flown looks like vs what your original rotation was scheduled. Just spitballing but assuming day 1 was just DTW-STL, I'd say L4 RRPY should be around 11-ish, maybe 12, somewhere in there. Basiically take 15:45, minus the block of DTW-STL and STL-ATL, minue 1/2 of ATL/BHM. That's roughly 3-3.5 hours total, so the rest is day 3 block and credit. L9 should be over 10. There is a scheduling alert (25 - 0 something) that lays out exatly how to calculate L4 using the archived rotation in icrew. Widgetcrew.com also has a paid subscription where you can just copy/paste and it'll walk through the pay, and there is a reroute app on the apple app store which will also do the math for you (can't remember if it's free or paid).

Do I get anything "extra" since my DH on day 3 actually rerouted again. I had Flight A originally, but after they rerouted me and pulled it, and then I was assigned flight B instead?

No. Like we both said, it's just comparing your original rotation to the final rotation when your trip ended.

Just for clarity, Res can be rerouted before the first airborne departure. And they can reroute you as many times as they want (but only one additional day, IIRC).

there are several apps/websites which will do allllll the math for you. Your massive reroute pay for this trip would more than pay for the rest of your career. Highly recommend. Widgetcrew.com, or “rerouted” on iPad Apple Store (with yellow icon).

There is only one way to calculate L4/L8/L9 reroute pay. This can only be done after the trip ends.

Once the (however diabolical) trip ends, it's compared to the original trip, and reroute pay can then be calculated.

The number of times you were actually "rerouted" during the course of the trip is irrelevant to the final pay calculation. It's the "originally scheduled" vs "as flown" that matters pay-wise. Hope this helps.

Just to clarify, for both REG and RES, once you are on a reroute you can be rerouted again and again and again UNTIL you reach your base. At that point the only two options scheduling has are to have you rejoin your rotation either directly from your base or via DH, or to release you from the rest of your trip. You cannot be rerouted through your base (but your reroute can start in your base, that’s different). Lastly, if they do attempt to reroute you through your base that is not a fly now, grieve later deal. You can simply walk away from the rotation.

Point of order. 2nd reroutes off of your original pairing after you have joined back up don't pay 50% before the break in duty. They go straight to 100%.

Rerouted+ on the App Store for your iPad, as others have said.

SRH page 151 (pay examples start on page 154) to learn the ins/outs of RR pay

Rerouted+ app to actually do the math.

I thought that's what I said. Once the rotation is over, you find the first rerouted leg vs the original rotation and the first break in duty after that reroute. Everything after that break in duty pays 100% RRPY. It doesn't matter how many times or how frequently a new "reroute" came off the ACARS printer.

Fixed my post for clarity.

Let’s say you have a four leg day. You’re a reserve pilot so the first turn gets swapped out before you even operate anything. Those two legs will be paid at 50%. Then you fly a leg that is part of your original rotation. Instead of operating to base for that last leg you get rerouted to deadhead back. That fourth leg will pay 100% above because it is a subsequent reroute after you’ve returned to your rotation, even though it is before the break in duty.

Has anyone ever had a reroute on a non-MAC charter rotation? Currently fighting a case. The SRH and the PWA state that you cannot change the origin or destination. you remove the pilot and rebuild the rotation. It’s an illegal assignment, but we flew it anyway and grieved later. So far, they disagree.

I don't believe this is true, but am happy to be corrected.

The SRH has this paragraph:

"If you are rerouted then subsequently returned to your original rotation, and then rerouted an additional time, the pay treatment continues to be single pay, no credit for any flight segments added to your original rotation, whether deadheading or operating. There is no initial one-half pay step in this instance, and any subsequent reroute will always pay single pay, no credit."

But that paragraph is sandwiched between 2 other paragraphs regarding break-in-duty. And the "continues to be single pay" portion seems to also reflect this break in duty. I don't see any PWA reference to support what you stated either.

Again, I'm happy to be corrected on this.