Return-Path: Received: from pop3.olsusa.com ([63.150.212.2] verified) by logan.com (CommuniGate Pro SMTP 3.5b5) with ESMTP id 922587 for rob@logan.com; Sat, 13 Oct 2001 21:30:49 -0400 Received: from king1.vineyard.net ([204.17.195.90]) by pop3.olsusa.com (Post.Office MTA v3.5.3 release 223 ID# 0-71866U8000L800S0V35) with ESMTP id com for ; Sat, 13 Oct 2001 15:45:01 -0400 Received: (from mail@localhost) by king1.vineyard.net (8.11.3/8.9.0) id f9DJv0J35752 for ; Sat, 13 Oct 2001 15:57:00 -0400 (EDT) Received: from psy104.vineyard.net(199.232.93.104) by K1.vineyard.net via smap/slg (V2.0) id sma035725; Sat Oct 13 15:56:54 2001 Message-ID: <004401c15422$29ff4120$655de8c7@direct> From: "Ted Stanley" To: "LML Posting" Subject: re: Builder's Log Date: Sat, 13 Oct 2001 14:30:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailing-List: lancair.list@olsusa.com Reply-To: lancair.list@olsusa.com <<<<<<<<<<<<<<<<--->>>>>>>>>>>>>>>> << Lancair Builders' Mail List >> <<<<<<<<<<<<<<<<--->>>>>>>>>>>>>>>> >> Whatever format you choose it's the content that matters. My comments may not be applicable to a builder's log but rather more useful towards keeping a sensible set of maintenance records. The system I use on my Baron which I fly for charter and therefore have to share my records with the Feds every six months is more or less as follows: Keep separate records for prop, engine, and airframe. Work performed on each item of the above goes in its own record. If the engine manufacturer sells the component it's engine. If the prop manufacturer sells it then it's prop. Don't try to log airframe items in sections, you'll go crazy. Log everthing in chronological order. Include part, model, serial, and date code numbers in each entry where applicable. Have a statement of the work performed IN BRIEF making reference to any manuals or tech data you used. All the paperwork that comes from outside sources such as "yellow tags", manufacturer's instructions, etc. go into plastic sleeves and into a three ring binder (again in chronological order so you can find this stuff again). Buy the polypropylene ones not the vinyl or else you get ink transfer. KEEP PHOTOCOPIES. If you loose your data your screwed, or at a minimum you'll be very unhappy. You can certainly keep a "logbook", but the concept you want to embrace is that of maintaining "maintenance records" which is what the FARs refer to. The Feds love paper. I've seen cases where the plane is a rat but if the records are good the Feds love it. The reverse is equally true. When it come to inspection time DO NOT let your records out of your sight. Let the Feds see anything they want but not without you being present. I've had stuff just disappear in the past at my local FSDO, never again. I refuse to allow FAA inspectors to go on an easter egg hunt through my records. I simply ask what specifically they would like to see and I'm prepared to show it too them. They are typically looking to see that required inspections have been performed (transponder, altimeter, fire extinguisher, life vests, flares, VOR check, annual, required overhauls, AD compliance, etc.). One thing I do prior to FAA inspection is to make a list of the required items with a date and/or airframe time reference for each item of when it was last done and next due. The Feds love it. They can run down the list see that everthing is in order and you're done, AND you'll know yourself that all is in order so you won't have to sweat as much. I really like this one .... "ENGINEERING? ..... When the weight of the paperwork equals the weight of the aircraft .... the aircraft will fly." attributed to Donald Douglas, Sr. Ted Stanley A&P-IA >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> LML website: http://www.olsusa.com/mkaye/maillist.html LML Builders' Bookstore: http://www.buildersbooks.com/lancair Please send your photos and drawings to marvkaye@olsusa.com. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>