Return-Path: Sender: (Marvin Kaye) To: lml Date: Wed, 28 Aug 2002 19:09:18 -0400 Message-ID: X-Original-Return-Path: Received: from imo-m05.mx.aol.com ([64.12.136.8] verified) by logan.com (CommuniGate Pro SMTP 4.0b7) with ESMTP id 1713620 for lml@lancaironline.net; Wed, 28 Aug 2002 17:24:05 -0400 Received: from RWolf99@aol.com by imo-m05.mx.aol.com (mail_out_v34.10.) id q.17.2d8806fe (3972) for ; Wed, 28 Aug 2002 17:24:03 -0400 (EDT) From: RWolf99@aol.com X-Original-Message-ID: <17.2d8806fe.2a9e9973@aol.com> X-Original-Date: Wed, 28 Aug 2002 17:24:03 EDT Subject: Re: Aircraft Log X-Original-To: lml@lancaironline.net MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 108 Bill - Good points. I have a very detailed BUILDER'S LOG which describes when I accomplished virtually everything. (I have visions of some day saying "Building wings took X hours, firewall forward took Y hours, I spent Z hours sanding") What I do not have in my BUILDER'S LOG is test plans, test conditions, quantitative results. I should rectify this. Since I have not done any tests other than landing gear tests, this is not really an issue. For other tests, such as fuel quantity and fuel transfer tests, perhaps I should write this up as an appendix to the builders log, with the fact that the test was done referenced in the chronological section ("performed fuel tank leak test per Appendix 2" for example). That way, I'll be able to remember what I did (or my survivors will, I suppose...). I had envisioned that the AIRCRAFT LOG might include compass swings, fuel tank calibration, the first flight, test period complete, and then the standard inspect-and-repair items that any aircraft log contains. Sounds to me like you and your AI agree with this approach. - Rob Wolf