23.M.7 Updated
#241
Gets Weekends Off
Joined APC: Nov 2011
Posts: 4,535
#242
Gets Weekends Off
Joined APC: Feb 2008
Posts: 19,599
#244
Roll’n Thunder
Joined APC: Oct 2009
Position: Pilot
Posts: 3,838
There's a difference between being on an assigned rest period on a trip or as a reserve vs just being "in rest" on your days off. They can obviously call you a million times on your off days, and you can be called and accept a GS/IA that reports in 5 minutes and be perfectly legal. It does get sketchier if you are within 10 hours of a known trip report as far as calling more than once, but as always whenever you are in rest/on off days you are never, ever obligated to answer your phone or acknowledge any contact from crew scheduling.
#246
Please write your Rep about this. ALPA needs to know.
It would appear this is actually a Green Slip with Conflict; 4x pay (and at least single pay for the pilot who should have gotten it) and ACE the crap out of it!!!! Then consider calling in for the FAR117 violation that this actually is & ASAP that.
Especially after the big concession we made to avoid this kind of thing.
If you don't mind telling us, what fleet and seat was this on?
It would appear this is actually a Green Slip with Conflict; 4x pay (and at least single pay for the pilot who should have gotten it) and ACE the crap out of it!!!! Then consider calling in for the FAR117 violation that this actually is & ASAP that.
Especially after the big concession we made to avoid this kind of thing.
If you don't mind telling us, what fleet and seat was this on?
#247
Gets Weekends Off
Joined APC: Jul 2008
Posts: 5,016
#248
We got something…it’s just not something that was important to everyone. Plenty of commuters were rightfully ticked off that GS coverage moved so slowly and then transitioned into IAs that they couldn’t get the premium flying they were due nor track if the right person (or anyone) was paid appropriately. Even if you don’t commute, more foresight on green slip assignments can now make some rotations flyable that previously were not. That is what I see as the most valuable end state for the winners here (yes there are losers), with tracking and transparency being less meaningful. Those who previously scored IAs they never could have held as timely green slips, and local folks who weren’t as encumbered by delayed assignments as commuters were are probably the big losers out of the settlement.
Fair enough. I'll change my wording to, we didn't get enough, or put in enough guide-rails. I'm all for spreading the wealth to commuters, but the timing piece would probably have been solved by covering trips two days out, we really didn't give that time to play out. Short notice GS would have still taken some time, but most people were either in the short notice bucket or they weren't. At the very least we should have retained some semblance of batch sizes, and not the free for all we have now. The promise on 23m7 kinda makes me laugh, especially when we still have schedulers calling from non recorded lines to offer side deals. Getting woken in the middle of the night with a batch size of 999 for a single rotation is beyond ridiculous. Yes I know about DND, but we shouldn't be forced to take ourselves out of the running for trips because the companies archaic software makes it a PITA to layer our preferences or turn on/off auto ack. If we had made that step easier and kept batch sizes, maybe widened to something like a percentage of pilots in category, I'd consider it a good deal. I get that others think it was a good deal. Maybe I'm just extra salty because yesterday I was re-reading all the stuff that does NOT pertain to the 717 in the last contract lol. Screwed on pay, screwed on trip mix, etc... Get off my lawn!
Last edited by crewdawg; 07-28-2023 at 05:42 AM.
#249
Roll’n Thunder
Joined APC: Oct 2009
Position: Pilot
Posts: 3,838
I'm sure ARCOS is junk software, so programming this would be way more difficult than it needed to be, but the simplest solution was to have automatically increasing batch sizes the close to report a trip got as it ran through the GS roster. Eventually, say within 2 hours to report, you'd do the mass blast, but for stuff 12, 18, 24+ hours out, it would start calling 1 pilot at a time then ramp it up slowly over specified windows.
#250
I'm sure ARCOS is junk software, so programming this would be way more difficult than it needed to be, but the simplest solution was to have automatically increasing batch sizes the close to report a trip got as it ran through the GS roster. Eventually, say within 2 hours to report, you'd do the mass blast, but for stuff 12, 18, 24+ hours out, it would start calling 1 pilot at a time then ramp it up slowly over specified windows.
Thread
Thread Starter
Forum
Replies
Last Post