X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Mon, 30 Jun 2008 21:04:22 -0400 Message-ID: X-Original-Return-Path: Received: from wind.imbris.com ([216.18.130.7] verified) by logan.com (CommuniGate Pro SMTP 5.2.4) with ESMTPS id 2997820 for lml@lancaironline.net; Mon, 30 Jun 2008 11:07:49 -0400 Received-SPF: none receiver=logan.com; client-ip=216.18.130.7; envelope-from=brent@regandesigns.com Received: from [192.168.1.144] (cbl-238-80.conceptcable.com [207.170.238.80] (may be forged)) (authenticated bits=0) by wind.imbris.com (8.14.2/8.12.11.S) with ESMTP id m5UF6njN056922 for ; Mon, 30 Jun 2008 08:06:55 -0700 (PDT) (envelope-from brent@regandesigns.com) X-Original-Message-ID: <4868F684.6030308@regandesigns.com> X-Original-Date: Mon, 30 Jun 2008 08:06:44 -0700 From: Brent Regan User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 X-Original-To: Lancair Mailing List Subject: Re: Chelton as a Flight Data Recorder: Post Accident Analysis Content-Type: multipart/alternative; boundary="------------000303010404090608060909" This is a multi-part message in MIME format. --------------000303010404090608060909 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Nudge nudge, wink wink, say no more. Jeff writes: <> This is more a legal question than a practical one. It comes down to who owns the data contained in the EFIS. If you think of it as a log book, then the NTSB can view and inspect it but it remains the property of the owner and likely covered under the fourth amendment. You must also consider that the last ~ 10 lights are recorded. I treat the raw data as "confidential" and will only share the data with the NTSB, the owner and the owners designate. Bottom line is that you would need the owners (or their estate's) permission, or have it be part of discovery in a legal proceeding, or be part of the investigating team to get at the raw data. Even then, interpreting the data requires an intimate knowledge of the aircraft configuration and the scope and limitations of the data capture. I doubt its usefulness to the average pilot. BTW, the NTSB has enacted a policy to have the data extraction and diagnostic equipment in house. Regards Brent Regan --------------000303010404090608060909 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Nudge nudge, wink wink, say no more.

Jeff writes:

<<I think there is a need for this type of detail beyond the NTSB summary report. Does anyone agree, and does anyone know how to gain access to it?>>

This is more a legal question than a practical one. It comes down to who owns the data contained in the EFIS. If you think of it as a log book, then the NTSB can view and inspect it but it remains the property of the owner and likely covered under the fourth amendment. You must also consider that the last ~ 10 lights are recorded. I treat the raw data as "confidential" and will only share the data with the NTSB, the owner and the owners designate.

Bottom line is that you would need the owners (or their estate's) permission, or have it be part of discovery in a legal proceeding, or be part of the investigating team to get at the raw data. Even then, interpreting the data requires an intimate knowledge of the aircraft configuration and the scope and limitations of the data capture. I doubt its usefulness to the average pilot.

BTW, the NTSB has enacted a policy to have the data extraction and diagnostic equipment in house.

Regards
Brent Regan
--------------000303010404090608060909--