X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: "Marvin Kaye" To: lml@lancaironline.net Date: Sun, 10 Apr 2005 11:04:28 -0400 Message-ID: X-Original-Return-Path: Received: from web60404.mail.yahoo.com ([216.109.118.187] verified) by logan.com (CommuniGate Pro SMTP 4.3c4) with SMTP id 863909 for lml@lancaironline.net; Sun, 10 Apr 2005 10:36:52 -0400 Received-SPF: none receiver=logan.com; client-ip=216.109.118.187; envelope-from=rkaplan@flyimc.com Received: (qmail 32871 invoked by uid 60001); 10 Apr 2005 14:36:03 -0000 X-Original-Message-ID: <20050410143603.32869.qmail@web60404.mail.yahoo.com> Received: from [151.201.243.214] by web60404.mail.yahoo.com via HTTP; Sun, 10 Apr 2005 07:36:03 PDT X-RocketYMMF: richardkaplan2 X-Original-Date: Sun, 10 Apr 2005 07:36:03 -0700 (PDT) From: Richard Kaplan Reply-To: rkaplan@flyimc.com Subject: Chelton EFIS-SV IFR Certification X-Original-To: lml@lancaironline.net MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Can pilots share their experience with certification of an experimental airplane with a Chelton EFIS-SV system? I have heard it said that the EFIS-SV system is not IFR-approved and thus separate IFR-approved avionics must be installed and operational to fly an approach with an EFIS-SV system. Chelton's literature in fact refers to this and quotes 91.205 -- but 91.205 refers to standard airworthiness category airplanes. 91.319 says no experimental airplane may be flown IFR without approval from the Administrator. Does that not give the Administrator discretion to approve an EFIS-SV for IFR navigation? Why is approval of an EFIS-SV for IFR navigation any different than approval of an airplane that is equipped with a non-TSO'd attitude indicator? It seems to me that since the operating logic of the EFIS-SV is so different than most other IFR GPS units, it would be a distraction to have the requirement to program IFR approaches both on the EFIS-SV system and on another GPS. Richard Kaplan rkaplan@flyimc.com www.flyimc.com