X-Virus-Scanned: clean according to Sophos on Logan.com X-SpamCatcher-Score: 50 [XX] (100%) RECEIVED: Received headers not consistent with Juno "FROM:" Return-Path: Received: from m12.lax.untd.com ([64.136.30.75] verified) by logan.com (CommuniGate Pro SMTP 5.1.9) with SMTP id 2062095 for flyrotary@lancaironline.net; Tue, 22 May 2007 20:42:45 -0400 Received-SPF: pass receiver=logan.com; client-ip=64.136.30.75; envelope-from=alwick@juno.com Received: from m12.lax.untd.com (localhost [127.0.0.1]) by m12.lax.untd.com with SMTP id AABDFHDQGA3ZM36J for (sender ); Tue, 22 May 2007 17:41:42 -0700 (PDT) X-UNTD-OriginStamp: L941HVjjYzDhN3itp//mkM0DryH9jt7X2JpCofvAWeDQ3akzT16+Sw== Received: (from alwick@juno.com) by m12.lax.untd.com (jqueuemail) id MNDU52B7; Tue, 22 May 2007 17:41:10 PDT To: flyrotary@lancaironline.net Date: Tue, 22 May 2007 17:40:01 -0700 Subject: Re: [FlyRotary] Re: Marginal Cooling Message-ID: <20070522.174007.4024.14.alwick@juno.com> X-Mailer: Juno 5.0.49 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Juno-Line-Breaks: 0,2,4-13,18-27,41-46,48,50-51 From: al p wick X-ContentStamp: 16:8:4177564147 X-MAIL-INFO:4f858504112571797414b904d9b98075454130b940a4351d11403041408140151929c4898521045d047d113980e101397925f5 X-UNTD-Peer-Info: 127.0.0.1|localhost|m12.lax.untd.com|alwick@juno.com On Mon, 21 May 2007 12:18:45 -0400 Ernest Christley writes: > Quite the contrary. My fuel and brake lines have supports every 6 to 8 > inches. You can take full credit for that. Thanks, appreciate that. > I initially jumped in with both feet trying to determine the failure > probability of various components, making charts to assign values to > failure probability and seriousness of effects. FMEA is often a tough one. It really helps to ignore probability and odds of noticing fault. Just deal with "What's the flight risk when it fails". If you do that for every item, then it's much easier. Only when done with all the risk items, do you focus on probability. Even then, it can be a challenge. > > We are not making hundreds or > thousands of an identical item. We're a varied group, working in > varied > environments, with varied amounts of skill on various types of > projects. Statistics are irrelevant when you have a sample size of > one. Wow, do I ever disagree with above statement. You can use any method of analysis you want, it's clear there are patterns to historical failures. If you have a failure, very likely it will be the same root cause as others. Does cooling problem sound familiar? How about exhaust fracture? It's almost impossible to have a failure on your plane that hasn't been discovered by someone else in the past. Particularly if you look at "other" causes, not just the one cause that's obvious. The key to preventing failures on our planes is to analyze past issues, complaints, and take effective action. This is tough to accomplish though, only because we live our entire lives making decisions based on feelings, familiarity. We are naturally ineffective at problem solving and are clueless. Tell me the last time you solved any problem and actually measured how effective the solution was? Further, when was the last time you measured the results and tried more than one solution? regards -al wick Cozy IV powered by Turbo Subaru 3.0R with variable valve lift and cam timing. Artificial intelligence in cockpit, N9032U 240+ hours from Portland, Oregon Glass panel design, Subaru install, Prop construct, Risk assessment info: http://www.maddyhome.com/canardpages/pages/alwick/index.html