X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Mon, 05 Nov 2012 11:39:16 -0500 Message-ID: X-Original-Return-Path: Received: from mtaz1.mailnet.ptd.net ([204.186.29.65] verified) by logan.com (CommuniGate Pro SMTP 6.0c2) with ESMTP id 5860568 for lml@lancaironline.net; Sat, 03 Nov 2012 07:37:53 -0400 Received-SPF: pass receiver=logan.com; client-ip=204.186.29.65; envelope-from=liegner@ptd.net Received: from mb7.mailnet.ptd.net (mb7.mailnet.ptd.net [204.186.29.17]) by mtaz1.mailnet.ptd.net (Postfix) with ESMTP id BA90432079D; Sat, 3 Nov 2012 07:37:18 -0400 (EDT) X-Original-Date: Sat, 03 Nov 2012 07:37:18 -0400 (EDT) From: jeffrey liegner X-Original-To: guyjill01@hotmail.com X-Original-Cc: lml@lancaironline.net Subject: re: Why is my fuel burn so high in my IV ???? X-Original-Message-ID: In-Reply-To: <9508402b-bd31-44da-8f12-c8c15190a4e4@mb7.mailnet.ptd.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Originating-IP: [184.6.215.116] X-Mailer: Zimbra 7.1.3_GA_3374 (ZimbraWebClient - SAF3 (Mac)/7.1.3_GA_3346) It would seem you are not LOP at this power setting, and in fact may be in the red box described by GAMI as within 50*F ROP, which is the place you do NOT want to be in regards to engine power settings and destructive effects. A GAMI Lean Test at 28"/2400 would define each cylinder's peak (should be <0.5 gph spread) and the fuel flows to best serve your needs. Jeff L LIVP From: Guy and Jill Foreman Subject: Why is my fuel burn so high in my IV ???? Date: November 2, 2012 7:50:50 AM EDT To: lml@lancaironline.net Reading some of the posts on the LML about IV/IVP drivers. Just wondering how they are getting around 18-19 GPH at cruze power? I have a straight IV with a TSIO-550-B. I usually fly around 10K feet, using 28in MAP, 2400 RPM, Leaning to 1550 TIT, and getting 21.5 GPH fuel burn. What am I doing wrong? How is everyone else getting there fuel flow so much lower? Any advice would be much appreciated. Thanks, Guy Foreman