X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Mon, 14 Nov 2005 00:06:34 -0500 Message-ID: X-Original-Return-Path: Received: from imo-m20.mx.aol.com ([64.12.137.1] verified) by logan.com (CommuniGate Pro SMTP 5.0.1) with ESMTP id 829835 for lml@lancaironline.net; Sun, 13 Nov 2005 23:34:20 -0500 Received-SPF: pass receiver=logan.com; client-ip=64.12.137.1; envelope-from=Sky2high@aol.com Received: from Sky2high@aol.com by imo-m20.mx.aol.com (mail_out_v38_r6.3.) id q.110.56faf2b3 (17377) for ; Sun, 13 Nov 2005 23:33:31 -0500 (EST) From: Sky2high@aol.com X-Original-Message-ID: <110.56faf2b3.30a96d9b@aol.com> X-Original-Date: Sun, 13 Nov 2005 23:33:31 EST Subject: Re: [LML] Re: Navigating in the IFR system in an experimental aircraft X-Original-To: lml@lancaironline.net MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1131942811" X-Mailer: 9.0 Security Edition for Windows sub 5300 X-Spam-Flag: NO -------------------------------1131942811 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 11/13/2005 10:16:59 P.M. Central Standard Time, cfi@instructor.net writes: Just another FYI, I'll bet there are a bunch of you out there flying in the IFR environment using GPS that do not have the required documentation from the local FSDO. You cannot fly legally without this paperwork, and also includes a POH suplement. I give WINGS seminars on this subject all over the Mountain states, and can elaborate more if there is interest. Ron, I have such documentation and a POH supplement because I had the 430 installed by an actual avionics shop before Garmin would sell direct to a builder and the shop wouldn't release my airplane until the FSDO signed off on the installation. I did have a little discussion with the FSDO about why I couldn't use my RMI micro-encoder as the altitude source for the GPS - even though it met TSO specs, it was not TSO'd. I had to buy an inferior TSO'd unit. FSDO could never explain the difference and I had to succumb to the interpretations of a functionary to get the signoff rather than continue to tilt his windmill. However, I thought the FSDO doc rule was rescinded a year or two ago? Anyone at a famous Lancair avionics shop care to comment? Scott Krueger AKA Grayhawk Lancair N92EX IO320 SB 89/96 Aurora, IL (KARR) PS: OTP = VFR ON TOP? -------------------------------1131942811 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

In a message dated 11/13/2005 10:16:59 P.M. Central Standard Time,=20 cfi@instructor.net writes:

<= FONT=20 style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size= =3D2>Just=20 another FYI, I'll bet there are a bunch of you out there flying in the IFR= =20 environment using GPS that do not have the required documentation from the= =20 local FSDO. You cannot fly legally without this paperwork, and also=20 includes a POH suplement. I give WINGS seminars on this subject all=20= over=20 the Mountain states, and can elaborate more if there is interest. =20

Ron,

I have such documentation and a POH supplement because I had the 430=20 installed by an actual avionics shop before Garmin would sell direct to a=20 builder and the shop wouldn't release my airplane until the FSDO=20 signed off on the installation. I did have a little discussion with th= e=20 FSDO about why I couldn't use my RMI micro-encoder as the altitude source fo= r=20 the GPS - even though it met TSO specs, it was not TSO'd. I had to buy an=20 inferior TSO'd unit. FSDO could never explain the difference= and=20 I had to succumb to the interpretations of a functionary to get th= e=20 signoff rather than continue to tilt his windmill.

However, I thought the FSDO doc rule was rescinded a year or two ago?&n= bsp;=20 Anyone at a famous Lancair avionics shop care to comment?

Scott Krueger=20 AKA Grayhawk
Lancair N92EX IO320 SB 89/96
Aurora, IL=20 (KARR)

PS: OTP =3D VFR=20 ON TOP?

-------------------------------1131942811--