X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from [67.8.176.36] (account marv@lancaironline.net) by logan.com (CommuniGate Pro WebUser 5.0.8) with HTTP id 997445 for lml@lancaironline.net; Fri, 24 Feb 2006 21:42:49 -0500 From: "Marvin Kaye" Subject: Overhead approach questions To: lml X-Mailer: CommuniGate Pro WebUser v5.0.8 Date: Fri, 24 Feb 2006 21:42:49 -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 "richard titsworth" : Lynn, etal, I fly at some airports with relatively high level of initial student training (private pilot). Most of these students have no exposure/knowledge of the overhead approach. It is generally not mentioned/described in any of the common training materials - nor commonly taught prior to solo or checkride. Any suggestions on how I should first announce my intentions when approaching the airport. Since "overhead approach" will not likely convey much understanding? What position reports are commonly made during an overhead approach? Do you include any reference to airspeed in the calls to help others estimate time/position? There can be some confusion when two airplane arrive to the pattern at nearly the same time. Logically, the faster plane should go first, but there is no allowance/reference to that in the FAR/AIM to my knowledge - only that the lower plane goes first (but I should not use that to advance my position). Also, I've often seen a hold-short airplane pull onto the runway for departure when there was another on downwind/base - assuming the normally slow inbound plane was still perhaps a minute or more from short final. Seems added speed info may be helpful here also. Any best practices on how to shorten these added/lengthened calls since the students can be a bit verbose themselves and often leave minimal radiotime? Any best practices on how to request an overhead approach at a towered airport? Rick