Sender: <marv@lancaironline.net>
To: lml@lancaironline.net
Date: Mon, 27 Feb 2006 00:21:59 -0500
Message-ID: <redirect-999452@logan.com>
Received-SPF: pass
 receiver=logan.com; client-ip=68.168.78.199; envelope-from=dfs155@adelphia.net
From: "Dan Schaefer" <dfs155@adelphia.net>
Subject: Overhead approach questions
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Though I agree (mostly) with the various listers giving advice regarding
proper execution of the overhead approach, I do have a small quibble.

Instead of just announcing to the tower that you've set up two miles out for
the overhead with all the other info (planning a right break over the
numbers, etc., etc.) and then reconsidering if you don't like what you hear,
try calling the tower as you would if making a "normal" entry (e.g. 5 or 6
miles out, with the ATIS and your location and BEFORE entering their
airspace) and REQUESTING the overhead. If the person on the mike knows what
you're talking about and have a standard overhead that they like to use,
you'll get something like "Lancair 123 ZZ, overhead approach approved, fly
runway 19 heading at or above 1600 feet, break left at mid-field, report two
miles". On the other hand, if you hear something like "UH, Lancair 123 ZZ,
UH, say again!", I'd say your decision is already made for you while you're
still outside of his airspace and you can make an approach that the
controller understands.

I've used this method often and it works for me.

Dan Schaefer