X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Wed, 23 Jan 2013 08:27:55 -0500 Message-ID: X-Original-Return-Path: Received: from imr-db01.mx.aol.com ([205.188.91.95] verified) by logan.com (CommuniGate Pro SMTP 6.0.1) with ESMTP id 6024862 for lml@lancaironline.net; Tue, 22 Jan 2013 21:56:50 -0500 Received-SPF: pass receiver=logan.com; client-ip=205.188.91.95; envelope-from=vtailjeff@aol.com Received: from mtaout-da06.r1000.mx.aol.com (mtaout-da06.r1000.mx.aol.com [172.29.51.134]) by imr-db01.mx.aol.com (Outbound Mail Relay) with ESMTP id D3328380000DE for ; Tue, 22 Jan 2013 21:56:16 -0500 (EST) Received: from [10.90.120.237] (mobile-166-147-080-156.mycingular.net [166.147.80.156]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-da06.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 946E5E0000AA; Tue, 22 Jan 2013 21:56:14 -0500 (EST) References: In-Reply-To: Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-4372CC82-90A6-4CE2-81E2-31ECF1B9BCCD X-Original-Message-Id: <261A0E54-1AB2-4252-A021-0AB0E02E1AA2@aol.com> Content-Transfer-Encoding: 7bit X-Mailer: iPad Mail (9B206) From: vtailjeff@aol.com Subject: Re: [LML] Re: the Legacy RG Static ports X-Original-Date: Tue, 22 Jan 2013 18:56:11 -0800 X-Original-To: Lancair Mailing List x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:402312064:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d338650ff514e0cb1 X-AOL-IP: 166.147.80.156 --Apple-Mail-4372CC82-90A6-4CE2-81E2-31ECF1B9BCCD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii What is the tower pass for? Sent from my iPad On Jan 22, 2013, at 12:47 PM, Joseph Czabaranek wr= ote: > My point was not very clear in that last post. If your airspeed is indica= ting incorrect, could modifying the static port to fix the airspeed problem= just be masking a problem with something else at the expense of a correct a= ltimeter? >=20 > Joe Czabaranek >=20 > On Jan 22, 2013, at 3:25 PM, Joseph Czabaranek w= rote: >=20 >> I havent bothered to check indicated airspeed or my altimeter in my 360. = My static ports are flush. They look like someone drilled a .010" hole thr= ough the paint/clear coat. =20 >>=20 >> Before you all added elevation to your static ports did you bother to che= ck the altimeter? At 1000' MSL on a standard day, a .02" error in your stat= ic line would give a 20' baro altitude error AND a 1.5 KIAS error (at about= 150 KIAS), IF your pitot line was measuring total pressure correctly. An i= ndicated airspeed error could be more than just your static port ... >>=20 >> A low pass at tower level to +/- 20' might be more accurate than trying t= o fly multiple legs of a course and measuring your KIAS to +/- 1.5 kts >>=20 >>=20 >> On Tue, Jan 22, 2013 at 12:25 PM, Dennis Johnson w= rote: >> I have a Legacy RG and put my static ports flush with the outer skin, loc= ated in accordance with the assembly manual. During my flight test phase, I= pleasantly noticed that I always had a tailwind! I knew I was lucky to be f= lying such a wonderful airplane and just figured I was equally lucky to alwa= ys have a tailwind. >>=20 >> Eventually, logic prevailed and I realized nobody could be that lucky. I= flew the four course GPS airspeed check and discovered that my indicated ai= rspeed was reading low. I added a tiny piece of machined aluminum, similar t= o a domed head rivet, to both static ports and it solved the problem. Other= Legacy builders who installed their static ports protruding slightly tell m= e that their indicated airspeed is accurate. >>=20 >> Dennis >> Legacy 580 hours=20 >>=20 >> -- >> For archives and unsub http://mail.lancaironline.net:81/lists/lml/List.ht= ml >>=20 --Apple-Mail-4372CC82-90A6-4CE2-81E2-31ECF1B9BCCD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
What is the tower pass for= ?

Sent from my iPad

On Jan 22, 2013, at 12:47 PM, Josep= h Czabaranek <joeczabaranek@gm= ail.com> wrote:

<= div>My point was not very clear in that last post.  If your airspeed is= indicating incorrect,  could modifying the static port to fix the airs= peed problem just be masking a problem with something else at the expense of= a correct altimeter?

Joe Czabaranek

On Jan 22, 2013, a= t 3:25 PM, Joseph Czabaranek <= joeczabaranek@gmail.com> wrote:

I havent bothered to check indicated airspeed or my a= ltimeter in my 360.  My static ports are flush.  They look like so= meone drilled a .010" hole through the paint/clear coat.  

Before you all added elevation to your static ports did you bother to check t= he altimeter?  At 1000' MSL on a standard day, a .02" error in your sta= tic line would give a 20' baro altitude error  AND a 1.5 KIAS error (at= about 150 KIAS), IF your pitot line was measuring total pressure correctly.=  An indicated airspeed error could be more than just your static port .= ..

A low pass at tower level to +/- 2= 0' might be more accurate than trying to fly multiple legs of a course and m= easuring your KIAS to +/- 1.5 kts

=
On Tue, Jan 22, 2013 at 12:25 PM, Dennis Johnson <= span dir=3D"ltr"><pinetownd@volcano.net> wrote:
I have a Legacy RG and put my static ports flush with the outer skin, locate= d in accordance with the assembly manual.  During my flight test phase,= I pleasantly noticed that I always had a tailwind!  I knew I was lucky= to be flying such a wonderful airplane and just figured I was equally lucky= to always have a tailwind.

Eventually, logic prevailed and I realized nobody could be that lucky.  = ;I flew the four course GPS airspeed check and discovered that my indicated a= irspeed was reading low.  I added a tiny piece of machined aluminum, si= milar to a domed head rivet, to both static ports and it solved the problem.=  Other Legacy builders who installed their static ports protruding sli= ghtly tell me that their indicated airspeed is accurate.

Dennis
Legacy 580 hours

--
For archives and unsub http://mail.lancaironline.net:81/lists/= lml/List.html

= --Apple-Mail-4372CC82-90A6-4CE2-81E2-31ECF1B9BCCD--