Hey. How come no talk about the PILOT SHORTAGE in Late December ??

[NewHampshire Black Bears]

I love it. APA should stick it up AA's ASSS, instead of working with them, when Management wouldn't go to the 'table' with the union, initially.

I'd piss myself laughing if APA said TRIPLE PAY, or G F Y !!

 

[Tom Talbert 1888]

Cause it’s settled

 

[IORFA]

Close, double pay. Supposedly.

 

[jimntx]

Of course you get these kinds of glitches in the computer systems when you don't control the programmers directly. I've said this before but...

When I started with Texaco in 1979 as a Programmer Trainee, American Airlines Sabre was the gold standard for corporate data processing. Then AA decided to "enhance shareholder value" by outsourcing trivial activities not directly related to the airline business (aka critical activities, such as computer programming, that AA upper management didn't really understand). Of course, AA did the outsourcing by simply selling off the entire Sabre department. The employees there lost their AA health insurance and retirement benefits, their travel privileges, and (I'm guessing here) their workplace near the airport.

AA became just another customer, and whereas the Sabre employees had (note past tense) a vested interest in the long-term survival of American Airlines, they now had only a vested interest in whether or not AA's last check bounced. Instead of outstanding, world-class work, Sabre now produces more or less adequate work. Texaco did similar for the same reason (enhancing shareholder value), but by terminating the majority of the IT staff, and outsourcing the programming to India. When's the last time you saw a Texaco station? When I left there in 1995, Texaco was the 3rd largest oil company in the U.S. Texaco no longer exists. I'm not judgin'. Just sayin'.

 

[swamt]

I love it. APA should stick it up AA's ASSS, instead of working with them, when Management wouldn't go to the 'table' with the union, initially.

I'd piss myself laughing if APA said TRIPLE PAY, or G F Y !!

I read an article that both sides have come to an agreement and I believe it is for double time pay. If on a holiday it will be T-time.

 

[eolesen]

Of course you get these kinds of glitches in the computer systems when you don't control the programmers directly. I've said this before but...

All true... however.... the story I'm hearing is that it wasn't the software.

The guy at AA who used to monitor TTOT apparently retired. Their replacement somehow managed to overlook the 3,000 or so warning messages sent out by the system to let the humans know there was a problem.....

The pessimist in me says this is a classic example where New and Improved AA management didn't see a whole lot of value in a job being done by a Legacy AA guy, and probably saw an opportunity to simply reduce specialist headcount when he retired. Clearly his replacement didn't keep his eye on the warnings...

 

[Tom Talbert 1888]

They already posted Director of Scheduling on AA’s job board.

 

[jimntx]

Day late and a dollar short. Eolesen I agree with you, because I saw a lot of elimination of job positions/activities over the last 2 years when incoming management (from Charlotte) decided to reduce cost by eliminating positions/activities that do not exist at LUS. "If it were needed we would already have a position like this in CLT ops." There's also been a significant loss in qualified, first class employees/managers at DFW to make room for CLT people being moved in. Here again, not judgin'. Just sayin'.

 

[Tom Talbert 1888]

Crew scheduling wasn’t based in CLT for LUS.

That was PIT then PHX.

 

[jimntx]

Doesn't matter if it was located in Timbuktu, LUS management seems to think that if they didn't think of it, it's not needed. Ergo, the scheduling snafu that resulted from no one watching the vacation scheduling. I still say it was ultimately a programming problem. Those sorts of things--like counting the number and duration of vacation awards during holiday seasons is fundamental "If A is equal to or is greater than B, then call routine C" programming.