X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Wed, 05 Mar 2014 07:28:33 -0500 Message-ID: X-Original-Return-Path: Received: from mailgate.tru.ca ([192.146.156.111] verified) by logan.com (CommuniGate Pro SMTP 6.0.8) with ESMTP id 6759824 for lml@lancaironline.net; Tue, 04 Mar 2014 15:34:23 -0500 Received-SPF: none receiver=logan.com; client-ip=192.146.156.111; envelope-from=DBaleshta@tru.ca Received: from mailgate.tru.ca (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 0DB0838461 for ; Tue, 4 Mar 2014 12:28:59 -0800 (PST) Received: from mail-relay.tru.ca (mail-relay.tru.ca [192.146.156.166]) by mailgate.tru.ca (Postfix) with ESMTP id A0C8A384F5 for ; Tue, 4 Mar 2014 12:28:58 -0800 (PST) Received: from tru-univ-casint.tru.univ (tru-univ-casint.tru.ca [198.162.23.234]) by mail-relay.tru.ca (Postfix) with ESMTP id 74125A6601 for ; Tue, 4 Mar 2014 12:33:48 -0800 (PST) Received: from TRU-UNIV-EXMBX2.tru.univ ([fe80::9452:3812:32ee:160f]) by tru-univ-casint.tru.univ ([2002:c6a2:17ea::c6a2:17ea]) with mapi id 14.03.0158.001; Tue, 4 Mar 2014 12:33:48 -0800 From: Doug Baleshta X-Original-To: Lancair Mailing List Subject: RE: [LML] Re: Canopy Latch modeling Thread-Topic: [LML] Re: Canopy Latch modeling Thread-Index: AQHPN98CGu5C64BuuEOT7tfUX8CAc5rRVWAQ X-Original-Date: Tue, 4 Mar 2014 20:33:48 +0000 X-Original-Message-ID: <286E3721ADF2544F80FE374F2D8D26915B5575EA@tru-univ-exmbx2.tru.univ> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [206.123.172.236] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.3.4.202416 X-PerlMx-Spam: Gauge=XIII, Probability=13%, Report=' __CP_URI_IN_BODY! 0.5, TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, SUPERLONG_LINE 0.05, BODY_SIZE_3000_3999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, URI_ENDS_IN_HTML 0, WEBMAIL_SOURCE 0, WEBMAIL_XOIP 0, WEBMAIL_X_IP_HDR 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_XOIP 0, __IMS_MSGID 0, __INT_PROD_MOTORBIKE 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT 0, __TO_MALFORMED_2 0, __URI_NO_WWW 0, __URI_NS ' I used a trunk closing system out of a Lincoln Continental for the latching= system on my forward tilting Lancair 360. The motor sits inside the canop= y and the attachment is mounted to the roll cage (with Carbon Fiber reinfor= cement) in the middle top. I have a remote FOB that allows me to close the= canopy and lock it when not in use. I have three release systems for it: = one is electrical mounted on the panel, there's a tab located on the roll = cage on the mechanism which unlocks it (in case of electrical failure) and = I have a lockable handle on a small aircraft cable (that I leave unlocked -= need to add this in my check list ;-) located on the outside that is placa= rded for emergency opening. Issues with this: - The main pull down is not enough to keep the bottom edges tight against t= he rail. Once in cruising speed the amount of force is able to lift the bo= ttom corners and allows air to flow. My canopy edges do extend past the ra= il, but there still enough force to somehow bulge and expand it. - When closing, there are two latch positions. The first position just hol= ds the canopy slightly open/closed and allows air to flow. The electrical = system will close it down tighter after the run-up etc. when I read my chec= k list... Yes, I have taken off without remembering to do the final pull d= own and there was no problem, the canopy sat around 2 inches above the uppe= r surface but is held by the mechanism - I have an additional latch at the bottom on each side in addition to the = main pull down which keeps the edges tight which is the last thing I do bef= ore the take-off roll and counters my first comment - I keep a tool on the key chain and in the console glove box that will sha= tter the plexi in case of emergencies. I've heard that some keep a small h= atchet in there as well... - If I am going to crash land then I will need to remember to release the s= ide latches as they are not accessible from the outside - If I am upside down, it's going to be very difficult to egress from the p= lane even if everything is unlocked/released with any system - There is a chance that an accident may damage the mechanism and jam it, b= ut if I have to get out, then I have the tools to shatter the plexi. - there's now a bunch of hardware between the passenger and pilot's head. = I have covered this with foam for some protection. When I read Paul's note= about Seat Belts this may or may not be a good thing to prevent the sidewa= ys motion in a crash? I know of one other person who just has the latch mechanisms located at the= bottom of each side with the plane placarded "Use An Axe To Remove Occupan= ts In Case Of An Emergency". Doug 12 hours and lots more to go... -----Original Message----- From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Paul= Miller Sent: March-04-14 11:22 AM To: lml@lancaironline.net Subject: [LML] Re: Canopy Latch modeling Kevin, I share the concern about egress. My Legacy has pins in the rear wi= ndow that can be pulled and drop the window from inside. I think that give= s me some comfort. however, upside down, who knows what condition the cabi= n might be in. As a matter of interest, does anyone know if the canopy wil= l shatter with one of the hammers sold for that purpose? Paul -- For archives and unsub http://mail.lancaironline.net:81/lists/lml/List.html