X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Mon, 19 Sep 2005 17:21:00 -0400 Message-ID: X-Original-Return-Path: Received: from mta10.adelphia.net ([68.168.78.202] verified) by logan.com (CommuniGate Pro SMTP 5.0c2) with ESMTP id 726883 for lml@lancaironline.net; Mon, 19 Sep 2005 17:05:29 -0400 Received-SPF: pass receiver=logan.com; client-ip=68.168.78.202; envelope-from=dfs155@adelphia.net Received: from f3g6s4 ([69.172.194.248]) by mta10.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with SMTP id <20050919210439.GRTN12165.mta10.adelphia.net@f3g6s4> for ; Mon, 19 Sep 2005 17:04:39 -0400 X-Original-Message-ID: <005601c5bd5e$8f6eb5a0$f8c2ac45@losaca.adelphia.net> From: "Dan Schaefer" X-Original-To: "Lancair list" Subject: Ailerons and flutter phenomena. X-Original-Date: Mon, 19 Sep 2005 14:10:26 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Gary, your post regarding the subject of flutter was an interesting and valuable dissertation but unfortunately, of mostly academic value unless one is designing one's own airplane. None the less, we all benefit by knowing as much as we can about the subject. That said, we who build from kits (any kits actually, but I'm referring to those with proven track records like our Lancairs) are hardly in the position to do the required (and potentially, destructive) testing to determine the structural parameters affecting flutter, among other critical airframe considerations. Basically, the old saw: "You pays your money and you takes your chances" is in play here, big time. Other than carefully following the building instructions published by the kit manufacturer (which includes resisting the urge to make any structural modifications), there is little the builder can, or should, do regarding those parameters. The urge to beef up something that "just looks like it needs it" often merely transfers loads to something else that wasn't meant to handle it, causing a failure. The eyes, like "gut feelings", are not very good structural testing devices. With that as a given, it still makes sense that we should pay close attention to those things that can contribute to flutter that we CAN control with maintenance, such as loose elements in control circuit linkages, e.g., worn rod-end bearings and/or pulleys (if your airplane uses such things) and loose control and trim surface hinges. (That's not intended to be a complete list of contributary items but merely to show where I'm coming from). Regarding flutter and keeping the airspeed below Vne; this is a given that any competent pilot should heed if he/she values their (and their passenger's) hide because of the chance that destructive flutter is lurking near or just beyond the red-line! I tested my LNC2 at different weights and CG's to 10% above Vne (incrementally) to be absolutely sure that it wasn't hiding anything from me if I ever needed to go TO red-line. And I only did this after making sure that my IAS and CAS were close enough that the difference wasn't an issue. Even with that, I approached this testing with the hair on my neck standing straight up and as alert as the proverbial cat in a room full of rocking chairs, knowing as I said in my earlier post, how quickly destructive flutter can ruin your whole day! Cheers, Dan Schaefer