Documenting your progress

[az_gila]

Originally Posted by erich weaver

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.

There is specific guidance on what constitutes proof/evidence of building from the FAA -

Pages 7 and 8 of this AC -

http://rgl.faa.gov/Regulatory_and_Guidance_Library/rgAdvisoryCircular.nsf/0/4db2c5cd655cb3cc86257647004af4ee/$FILE/AC%2020-27G.pdf

[MikeyDale]

My blog leaves a lot to be desired! I am very thankful to the hundred + guys who kept an extensive build site because I dont think I could had made it this far without them! I have bookmarks organized in different categories.

[blueflyer]

That's great Gil! I had never seen it spelled out from the FAA before.

Originally Posted by az_gila

There is specific guidance on what constitutes proof/evidence of building from the FAA -

Pages 7 and 8 of this AC -

http://rgl.faa.gov/Regulatory_and_Gu...C%2020-27G.pdf

[9GT]

I had my appointment with the South East MI FSDO office this morning to obtain the repairman's certificate for my RV-10. I did not use a computer style kit log, just noted the date and time spent in my plans book as I built. I also had about 200 photos on a CD. I brought these items along with the file folder of receipts and the required application forms. The inspector I dealt with was a younger guy and very interested in EXP aircraft, in-particular RV's. I offered, but he did not need or want to see anything other than the application/eligibility forms and my ID. He stated that the DAR who inspected my plane and issued the AW certificate already verified I was the builder. Judging from some of the horror tales others here have posted here in regards to dealing with some inspectors, I was ready for a derogatory beat down. I had a great experience and this particular inspector who was courteous and helpful. A true asset to the FAA for sure. I was in and out in about 25 minutes.

[bret]

I did a web base build site to pay it forward for all the build sites that I looked at of other builders to help me. lots of work, but it was fun, and my wife did the website. So there ya go

[Kato's 8]

I know that lots of photos and descriptions is time consuming and probably overkill for min requirements to prove who built the airplane but I look at it as a helpful tool for others who are looking to see just how we did something. Sometimes just seeing it done helps calm some nerves. I also think that it could serve to help you remember jst how you did something if the need to revisit that item ever comes up again. Plus it looks neat to go back thru a gazillion log postings!
One thing I wish I could find more of are the things at the end of a build. The final prep for example. I know from experience now that its probably due to the exhaustive process after each work session. But I try and I hope others will too.

[ppilotmike]

This software is very simple and makes it a breeze to keep a log. I think, in general, keeping a log is a good thing.
Cons:
- Takes extra time
- Costs $50 (Kitlog)

Pros (Kitlog):
- Tracks work and costs (although you may not want to know)
- "Pays it Forward" to other builders
- "Pays it Backward" as a momento of your build
- Tracks your Phase 1 testing
- Has docs for registration
- You can use it for multiple projects (if the bug bites you that hard)
- It's stored on your home computer, not the cloud
- You don't pay a monthly fee to a web host
- You can filter / print the entire log out in PDF to have a hardcopy
- Helps you remember what you did
- Documents efforts of friends and family, so they can show others
- Easily answers the question, "So what kind of progress have you made?"

[erich weaver]

Originally Posted by az_gila

There is specific guidance on what constitutes proof/evidence of building from the FAA -

Pages 7 and 8 of this AC -

http://rgl.faa.gov/Regulatory_and_Gu...C%2020-27G.pdf

I stand corrected!
Thanks for the catch

[agough277]

my FISDO accepted initials and date of completion of each task along side Vans instruction manual. Pictures helped.

[David Paule]

1. A blog in "My RV Build Project." This is the public one.

2. A Word file, chapters for each section, more photos and step by step descriptions of things worth noting or remembering. Includes dates and hours total. This is for me, to track things I want to remember -- and for the DAR. Unfortunately it's very large, and there's a possibility that the DAR will die of boredom reading it.

3. Work folder, a paper notebook, with day to day work time and the various calculations. Just a shop log.

4. Spreadsheet to track costs. Frightening to examine; I had to add a whole page just for replacement parts.

Dave
RV-3B in Colorado