JS Disagreement
 

So UAL is pretty tilted at what’s going on between our JS committe and UAL.

Reading some of the posts over on the greener pastures forum (UAL forum) it looks like these guys/gals are fuming.

It wouldn’t turn out well for us, in the sense we would have a lot more to lose as OO would never positive space us like mainline would for their people. Also the optics look terrible since we aren’t unionized and are supposed to stand in solidarity with other unionized carriers.

What y’all think, cooler heads will prevail right?

Depends on the United MEC.

Hope they figure it out. It’s pretty embarrassing the way the student council is handling this. For example sending out threatening letters escalating the situation instead of trying to diffuse it.

Dunno I see it as proactive.
The united computer system is going live in the next few months.
Preventing a computer system or altering the code seems easier than getting United to spend money on it after it has been implemented.
I’d rather this situation not be reactionary because it would go full nuclear quickly. All imo.

The only person calling for a JS war is and was *** Who’s the hot head here?

Your own thread in your forum is called jumpseat war? Smh

Also I don’t think it’s fair that someone from here took a picture on our forum giving out the guys name. That’s lame and unfair.

Also if you look at my post I used the word tilted, not hothead...

SMH.
Yea because *he* PLAINLY stated that at the end of his initial OFFICIAL communication. Jumping straight to level 10 rage is probably why he still works at Skywest.

I have clearly stated that I’m embarrassed by it. You are honestly preaching to the choir with me. The situation was escalated by the letter for sure.

Let's be honest, UALPA trying to dictate jumpseat priority on our metal is nearly just as bad. Don't get me wrong, denying jumpseats is a childish way to handle anything. His tact was definitely not well though out. Hopefully cooler heads prevail on both sides.

Update just came out. Said expect something jointly from all UAX operators... will see..