X-Virus-Scanned: clean according to Sophos on Logan.com
Return-Path: <marv@lancaironline.net>
Sender: <marv@lancaironline.net>
To: lml
Date: Tue, 14 Nov 2006 12:49:14 -0500
Message-ID: <redirect-1565027@logan.com>
X-Original-Return-Path: <kevin@airforcemechanical.com>
Received: from vms042pub.verizon.net ([206.46.252.42] verified)
  by logan.com (CommuniGate Pro SMTP 5.1.2)
  with ESMTP id 1564709 for lml@lancaironline.net; Tue, 14 Nov 2006 11:11:05 -0500
Received: from [192.168.111.2] ([70.18.205.49])
 by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr
 3 2006)) with ESMTPA id <0J8Q0090OA8XYI41@vms042.mailsrvcs.net> for
 lml@lancaironline.net; Tue, 14 Nov 2006 10:10:09 -0600 (CST)
X-Original-Date: Tue, 14 Nov 2006 11:10:05 -0500
From: Kevin Kossi <kevin@airforcemechanical.com>
Subject: Re: [LML] for the record
In-reply-to: <list-1564496@logan.com>
X-Original-To: "Lancair Mailing List" <lml@lancaironline.net>
X-Original-Message-id: <B769AD1C-1866-4CC3-8600-3207D6048872@airforcemechanical.com>
MIME-version: 1.0 (Apple Message framework v752.2)
X-Mailer: Apple Mail (2.752.2)
Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-transfer-encoding: 7bit
References: <list-1564496@logan.com>

I am starting to wonder if it is a bad idea for the LML to be used as  
a form for speculation regarding the causes of an accident,  
especially after a death.
Would it make more sense to wait until the NTSB publicly publishes  
their results. At which time we can have an informed dialogue where  
we all can potentially learn something from the tragedy.


Person's and companies reputations are at stake in this.


Just my thoughts open for discussion



Kevin Kossi