![]() |
Originally Posted by SEDPA
(Post 1453088)
UCH managed each subsidiary since MAD per the TPA and each legacy contract, until the UPA became effective. Once the UPA was in effect, then UCH managed each side via the effective parts of the UPA, the applicable parts of each legacy contract, and the applicable parts of the TPA. Some believe that since it was the same company managing each subsidiary at MAD, nothing post MAD is relevant to the SLI. I think it is very relevant because it represents an equity that advantages CAL and disadvantages UAL. The TPA only protected 90% of your pre-merger block hours ... the CAL contract protected 100 % of CAL pre-merger block hours, and ensured that CAL aircraft orders and jobs went to the CAL side. If you argue a MAD "snapshot", and then only account for the UAL wide body "advantage" in a career expectation valuation, then viola, those 635 jobs created since MAD don't get a value.
|
Originally Posted by routemap
(Post 1453147)
CAL considered it, determined LUAL was over staffed.
LUAL's hybird proposal, unprecedented. We can go on forever. Both proposals went to the extreme, NOT just CAL. Those that find this hard to believe might be in for a big surprise. cheers! |
Originally Posted by gettinbumped
(Post 1453207)
A MAD snapshot is historical precedent and law, so I feel comfortable using that. The provisions for block hour and flying post merger were dictated by the TPA, and still are. It did not default back to your previous contract. The SFO 737 base was a new tri-party negotiation.
The arbs are not bound by anything other than merger policy, and precedent (indirectly) ... I am not aware of any law that states MAD must be the "snapshot" ... precedent, in fact, doesn't exclude using a different date than MAD nor MCD ... other dates have been used, recently. The two parties have already agreed that the arbs may use whatever date they conclude is appropriate, and to date, I don't believe they have asked for a differnt certified list other than those already supplied in the direct cases (2010 and 2013) ... remember, your side is proposing the arbs use a MCD snapshot, not the 2010 certified list as presented by both MCs. But if you must believe that they will/must use a MAD list/snapshot, so be it. |
Originally Posted by routemap
(Post 1453147)
CAL considered it, determined LUAL was over staffed.
LUAL's hybird proposal, unprecedented. We can go on forever. Both proposals went to the extreme, NOT just CAL. Those that find this hard to believe might be in for a big surprise. cheers! There are a great many "unprecedented" firsts in previous SLIs starting with the "pull & plug" methodology used in the DAL/NWA SLI, but having said that the supposed "hybrid" proposal UAL put forth simply used a mathematical algorithm to create a "stovepipe". It may look new, but in reality it is a good 'ole fashioned stovepiping of category and status. If you look you will see that CAL 777 CAPs had the same score as UAL 777 CAPs for their "hybrid" calculation. On a separate note, the arbitrators in the DAL/NWA SLI published their results 10 days after their last executive session. Lastly, the DAL/NWA list was mostly what the DAL pilots proposed with the exception of the 400 or so pilots from NWA who were "pulled & plugged", so I don't know where 80Kts is getting off saying it has to be a "hybrid" result from the arbs. It wasn't in DAL's case, it wasn't in AWA's case and it won't be in this case either. Stovepiped Cat & Stat sorted by ratios or longevity. It's not rocket science. The only question for the arbs is what Cats to use. |
United still had minimum mainline block hours. It also would have been difficult to shrink lual without compromising rj block hours.
|
Originally Posted by LAX Pilot
(Post 1453076)
SEDPA,
With all respect, I think there is confusion over the term "considered". Considered to most people means "I'll think about it". In contract law, considered means "A factor taken into account in evaluating or judging something" Consider doesn't mean OPTIONAL. It means YOU WILL TAKE IT INTO ACCOUNT. Also, consideration must "have a value that can be objectively determined." The arbitrators obviously understand the meaning of the word, and the policy itself, and why that one factor was added. So when you substitute the definition into the word it reads like this.... "The merger representatives shall carefully weigh all the equities inherent in their merger situation. In joint session, the merger representatives should attempt to match equities to various methods of integration until a fair and equitable integrated seniority list is reached. Factors to be TAKEN INTO ACCOUNT in constructing a fair and equitable integrated list, in no particular order and with no particular weight, shall include but not be limited to the following... LONGEVITY, STATUS AND CATEGORY, and CAREER EXPECTATIONS" -emphasis added. They SHALL include it. It WILL be used. I find it a bit amusing, in light of the testimony from Brucia and Smith concerning the policy change and the ALPA MPRC, that so many folks believe that the policy was changed, on purpose, and with supremecy of cause, to add weight to longevity. The direct testimony of both Brucia and Smith (MPRC board members) does not indicate that to be the case. Brucia testified that the goal of the policy change was 1) enhance comm about merger policy; 2) give the option of JCBA first, then SLI (as to prevent US/AWA); and 3) clarify that merger reps and arbs should consider everything, and that fair and equitable is the end state threshold to cross. From the transcripts: Redirect of Smith ... Question: About this additional language ... did that mean ... that there might be other factors that the Arb board would want to consider and it would be appropriate for them to do so? Answer from Smith: Correct, we left it up to the arbs (what factors to use, and what weight to be given) Question: and did it also mean that since it was no particular weight, that some of these factors could be considered and then not used in the final decision of the Arb board if they felt that was necessary to accomplish a fair and equitable merged list? Answer from Smith: Correct. As I stated earlier, and in many posts before, I sincerely hope the arbs consider and factor longevity into thier award ... that would be the fair and equitable thing to do. What do you think the arbs are going to use as the yardstick for fair? In many, no, most past awards, the arbs measured fairness by "bidding power", and how much was lost or gained by the award ... even in the post merger policy change Pinnacle/Mesaba/Colgan award, the arb paid great attention to the effect of the award on bidding power, and used that to measure fairness. In the UAL proposal, I would lose about 30% bidding power from the day before the award is effective ... does that cross the fairness threshold? Would any UAL folks like to lose 30% overnight? As for equitable, yes, it is an equity that should be valued and "compensated" for in regards to the UAL furloughed pilots. But how much equity is that longevity worth, especially considering that it could have been years before they were recalled, all the while long, the same bottom 1437 pilots on the CAL side would be gaining longevity while the UAL furloughs were not. So what kind of equity should the arbs transfer from the CAL side to the UAL side? Well, I'm glad I don't have to make that decision or calculation, but I sure don't think taking 30% bidding power from me and giving it to a pilot who doesn't have a job is equitable either ... some, yes, but not 30%. As stated earlier, we shall see soon enough. |
Originally Posted by routemap
(Post 1453147)
CAL considered it, determined LUAL was over staffed.
LUAL's hybird proposal, unprecedented. We can go on forever. Both proposals went to the extreme, NOT just CAL. Those that find this hard to believe might be in for a big surprise. cheers! |
Originally Posted by syd111
(Post 1453230)
Both went to the extremes? This comment is almost comical if it was not so pathetic!
Consider yourself lucky. |
Originally Posted by SEDPA
(Post 1453229)
But how much equity is that longevity worth, especially considering that it could have been years before they were recalled, all the while long, the same bottom 1437 pilots on the CAL side would be gaining longevity while the UAL furloughs were not.
Also, the only other merger under the new policy they used 100% LONGEVITY within each status and category bucket. Either way it doesn't affect me because I come out about the same in both. My status and category bucket and longevity buckets put me at about 48% of the CAL list no matter how you slice it. I think its the 1997 hires at UAL and 2001 hires at CAL and beyond that there is the most variability in their post-SLI seniority based on how much longevity gets factored in. We will all know before the end of August (my prediction). |
Originally Posted by Sunvox
(Post 1453223)
There are a great many "unprecedented" firsts in previous SLIs starting with the "pull & plug" methodology used in the DAL/NWA SLI, but having said that the supposed "hybrid" proposal UAL put forth simply used a mathematical algorithm to create a "stovepipe". It may look new, but in reality it is a good 'ole fashioned stovepiping of category and status. If you look you will see that CAL 777 CAPs had the same score as UAL 777 CAPs for their "hybrid" calculation.
On a separate note, the arbitrators in the DAL/NWA SLI published their results 10 days after their last executive session. Lastly, the DAL/NWA list was mostly what the DAL pilots proposed with the exception of the 400 or so pilots from NWA who were "pulled & plugged", so I don't know where 80Kts is getting off saying it has to be a "hybrid" result from the arbs. It wasn't in DAL's case, it wasn't in AWA's case and it won't be in this case either. Stovepiped Cat & Stat sorted by ratios or longevity. It's not rocket science. The only question for the arbs is what Cats to use. The DL/NW list was a hybrid. DL proposed a strict cat/stat stovepipe. I would have integrated in with a Jul 1999 NW hire (I was hired Feb 2007) under that proposal and moved up overall relativeabout 3%. NW proposed strict DOH. I would have lost about 3% relative position on that. The end result had about 200 pull/plug and was more of a straight relative list than anything. I moved up a quarter of a percent relative position and integrated with a Sept 2000 NW hire. So yes, It was a hybrid that leaned a bit more toward the DL proposal. |
| All times are GMT -8. The time now is 10:50 PM. |
Website Copyright © 2026 MH Sub I, LLC dba Internet Brands