While I agree not understanding his aircraft's systems was a contributing factor, in my mind the primary problem for this pilot was poor decision making. Why in the world would you fly with a malfunction you don't understand the cause and/or ramifications of?
That being said, here are my suggestions for non-builder owners who might like to avoid such mishaps:
1. If possible, contact the original builder. Keep his/her phone number in your contact list. Consult with him/her when facing problems such as the one related here.
2. Get the system schematics the original builder used (if available) and study/verify them.
3. If no schematics exist create them yourself. Get the help of an experienced builder and/or maintenance professional.
4. Develop a go/no-go checklist based on knowledge of the systems.
I'm sure the excellent minds here on the LML can come up with more suggestions.
--Mark Sletten
In a message to the LML dated Mon, 21 Oct 2013, Peter Williams wrote:
"The Lancair 235 that crashed near Hudson, Ky., on April 14, 2012..."
"Systems knowledge is crucial to the go/no-go situation in any case, but the lack of standardization makes it especially critical for buyers of experimental aircraft. Later owners don’t automatically inherit the builder’s intimate familiarity with all the design decisions that could have unexpected implications. Operating these aircraft safely requires learning all their quirks while maintaining a healthy respect for risks that haven’t been anticipated."