Originally Posted by
Hotel Kilo
A very silly rant and well out in left field for what we're talking about here.
Not true on many levels. For one, all I'm doing is using a system, one provided by the company and that's in our PWA. The fact I make the choices in iCrew for auto accept and auto acknowledge is nowhere close, or can be construed as a job action.
What the 49'ers did was something absolutely different. This is not even in the same universe.
Again, auto accept and auto acknowledge are agreed upon tools by both the company and the association. How they are used is not a job action as they are provided features of the system. No judge is going to look at you and say that you committed a "job action" by utilizing a UI that is supported, provided by the company and codified in a PWA.
The point I’m making is a pilot advocating widespread usage of auto accept for the
express purpose of grinding down trip coverage times can certainly be viewed as a job action.
You’ve been here long enough (as you like to remind everyone) to know that the company will go tooth and nail if it starts costing them money or disrupting the operation. We’ve all seen which side the judge/arbitrator usually takes.
What the union has put out, and I fully support, is that each individual may want to consider using auto accept for the reason it was designed - to minimize disruptions when not actually up for a trip.
Your point about the UI doesn’t hold. icrew is the very same UI used to elect or not elect GS’s. We did stop using green pieces of paper btw in case you’re not aware
Individual choices = fine
Collective action that results in disruption = giving them an argument unnecessarily
Words matter