Airline Pilot Central Forums

Airline Pilot Central Forums (https://www.airlinepilotforums.com/)
-   American (https://www.airlinepilotforums.com/american/)
-   -   Jumpseat Battle Brewing (https://www.airlinepilotforums.com/american/133397-jumpseat-battle-brewing.html)

sanicom3205 03-22-2021 03:57 PM


Originally Posted by magnus0322 (Post 3210217)
How many is numerous? Or was it just a few rogue CA? You really think if the number was as large as you insinuate with your strong language that there would still be a JS agreement for YX on AA? Look at all the heartburn asking why AA gets priority but YX does not is causing

Sent from my GM1917 using Tapatalk

Moving the goalposts yet still putting words in my mouth.

I said “multiple recorded instances”. That’s my strong language?

sanicom3205 03-22-2021 04:11 PM


Originally Posted by Cyio (Post 3210288)
Did they ignore them or did they disagree with it? If they flat out ignored them, well I don’t know what to say. Does the agreement have an amendable date attached to it?

As to your second point, I have no idea.

I guess my issue with this approach is that a contract or agreement should mean something. If we can just up and change agreements at will, or worse choose to ignore said agreement at will, they will forever lose their power.

It’s like a child asking for a cookie.... you ask and get told no the first time. Asking more and not getting a response on the sixth try doesn’t mean you got ignored.

Im not calling republic children, it’s just an example.

Did your union tell you guys we didn’t answer?

captive apple 03-22-2021 05:04 PM


Originally Posted by Cyio (Post 3210288)

I guess my issue with this approach is that a contract or agreement should mean something. If we can just up and change agreements at will, or worse choose to ignore said agreement at will, they will forever lose their power.

You are right, Republics only option they can take unilaterally is to end the Jumpseat agreement between republic and AA. It is a bad option but one I think they will take after these direct talks break down.

LAXtoDEN 03-22-2021 05:23 PM


Originally Posted by sanicom3205 (Post 3210316)
It’s like a child asking for a cookie.... you ask and get told no the first time. Asking more and not getting a response on the sixth try doesn’t mean you got ignored.

Im not calling republic children, it’s just an example.

Did your union tell you guys we didn’t answer?

So are you like the APA VP?? Who’s “we”??

sanicom3205 03-22-2021 05:30 PM


Originally Posted by LAXtoDEN (Post 3210365)
So are you like the APA VP?? Who’s “we”??

Acting like you don’t know that I mean the union of which I’m a member isn’t the look you think it is :cool:

Did Republic Teamsters say that The Allied Pilots Association ignored them? Do you approve of this wording lol

LAXtoDEN 03-22-2021 05:35 PM


Originally Posted by sanicom3205 (Post 3210370)
Acting like you don’t know that I mean the union of which I’m a member isn’t the look you think it is.

Did Republic Teamsters say that The Allied Pilots Association ignored them? Happy ?

Yeah alright sounds good bootlicker.

DocMcFly 03-22-2021 08:46 PM


Originally Posted by sanicom3205 (Post 3210370)
Acting like you don’t know that I mean the union of which I’m a member isn’t the look you think it is :cool:

Did Republic Teamsters say that The Allied Pilots Association ignored them? Do you approve of this wording lol

That’s the impression I got from them- ignored after many many attempts to contact and discuss the situation. Then both managements got involved because this really was affecting our pilots ability to commute to work AE flights. So we had IBT, YX management and AA management and AA IT working on this (pre-Covid) and they came up with a solution for IT to fix the software. AA management was not wanting to pay for the software fix (due to Covid) so YX management offered to pay for it. A band-aid was put in place that allowed YX pilots to tell GA about the fix to give us the priority we were asking for above OAL and they could do it manually. AA and YX management, AA IT, and IBT were all fine with the band aid until the software fix was done. Crickets from APA. YX pilots ran into some random issues with GA who weren’t wanting to play by the band aid established. Ok whatever we just moved along and made the best of it. AA management got back in touch with YX after Covid settled down to make the software changes and be done with all this- THAT’S when APA finally woke up and published Letter Q.

I’m not a union rep. I have spent well over 50 hours in the last two weeks reading up on all this and communicating with people trying to learn what was going on and figure out where the truth was in all the bologna.

I have had plenty enough interaction with our union reps to find them to be honorable men and women who have done an amazing job for us throughout the last year. Their communications to the members are always professional and timely. If they say they attempted to discuss this with APA and were ignored they have given me no cause not to believe them. These are the same reps who point blank said “Do not circumvent the current Js agreement” now and in the past. They have done nothing but attempt to go through the proper channels while telling our members specifically not to start a JS war as far as I can tell.

I did my best to create a timeline as was communicated. I’m not comfortable with writing this in stone but it’s the best I could glean from all the words flying back and forth and to and fro. If anyone has more inside knowledge or experience please feel free to correct me.

Wanderlust 03-24-2021 06:41 AM

AA has never embraced jumpseat reciprocity. When I was at a tiny commuter airline about fifteen years ago we would frequently take 8 or 9 AA pilot and flight attendant jumpseaters on a 19-seat plane between Tampa and Miami. We would also take them internationally. At the same time, American refused to take our pilots internationally and would not allow more than one or two jumpseaters at a time no matter how empty the plane was. The captain had no authority on it and would be overridden by the gate agent.

Sent from my SM-G973U using Tapatalk

Cujo665 03-25-2021 07:57 AM


Originally Posted by DocMcFly (Post 3210456)
That’s the impression I got from them- ignored after many many attempts to contact and discuss the situation. Then both managements got involved because this really was affecting our pilots ability to commute to work AE flights. So we had IBT, YX management and AA management and AA IT working on this (pre-Covid) and they came up with a solution for IT to fix the software. AA management was not wanting to pay for the software fix (due to Covid) so YX management offered to pay for it. A band-aid was put in place that allowed YX pilots to tell GA about the fix to give us the priority we were asking for above OAL and they could do it manually. AA and YX management, AA IT, and IBT were all fine with the band aid until the software fix was done. Crickets from APA. YX pilots ran into some random issues with GA who weren’t wanting to play by the band aid established. Ok whatever we just moved along and made the best of it. AA management got back in touch with YX after Covid settled down to make the software changes and be done with all this- THAT’S when APA finally woke up and published Letter Q.

I’m not a union rep. I have spent well over 50 hours in the last two weeks reading up on all this and communicating with people trying to learn what was going on and figure out where the truth was in all the bologna.

I have had plenty enough interaction with our union reps to find them to be honorable men and women who have done an amazing job for us throughout the last year. Their communications to the members are always professional and timely. If they say they attempted to discuss this with APA and were ignored they have given me no cause not to believe them. These are the same reps who point blank said “Do not circumvent the current Js agreement” now and in the past. They have done nothing but attempt to go through the proper channels while telling our members specifically not to start a JS war as far as I can tell.

I did my best to create a timeline as was communicated. I’m not comfortable with writing this in stone but it’s the best I could glean from all the words flying back and forth and to and fro. If anyone has more inside knowledge or experience please feel free to correct me.

Don't your pilots get employee/family travel on all three mainline carriers? Isn't that status well above the ZED status the rest of us get? That does not, nor ever will, happen for wholly owned carriers or other mainlines.

Should everybody at AA write letters to their companies, since we do full codeshares with them? Should all AA pilots go ahead of you on JetBlue and Alaska then also?

There are clearly advantages and disadvantages to going to a WO vs an independent contractor.
This is one of those examples.

JetBlue, Alaska and others have full codeshare agreements with AA..... why shouldn't they go ahead also? You are going down a slippery slope that ends in JS war. That serves nobody. Your union leaders should smarten up. Tell them to stop starting JS wars (third time in 12 years) and concentrate instead on helping guys get out of regionals.

Saabs 03-25-2021 08:06 AM


Originally Posted by Wanderlust (Post 3210839)
AA has never embraced jumpseat reciprocity. When I was at a tiny commuter airline about fifteen years ago we would frequently take 8 or 9 AA pilot and flight attendant jumpseaters on a 19-seat plane between Tampa and Miami. We would also take them internationally. At the same time, American refused to take our pilots internationally and would not allow more than one or two jumpseaters at a time no matter how empty the plane was. The captain had no authority on it and would be overridden by the gate agent.

Sent from my SM-G973U using Tapatalk

Same when I was at a commuter trying to get on AA. but that has ended a while back.


All times are GMT -8. The time now is 11:51 AM.


User Alert System provided by Advanced User Tagging v3.3.0 (Lite) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Website Copyright ©2000 - 2017 MH Sub I, LLC dba Internet Brands