X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Fri, 27 Jun 2008 19:31:06 -0400 Message-ID: X-Original-Return-Path: Received: from imo-m20.mx.aol.com ([64.12.137.1] verified) by logan.com (CommuniGate Pro SMTP 5.2.4) with ESMTP id 2993441 for lml@lancaironline.net; Thu, 26 Jun 2008 23:12:10 -0400 Received: from RWolf99@aol.com by imo-m20.mx.aol.com (mail_out_v38_r9.4.) id q.d1c.28831d39 (34935) for ; Thu, 26 Jun 2008 23:12:00 -0400 (EDT) Received: from webmail-nc10 (webmail-nc10.sim.aol.com [207.200.67.31]) by cia-da04.mx.aol.com (v121.5) with ESMTP id MAILCIADA048-887748645a7f105; Thu, 26 Jun 2008 23:12:00 -0400 X-Original-To: lml@lancaironline.net Subject: Runaway Trim X-Original-Date: Thu, 26 Jun 2008 23:11:59 -0400 X-MB-Message-Source: WebUI X-AOL-IP: 72.19.171.41 X-MB-Message-Type: User MIME-Version: 1.0 From: rwolf99@aol.com Content-Type: multipart/alternative; boundary="--------MB_8CAA61AB2E0B1AE_AF0_5E7A_webmail-nc10.sysops.aol.com" X-Mailer: AOL Webmail 37434-STANDARD Received: from 72.19.171.41 by webmail-nc10.sysops.aol.com (207.200.67.31) with HTTP (WebMailUI); Thu, 26 Jun 2008 23:11:59 -0400 X-Original-Message-Id: <8CAA61AB2BCEE4A-AF0-2EDD@webmail-nc10.sysops.aol.com> X-Spam-Flag:NO ----------MB_8CAA61AB2E0B1AE_AF0_5E7A_webmail-nc10.sysops.aol.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" I read the description of a pitch trim that failed to opeate.? But the logical step from the nuisance?"it doesn't move when I want it to" to the hazardous "it moves when I don't want it to" isn't quite so logical.? Failing one way just isn't as likely as failing the other way. 1)? Why would the motor fail to run?? It's either not getting any power, or the motor is broken.? This can happen due to a wire connection failue ("broken wire") anywhere in the chain from the power bus to the ground.? Count the connections -- there could be as many as a dozen or more.? A pin-socket connector has three junctions -- the wire to the pin, the pin to the socket, and the socket to the wire.? The junction between the wire and the switch is another, and so forth.? A continuity break anywhere in the loop will cause the trim to not operate. 2)? Why would the motor run uncommanded?? Either the switch has failed (mechanically broken so that the contacts touch) or it is welded shut.? There's really no other way for it to happen.? We don't really put enough power through the switch to weld it, so it's really only a physically broken switch that would cause it.? Yeah, it can happen, but I wouldn't lose sleep over it.? Check it during the preflight and the likelihood of it failing in the next hour is pretty small. - Rob Wolf ----------MB_8CAA61AB2E0B1AE_AF0_5E7A_webmail-nc10.sysops.aol.com Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="us-ascii" I read the description of a pitch trim that failed to opeate.  But the logical step from the nuisance "it doesn't move when I want it to" to the hazardous "it moves when I don't want it to" isn't quite so logical.  Failing one way just isn't as likely as failing the other way.

1)  Why would the motor fail to run?  It's either not getting any power, or the motor is broken.  This can happen due to a wire connection failue ("broken wire") anywhere in the chain from the power bus to the ground.  Count the connections -- there could be as many as a dozen or more.  A pin-socket connector has three junctions -- the wire to the pin, the pin to the socket, and the socket to the wire.  The junction between the wire and the switch is another, and so forth.  A continuity break anywhere in the loop will cause the trim to not operate.

2)  Why would the motor run uncommanded?  Either the switch has failed (mechanically broken so that the contacts touch) or it is welded shut.  There's really no other way for it to happen.  We don't really put enough power through the switch to weld it, so it's really only a physically broken switch that would cause it.  Yeah, it can happen, but I wouldn't lose sleep over it.  Check it during the preflight and the likelihood of it failing in the next hour is pretty small.

- Rob Wolf ----------MB_8CAA61AB2E0B1AE_AF0_5E7A_webmail-nc10.sysops.aol.com--