X-Virus-Scanned: clean according to Sophos on Logan.com X-SpamCatcher-Score: 1 [X] Return-Path: Received: from [65.173.216.69] (account rob HELO [192.168.95.252]) by logan.com (CommuniGate Pro SMTP 5.1.5) with ESMTPSA id 1797249; Mon, 29 Jan 2007 13:01:52 -0500 Message-ID: <45BE362A.4060308@Logan.com> Date: Mon, 29 Jan 2007 13:00:10 -0500 From: Rob Logan User-Agent: Thunderbird 1.5.0.5 (X11/20060925) MIME-Version: 1.0 To: Lancair Mailing List Subject: Re: Turbine crash - power lost on takeoff: ba ba paperwork References: <45BE3110.2040008@meself.com> In-Reply-To: <45BE3110.2040008@meself.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit > From: Joel I was waiting for somebody to mention the obvious. Did anyone also notice that the field was in close proximity to Walter USA repair facility? I fly a turbine too and I think we should explore the root causes of the crash. I follow all turbine IVP incidents closely and a significant fraction of the fleet is no longer flying - pilot errors, stall practice after converting plane from piston to turbine, engine failure twice in two weeks with landing on icy runway totalling plane, another early model non-fastbuild window blowout, driving one into water near Provo, fuel mismanagement over Georgia, etc. Almost all of these were preventable. So now that we exhausted the paperwork issue let's try to get some info that may make IVPs and turbines in particular safer and insurable. So who has the scoop on this crash? Joel - N42GG IVPT [ the meself.com mailserver (MX) didn't accept a callback for joel and this message was rejected. I found it in the system wide spam folder that I often trash without looking at -Rob@Logan.com ]