Originally Posted by
flyboygt
I will read it all again. And look even closer at the language. Luckily we have almost all month to make as informed decision as possible. Based on current readings and interpretation I'm a yes that being said I'm very open to all input to clarify any misleading language that I missed or misinterpreted.
The contract may seem long but in reality it's pretty short. I mention this because there's a lot of stuff not in there. For example, in the healthcare section, the company doctor gets contract power to do things but there aren't 10 pages worth of healthcare information protection clauses. Also, rather than spelling out hard boundaries for the Dependability Policy, it 100% outsources externally to a document BJ can still change at whim. Also, since it doesn't say how many infractions are too many, so they can hang you whenever they want or based on who you are - there are no constraints so it's entirely subjective. It's unequal treatment. The apologists will say that it won't affect you (same thing the chief pilots say) unless you're a bad guy but it doesn't change the fact that it's in the contract, and a contract is a contract. There is no negotiation after it's signed - it won't be like the current FSM, BlueBook, or PEA where there is negotiation involved in application.
Also, things like positive contact are still not sufficiently and explicitly defined. In the past, BJ has gotten a pilot in trouble for standing firm on their position that leaving voicemail is positive contact. Apologists will defend BJ saying that it hardly ever happens but it doesn't change that it DID happen.
Lastly, notice how they vaguely allude to JETCRW as a means of positive contact but they don't get specific. BJ can simply push the notification to JETCRW but there are too many plausible scenarios where you don't get the message, yet you're now legally liable under the power of contract law.
I've only cherry picked the easiest examples but almost every section has some large weaknesses. Flow chart things out... diagram them... "what if" every sentence. A good contract will not have loopholes or holes. If we allow this, it will be 100% OUR fault.
Lastly, there's no language that limits BJ in most sections. The contract draws out pathways but it doesn't limit them whenever the contract has nothing to say about an issue. For example, it doesn't say something like "pilots shall not be assigned any duties not inherent to FAA certified Airmen. Currently this only includes: preflight duties, navigation, emergency procedures, informing passengers, maintaining safety of flight, following applicable 14 CFR, ICAO, regulations, etc......." It's open ended so that tomorrow they could attach more strings to commuting or even getting your "crew meals" by simply putting out another training CBT that has you put your initials that you agree (a contract). So tomorrow there's nothing stopping them from making you cleaning toilets or push wheelchairs or even driving a jetbridge. TA 1.0 draws a pathway, but doesn't really limit them in any way.
If it's not explicitly written in the contract, it doesn't exist.
This communique is for entertainment purposes only. It does not implicitly or explicitly acknowledge employment with any air carrier nor is any relationship implied. This communique does not represent the opinions or policies of ALPA or JB ALPA and does not represent the collective pilot group, ALPA, nor does it imply collective bargaining, advocacy, or workforce actions intended to disrupt operations.