When you have "beeper available" in current book, that's enough for me. Current book doesn't keep up with the way this place operates anymore. Between planning and execution their are almost 40% more restrictions than current book. On top of that, we are forcing the company to invest in needed IT for US! Something that should have been done a decade ago.

 

2% on 1.3 billion is about 26 million dollars that we as a pilot group are giving up. Personally, it's only about $2,300 for me. One of my lines in the sand was full retro. Now "full" retro is just about impossible to categorize as it means different things to different individuals. However, I think the majority would agree that full retro includes work performed at the new pay rates, and NEC match on that worked performed. I'm not a smart individual, but it seems to me if the new NEC is 17% then the Retro should have a 17% NEC match. Heck, it should include another 1% into the MBCBP as well.

There are a lot of things in the new contract I'm happy with. I can overlook the pay rates because with our rigs we come out ahead of our peers in the LNB category when you compare min guarantee to min guarantee. I can also overlook the lack of monetary penalties in the implementation plan for the company not meeting it's deadlines.

Side note, I found it interesting that in the implementation plan if the company does not meet the payout of Retro on 20 Feb they then have to pay a 17% NEC match vice a 15% NEC match on the retro payment. Do you think they are going to miss that deadline? Just imagine if there was more language like that in the implementation plan.

However, I can most definitely send it back because of not getting "full" retro when a portion of that retro is easily definable. I can't in good conscience reward the company for dragging this negotiation out. I have no idea how much longer it would take to get TA2. However, I know I'm willing to wait as long as it takes. The more we go down the RLA pathway, the more leverage we weld. That being said, this TA will pass with at least 70% voting yes and I'll be ok with that. Each individual has to make an informed decision on what's best for them and their family and I will not fault them for that. We are empty nesters and my retirement plus half of monthly guarantee covers our bills easily so I can wait as long as needed without any financial pressure on the family side of the house...

 

Now you are moving the goal posts.[/size]

Nobody said anything about getting a flat tire today.

The subject was premium and parking for a co-terminal call out.

The language that YOU posted shows if you beat the callout you get paid premium. If you get stuck in cross town traffic the company puts you back on reserve.

You made the claim "Here is the language and nowhere does it say you'll lose the pay. "

Your claim appears to be incorrect given the very language you posted.

I really don't care since I don't live there. But it seems strange that some pilots are such big cheer leaders for co-terminals that they can't see how the company will realistically handle the situations that are written in black and white.

.

 

Reason there’s not 17% on the RB is because the RB is for work completed in the past…when NEC was 15%. We’re capturing NEC on all RB periods whereas UAL and AA only got NEC on 2023.

I thought they should have made it so the 17% is effective the 1st full month post ratification (or Feb). They’d have to pay it in arrears as Schwab needs more than 8-10 days heads up but I’m fine with that. Waiting til March is lame….but it’s not my line in the sand….simply an annoyance.

 

no, I'm just offering a scenario where one might not be able to make push. Now play it out today under current book and then tomorrow under the TA for both an open time premium award and a reserve assignment. Co-terminal or not, does not matter...the answers will be the same.

 

So lets think this through. They will pay a reserve premium in this instance. But yet if you don't make it, you lose it and go back on reserve. So the reserve calls scheduling and says he/she won't make push. Remember, this is three hours PLUS one hour before push. Do you really believe it would benefit the company just to send the guy back home? Doesn't make any sense. If they can't make it they burn the RAP. When he or she gets back home that's another three hours to start the clock. So they wind up reassigning some one else with all these silly overides now that are on top of the rig. The company "CAN" put you back on reserve. They are only screwing themselves in this instance. Somebody else is going to get premium. And most likely they burn a reserve for the day. Because if their is traffic going to IAH or ORD, it's probably going back too. Since when has SWA ever cared about pushing ontime? Their EMO's are a joke. That provision is only in their so IF they decide to JA/reassign somebody and you can't make it, they are not paying premium to both.

 

So the work the RB captures in the past is being "trued" up to new negotiated rates, correct?

If so, that same reasoning means the NEC match should be trued up to new negotiated NEC? What's the difference? Again, I'm not a smart individual so please tell me what I'm missing (this is a sincere question BTW)...

 

I guess now I have to trade my beeper in on an Apple Watch.

 

I voted on dues increase for 2023, not 2022, 2021 and 2020. So SWAPA can keep their gruby hands off my money! SWAPA has already collected 1% extra dues for most all of 2023 if not all and now they want another 1% for 2023 so now thats 2% for 2023 and 1% for the previous years as well. SWAPA going to have to do better than that, because it seems to me they only try to represent about 1/2 of the pilot group.

 

The ratification bonus ends Dec 31st 2023. Thats the old pay rates and NEC of 15%. The true up's eventually go to 23% of all of 2023. New payrates take effect Jan 1st and that's 29.5% increase. Bonus is based on past W2's and not the new and includes the NEC portion. I do like the fact if they screw payroll up in FEB we get 17% NEC. I'm pretty sure they won't let that happen.