Documenting your progress

Jasonm · #1 11-26-2014, 04:47 AM

Is it required to document your build process by using KitLog or other software? I agree with taking pictures along the way to prove you are the actual builder, but it seems very redundant and time consuming to log the same steps already printed in the book.

Jason

N941WR · #2 11-26-2014, 05:02 AM

As my FSDO said, you need proof you built the plane.

So, take some pictures with you in them and log your time. BTW, I used Excel and the template is available on my website.

erich weaver · #3 11-26-2014, 05:07 AM

No. There is no specific guidance on what documentation is required. You just need to be able to convince the FAA rep or DAR that the plane was primarily amateur built. Progress pictures with you in the photos and/or handwritten notes or just instructions with noted completion dates for each step all help. Since the type and amont of documentation required is a bit subjective, my suggestion is to either make sure you have plenty or to establish early on who will be doing your airworthiness inspection and seek that individuals guidance so that there is no issue when the time comes.

fixnflyguy · #4 11-26-2014, 05:22 AM

Jason,
Great to see another NC builder! There has been much posted on this issue in the past, and many will comment. The tech natured computer types love the software...I hate it. I'm old school simple, and make my living in the aircraft overhaul industry with mountains of documentation. For the kit build project, I simply used my build instruction book that came with the plans and documented steps I completed in the margin with dates. Nothing fancy, just the facts. I also took pictures along the way which I love to look back on anyway. I had my inspection done by the GSO FSDO (great guys there), and we spent little time looking at the build book and pictures..your inspector will have a pretty good idea who built it just talking with you. If your ever in the Winston Salem area, stop by 8A7 (twin lakes airport) and chat. We have 7 RVs there, and a -7 and 8A in build .

Jasonm · #5 11-26-2014, 05:44 AM

Quote:

Originally Posted by fixnflyguy

... The tech natured computer types love the software...I hate it. I'm old school simple ...

Same here. Thanks for the invite, I'll be sure to look you up if I get over your way.

Jason

RV7Ron · #6 11-26-2014, 06:51 AM

I just went through this. Although I did a build blog with lots of pictures and detail, I dont think anyone looked at it, if they did they didnt mention it specifically. They pretty much just took my word for it that I built it and signed me off. I was surprised at that. My take is it depends on the DAR/FSDO...but it seemed pretty informal to me.

B Cunningham · #7 11-26-2014, 07:26 AM

Quote:

Originally Posted by Jasonm

it seems very redundant and time consuming to log the same steps already printed in the book.

Jason

imo, far too much time is spent putting this type of log together. You will never again look at it with all of the fun time you will spend flying. Do the minimal documentation requirement to satisfy your DAR and get it in the air.

wirejock · #8 11-26-2014, 07:31 AM

Quote:

Originally Posted by N941WR

As my FSDO said, you need proof you built the plane.

So, take some pictures with you in them and log your time. BTW, I used Excel and the template is available on my website.

+ 1
I also keep a Google blog and plan to create a binder when the time comes. My reasoning is someday the next owner will want to know how this bird was built. I figure it helps resale value. Also, not everyone follows the Vans destruction manual. Z-brackets for instance. I think it's important to document how diversions from the book were done. If not for yourself or the next owner, then for the VAF community. That said, I'm sure there are an equal number of builders who take the simpler method of writing notes in the book. Use which ever works for you.

dlloyd3 · #9 11-26-2014, 07:58 AM

I kept mine real simple. Spiral notebook. I wrote the date and what was done that day. On the back side of each page I wrote the next work session to be accomplished--great for keeping on task. Took pictures with dates. Tried to take a picture a day. FSDO guy looked at that stuff for about 2 seconds.

flion · #10 11-26-2014, 08:05 AM

Quote:

Originally Posted by B Cunningham

imo, far too much time is spent putting this type of log together. You will never again look at it with all of the fun time you will spend flying. Do the minimal documentation requirement to satisfy your DAR and get it in the air.

If your object is just to get the aircraft certificated, then I agree. But I have referred to my log many times for servicing and repair guidance and even, on occasion, to revisit some of the build process. Those were fun times, too, and I like to look back on them. Hally carp! I had hair when I was pro-sealing my RV-6A tanks! And it was black!!!

But I agree that there are many ways to accomplish a useful log. I use KitLog Pro because I am too lazy to write something better (a monumental task; it is not perfect but what is? It's been stable for years, and that's a major victory for most software). Before that, it was a paper log and a hand-coded website for me. I don't sneer at 'old school'; it works and was around long before digital computers appeared.