X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 20 Sep 2007 10:24:46 -0400 Message-ID: X-Original-Return-Path: Received: from elasmtp-kukur.atl.sa.earthlink.net ([209.86.89.65] verified) by logan.com (CommuniGate Pro SMTP 5.1.12) with ESMTP id 2341730 for lml@lancaironline.net; Thu, 20 Sep 2007 08:56:37 -0400 Received-SPF: none receiver=logan.com; client-ip=209.86.89.65; envelope-from=rtitsworth@mindspring.com DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=EbCofuwMjydugoiHba+pbFrt4pAmDqB050kbX1JqDiTr3mLif1V3zBbuQbcA1SRi; h=Received:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:In-Reply-To:X-MimeOLE:thread-index:X-ELNK-Trace:X-Originating-IP; Received: from [71.238.59.21] (helo=RDTVAIO) by elasmtp-kukur.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1IYLZY-0002zm-8f for lml@lancaironline.net; Thu, 20 Sep 2007 08:56:00 -0400 From: "rtitsworth" X-Original-To: "'Lancair Mailing List'" Subject: RE: [LML] product liability X-Original-Date: Thu, 20 Sep 2007 08:55:35 -0400 X-Original-Message-ID: <009f01c7fb85$897c8610$6600a8c0@RDTVAIO> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A0_01C7FB64.026AE610" X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 thread-index: Acf7ggyne7aOz+HVSuG1bz7J3LrlogAArRDA X-ELNK-Trace: b17f11247b2ac8f0a79dc4b33984cbaa0a9da525759e2654621bb17abdb1cfec40e6bc3743991cc992764449e275203c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 71.238.59.21 This is a multi-part message in MIME format. ------=_NextPart_000_00A0_01C7FB64.026AE610 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Note, the FAA normally requires a "builder" to be a human (same for the name on the repairman certificate). You can register the "owner" of the aircraft as a non-human entity. However, future lawsuits could still be directed toward you personally as the "builder". Some folks have got a non-human entity listed as the builder with the FAA - but that is not the normal FAA process/policy. (only my understanding) Rick _____ From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Russell Sent: Thursday, September 20, 2007 8:31 AM To: lml@lancaironline.net Subject: [LML] product liability Years ago I was involved with the company that manufactured cloth towel cabinets used in public restrooms. To our surprise kids were hanging in themselves in the loop of the towel. We had several lawsuits and we were able defend ourselves. It was very costly. The interesting thing was many of these cabinets were over 30 to 40 years old and rebuilt by other companies. We ended up taking steps of plastering warning labels and specials shields on the cabinets. It seemed to work. But presently you do not see this product on the market in this country any more. I'm about to start building my legacy and I'm very concerned about liability. Something no one mentioned but I am doing is creating a company for the aircraft. I am going to build the aircraft under the entity other than myself. Whenever it's time to depart with the aircraft the company will be sold with its assets. It happens to be the only asset will be the aircraft. After putting my blood sweat and tears into this project there is no way I can take a chainsaw to it. So creating layers of protection is the only way to cover ones behind. Russell No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.487 / Virus Database: 269.13.22/1013 - Release Date: 9/17/2007 1:29 PM ------=_NextPart_000_00A0_01C7FB64.026AE610 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Note, the FAA normally requires a = “builder” to be a human (same for the name on the repairman certificate). = You can register the “owner” of the aircraft as a non-human entity. = However, future lawsuits could still be directed toward you personally as the = “builder”. Some folks have got a non-human entity listed as the builder with the = FAA – but that is not the normal FAA = process/policy.

(only my = understanding)

Rick

From: = Lancair Mailing List = [mailto:lml@lancaironline.net] On Behalf Of Russell
Sent: Thursday, September = 20, 2007 8:31 AM
To: = lml@lancaironline.net
Subject: [LML] product = liability

Years ago I was involved with the company that manufactured cloth towel = cabinets used in public restrooms. To our surprise kids were hanging in = themselves in the loop of the towel. We had several lawsuits and we were able = defend ourselves. It was very costly. The interesting thing was many of = these cabinets were over 30 to 40 years old and rebuilt by other = companies. We ended up taking steps of plastering warning labels and specials shields = on the cabinets. It seemed to work. But presently you do not see this = product on the market in this country any more.

I’m about to start building my legacy and I’m very concerned about = liability. Something no one mentioned but I am doing is creating a company for the aircraft. I am going to build the aircraft under the entity other = than myself. Whenever it’s time to depart with the aircraft the = company will be sold with its assets. It happens to be the only asset will = be the aircraft. After putting my blood sweat and tears into this project = there is no way I can take a chainsaw to it. So creating layers of = protection is the only way to cover ones behind.

Russell

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.487 / Virus Database: 269.13.22/1013 - Release Date: = 9/17/2007 1:29 PM

------=_NextPart_000_00A0_01C7FB64.026AE610--