Originally Posted by
cencal83406
The scenario is “I was assigned short call, and at some point prior to the short call window starting, I received a short call rotation.”
Agreed, that's what I was saying (and, I cited the risk of a potential change). I disagree with your conclusion, though. To flesh out the scenario: Say I live three hours (drive) from base. I have SC starting at 1000 assigned early, have NOT invoked NC, with a rotation reporting at 1300 assigned at some point after 1900 the night prior (so, less than 18 hours). I have failed to take your excellent advice and checked my schedule even though not required and see the rotation. I acknowledge same in iCrew.
I now have an acknowledged rotation on my schedule. I need to leave my house at 1000 to make my report time, and I like to pad that by :15 minutes for potential traffic--so I leave at 0945. At what time am I contactable for that SC period? I think §23.S.9.b.2) is rather clear on that.
If the sched gets changed and they call me at 1000 to tell me to be there at 1005... well, that's the rub. "Risky?" Perhaps--but that's not my point. If I've checked my schedule and "depart[ed] to report for an awarded/assigned rotation," where have I failed to meet my contractual obligations?
Originally Posted by
cencal83406
Also, you’d blow up the whole trip coverage ladder if you did what you propose (“not pre-post short call assignments”). The problem is that pilots are hell bent on looking at their schedules. Let 23.M.6. and 23.N. or O. do the job. When you’re within 18 hours of your SC start time, just de-couple since you’re released from duty.
That's a fair point all the way around....