Reserve for Dummies
#1761
Line Holder
Joined: Jan 2008
Posts: 1,775
Likes: 18
#1762
Gets Weekends Off
Joined: Oct 2013
Posts: 523
Likes: 1
to close the loop.
I spoke with scheduling. They agreed that:
I was NOT properly notified of 30 hours of rest. So that went away.
I WAS properly notified of short call. So I’m currently sitting short with 30hr rest to follow. (I’m 117 legal for short).
for the 350 types….
scheduling intended for this to be an FRMS shortcall. But nowhere in the CNO was FRMS ever mentioned and the wording was completely different than previous mid-block FRMS shorts I’ve gotten.
>BUT< scheduling also agreed that I was not properly notified of the >= 24 hours of FRMS rest required for an FRMS short call …. So this turned into a regular short.
I spoke with scheduling. They agreed that:
I was NOT properly notified of 30 hours of rest. So that went away.
I WAS properly notified of short call. So I’m currently sitting short with 30hr rest to follow. (I’m 117 legal for short).
for the 350 types….
scheduling intended for this to be an FRMS shortcall. But nowhere in the CNO was FRMS ever mentioned and the wording was completely different than previous mid-block FRMS shorts I’ve gotten.
>BUT< scheduling also agreed that I was not properly notified of the >= 24 hours of FRMS rest required for an FRMS short call …. So this turned into a regular short.
#1763
Banned
Joined: Feb 2022
Posts: 874
Likes: 0
#1764
Line Holder
Joined: Mar 2014
Posts: 509
Likes: 21
From: 757/767
ACE in this context has nothing to do with 117. He misspoke. ACE is in no way comparable to FCView. You don't seem to be grasping the capabilities that were about to be turned on with the ACE app that we just significantly set back when the MEC dumped the app.
#1765
Before diving into this, I've dug through the SRH, PWA and the Scheduling Comms. The scenario is an extension/RR from an international diversion resulting in a Return-To-Base w/in 25 hours, but interupting the an X-day with no RES days left in the month.
On the way home (DH ocean crossing(as scheduled, NON-Deviate)) we ended up diverting for a medical and Op. crew timing out. After a break-in-duty (legal rest) my DH flight # was changed to an earlier DH than riding with the original crew, and I was RTB on a NON-ocean crossing flight. (the second segment DH didn't involve an ocean crossing. (Clear as mud??) Sequence: Ocean cross scheduled DH/divert/beak in duty/Non-O.c. DH home.
On my iCrew month schedule it's showing RR in the far left column.
On my timecard pay/credit is for the rotation 'as operated' (TRP rig applied, which is higher than TBL+TDHD+TMU and is also higher than ADG)
Looking through the listed references, i don't THINK that this is going to trigger any RR pay since the original schedule was a O.Cross and they returned me to base w/in 25 hours.
My questions are:
1) even though it was on an OC scenario, it interupted an X-day with no further RES obligation; shouldn't I get 2 banked PB days? (Block-in + 9 (13 if you really want to argue the OC scenario) into my X-day +24 causing a PR on my second X-day, to be banked as a 2nd PB due to no more RES??
2) is my interpretation of the RR pay treatment correct and I'm probably not going to see any RR pay since it's an OC and I'm a RES.
Trips been CLSD since Saturday and my number of 'PB available for use' is still showing 0.
References:
PWA 23.S.11. ("flies on an X-day due to an IA, GS, or reroute", RR is my question)(RR not caused by airport closed due to weather)
SRH rev 17 pg 117
On the way home (DH ocean crossing(as scheduled, NON-Deviate)) we ended up diverting for a medical and Op. crew timing out. After a break-in-duty (legal rest) my DH flight # was changed to an earlier DH than riding with the original crew, and I was RTB on a NON-ocean crossing flight. (the second segment DH didn't involve an ocean crossing. (Clear as mud??) Sequence: Ocean cross scheduled DH/divert/beak in duty/Non-O.c. DH home.
On my iCrew month schedule it's showing RR in the far left column.
On my timecard pay/credit is for the rotation 'as operated' (TRP rig applied, which is higher than TBL+TDHD+TMU and is also higher than ADG)
Looking through the listed references, i don't THINK that this is going to trigger any RR pay since the original schedule was a O.Cross and they returned me to base w/in 25 hours.
My questions are:
1) even though it was on an OC scenario, it interupted an X-day with no further RES obligation; shouldn't I get 2 banked PB days? (Block-in + 9 (13 if you really want to argue the OC scenario) into my X-day +24 causing a PR on my second X-day, to be banked as a 2nd PB due to no more RES??
2) is my interpretation of the RR pay treatment correct and I'm probably not going to see any RR pay since it's an OC and I'm a RES.
Trips been CLSD since Saturday and my number of 'PB available for use' is still showing 0.
References:
PWA 23.S.11. ("flies on an X-day due to an IA, GS, or reroute", RR is my question)(RR not caused by airport closed due to weather)
SRH rev 17 pg 117
#1766
...
My questions are:
1) even though it was on an OC scenario, it interupted an X-day with no further RES obligation; shouldn't I get 2 banked PB days? (Block-in + 9 (13 if you really want to argue the OC scenario) into my X-day +24 causing a PR on my second X-day, to be banked as a 2nd PB due to no more RES??
...
My questions are:
1) even though it was on an OC scenario, it interupted an X-day with no further RES obligation; shouldn't I get 2 banked PB days? (Block-in + 9 (13 if you really want to argue the OC scenario) into my X-day +24 causing a PR on my second X-day, to be banked as a 2nd PB due to no more RES??
...
I talked to C.S. and, even though the last activity was a non-O.Cross segment, it was still caused by the O.Cross event. When calculating PB/PR days the system automatically takes block-in+13:30 to do the calculation. In my case the flight blocked in at 09:25 + 13:30 = 22:55 on my first X-day.
I'm still confused as to whether I should get 1 PB day (the one X-day interupted) or 2 PB days (the one X-day + 24 hours).
#1767
Roll’n Thunder
Joined: Oct 2009
Posts: 5,170
Likes: 581
From: Pilot
I don't like to quote my own post, but I had to correct/clarify this statement, and it's been too long to edit.
I talked to C.S. and, even though the last activity was a non-O.Cross segment, it was still caused by the O.Cross event. When calculating PB/PR days the system automatically takes block-in+13:30 to do the calculation. In my case the flight blocked in at 09:25 + 13:30 = 22:55 on my first X-day.
I'm still confused as to whether I should get 1 PB day (the one X-day interupted) or 2 PB days (the one X-day + 24 hours).
I talked to C.S. and, even though the last activity was a non-O.Cross segment, it was still caused by the O.Cross event. When calculating PB/PR days the system automatically takes block-in+13:30 to do the calculation. In my case the flight blocked in at 09:25 + 13:30 = 22:55 on my first X-day.
I'm still confused as to whether I should get 1 PB day (the one X-day interupted) or 2 PB days (the one X-day + 24 hours).
#1768
Thanks. I was looking at all the examples in the PWA and SRH and they all showed examples with RES days left. Since those all showed the '24-hours' into the next RES day, I was a little confused.
#1769
Roll’n Thunder
Joined: Oct 2009
Posts: 5,170
Likes: 581
From: Pilot
What confuses most people is that if you release before 1500 for a domestic rotation, your PB time starts on that day (9 hours after release). So a 1 day GS on an X day that releases at 1000 only generates a PR on your next LC day until 1900 (24 hours from 1900 on your X day with the GS until 1900 on your first LC day). Lots of people think they should see a full PB day AND a PR on their schedule and that is not correct.
#1770
What confuses most people is that if you release before 1500 for a domestic rotation, your PB time starts on that day (9 hours after release). So a 1 day GS on an X day that releases at 1000 only generates a PR on your next LC day until 1900 (24 hours from 1900 on your X day with the GS until 1900 on your first LC day). Lots of people think they should see a full PB day AND a PR on their schedule and that is not correct.
Thread
Thread Starter
Forum
Replies
Last Post




