BOAC:
No-one is 'carrying' an unfixed defect.
.
In some respects, I beg to differ. Many a snag is not fully fixed when I fly, as the first 'test flight' is always with passengers onboard. And that is true of even the most professional of organisations.
The trouble being that some snags are difficult to trace (as every engineer knows), and the snag is unlikely to be fully fixed. Plus, the next occurrence of this snag may not occur for another few flights (
a la AMS Turkish incident), and by that time there is a new crew and a new engineering shift - and nobody knows about snag XXX 4 days ago. The assumption of 'fixed' is a dangerous assumption.
My point still stands. The new 'smoke and mirrors' over-zealous regime regarding techlogs is creating risk, not reducing it. We have a small team at XXX Airlines, so we just email each other with the latest odd 'grey' snag, to keep us all in the picture, but that is not possible with larger organisations (and it goes against the whole spirit of the techlog system).
Perhaps, if the CAA REALLY don't like open ADDs with wobbly PFDs and jumpy autopilots mentioned in it, they need a new class of 'defect' page.
The new Silverstrata-inspired page would be called the ACD - the 'A' Cleared Defects page. Any cleared defects - all those annoying "T-F-S" entries - would be placed in the ACDs for 14 days, so the next crews know what has been going on last week. You might say that that is what the techlog is for, but frankly I don't have time to go through the last 50 techlog pages to decipher the faint carbonised writing and illegible comments.
A separate ACD sheet would be much easier - and if employed by Turkish Airlines (among others) a nice new airliner and its crew might still be flying.
.