X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao103.cox.net ([68.230.241.43] verified) by logan.com (CommuniGate Pro SMTP 5.2.14) with ESMTP id 3670720 for flyrotary@lancaironline.net; Wed, 03 Jun 2009 17:41:20 -0400 Received-SPF: none receiver=logan.com; client-ip=68.230.241.43; envelope-from=alventures@cox.net Received: from fed1rmimpo02.cox.net ([70.169.32.72]) by fed1rmmtao103.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090603214039.SPDA2915.fed1rmmtao103.cox.net@fed1rmimpo02.cox.net> for ; Wed, 3 Jun 2009 17:40:39 -0400 Received: from BigAl ([72.192.135.181]) by fed1rmimpo02.cox.net with bizsmtp id zZge1b00K3uzsQg04Zge2m; Wed, 03 Jun 2009 17:40:38 -0400 X-VR-Score: 0.00 X-Authority-Analysis: v=1.0 c=1 a=7oCblTc5tKShA0KVhfEA:9 a=xC-IugVF-fMENE6UYagA:7 a=Z5yq_dWXt7aUcMF8DHcocMtQ-aoA:4 a=RSYTueJW-iGMuBEkUSEA:9 a=Lpv8BdtUq9GtMtArSBkA:7 a=X3zSOPeky4z8hA0ZNeHV_EnrAPwA:4 X-CM-Score: 0.00 From: "Al Gietzen" To: "'Rotary motors in aircraft'" Subject: Lessons learned Date: Wed, 3 Jun 2009 14:40:59 -0800 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C9E459.4F868CD0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6838 Thread-Index: Acnkdj5YSWXv82h4QtuGtu29wbIbOAAI4IIg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: Importance: Normal This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C9E459.4F868CD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ed set the example by pointing out contributing factors in his = =91incident=92, and for the sake off completeness I should do likewise. =20 We were planning on being wheels up by 8:00 am; and making the roughly 7 = =BD hr flying time to Austin that day. But the airport was socked in with unusually heavy marine layer =96 400 ft ceiling. This generally breaks = up pretty early 20 miles inland at F70. We waited, and waited, looking at = the sky; no change. Finally, and rather suddenly we saw breaks in the = clouds. At 10:15 I decided we were good to go; we strapped in, and headed out. = Still some low clouds in the direction of takeoff, but I saw we could be off, = make a 180 and climb. =20 =20 IF the cause was that the door latch was not fully engaged it was = because I was impatient to get going; not thorough on the pre-takeoff checklist. = Hey, I had closed and latched that door 100 times =96 of course it was fully latched. =20 Don=92t ever be in a hurry when you are going flying. Don=92t ever be in = a hurry when you are going flying. =20 Al G ------=_NextPart_000_0006_01C9E459.4F868CD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Ed set the example by pointing = out contributing factors in his ‘incident’, and for the sake off = completeness I should do likewise.

 

We were planning on being wheels = up by 8:00 am; and making = the roughly 7 =BD hr flying time to Austin that day. =A0But the airport was socked in with unusually = heavy marine layer – 400 ft ceiling.=A0 This generally breaks up pretty = early 20 miles inland at F70.=A0 We waited, and waited, looking at the sky; no = change. Finally, and rather suddenly we saw breaks in the clouds. =A0At = 10:15 I decided we = were good to go; we strapped in, and headed out. Still some low clouds in the = direction of takeoff, but I saw we could be off, make a 180 and climb.=A0 =

 

IF the cause was that the door latch was not fully engaged it = was because I was impatient to get going; not thorough on the pre-takeoff checklist.=A0 Hey, I had closed and latched that door 100 times – = of course it was fully latched.

 

Don’t ever be in a hurry = when you are going flying. Don’t ever be in a hurry when you are going = flying.

 

Al G

------=_NextPart_000_0006_01C9E459.4F868CD0--