Tech Log Entries

[BigTellyMan]

A colleague was telling me about a problem a friend of his had the other day.

The inbound captain gave the outbound captain a verbal report about vibration in the tail. NO tech log entry was made and the aircraft flew two more sectors with an engineer on board to monitor the vibration.

The aircraft was grounded on it's return for repairs.

Please somebody tell me this didn't happen?

Incidentally the inbound captain was the same "gentleman" that suspends you if you refuse to use discretion.

BTM:sad:

[Golden Rivet]

Difficult one, vibration is sometimes hard to quantify. When does vibration become a reportable snag ?

The above description sounds like a common sense approach to the problem.

[BigTellyMan]

I agree entirely but surely there must be an entry in the tech log?

What would have happened if the two captains hadn't met?

BTM:ok:

[canadair]

"I agree entirely but surely there must be an entry in the tech log"

I would agree with GR here, he makes a great point, when is vibration ( airframe, not engine) reportable? and just how would you write that up? vibration in the tail, was it felt through the rudder pedals? if so there are other things that can cause this, how can you pin it down? sounds like sending the mechanic along was by far the best move here, as well , was it the outbound CPT that requested the mech? more probable reporting by the inbound CPT directly to maintenence was what prompted the sending of the tech, therefore no reason whatsoever to report this to the outbound crew.
But more to the point, what should and should not be put in the tech log? well this is always a question, debate, etc
if it is a vaild safety, or clear cut reportable point, an item that can be identified with a proper fault reporting code, or clearly explained by the FE, ( or equiv with 2 man crews) then of course add it, but there are certainly times when discussion with maint is preferable to instantly writing.
Personally I always ask the FE to discuss any writeups he is interested in putting in the log prior to doing so, because at the end of the day, I sign it, he does not, and if I am going to potentially ground an aircraft, I like to at least know I am doing so! the vast maj of FE`s will do so anyway without being asked, but the odd one feels tech write ups are his domain, and therefore not really required as a discussion item.( and yes I do read it before signing! but it`s a little late at that point)

[MaximumPete]

I remember a captain who didn't put an item in the tech log. The aeroplane, a freighter, crashed on the next sector killing the crew.

That one was something to do with the tail!

MP

:(

[Meeb]

<<more probable reporting by the inbound CPT directly to maintenence was what prompted the sending of the tech, therefore no reason whatsoever to report this to the outbound crew.>>

Are you serious? Not reporting to the next crew is, at minimum, negligent, but nevertheless should have been written up in the Tech Log.

I am surprised there are people who do not understand their responsibility in this regard.

Pete has got this one right, not least because if anything did happen you would have a clear conscious, not much consolation, but legally correct.

<<Incidentally the inbound captain was the same "gentleman" that suspends you if you refuse to use discretion.>>

Bigtellyman, discretion is just that, commanders descretion whether or not to continue the duty, it is not enforceable by management. If indeed this is happening in your company you need to speak to your union rep immediately and the 'gentleman' concerned will be the one who is 'suspended'.... :mad:

[Bus429]

Let the engineer decide - stick it in the book. Be as precise as possible.

[411A]

Tech log entries.

If it's not normal, it goes in....case closed.
Those that think that a 'short note' to the next crew (ISO tech log entry) are not to be trusted...period.

And, use the FIRM code...saves a lot of work for the ground folks.

[Johnman]

NO one should rely on verbal briefings . let every one do his job right . An entry in the log book will save the troubles at the end of the day , and all other crews will be in the picture of repeated and rectified snags .

[Capt H Peacock]

For any defect such as an indeterminate vibration, it's important to raise a tech log entry so that a proper engineering survey report can be accomplished. This would usually take the form of a worksheet to be completed with symptoms noted against configuration, profile, and airspeed for instance.

The final judgment as to whether the airplane is operable in that condition is made by the Captain alone.:ok:

[ecj]

I agree entirely with Capt. Peacock.

If in doubt put it in the book. How would you feel if you did nothing, and then something serious then happened? You would feel really bad for a long long time.

The acid test I use is to ask myself whether I would be happy for my wife and kids to go flying in that aircraft? If the answer is no, then it goes in the book. The buck stops with you as Captain. Simple as that.