X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from smtp106.mail.sc5.yahoo.com ([66.163.169.226] verified) by logan.com (CommuniGate Pro SMTP 5.0.3) with SMTP id 863175 for flyrotary@lancaironline.net; Sun, 04 Dec 2005 20:18:35 -0500 Received-SPF: none receiver=logan.com; client-ip=66.163.169.226; envelope-from=prvt_pilot@yahoo.com Received: (qmail 58171 invoked from network); 5 Dec 2005 01:17:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Reply-To:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:In-Reply-To:Importance; b=Jg4hEt0tHaFq+e700wp6GEb2GMKstV8PfDC8ChyuHGxdXSMBJsuabS2CeQl7AIqiho0ilWx6BLp/uEAOy5W+7hLLJIbtL2zMbDE2vCghC0UPOdIeVEW8HA2rXa+2SCYflD6I5AsV5dssO5iWLZli67bNW8jDCmRMUP136O/8XCY= ; Received: from unknown (HELO stevehome) (prvt?pilot@71.0.19.116 with login) by smtp106.mail.sc5.yahoo.com with SMTP; 5 Dec 2005 01:17:49 -0000 Reply-To: From: "Steve Brooks" To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: Intersting flight Date: Sun, 4 Dec 2005 20:22:37 -0500 Message-ID: <002901c5f93a$63bc2060$6400a8c0@workgroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 In-Reply-To: Importance: Normal Al, You make some excellent points. I am already starting a list of things to do to the plane on my next trip down. Having a copy next to my computer will definitely keep it fresh. Steve -----Original Message----- From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net]On Behalf Of al p wick Sent: Sunday, December 04, 2005 1:56 PM To: Rotary motors in aircraft Subject: [FlyRotary] Re: Intersting flight Nice of you to share the information Steve. That represents the best opportunity for other conversions to be successful. Glad it worked out as well as it did. There are all these patterns to failures. I've found it's important to understand the patterns. Other pilots will read your report, feel uncomfortable, decide they need to........... but gradually this discomfort will fade. And they still haven't taken the action they need to take. So it's important to write down your action list. If you write it down in 12" high letters and post at your work station, you greatly increase your chances of taking action...because you've increased social pressure. We had a crash just two months ago with exact same root cause. Electrical failure causes loss of power. Keith too crashed for same reason 2 years ago. Our installations are at much higher risk than Lyc because we are power dependant. So we need to be most thorough in this area. So let's consider the "other" causes. 1) All crashes are the result of change. So when you were improving your wiring, that change opened you up to new potential failures. So any time we work on the plane, we take a minute before we close it up to seek the inadvertent change. We look around, wiggle things, try to find our oversight. 2) Why don't auto's have this same failure? I noticed on my engine they have multiple sources for ground. Something like 5 attach points. Two power sources to ecm. They have all wires in looms, so you can't strain one wire. Looms have anchors, so you can't strain the looms. So there is great value in understanding why other installs are successful. We seldom notice stuff like this. 3) We go brain dead in emergencies. We focus better in some ways, but lose stuff too. It's pretty interesting. So practicing failure is valuable. I've found even more effective is using graphics, audible warnings, computer monitoring. So, the computer would have found that first 10 ms power blip when you fired up the plane. Perhaps not. Off soap box. Thanks for sharing info. I've added "review ignition wiring" to my list. -al wick Artificial intelligence in cockpit, Cozy IV powered by stock Subaru 2.5 N9032U 200+ hours on engine/airframe from Portland, Oregon Prop construct, Subaru install, Risk assessment, Glass panel design info: http://www.maddyhome.com/canardpages/pages/alwick/index.html On Sat, 3 Dec 2005 06:28:46 -0800 (PST) Steve Brooks writes: > I made it down to South Carolina, to among other > things, fly the Cozy. It had been 2 months to the day > since I had been down, so the remaining 8 hours of the > 40 test hours have been slow to come off. > > On Thursday I washed about 30 lbs of dust off of the > plane (open T hanger) and checked everything out. I > did a high speed run down the runway, but didn't have > time to get in a flight. > > Yesterday I went to the airport after it warmed up a > few degrees, and took off. The engine was running > very strong in the cooler air (54 degrees). I had > planned to do about a 30 minute flight ad land, just > to check everything out, and was was doing turns and > just cruising around about 6-7 miles from the airport > at about 2900 MSL (2300 AGL). While flying straight > and level, I felt a sudden miss in engine. When I > check the I/P, I also noticed that the digital gauges, > fuel and oil, had rebooted. I immediately started a > turn toward the airport. > > About 15 seconds later, I lost total electric. The > I/P went dead, and so did the engine. This isn't > good, I thought. Actually, it was more like, OH SH**. > I took a look at the airport, and I was too far to > make it there, so I looked around, and a 4 lane > highway, which has light traffic appeared to be my > best option. I had just started turning toward that > highway, when the electric power came back, and the > engine picked back up. > > I immediately started a climb, and headed toward the > airport again. I already knew that there was a plane > in the pattern doing touch and goes (unicom field), so > I called the airport and advised the other aircraft > that I had a serious issue, and needed to make a > straight in landing. > > It didn't lose power again, on the trip back to the > airport, but that 6-7 miles seemed to take forever. I > stayed on the high side on altitude, for obvious > reasons, and then had to bleed altitude (and speed) > while on short final. I came in a little fast, and > touched down earlier than normal, but still was on the > ground, and very happy. > > Since I have two separate electrical systems (engine > and everything else), I was really stunned that I lost > both like that. After thinking about it for I while, > I figured out that the master switch was the only > common link. I pulled the I/P cover off, and found > that the ground connector was pulled off of the > terminal and just sitting there barely touching the > contact. > The cause of this was the fact that when I did an > annual on the plane in May, I had added some addition > ty-raps to dress up the wiring a little more. In > doing so, I had stretched the ground wire which runs > to the master switch, which energizes the two master > relays. > > It was an easy fix, but now I have to replenish the > adrenalin supply, and figure out how to get the ridge > out of the seat cushion. > > After some ground testing, I made another flight > (circling the airport) and everything checked out OK. > > > I have an emergency bypass switch that will supply > power to the engine systems from either the forward or > aft battery. I didn't think to switch it over, but I > really didn't get to the point of doing any trouble > shooting, so I'm not sure if I would have thought of > that option or not. It was without power for only > about 20 seconds, but it seemed much longer. I will > definitely remember the emergency power switch, should > I every have an issue like that again, but I hope that > never happens. > > This isn't nearly as harrowing as some of the > experiences that Ed or John have had, but it was > plenty for me. I don't want any more glider time. > > Steve Brooks > Cozy MKIV > Turbo rotary > > > -- > Homepage: http://www.flyrotary.com/ > Archive and UnSub: http://mail.lancaironline.net/lists/flyrotary/ > > -al wick Artificial intelligence in cockpit, Cozy IV powered by stock Subaru 2.5 N9032U 200+ hours on engine/airframe from Portland, Oregon Prop construct, Subaru install, Risk assessment, Glass panel design info: http://www.maddyhome.com/canardpages/pages/alwick/index.html -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net/lists/flyrotary/