if I called scheduling first about every violation i saw I would be on the phone all day

Kind of funny coming from the same people who were begging us all to “get our slips in” a year or two ago.

Yeah, getting a million pilots paid for "batch size" violations is the least of my concerns. I'd give that up in a second for an equivalent amount of money in any other area.

But...a contract is a contract. So I want that paid as appropriate. What I really want is an instant remedy for RR and coverage issue instead of the "fly now, grieve later, and maybe get paid months down the road and get nothing if you don't catch it in real time with a million moving pieces going on" system we have.

I remember a time not too long ago when Deltanet proudly tracked the number of consecutive cancel-free days. And it was generally an impressive number. You know, back when management actually cared about running a tight operation. If we truly are properly staffed (as we keep hearing over and over), when do we return to those days? We were still making $ by the truckload, by the way.

I feel like some lackey built a spreadsheet showing how long we can keep loyal customers based on the memory of that time, but not actually spend the resources it took to make it happen. As long as that timeline is longer than someone’s retirement plans, it’s all good!

Because 78% of pilots prefer shiny coins rather than work rule gains?

do you think there were no work rule gains in the new CBA?

100% agree. Some like to WS and that’s their business. I admit, broken trips are nice. But I’d much rather fly right to the GS trigger (no straight pay over the trigger) and then pick up one nice 2-3 day greenie near the end of the month and call it a day. The goal isn’t to work as much as possible, it’s to get as much pay for the least amount of work possible

I think this is predominantly an issue in the larger NB categories, like ATL 7ER. To your point, they’re not getting thru 400+ pilots 5 at a time in a reasonable time, so I’m not surprised that they’re pulling the IA trigger at 3 prior. I’m not saying it’s right or that I agree with it, the system is clearly broken. But that’s the simple reality of the situation.

I haven’t witnessed the same shenanigans on the NYC 73. Yes we have our fair share of IAs, but the category is half the size of the one’s really getting beat up by 23M7.

the blanket greenies in the system are certainly bogging it down further, but there isn’t any way to validate who’s planning on flying if called, vs just leaving one in the system for violation purposes. Either way, it’s legal per the PWA and I don’t expect it to stop any time soon.

I’m really interested to see how the next few months play out. Reserve coverage moving to 18-hour callouts is bound to stress the system (that is so reliant on short notice coverage). It will also be interesting to see how the company handles the new reroute pay implementation on 8/1 - will they magically stop rerouting crews the way they’ve tried to seriously limit 30 hour layovers? Or will they just fork over the cash hand over fist and reroute the crap out of folks business as usual? This summer is going to be…

I’m also interested to watch the changes at work. My hunch is that starting the coverage ladder a full day earlier than baseline will more than offset the effects of 18 hour LC. SCs will potentially be assigned earlier and more efficiently, GS will flow earlier to the benefit of commuters. Out of base reserves will be allocated cross-country more easily. 23M7 usage will likely drop. All in all I think we will see less chaos, which I believe will help more people than it hurts. Naturally there will always be winners and losers though…