X-Virus-Scanned: clean according to Sophos on Logan.com
Return-Path: <marv@lancaironline.net>
Sender: <marv@lancaironline.net>
To: lml@lancaironline.net
Date: Sat, 09 Jul 2005 17:33:17 -0400
Message-ID: <redirect-1051586@logan.com>
X-Original-Return-Path: <colyncase@earthlink.net>
Received: from HQEMGATE01.nvidia.com ([216.228.112.170] verified)
  by logan.com (CommuniGate Pro SMTP 4.3.6)
  with ESMTP id 1051323 for lml@lancaironline.net; Sat, 09 Jul 2005 11:13:54 -0400
Received-SPF: none
 receiver=logan.com; client-ip=216.228.112.170; envelope-from=colyncase@earthlink.net
Received: from hqemfe03.nvidia.com (Not Verified[172.16.227.123]) by HQEMGATE01.nvidia.com
	id <B42cfe9830001>; Sat, 09 Jul 2005 08:13:07 -0700
Received: from ccaselt ([172.16.228.84]) by hqemfe03.nvidia.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Sat, 9 Jul 2005 08:13:03 -0700
X-Original-Message-ID: <0f4901c58498$b3ae57d0$5d11020a@nvidia.com>
From: "colyncase on earthlink" <colyncase@earthlink.net>
X-Original-To: "Lancair Mailing List" <lml@lancaironline.net>
References: <list-1051268@logan.com>
Subject: Re: [LML] Re: Turbo Loss Consequences
X-Original-Date: Sat, 9 Jul 2005 08:13:01 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Original-Return-Path: colyncase@earthlink.net
X-OriginalArrivalTime: 09 Jul 2005 15:13:03.0756 (UTC) FILETIME=[B3DF04C0:01C58498]

George et al,

I don't think anyone has said yet what you actually end up with for 
available MP
in the case of a hard turbo failure.
e.g. let's take the classic turbine wheel jams scenario, causing a pretty 
good blockage
on that compressor.   You're now feeding the whole engine from the other 
turbo. Am I right
that you are now at NA power levels or less before you execute your safety 
procedures?

Colyn