X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 05 Jul 2007 15:46:12 -0400 Message-ID: X-Original-Return-Path: Received: from mail.glasair.org ([65.75.24.102] verified) by logan.com (CommuniGate Pro SMTP 5.1.10) with ESMTPS id 2159506 for lml@lancaironline.net; Thu, 05 Jul 2007 09:53:24 -0400 Received-SPF: none receiver=logan.com; client-ip=65.75.24.102; envelope-from=Bruce@glasair.org Received: from glasair1 by mail.glasair.org (VisNetic.MailServer.v8.5.0.8) with ESMTP id KUF66945 for ; Thu, 05 Jul 2007 09:52:45 -0400 From: "Bruce Gray" X-Original-To: "'Lancair Mailing List'" Subject: RE: [LML] Re: ADAHRS TSO X-Original-Date: Thu, 5 Jul 2007 09:52:42 -0400 X-Original-Message-ID: <001001c7bf0b$c2929400$0f01a8c0@glasair1> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: Importance: Normal Don't forget the third ADI tie breaker gyro! Bruce www.glasair.org -----Original Message----- From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Lancair Sent: Thursday, July 05, 2007 9:45 AM To: lml@lancaironline.net Subject: [LML] Re: ADAHRS TSO 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). Thoughts? Robert M. Simon ES-P N301ES ________________________________ From: Brent Regan [mailto:brent@regandesigns.com] 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 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. -- For archives and unsub http://mail.lancaironline.net:81/lists/lml/List.html