X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Fri, 26 Aug 2005 15:05:39 -0400 Message-ID: X-Original-Return-Path: Received: from mta10.adelphia.net ([68.168.78.202] verified) by logan.com (CommuniGate Pro SMTP 5.0c1) with ESMTP id 682939 for lml@lancaironline.net; Fri, 26 Aug 2005 13:24:36 -0400 Received-SPF: pass receiver=logan.com; client-ip=68.168.78.202; envelope-from=dfs155@adelphia.net Received: from f3g6s4 ([67.22.49.202]) by mta10.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with SMTP id <20050826172344.SFAU19267.mta10.adelphia.net@f3g6s4> for ; Fri, 26 Aug 2005 13:23:44 -0400 X-Original-Message-ID: <007701c5aa63$53fcfc60$ca311643@losaca.adelphia.net> From: "Dan Schaefer" X-Original-To: "Lancair list" Subject: Re: Lancair Accident Info X-Original-Date: Fri, 26 Aug 2005 10:26:42 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Chris Zavatson wrote: >>>On top of that, most prop strikes, gear-up landings etc. never make into the NTSB data base.<<< Chris, following a gear-up experienced by a friend in his Falco a couple of years ago here in Coeur d'Alene, Idaho, (mechanism failure - not a head failure) the local FSDO in Spokane referred to it as an "incident" rather than an accident. I don't think "incidents" make it into the database. Perhaps if there had been an injury or fatality that would change the characterization. I believe prop strikes, if even reported, fall into the same category. I'm sure we have some Friendly Aviation Administration types on the list - what say you? Dan Schaefer