X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from [69.171.52.140] (account marv@lancaironline.net) by logan.com (CommuniGate Pro WebUser 5.0.4) with HTTP id 887201 for lml@lancaironline.net; Sun, 18 Dec 2005 12:32:40 -0500 From: "Marvin Kaye" Subject: Re: Night Flying To: lml X-Mailer: CommuniGate Pro WebUser v5.0.4 Date: Sun, 18 Dec 2005 12:32:40 -0500 Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit Posted for Gary Casey : The thoughts posted by Rick are useful and valid. One flyer suggested you never accept more than 2 of the following risks: Single engine(oops, there goes one already), IFR, night and mountains. I expand on that a little bit: Single engine - can't fix that, but a single engine that is already running and has lots of fuel is pretty reliable, so I'll possibly count it as 1.5 engines during the middle of a flight. Night - I used to fly at any time at night, but I'm getting more conservative. I'll finish a flight at night given it is over controlled terrain (lots of airports, flat land, etc), but probably wouldn't start one. IFR - I don't consider it "IFR" if the weather is VFR on the ground as I don't consider just flying through a cloud as a risk. Mountains (or water) - A single ridge with lower terrain on both sides is probably not "mountains" unless the tops poke into my cloud. I'll admit I've accepted three of these risks, but it probably wasn't prudent. I think the list of risks above is logical and I tend to keep it in mind. Gary Casey