X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Tue, 27 Dec 2005 00:16:04 -0500 Message-ID: X-Original-Return-Path: Received: from mail.telcomplus.net ([64.40.39.4] verified) by logan.com (CommuniGate Pro SMTP 5.0.5) with ESMTP id 901875 for lml@lancaironline.net; Mon, 26 Dec 2005 13:47:41 -0500 Received-SPF: none receiver=logan.com; client-ip=64.40.39.4; envelope-from=jakey@telcomplus.net Received: by mail.telcomplus.net from localhost (router,SLmail V5.1); Mon, 26 Dec 2005 10:46:50 -0800 for Received: from hoben1 [64.40.39.159] by mail.telcomplus.net [64.40.39.4] (SLmail 5.5.0.4433) with SMTP id ED2F554186104FD28557E6722B3C490C for ; Mon, 26 Dec 2005 10:46:40 -0800 X-Original-Message-ID: <002401c60a4c$b8e2c760$9f272840@hoben1> From: "James Keyworth" X-Original-To: "Lancair Mailing List" References: Subject: Re: [LML] Re: N320WH Destroyed, No Injuries X-Original-Date: Mon, 26 Dec 2005 10:46:45 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0021_01C60A09.AA0E5FD0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-SLUIDL: 311CAAB3-4ACD456A-81479D4B-DDF38753 This is a multi-part message in MIME format. ------=_NextPart_000_0021_01C60A09.AA0E5FD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In a message dated 12/25/2005 8:05:31 P.M. Central Standard Time, = Lee.Metcalfe@jocogov.org writes: ...He was entering the traffic pattern... when he added throttle to = level off for the traffic pattern the engine didn't respond... =20 I'm certainly glad the occupants got out OK. I look forward to an = analysis of what caused the engine to not respond. Any thoughts?=20 Scott Krueger AKA Grayhawk Something similar happened to me after crossing the Rockies in my = 112TC-A at 14,500 ft as I prepared to land at an airport in a rather = narrow valley at 1100 ft ASL. After a steep descent from altitude at = near idle power, at 1100 ft AGL when I advanced power, the engine choked = and coughed like it was going to die. With a quick scan I realized the = mixture was still at high-altitude lean. I enriched it, the engine = growled satisfyingly, and the flight ended safely a minute or so later. = My pax felt relieved; I felt somewhat embarrassed. Could the accident have been a forgotten mixture setting? JHK ------=_NextPart_000_0021_01C60A09.AA0E5FD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

In a message dated 12/25/2005 8:05:31 P.M. Central Standard Time, = Lee.Metcalfe@jocogov.org=20 writes:

...He=20 was entering the traffic pattern... when he added throttle to level = off for=20 the traffic pattern the engine didn't respond... =20

I'm certainly glad the occupants got out OK. I look forward = to an=20 analysis of what caused the engine to not respond. Any thoughts?=20

Scott Krueger=20 AKA Grayhawk

Something similar happened to me after crossing the Rockies = in=20 my 112TC-A at 14,500 ft as I prepared to land at an airport in = a=20 rather narrow valley at 1100 ft ASL. After a steep descent from = altitude=20 at near idle power, at 1100 ft AGL when I advanced power, the engine = choked and=20 coughed like it was going to die. With a quick scan I realized the = mixture was=20 still at high-altitude lean. I enriched it, the engine growled=20 satisfyingly, and the flight ended safely a minute or so later. My = pax felt relieved; I felt somewhat = embarrassed.

Could the accident have been a forgotten = mixture=20 setting?

JHK

------=_NextPart_000_0021_01C60A09.AA0E5FD0--