Document Information
Version 1
Created 01/01/2016 00:25
Last Updated 08/21/2021 01:16
by Matthew Woerly

OVERHEAD MANEUVERS (3-10-12)

Overhead Maneuver

Issue the following to arriving aircraft that will conduct an overhead maneuver:

a. Pattern altitude and direction of traffic. Omit either or both if standard or when you know the pilot is familiar with a nonstandard procedure.

PHRASEOLOGY-PATTERN ALTITUDE (altitude). RIGHT TURNS.

b. Request for report on initial approach.

PHRASEOLOGY-REPORT INITIAL.

c. “Break” information and request for pilot report. Specify the point of “break” only if nonstandard. Request the pilot to report “break” if required for traffic or other reasons.

PHRASEOLOGY-BREAK AT (specified point). REPORT BREAK.

d. Overhead maneuver patterns are developed at airports where aircraft have an operational need to conduct the maneuver. An aircraft conducting an overhead maneuver is on VFR and the IFR flight plan is canceled when the aircraft reaches the “initial point” on the initial approach portion of the maneuver. The existence of a standard overhead maneuver pattern does not eliminate the possible requirement for an aircraft to conform to conventional rectangular patterns if an overhead maneuver cannot be approved.

NOTE- Aircraft operating to an airport without a functioning control tower must initiate the cancellation of the IFR flight plan prior to executing the overhead maneuver or after landing.

EXAMPLE:

FOX1: Portland Tower, FOX1 is on a 5 mile straight in for runway 28R, requesting overhead maneuver

PDX_TWR: FOX1, Portland Tower, Pattern Altitude 2,500, Right Turns. Report Initial

FOX1: Pattern Altitude 2,500 with right turn. Will report initial for FOX1

FOX1: FOX1 is Initial

PDX_TWR: FOX1, Break at midfield, Report Break

FOX1: Break at midfield and will report the break for FOX1

FOX1: FOX1 is Break

PDX_TWR: FOX1, Runway 28R, Check wheels down, Wind 280 at 6, Cleared to Land

FOX1: Three in the green, Cleared to land Runway 28R for FOX1

 

Military Procedures (2-1-12)

Procedures referenced to specific military branches only apply in the following situations:

A facility operated by that military service, or that only provides service to a military location. The applicable procedures will be applied for all aircraft, military or civilian. Examples:

  • LMT RAPCON
  • NUW RAPCON
  • Towers at military fields.

By LOA. Military procedures applied to military aircraft, civilian procedures applied to civilian aircraft. Typically at mixed-use airports. Examples:

  • PDX ORANG

The following is a summary of some procedures applicable for certain military branches:

US Navy

  • "Perform landing check" on downwind. 5-10-6
  • "Check wheels down" on each approach. 2-1-25
  • Do not authorize aircraft to line and wait simultaneously on intersecting runways. 3-9-4
  • "Continue holding" or "taxi off the runway" with each instruction to a holding aircraft. 3-9-4
  • Issue wind on takeoff and any option clearance. 3-9-10/3-10-5
  • Cannot issue takeoff clearance if aircraft landing/LAHSO on intersecting rwy. 3-10-4
  • Do not issue charted visual approach clearances. 7-4-5
  • Approve flight plans requesting celestial navigation. 9-2-2

US Air Force

  • "Continue holding" or "taxi off the runway" with each instruction to a holding aircraft. 3-9-4
  • All departing IFR military transport/cargo type aircraft operating in formation flight can be instructed to change to departure control frequency before takeoff. 3-9-3
  • When an aircraft is cleared for takeoff, inform it of the closest traffic within 6 miles on final approach to the same runway. If the approaching aircraft is on a different frequency, inform it of the departing aircraft. 3-9-10
  • Issue wind on takeoff and any option clearance. 3-9-10/3-10-5
  • Cannot issue takeoff clearance if aircraft landing/LAHSO on intersecting rwy. 3-10-4
  • If issuing an altitude assignment, only include one other instruction. 4-2-1
  • Approve flight plans requesting celestial navigation. 9-2-2

US Army

  • "Perform landing check" on downwind. 5-10-6
  • "Check wheels down" on each approach. 2-1-25
  • Wake turbulence hold time interval for intersection departures is required even if the intersection is 500 feet or less from the departure point of the preceding aircraft and both aircraft are taking off in the same direction. 3-9-8
  • Issue wind on takeoff and any option clearance. 3-9-10/3-10-5
  • Cannot issue takeoff clearance if aircraft landing/LAHSO on intersecting rwy. 3-10-4
  • Do not issue charted visual approach clearances. 7-4-5