[BC] Maintanence Log

[Cowboy]

On Friday 10 February 2012 12:25:08 pm Mike McCarthy wrote:
> OK...  Let's be really careful. 

> Then there is the non-compulsory maintenance log which covers everything
> else.

 As usual, Mike and I are in near 100% agreement.

 *I* would never refer to a maintenance record with the word "log" in
 any context anymore, and for reasons previously elaborated on
 this very list. ( prima facia evidence of a falsified log at minimum )

On Friday 10 February 2012 01:18:22 pm Tom Spencer wrote:
> If I were to design one today, I'd probably start with a blank page in 
> Open Office's SCALC and go from there (in other words, a blank 
> spreadsheet) with what the FCC requires, then whatever else seems like 
> useful info to keep track of for future diagnostics.

 Not just no, but H377 no !!
 "whatever else seems" like it could be used as prima facia proof of
 violation, and result in a NAL ??
 No, never, nada !

 Were I designing a log today, it would include, but ONLY include,
 that which is explicitly spelled out in the rules, and nothing more.
 And I do mean nothing, with possible exception of reference to
 chapter and verse number of which rule this particular entry satisfies.

 The "Maintenance Record" is a different thing, *provided* it is never
 referred to as a "log" of any kind.

 A case of lawyers scrambling plain English so that it means something
 that can only hurt you, if used as it's historically always been used.
 A "log" as in "ship's log" is a record of what happened.
 A "log" in FCC parlance is something entirely different.
 And, while a "program log" should intuitively be a record of what
 programs actually played, it's understood to be the opposite, and
 is really a schedule of what programs will probably play, unless
 circumstances dictate otherwise.


-- 
Cowboy