Airplane / Engine Logbook Entries ??

[24Golf]

We are nearing the completion of our RV9A and are trying to figure out what, if anything, goes in the logbooks during construction. We have a new factory (Vans) Lycoming IO-320 and new prop and slow build kit. Do we make entries in the engine or airplane logbook about the date of engine install, alternator install or ELT... etc??? Or, is the first entry in the logbook the " I certify..." statement that follows the building process?

Honestly, we are not really sure what goes into the plane logbooks after completion.... we have never owned a plane before. We assume, oil changes go in engine logbook, annuals go in airplane logbook, etc... of course we all know what you get when you ***-u-me!

Any guidance would be appreciated...

[Ironflight]

The truth is that for an experimental, as long as you have the annual statement in the aircraft records required by your Op Lims, you have legally met the MINIMUM requirements for record-keeping.

Minimums aside, you can keep track of anything that you like. Some argue that less is better - I tend to follow the same logging protocols as I have for certified airplanes (log whenever you do something) out of shear habit and the engineer's fondness for record-keeping.

AS to what goes where - I put anything that is definitely engine related in the engine book, anything that is airframe related in the airplane log, and propeller maintenance goes in it's own book. Anything essential to engine operations, such as magnetos and carbs - engine book. accessories that are not "part" of the engine (alternator) - airframe book.

Just my system,

Paul

[az_gila]

Originally Posted by 24Golf

We are nearing the completion of our RV9A and are trying to figure out what, if anything, goes in the logbooks during construction. We have a new factory (Vans) Lycoming IO-320 and new prop and slow build kit. Do we make entries in the engine or airplane logbook about the date of engine install, alternator install or ELT... etc??? Or, is the first entry in the logbook the " I certify..." statement that follows the building process?

Honestly, we are not really sure what goes into the plane logbooks after completion.... we have never owned a plane before. We assume, oil changes go in engine logbook, annuals go in airplane logbook, etc... of course we all know what you get when you ***-u-me!

Any guidance would be appreciated...

...the FAA does not use the words "log book", even for certified aircraft.

They want maintenance records, so you can have several books separated into different functions if you want.

One example might be to keep a detailed copy, with comments and work performed, of the checklist you use for inspections in a 3-ring binder, and just put the Ops Limitations required statement into a "traditional" log book.

[pierre smith]

During construction, keep a build record and take a bunch of pictures.

e.g...left aileron completed 12/31/09, right flap finished 1/1/10 and so on.
The DAR will want a record of some sort when he/she inspects your airplane.

I used a three ring binder for the photos and some create and burn a CD...your call.

Best,

[apkp777]

I would be a statement in the log with the Heading TTAF 0 and TTSN 0. Just because it'll look cool!

Also, though not required, I would put a statement like this:

"I certify that this aircraft has been constructed in accordance with Van's Aircraft assembly instructions and related Van's Aircraft assembly drawings. Standard aircraft maintenance practices found in AC43:13 were followed. The following processes were not in accordance with Van's assembly instructions: (list all custom mods, Sika etc.)" Builder's Name and Repairman's Cert #

[flion]

In my engine logbook, I made an entry to the effect that the engine was installed on such and such a date according to the manufacturer's specifications in section/pages and was ops checked for proper operation. I made similar notation on my Hartzell propeller in it's log. The ops check, and therefore the install date, are the first engine run; it's not a complete install without the operational check. Subsequent notations have been for the periodic inspections, routine servicing, and the starter/ring gear replacement I had to do. The latter also included a prop reinstall and, for both engine and prop, yet another ops check.

The airframe logbook got entries for the ELT check at installation and the transponder and pitot/static inspections. Then, when it was inspected, the DAR helped me put the correct entries in and showed me what the operating limitations required at the end of Phase I. Other than airframe repairs or modifications (neither of which I've had to do), there's only equipment inspections and the annual condition inspection to log. For the latter, I adapted a checklist posted to VAF and keep a copy in a file so I will have a record of details (just did the first one earlier this month) along with a notation in the logbook using the verbiage taken from the operating limitations.

Paul is correct in that you don't need to log everything but I think you should at least log routine maintenance/inspections if only to improve resale by showing that it was done. Too much disclosure can also be a bad thing, which is why I keep my detail checklist separate. I can track all the little squawks I find and fix but they are not part of the official logs and I can use my discretion on whether to disclose them to an authority or potential buyer.

Experimentals (not necessarily LSAs) are specifically excluded from the maintenance and inspection regulations in the FARs (except that the Operating Limitations then turn around and specifically require an annual condition inspection), so you really don't need to log anything other than the airworthiness, Phase I, and condition inspections (I was wrong about this in another thread; I thought the OpLims also spelled out maintenance requirements, too).

[24Golf]

Thanks all.... these are great responses as usual. I like the idea of having a notebook or diary of little things done and putting only required or needed things in the official record.

Also, we have detailed build records and photos and use the Kitlog Pro software to store the data.