PPRuNe Forums - View Single Post - Qf LAME EBA Negotiations Begin
View Single Post
Old 11th Aug 2011, 10:36
  #1661 (permalink)  
GodDamSlacker
 
Join Date: Aug 2005
Location: NSW
Posts: 17
Likes: 0
Received 0 Likes on 0 Posts
Hard To Stomach

A few interesting points.....
Qantas say the International Operation is loosing money hand over fist, Domestic operation and Jetstar are making money...
So you have Domestic operation, which basically operates on one man transits, turn arounds and pushbacks for B767/B737/A330 and Management want to reduce costs even further and have a LAME less tarmac, no engineer there for the majority of transits (except ETOPS)...
Yet over at the International Terminal...the loss making operation, a single A380 arrives on a 6 hours transit with 14 engineers and 2 to 3 LAME's????
Surely if Qantas Management are going to reduce costs wouldnt you look at the loss making operation first???
If the A380 requires that much manpower to transit the aircraft, why would you by 20 of the Pigs? A quick way to bankruptcy!!!

So to the ALAEA how do you agree and sell this to the Domestic guys, who during the day, transit a variety of aircraft, 737/767/A330 and maintain a high dispatch rate and I am sure the majority fix alot of stuff they see broken and save QF heaps off $$ and help provide a produce to the flying public, yet when they look across the tarmac and see a total loss and a huge waste of manpower to try and provide a produce that isnt paying its way.....

Feel free to shoot me down but the reality of this is substantiated over and over....
Who is more cost effective? A domestic LAME handling between 10 to 12 aircraft per shift or a group of 14 engineers handling one aircraft on a 6 hour transit which is operating heavy discounted fares?
A cold hard look at this LAME less tarmac should be, one aircraft, all aircraft, from B737 thru to the Sky Pig.....How many times has management said new technology requires less maintenance thus the B738 and A380 should have LAME less tarmac handling....
GodDamSlacker is offline