X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 05 Jul 2007 09:44:43 -0400 Message-ID: X-Original-Return-Path: Received: from [70.62.14.124] (HELO server1.USTEK) by logan.com (CommuniGate Pro SMTP 5.1.10) with ESMTP id 2159336 for lml@lancaironline.net; Thu, 05 Jul 2007 08:39:26 -0400 Received-SPF: none receiver=logan.com; client-ip=70.62.14.124; envelope-from=r.simon@ustek.com Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: ADAHRS TSO X-MimeOLE: Produced By Microsoft Exchange V6.5 X-Original-Date: Thu, 5 Jul 2007 08:41:29 -0400 X-Original-Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ADAHRS TSO Thread-Index: Ace/Ac8z+FH5itLZSP64GmjaV8PTvw== From: "Lancair" X-Original-Sender: "Robert Simon" X-Original-To: "Brent Regan" , I will certainly check into this. But the problem brought up a limitation to my panel - lack of ADHRS redundancy. I started shopping and found that a second Pinpoint might cost $17k whilst a new-and-improved Crossbow 425 is about $3k. I'm now considering the current Pinpoint running screens 1 an 3 and the Crossbow feeding screen 2. (after we have traced down the current problem naturally). =20 =20 Thoughts? =20 Robert M. Simon ES-P N301ES ________________________________ From: Brent Regan [mailto:brent@regandesigns.com]=20 Sent: Tuesday, July 03, 2007 3:18 PM To: lml@lancaironline.net Subject: Re: ADAHRS TSO Robert writes: <The displays reverted to the "blue screen of death" and I landed actually looking out the window. The screens stayed blue for the next short hop, but after that they came up and ran fine to the completion of the=20 flight. After the paint is complete and I am back in the air I'll be interested to see if this fall out repeats. >> Robert, you have a problem and you need to identify the source. . . . My strong recommendation is that Robert take steps to find and eliminate the source of the failure. The "wait and see" approach is unacceptable. If a fault happened then it happened for a reason and that reason, at a minimum, must be identified. Contact the avionics installer and relate ALL information surrounding the fault. He should download and forward the log files to CFS for analysis.=20