Originally Posted by
waldo135
Just to play devil’s advocate for a second…With greatly expanded batch sizes, trips would get covered much faster, less 23M7, so less guys with blanket GS in trying to get paid for violations with no chance of actually flying a GS. Also, with larger batch sizes, less chance to no chance of batch size violations, so less people putting in blanket GS just trying to get paid for those violations. And, if there was NO batch size, there would almost never be a 3AM call since trips would be covered in 30 minutes or less vs the HOURS it takes now.
I’m not advocating for no batch size limit, but increasing it has definite upsides. For those that keep claiming “we shouldn’t fix the company’s problems”, let’s be honest and admit that we (through everyone putting in a blanket GS just to try to get paid for violations) is making the problem much worse that it should be.
I beg to differ! Before we had batch size limits I got numerous ARCOS calls during 'quiet hours' (let's say midnight to 5am?) that were remarkably similar to my example scenario. I.e. the trip was many hours away and they had
plenty of time to cover it by calling only one pilot at a time (the respectful thing to do), instead they called everyone at once and woke up 10-15 pilots needlessly. And again...hence why we have batch sizes.
I agree that batch sizes need to be tweaked and maybe we need dynamic limits based on how soon the trip starts. But don't think for a second that they will magically cover trips more logically without batch limits.
As to the harvesting of violations with blanket GSs, maybe if they didn't violate the batch sizes so much pilots wouldn't all have GSs in to catch those? I mean, this is a multi-billion dollar corporation right? They should be able to handle programming ARCOS to correctly follow the PWA?
