X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Wed, 26 Sep 2007 00:55:05 -0400 Message-ID: X-Original-Return-Path: Received: from fmailhost01.isp.att.net ([204.127.217.101] verified) by logan.com (CommuniGate Pro SMTP 5.1.12) with ESMTP id 2351999 for lml@lancaironline.net; Tue, 25 Sep 2007 23:15:35 -0400 Received-SPF: pass receiver=logan.com; client-ip=204.127.217.101; envelope-from=Lancair1@bellsouth.net Received: from p4desktop (unknown[74.235.133.224]) by bellsouth.net (frfwmhc01) with SMTP id <20070926031457H01002dvmle>; Wed, 26 Sep 2007 03:14:57 +0000 X-Originating-IP: [74.235.133.224] From: "Douglas W. Johnson, MD" X-Original-To: "Lancair Mailing List" Subject: Airspeed Indicator Consult X-Original-Date: Tue, 25 Sep 2007 23:15:26 -0400 X-Original-Message-ID: <020d01c7ffeb$7c75a270$6501a8c0@p4desktop> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_020E_01C7FFC9.F5640270" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Thread-Index: Acf/63vN5hrBYkE5Qre+/rILXfyQbA== This is a multi-part message in MIME format. ------=_NextPart_000_020E_01C7FFC9.F5640270 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In true medical fashion, I would like to request of you all 2nd and 3rd opinions about the cause of an Airspeed Indicator (AS) problem I developed last week. The problem: I am getting erroneously low (by 20-40kts) AS readings. This came about suddenly, and has never been a problem before. The history: First, you must know that the plane (L-IVP) has 970hrs TT and has always had a very accurate AS, matching very closely GPS readings (adjusting for wind and altitude) over the last 10 years. It is my habit to always verbally call out "airspeed alive" as I accelerate down the runway for takeoff--the AS usually becomes active at about 40kts or so. Recently, however, the AS did NOT become active at the usual spot down the runway during a takeoff run, despite a normal runup and full power settings. Just as I pulled the power to abort the takeoff, the AI seemed to bump to life. I exited the runway and regrouped. I shut down and inspected everything externally--all looked good. Oh well, perhaps I had inadvertently left the pitot cover on, and it later blew off as I ran down the runway, I thought (no dice, as it turns out, as I later found the cover safely stowed in the baggage compartment). Sooo, I tried another takeoff with the same result--this time the AS became active, but far down the runway, and I aborted again. The local A&P did a thorough inspection of the pitot system (all A-OK), and did a full test of the AS with a meter attached to the pitot tube showing that indicated AS was the same as the metered setting on the calibration device through a full normal range of speeds up to VNE. He also "set" an airspeed with the pressure on the pitot and clamped it off, making sure there was no decay in the indicated airspeed, which might have indicated a leak in the pitot system. He also disconnected the pitot system within the cockpit and reverse blew some air back out toward the pitot tube, on the outside chance a bug or something had temporarily blocked the system. All appeared normal, so I went out today to do another test flight. Results: I ran down the runway today once again after normal runup at full power. Once again, NO active AS at the usual point. I decided to proceed with the takeoff referring to the GPS speed. After takeoff and climbing into the pattern at 120kts (GPS) the AS started swinging back and forth between 70 and 88kts--it never stabilized and I could not even retract the gear, indicating that the squat switch did not think I had enough airspeed to trip the solenoid. I brought the plane around the pattern and landed without incident, using the GPS speed indication + a good margin for safety. The AS throughout the flight was always significantly below normal reading by anywhere from 15-40kts. So, we have here a situation in which the AS tested out fine on the ground, and bad in the air. Any idea why? The mechanic is stumped. I am stumped. One opinion has suggested that the gear speed switch diaphragm may have ruptured, but wouldn't that result in a decay in indicated speed with a test device putting clamped air pressure on the pitot tube? Help and ideas appreciated. Doug Johnson ------=_NextPart_000_020E_01C7FFC9.F5640270 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
In = true medical=20 fashion, I would like to request of you all 2nd and 3rd opinions about = the cause=20 of an Airspeed Indicator (AS) problem I developed last = week.
 
The = problem: I am=20 getting erroneously low (by 20-40kts) AS readings. This came about = suddenly, and=20 has never been a problem before.
 
The = history:=20
 
First, = you must know=20 that the plane (L-IVP) has 970hrs TT and has always had a very accurate = AS,=20 matching very closely GPS readings (adjusting for wind and altitude) = over the=20 last 10 years.
 
It is = my habit to=20 always verbally call out "airspeed alive" as I accelerate down the = runway for=20 takeoff--the AS usually becomes active at about 40kts or so.  = Recently,=20 however, the AS did NOT become active at the usual spot down the runway = during a=20 takeoff run, despite a normal runup and full power settings. Just as I = pulled=20 the power to abort the takeoff, the AI seemed to bump to = life.  I=20 exited the runway and regrouped. I shut down and inspected everything=20 externally--all looked good. Oh well, perhaps I had inadvertently left = the pitot=20 cover on, and it later blew off as I ran down the runway, I = thought (no=20 dice, as it turns out, as I later found the cover safely stowed in the = baggage=20 compartment). Sooo, I tried another takeoff with the same result--this = time the=20 AS became active, but far down the runway, and I aborted=20 again.
 
The = local A&P=20 did a thorough inspection of the pitot system (all A-OK), and did a full = test of=20 the AS with a meter attached to the pitot tube showing that indicated AS = was the=20 same as the metered setting on the calibration device through a full = normal=20 range of speeds up to VNE. He also "set" an airspeed with the pressure = on the=20 pitot and clamped it off, making sure there was no decay in the = indicated=20 airspeed, which might have indicated a leak in the pitot system. He also = disconnected the pitot system within the cockpit and reverse blew some = air back=20 out toward the pitot tube, on the outside chance a bug or something had=20 temporarily blocked the system.  All appeared normal, so I went out = today=20 to do another test flight.
 
Results: I ran down=20 the runway today once again after normal runup at full power. Once = again, NO=20 active AS at the usual point. I decided to proceed with the takeoff = referring to=20 the GPS speed.  After takeoff and climbing into the pattern at = 120kts (GPS)=20 the AS started swinging back and forth between 70 and 88kts--it never = stabilized=20 and I could not even retract the gear, indicating that the squat switch = did not=20 think I had enough airspeed to trip the solenoid. I brought the plane = around the=20 pattern and landed without incident, using the GPS speed = indication +=20 a good margin for safety. The AS throughout the flight was always = significantly=20 below normal reading by anywhere from 15-40kts.
 
So, we = have here a=20 situation in which the AS tested out fine on the ground, and bad in the = air. Any=20 idea why?
 
The = mechanic is=20 stumped. I am stumped. One opinion has suggested that the gear speed = switch=20 diaphragm may have ruptured, but wouldn't that result in a decay=20 in indicated speed with a test device putting clamped air = pressure on=20 the pitot tube? 
 
Help = and ideas=20 appreciated.

Doug Johnson

------=_NextPart_000_020E_01C7FFC9.F5640270--