Received-SPF: pass
 receiver=logan.com; client-ip=206.46.173.1; envelope-from=N4ZQ@VERIZON.NET
Content-type: text/plain; charset=iso-8859-1
MIME-version: 1.0 (Apple Message framework v1085)
Subject: Re: Fuel flow
From: "Greenbacks, UnLtd." <N4ZQ@VERIZON.NET>
In-reply-to: <listdigest-6309035@logan.com>
Date: Wed, 05 Jun 2013 15:13:49 -0400
Content-transfer-encoding: quoted-printable
Message-id: <4AAE0EEC-8035-4449-AC33-630DF80FA10C@VERIZON.NET>
References: <listdigest-6309035@logan.com>
To: "Lancair Mailing List" <lml@lancaironline.net>

The 550 mile flight this morning from KBVY-KRKD-KEPM-KBVY was crystal =
clear VFR with 195kts TAS, 5500ft, 24"MP, 2400RPM, 8.2GPH, 25=BALOP
and 22.5MPG...not too shabby for this little pip-sqweak of a plane.=20

The good news is that my continuing issue with erratic MVP-50 fuel flow =
readings
has now been identified but the solution will be a real pain to fix. =
Turning off the ALT instantly caused FF readings to become rock solid! =
Go figure.
I'll have to remove the cowl in order to refresh my aging memory on how =
the ALT output lead is plumbed but at some point it must be too close to =
the FF cable. After the fact it sounds like common sense but don't run =
any sensor wires aft from the engine compartment in the same wire bundle =
which includes the ALT lead. Short of relocating wires, do we have an =
electrical wizard here with a more elegant solution? I suppose that any =
time I want to see accurate fuel data, I could simply shut off the ALT =
for a few seconds. :-)

Angier Ames
N4ZQ
35hrs
  =20=