X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: "Marvin Kaye" To: lml@lancaironline.net Date: Mon, 11 Apr 2005 11:46:11 -0400 Message-ID: X-Original-Return-Path: Received: from imo-d20.mx.aol.com ([205.188.139.136] verified) by logan.com (CommuniGate Pro SMTP 4.3c4) with ESMTP id 864911 for lml@lancaironline.net; Mon, 11 Apr 2005 11:20:03 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.188.139.136; envelope-from=Sky2high@aol.com Received: from Sky2high@aol.com by imo-d20.mx.aol.com (mail_out_v38.7.) id q.d4.25c27b6a (4410) for ; Mon, 11 Apr 2005 11:19:13 -0400 (EDT) From: Sky2high@aol.com X-Original-Message-ID: X-Original-Date: Mon, 11 Apr 2005 11:19:13 EDT Subject: Re: [LML] Re: Chelton EFIC-SV IFR Certification X-Original-To: lml@lancaironline.net MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1113232753" X-Mailer: 9.0 Security Edition for Windows sub 5000 -------------------------------1113232753 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 4/11/2005 9:35:16 A.M. Central Standard Time, brent@regandesigns.com writes: _http://members.eaa.org/home/homebuilders/faq/Equipping%20a%20Homebuilt%20for% 20IFR%20operations.html_ (http://members.eaa.org/home/homebuilders/faq/Equipping%20a%20Homebuilt%20for%20IFR%20operations.html) Brent, Richard, et al, That is the best straight forward explanation of the IFR requirements I have ever read. Some years ago, when I installed (um, had installed) a Garmin 430, the shop had to have the DuPage FSDO sign off before the they could release the airplane. The FSDO would not accept the Rocky Mountain Micro-Encoder (meets TSO specs) as the altitude data source for the GPS - I had to install a TSO'd encoder. I had pleaded, cajoled, logically argued my RMI case and, ultimately, found it was easier to comply with the local FAAers (Hi, I am here to help you). BTW, I flew the required GPS flight check for the shop since none of them could understand 100+ Kts in the pattern (they could fly out but never return?). Times and FSDOs have changed - good luck Richard, whatever you decide. Scott Krueger AKA Grayhawk Lancair N92EX IO320 SB 89/96 Aurora, IL (KARR) Fair and Balanced Opinions at No Charge! Metaphysical Monologues used at your own Risk. -------------------------------1113232753 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
In a message dated 4/11/2005 9:35:16 A.M. Central Standard Time,=20 brent@regandesigns.com writes:
<= FONT=20 style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size= =3D2>
http://members.eaa.org/home/homebuilders= /faq/Equipping%20a%20Homebuilt%20for%20IFR%20operations.html

Brent, Richard, et al,
 
That is the best straight forward explanation of the IFR requirements I= =20 have ever read.
 
Some years ago, when I installed (um, had installed) a Garmin 430, the=20= shop=20 had to have the DuPage FSDO sign off before the they could release the=20 airplane.  The FSDO would not accept the Rocky Mountain Micro-Encoder=20 (meets TSO specs) as the altitude data source for the GPS - I had to install= a=20 TSO'd encoder.  I had pleaded, cajoled, logically argued my RMI=20 case and, ultimately, found it was easier to comply with the local= =20 FAAers (Hi, I am here to help you).
 
BTW, I flew the required GPS flight check for the shop since none of th= em=20 could understand 100+ Kts in the pattern (they could fly out but never=20 return?).
 
Times and FSDOs have changed - good luck Richard, whatever you decide.=20
 
Scott Krueger=20 AKA Grayhawk
Lancair N92EX IO320 SB 89/96
Aurora, IL (KARR)

Fai= r=20 and Balanced Opinions at No Charge!
Metaphysical Monologues used at your=20= own=20 Risk.

 -------------------------------1113232753--