X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml Date: Thu, 16 Nov 2006 12:53:25 -0500 Message-ID: X-Original-Return-Path: Received: from gateway1.stoel.com ([198.36.178.141] verified) by logan.com (CommuniGate Pro SMTP 5.1.2) with ESMTP id 1572910 for lml@lancaironline.net; Thu, 16 Nov 2006 11:57:30 -0500 Received-SPF: pass receiver=logan.com; client-ip=198.36.178.141; envelope-from=JJHALLE@stoel.com Received: from PDX-SMTP.stoel.com (unknown [172.16.103.137]) by gateway1.stoel.com (Firewall Mailer Daemon) with ESMTP id 483C8AF0C1 for ; Thu, 16 Nov 2006 08:55:12 -0800 (PST) Received: from PDX-MX6.stoel.com ([172.16.103.64]) by PDX-SMTP.stoel.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 16 Nov 2006 08:56:58 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: Down anywhere !! spinning X-Original-Date: Thu, 16 Nov 2006 08:56:58 -0800 X-Original-Message-ID: <17E9FE5945A57A41B4D8C07737DB607203891CAA@PDX-MX6.stoel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Down anywhere !! spinning Thread-Index: AccJb9ylS5u+STsSQF2e5AAuoubLQQALKmdA From: "Halle, John" X-Original-To: "Lancair Mailing List" X-OriginalArrivalTime: 16 Nov 2006 16:56:58.0906 (UTC) FILETIME=[3AC9A7A0:01C709A0] As usual, the response to my post ought to convince anyone with any sense that the best policy is to shut up. Never did have any sense. First let me make a confession: No, I have never found myself in an inadvertent spin in IMC. If that is the requirement for comment on the subject, I suspect the string will be short. I have found myself in a number of unanticipated and difficult situations so I don't have any problem understanding that, when those things happen, rational analysis is difficult or impossible. That is one reason why I try to create a sizeable buffer between what I am actually doing and the most I can handle. I also recognize that, despite all possible prudence, we can and, if we fly long enough, will find ourselves in a serious pickle that we did not create and should not have anticipated. A critical autopilot malfunction is obviously fits that bill. I have experienced autopilot glitches like that both in and out of IMC and I know for a fact that it takes a second or two to get the situartion under control, most of which involves sitting there with your mouth open thinking "what the *****". My comments on prevention were not intended to address those situations. On the other hand, the string seemed to me to be searching for a way for other pilots to deal with the possibility of an inadvertent IMC spin. I do not apologize for the notion that prevention is a part of an intelligent approach to the problem. That said, I don't buy the "instantaneous stall" concept in most cases. Granted, if you have just rotated or are climbing at best angle to comply with the angle requirements of a departure procedure, it could happen. In that case, I think that I would probably not be on autopilot at all. Absent reason to do otherwise, my climbout speed is 160K. Stalling from that speed would take either several seconds, some really radical control inputs or both. One of the things that my military training ingrained in me is that you cannot stall at zero G. I think if I was confused by some unanticipated event, my tendancy would be to reduce G for long enough to assess the situation and come up with a plan. I was also taught to "step on the ball" to recover from a spin. It is particularly useful for inverted spins where it may be hard to figure out the direction of rotation but it would be useful in IMC too. I am told, however, that some airplanes have spin characteristics in which the ball does not necessarily go to the outside of the turn. If anyone knows about this I would certainly like to know. John J. Halle Stoel Rives LLP 900 SW 5th Avenue Portland, Oregon 97204 (503) 294-9233 office (503 545-4307 cell