X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 09 Sep 2010 20:07:36 -0400 Message-ID: X-Original-Return-Path: Received: from mail-px0-f180.google.com ([209.85.212.180] verified) by logan.com (CommuniGate Pro SMTP 5.3.9) with ESMTP id 4461175 for lml@lancaironline.net; Thu, 09 Sep 2010 14:47:17 -0400 Received-SPF: pass receiver=logan.com; client-ip=209.85.212.180; envelope-from=carbonflier@gmail.com Received: by pxi7 with SMTP id 7so865417pxi.25 for ; Thu, 09 Sep 2010 11:46:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=ISiAthaICbdXqttAyCVPk5JxuL4knHkkx96VsJDS5SzgBl/vjqNKtGA5bT7PLuhPQa sibBrD8K3DgV92buIPosHiPrJFwpV+lph++k0cs4HqgRKYvdm2/iR9pjLTCc8swDWN9q j++mGotpsQVTvdSKXLiA2kjiQ5dkwC1srzobE= Received: by 10.114.15.5 with SMTP id 5mr104621wao.200.1284058000348; Thu, 09 Sep 2010 11:46:40 -0700 (PDT) X-Original-Return-Path: Received: from [172.16.45.206] ([209.137.234.30]) by mx.google.com with ESMTPS id q6sm2769001waj.10.2010.09.09.11.46.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 09 Sep 2010 11:46:39 -0700 (PDT) X-Original-Message-ID: <4C892B94.80603@gmail.com> X-Original-Date: Thu, 09 Sep 2010 12:46:44 -0600 From: David Standish User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 X-Original-To: Lancair Mailing List Subject: Re: Re: Loss of use after prop damage References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit No invoices have been received or paid as of yet. The FBO's insurance company has been cooperative and not adversarial so far. We shall see when it is actually time for money to change hands if they are still so nice. David Gary Casey wrote: > I'm afraid I have no expertise in the conventions regarding "loss of > use", but I'm a little surprised that the insurance company would be > willing to pay for a teardown. As I understand it, the requirement > for a teardown after a prop strike evolved when occasional accessory > drive and magneto problems surfaced after an event. With the engine > not turning, none of those problems could occur and even a crankshaft > failure is almost impossible without the flange being bent. I can > understand TCM saying it was required, as it releases them from any > future liability - it would go to the rebuilder. And they're not > paying for it. And the owner would likely "require" a teardown for > the same reasons - and he's not paying for it and he logically wants > everything done that is possible. I'm only a little surprised at the > insurance company paying for it, as paying for the teardown helps > release them from future liability. It's all about putting up a > shield against future liability claims - all just my opinion, of > course :-) > Gary Casey > No law experience except on the receiving end of frivolous lawsuits > * > * > Any suggestions as to how to value loss of use of my airplane after my > propeller incident? The propeller was damaged by an FBO in Spokane. > Does any one know of some formula the insurance industry might use > based on typical hourly expense multiplied by days grounded? Would > one attempt to claim the expense of planned trips on the airlines vs. > expense of flying my airplane? For example the price of three airline > tickets to Reno less six hours expenses for my LNC-4. I was at the > beginning of a flying vacation when the incident happened. During > August to October I had planned to fly to Spokane (twice), Eugene, > Front Range, Races at Reno, and perhaps training at Napa. All those > airline tickets would be thousands of dollars not to mention loss of > use for spur of the moment purposes. > > The propeller is being repaired in Seattle. The engine is in the > middle of tear down for inspection in Tulsa (Barrett). TCM's position > was that if the propeller could not be repaired on the airplane that > mandatory tear down and inspection was required regardless of the > results of the propeller and prop. flange inspection. > > David >