X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from [216.254.136.67] (HELO slipstream-tor2.pvt.primus.ca) by logan.com (CommuniGate Pro SMTP 5.0.8) with ESMTPS id 1031416 for flyrotary@lancaironline.net; Sun, 12 Mar 2006 11:56:35 -0500 Received-SPF: none receiver=logan.com; client-ip=216.254.136.67; envelope-from=aouellet@icecanada.com Received: from alain (slipstream-tor2.pvt.primus.ca [127.0.0.1]) by slipstream-tor2.pvt.primus.ca (8.12.11/8.12.11) with SMTP id k2CGSmum032630 for ; Sun, 12 Mar 2006 11:28:49 -0500 Received: from 67.71.123.74 (aouellet%40globalserve.net@67.71.123.74 [67.71.123.74]) by slipstream-tor2.pvt.primus.ca (SlipStream SP Server 3.2.55 built 2005/01/19 11:21:25 -0500 (EST)); Sun, 12 Mar 2006 11:28:49 -0500 (EST) From: "Alain Ouellet" To: "Rotary motors in aircraft" Subject: RE: [FlyRotary] Re: flutter encounter....AOPA article Date: Sun, 12 Mar 2006 11:55:56 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0021_01C645CB.EBB5B6B0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 This is a multi-part message in MIME format. ------=_NextPart_000_0021_01C645CB.EBB5B6B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit reviewI concur that when it happen to you I definitely can really ruin a perfect day. I experienced it first hand in my Zenith CH300 last fall on the way back from a flight from Hanover to Brampton Ontario. Coming down to get into the Toronto control zone. Speed was increasing to 145 mph. At the time I thought the engine wanted to leave the aircraft. It stopped after throttling back. Quite an experience. After landing we checked around the plane. The engine seems ok, then the wings, ailerons and the tail, still no luck. The next day, took the plane in the circuit and started experiencing it again when turning crosswind at 80 mph. Oh shit again, ok throttle back then went around the circuit at 70 mph and landed. After further investigation, had someone holding the stick and went around moving the ailerons we found that the source was a tie rod end bearing with some wear. The nut holding it in place was still fully secured but not torqued enough allowing the inner bearing to rotate on the rod itself. All the other components were checked, control cable tension was as per specs. Found a new rod end bearing and replaced it and made sure it was torqued with no chance to rotate anymore. Got it fired up and went to test fly it. No more problems. Recently had the plane at 160 mph with no indications of any more symptoms. A lesson learned is to go with a really fine tooted comb over your control system for any signs of wear or looseness. It is not evident when doing the standard preliminary flight inspection or annual. Lets be safe. Alain -----Original Message----- From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net]On Behalf Of David Carter Sent: March 12, 2006 1:30 AM To: Rotary motors in aircraft Subject: [FlyRotary] Re: flutter encounter....AOPA article One of the A-7Ds in my squadron had an aileron flutter problem - found a bearing for the aileron was loose in its mounting to the wing (was "unstaked", not secured properly). When climbing at 400 KIAS passing between 15,000 and 17,000, the mach number was coming up to about .80 and the flutter would self-excite with no manuevering - no damage, just scared the pilot (yanked throttle to idle and pulled up to slow down and it would stop, then returned to land declaring an emergency - thought it was an engine vibration such as would be caused by losing a turbine blade in aft end of engine. Engine was checked OK - flutter (never saw what was fluttering, just felt an awful shaking of everything in the cockpit) was repeatable on 3 different test flights. As this was a speed-altitude condition no one ever flew at we kept flying the plane on regular missions. Took several months before Vought led us to the cause - the loose aileron bearing. David ----- Original Message ----- From: Marc Wiese To: Rotary motors in aircraft Sent: Saturday, March 11, 2006 4:17 PM Subject: [FlyRotary] flutter encounter....AOPA article >NEVER AGAIN ONLINE: FLUTTERING WITH DISASTER Flutter and wing oscillations rendered the aircraft uncontrollable with imminent structural failure as a probable ending: a harrowing event with a remarkable outcome. The pilot's swift action and a good dose of luck helped him and his passengers survive the ordeal. Read ( http://www.aopa.org/epilot/redir.cfm?adid=8497 ) how this pilot handled an extreme emergency--a lesson he would not wish to repeat.< ------=_NextPart_000_0021_01C645CB.EBB5B6B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable review
I=20 concur that when it happen to you I definitely can really ruin a perfect = day.=20
 
I=20 experienced it first hand in my Zenith CH300 last fall on the way back = from a=20 flight from Hanover to Brampton Ontario. Coming down to get into the = Toronto=20 control zone. Speed was increasing to 145 mph. At the time I = thought=20 the engine wanted to leave the aircraft. It stopped after = throttling=20 back.
 
Quite=20 an experience. After landing we checked around the plane. The = engine seems=20 ok, then the wings, ailerons and the tail, still no luck. The next day, = took the=20 plane in the circuit and started experiencing it again when turning = crosswind at=20 80 mph. Oh shit again, ok throttle back then went around the = circuit at 70=20 mph and landed.
 
After=20 further investigation, had someone holding the stick and went around = moving the=20 ailerons we found that the source was a tie rod end bearing with = some wear.=20 The nut holding it in place was still fully secured but not torqued = enough=20 allowing the inner bearing to rotate on the rod itself. All the other = components=20 were checked, control cable tension was as per = specs.
 
Found=20 a new rod end bearing and replaced it and made sure it was torqued with = no=20 chance to rotate anymore. Got it fired up and went to test fly it. No = more=20 problems. Recently had the plane at 160 mph with no indications of any = more=20 symptoms.
 
A=20 lesson learned is to go with a really fine tooted comb over your control = system=20 for any signs of wear or looseness. It is not evident when doing the = standard=20 preliminary flight inspection or annual.
 
Lets=20 be safe.
 
Alain
 
 
-----Original Message-----
From: Rotary motors in = aircraft=20 [mailto:flyrotary@lancaironline.net]On Behalf Of David=20 Carter
Sent: March 12, 2006 1:30 AM
To: Rotary = motors in=20 aircraft
Subject: [FlyRotary] Re: flutter encounter....AOPA=20 article

One of the A-7Ds in my squadron had = an aileron=20 flutter problem - found a bearing for the aileron was loose in its = mounting to=20 the wing (was "unstaked", not secured properly).  When climbing = at 400=20 KIAS passing between 15,000 and 17,000, the mach number was coming up = to about=20 .80 and the flutter would self-excite with no manuevering - no damage, = just=20 scared the pilot (yanked throttle to idle and pulled up to slow = down and=20 it would stop, then returned to land declaring an emergency - thought = it was=20 an engine vibration such as would be caused by losing a turbine blade = in aft=20 end of engine.  Engine was checked OK - flutter (never saw what = was=20 fluttering, just felt an awful shaking of everything in the = cockpit) was=20 repeatable on 3 different test flights.  As this was a = speed-altitude=20 condition no one ever flew at we kept flying the plane on regular=20 missions.  Took several months before Vought led us to the = cause -=20 the loose aileron bearing.
 
David
----- Original Message -----
From:=20 Marc=20 Wiese
To: Rotary motors in = aircraft=20
Sent: Saturday, March 11, = 2006 4:17=20 PM
Subject: [FlyRotary] flutter=20 encounter....AOPA article

>NEVER=20 AGAIN ONLINE: FLUTTERING WITH DISASTER Flutter and wing oscillations = rendered the aircraft uncontrollable with imminent structural = failure as a=20 probable ending: a harrowing event with a remarkable outcome. The = pilot's=20 swift action and a good dose of luck helped him and his passengers = survive=20 the ordeal. Read ( http://www.aopa= .org/epilot/redir.cfm?adid=3D8497=20 ) how this pilot handled an extreme emergency--a lesson he would not = wish to=20 repeat.<

 =20

 

------=_NextPart_000_0021_01C645CB.EBB5B6B0--