Dunno...just checked the Shuttle America employee site and there is nothing there.... yet.

UAX guys have been getting kicked out of their own jumpseats. The problem is several years old, and is being ignored by UAL management (not surprisingly).

Unfortunately UA Alpa hasn't been helpful either, so this is an attempt to get the UA union to pressure the company into making a simple fix.

The folks working on this have been trying for 2 years...I guess they think this is the only.

Personally I'm pretty uncomfortable with this...it feels draconian, but I suspect it is being driven by some UAX commuters who are justifiably POed about getting booted off their own airplanes. I agree that all RJ's (and RJ pilots) should be on mainline's list, but that was out of OUR hands a long time ago.

I guess any time we get a JSer, somebody needs to walk up and make sure that nobody is getting left behind out of priority.

Bingo!!! How do you guys think the other mainline carriers will feel about this? Maybe you should think twice about that one. :rolleyes:

An unfortunate reality.

After almost happening to me (only saved by the CA seeking a cup of coffee) I made it a habit to check for jumpseaters on every turn, hub or otherwise. Never caught anybody getting put on out of priority, but did find a few JSers the agents never told us about - and they ALWAYS got on.

Originally Posted by Flex81:
"So let me get this straight... You (UAX) are going to kick mainline pilots off of your jumpseat, on a lot of routes that SHOULD be flown by mainline anyway, just because of a computer glitch. Good luck with the war you are about to start."

I am shocked. this business will get out of control. Can’t you see what this will do for you and everyone else at UAL/UAX? Not to mention the repercussions from other pilot groups. Flex81 is right: You don’t realize that ONLY BAD THINGS will come of this.

(On a side note, I’m sad to hear of Alaska pilots’ group threatening some sort of embargo on their jumpseats as well).

First and foremost, leave those decisions to the PIC. I know in my airplane, as I am a commuter and realize what a privilege we all share, NO ONE gets left behind if I can help it. And in the case of a computer malfunction or mismanagement or whatever, the PIC should always be coherent about his jumpseat. If a mainline or feeder pilot is waiting, YOU know your company’s rules. Use ‘em. It takes two minutes to run up to the gate. But banning your mainline bretheren altogether is simply a knee-jerk decision by someone who should be pulled aside and adjusted. To support this behavior will only damage the years of work and the foundation of our fellow pilots’ reciprocity.

Well then, have UALPA pressure UAL mgmt to change the jumpseat software so the agents don't screw US out of OUR jumpseats.

Mainline brethren......maybe when mainline starts acting their age about this kind of stuff, will we think of them as brethren.

This is quite possibly the most moronic thing I have ever heard of...I hope its untrue.

This action is a truly horrible idea. I never "voted" on it, and I would have voted against it given the opportunity.

This action is not likely to fix the problem, but it will most definitely strike a nerve with United pilots - a pilot group that doesn't need any more dung on its plate. This is a relatively small "deal" in an era of much bigger industry problems. It's not the pilot's fault the "computer glitch" hasn't been fixed.

I fear this will come full-circle to regional folks who rely on mainline to commute. (A number I would guess is larger than the number of pilots who rely on regional service to commute - but that's just a guess.) I hope regional captains will not support this - at least not at my airline. For the first time, I am going to be embarrassed to show my credentials to a United captain.

I don't think many captains will support this.

Well, true. But there was a time not too long ago when UAL pilots had a lot of "dung on their plate" and they were able to change their existing JS policy.

If you remember, UAL (and other "legacies") used to have some very archaic JS policies. ONLY as many JS'ers allowed to ride as JS's installed on the aircraft. You could be trying to JS one of their 767's, if the plane was half empty and there were 2 other JS'ers there before you, you were not getting on.

The problem here is that it's a software issues and not a policy issue.