Don't put it in the Tech Log!
We carry a separate 'cabin log' for 'minor' cabin items which seemed like a good idea at the time but has proven to be more trouble than it's worth, with Flight Attendants writing up airworthiness items which then have to be transfered to the main log anyway.
I am hoping we will get rid of it, the most serious problem with this system shows up when the incoming Captain does not check the cabin log thoroughly enough and misses an airworthiness item.
Anyone else use this system ?
I am hoping we will get rid of it, the most serious problem with this system shows up when the incoming Captain does not check the cabin log thoroughly enough and misses an airworthiness item.
Anyone else use this system ?
Join Date: Dec 1998
Location: .
Posts: 2,997
Likes: 0
Received 0 Likes
on
0 Posts
Yes we have cabin logs, better than have just a tech log, if you have the right procedures in place then any airworthiness item is then transferred to the tech log by the crew. or if they miss it then an engineer will do it, we have a code system which automatically tells the crew it should go in the tech log.
Join Date: Jul 2008
Location: Lost
Posts: 22
Likes: 0
Received 0 Likes
on
0 Posts
Nutloose,
Ok I get it now. Seems like a weird scenario with diff limits from engine and ariframe. Well all the better, you had a "tight" engine. Now if the pilots would just pull the throttle back a little to set max RPM.
Ok I get it now. Seems like a weird scenario with diff limits from engine and ariframe. Well all the better, you had a "tight" engine. Now if the pilots would just pull the throttle back a little to set max RPM.
Join Date: Mar 2006
Location: Festung Europa
Posts: 53
Likes: 0
Received 0 Likes
on
0 Posts
Interesting to see the discussion of write it up / don´t write it up.... Lets go back to the very basics. If there was any problem:
"Stay with Ac until the Eng arrive"
I´ve lost count of the number of times I´ve encountered the Ac bedded down with the log book open inside with a snag or two that have taken the whole night to trouble shoot. Why all night? Because the crew buggered off and instead of being available for questioning we had to determine in exactly what config the Ac was when the defect appeared.
"Stay with Ac until the Eng arrive"
I´ve lost count of the number of times I´ve encountered the Ac bedded down with the log book open inside with a snag or two that have taken the whole night to trouble shoot. Why all night? Because the crew buggered off and instead of being available for questioning we had to determine in exactly what config the Ac was when the defect appeared.
Join Date: Dec 1998
Location: .
Posts: 2,997
Likes: 0
Received 0 Likes
on
0 Posts
Airline maintenance cuts 'threaten safety'
interesting Airline maintenance cuts 'threaten safety'
Met a flt the other day capt says "I haven't put it in the book, but..."
OK, checked the MEL 2 installed, 1 required, but there were none on the a/c, AOG overnight waiting bits, why not just write it in the book. Covered myself as 1st line of defect read, on crew verbal report....
Why not just write it in in the 1st place,
A survey of aircraft maintenance engineers by the AEI found that 85 per cent of faults were reported only after a pilot had made a homeward flight or at the end of the day’s flying. This allows airlines to fix problems at more convenient times, avoiding extra expense.
But a spokesman for the British Airline Pilots Association (Balpa) said that its own inquiry found that no major problems go unreported.
“Pilots are under pressure,” he said, “but not to the extent that they would compromise the safety of the plane or passengers. We have not reached that point yet, but who knows whether it will be a different story in a year’s time.”
“Pilots are under pressure,” he said, “but not to the extent that they would compromise the safety of the plane or passengers. We have not reached that point yet, but who knows whether it will be a different story in a year’s time.”
OK, checked the MEL 2 installed, 1 required, but there were none on the a/c, AOG overnight waiting bits, why not just write it in the book. Covered myself as 1st line of defect read, on crew verbal report....
Why not just write it in in the 1st place,
Join Date: Oct 2001
Location: farrrr east
Posts: 263
Likes: 0
Received 0 Likes
on
0 Posts
Then theres the other side, the inbound crew write up a defect, engineer gets called at the last minute, go onboard, the new crew and SLF are sat there all expectant and ready to go, the captain say's "Just sign it off, it's alright, I'll take it!"
I informed him it dosn't work like that, I asked him to offload the passengers so I could do my investigation with the electrical power off, and lift him mouth opened and went below to have a look around below the cockpit. When I got back they were all still sat there, nothing had happened until I informed him, I had found rodent droppings and I was not allowed to dispatch the aircraft.....
I informed him it dosn't work like that, I asked him to offload the passengers so I could do my investigation with the electrical power off, and lift him mouth opened and went below to have a look around below the cockpit. When I got back they were all still sat there, nothing had happened until I informed him, I had found rodent droppings and I was not allowed to dispatch the aircraft.....
Join Date: Jun 2008
Location: india
Age: 43
Posts: 29
Likes: 0
Received 0 Likes
on
0 Posts
Its great to see so many answers to a catch 22 i was always in, whether to write a snag in the tech log or not. I agree with CESSNA 24, in one of the earlier posts that it does make sense not to write small snags in the log. to give you an example, for the guys operating A320 aircraft, we had an ECAM that used to be generated every flight for a period of 8 months continously, ECAM : R OUTER TANK HI TEMP. This snag was written numerous times in the log and the reason it used to be generated was due to interference of communication equipment. Engineers told us to stop writing it because there was nothing they could do about it after having tried resolving the problem with Airbus. I do agree that any small snag should be written down as we are legally bound to do so. I cant understand why many people dont write things down in the log even if it is something as small as changing the bulb of the landing light 
.
.
Join Date: Apr 1999
Posts: 235
Likes: 0
Received 0 Likes
on
0 Posts
Mobid
in an ideal world yes, stay with a/c to help troubleshooting. However, after long day, discretion and 0200+ arrival how long do you wait for engineers, 1h, 2, 3? putting you out of hours to operate next flight...
in an ideal world yes, stay with a/c to help troubleshooting. However, after long day, discretion and 0200+ arrival how long do you wait for engineers, 1h, 2, 3? putting you out of hours to operate next flight...
Join Date: Aug 2000
Location: U.K.
Posts: 42
Likes: 0
Received 0 Likes
on
0 Posts
You could call up the line mx office or maintrol & ask for someone to attend asap to debrief you (or talk to you on the 'phone)?
It's not always possible to meet each a/c as it arrives when most of the fleet roll up at the same time.
It's not always possible to meet each a/c as it arrives when most of the fleet roll up at the same time.
Join Date: Jan 2005
Location: In t'sky
Posts: 575
Likes: 0
Received 0 Likes
on
0 Posts
This thread is pretty interesting, as a low-ish (<1000 hours on type) guy I don't see much of the techlog.
One question I do have, is at my airline, it seems cabin crew are actively encouraged to write up defects in the Cabin Defects Log (managers assume if there aren't defects you aren't looking hard enough and are reprimanded). A favorite past-time in delay situations is for them to look for dings and bulbs gone and write them up, am I writing in thinking at the end of the day we should have a look in it and transfer pertinent ones to the main Tech log?
I'm just as bad, part of my pre-flight includes a light test and if I have time i'll replace all the bulbs that are gone from the onboard spares box, do you Techlog it if you've taken one or two out? Or is this sort of thing operator specific?
Horgy
One question I do have, is at my airline, it seems cabin crew are actively encouraged to write up defects in the Cabin Defects Log (managers assume if there aren't defects you aren't looking hard enough and are reprimanded). A favorite past-time in delay situations is for them to look for dings and bulbs gone and write them up, am I writing in thinking at the end of the day we should have a look in it and transfer pertinent ones to the main Tech log?
I'm just as bad, part of my pre-flight includes a light test and if I have time i'll replace all the bulbs that are gone from the onboard spares box, do you Techlog it if you've taken one or two out? Or is this sort of thing operator specific?
Horgy
Join Date: Aug 2008
Location: moving around
Age: 47
Posts: 98
Likes: 0
Received 0 Likes
on
0 Posts
. to give you an example, for the guys operating A320 aircraft, we had an ECAM that used to be generated every flight for a period of 8 months continously, ECAM : R OUTER TANK HI TEMP. This snag was written numerous times in the log and the reason it used to be generated was due to interference of communication equipment. Engineers told us to stop writing it because there was nothing they could do about it after having tried resolving the problem with Airbus. I do agree that any small snag should be written down as we are legally bound to do so. I cant understand why many people dont write things down in the log even if it is something as small as changing the bulb of the landing light .
then the engineers should have put on board details of the correspondence between them and airbus. normally airbus would issue a TFU with regard to a reoccuring problem like this. i have searched and not found anything with this message.
i know that the word of the engineer should be trusted, but in this case with a known problem, the crew should have all the info to decide whether it is an airworthiness issue or not.
then the engineers should have put on board details of the correspondence between them and airbus. normally airbus would issue a TFU with regard to a reoccuring problem like this. i have searched and not found anything with this message.
i know that the word of the engineer should be trusted, but in this case with a known problem, the crew should have all the info to decide whether it is an airworthiness issue or not.
Moderator
the crew should have all the info to decide whether it is an airworthiness issue or not.
defeats the underlying system. If there is a recurring minor snag, then the appropriate way to handle it is by notice to aircrew with whatever instructions .. keeps it closed loop and all relevant parties in the loop.
defeats the underlying system. If there is a recurring minor snag, then the appropriate way to handle it is by notice to aircrew with whatever instructions .. keeps it closed loop and all relevant parties in the loop.
Join Date: Jan 2000
Location: Europe
Posts: 168
Likes: 0
Received 0 Likes
on
0 Posts
Consequence
Doesnt that tell you what kind of company you work for.
You can tell the ones give you flack for writing stuff in the Tech log.
One should know the consequence of what one is writing and the MEL.
You can tell the ones give you flack for writing stuff in the Tech log.
One should know the consequence of what one is writing and the MEL.
