Skip to content

Reference

Airport Operations

UOAF airport-recovery guidance, focused on the overhead break and the specific recovery procedures referenced by the event checklist.

Overhead break TRP

Overhead Break

The military pattern, otherwise known as the overhead break, is the standard for USAF fighter operations. It is designed to deconflict traffic and get aircraft on the ground quickly.

Theory

The overhead break is used to accomplish three main objectives:

  • Deconflict traffic by making traffic flow intuitive and predictable when altitude and DME restrictions are followed.
  • Save time by landing many aircraft safely in a short span.
  • Configure the aircraft efficiently through the turns used to bleed speed and reach landing configuration.

Key numbers:

  • Landing gear ops limit: 300 KIAS
  • On-speed target: 11° AoA or green donut

Terminology

  • Pattern altitude: altitude in MSL flown on downwind.
  • Initial: theoretical point 2.0 nm in front of the runway threshold at 2,000 AGL, aligned with the active runway.
  • Break turn: continuous 3G, 70° bank, constant-altitude, 180° turn at 300 knots executed by lead at the halfway point of the active runway.
  • Downwind: parallel opposite-direction leg where airspeed is reduced to 200 knots by perch and gear goes down abeam the runway midpoint.
  • Perch: point where a line from the aircraft to the runway threshold is about 45°.
  • Base turn: descending 180° turn at about 45° bank and on-speed AoA from perch to runway alignment.
  • Final: aligned, landing configured, committed to land.
  • Closed turn: ascending 180° turn from runway end to intercept downwind, used for go-arounds or touch-and-goes.

Restrictions

The military pattern is intended for:

  • VFR weather conditions
  • 3 statute miles visibility
  • 500 ft below cloud clearance
  • 1,000 ft above
  • 2,000 ft horizontal
  • No IFR conditions or instrument approaches in effect
  • No emergency procedures affecting the flight or other landing aircraft
  • Multi-ship flights breaking at the briefed interval from lead

UOAF Observed Parameters

  • Initial is declared at 2.0 nm from the active runway threshold and overflown at 2,000 AGL.
  • Prior to initial, the flight must be established in echelon and on runway heading no later than 5.0 nm from the runway threshold.
  • Pattern altitude is 2,000 AGL at all stations unless otherwise briefed.
  • Airspeed at initial is 300 KIAS or slower.
  • Communications are expected to be deliberate and accurate.
  • Airport-operation altitudes are referenced in MSL, so convert AGL by adding airport elevation.

UOAF Procedures

  1. Fly to initial in close trail or echelon at 2,000 AGL and 300 knots.
  2. Continue through initial to the break zone at runway midpoint.
  3. Pull approximately 3G at 70° bank until established on downwind.
  4. Slow on downwind to 200 knots minimum and configure for landing so you arrive at perch on speed.
  5. Begin base turn from perch at about 45° bank on AoA.
  6. Intercept runway glidepath at about 0.5 nm with appropriate AoA.
  7. Touch down and use the full runway.

Responsibilities

Flight Leaders

  • Ensure landing procedures are flown with precision and purpose.
  • Make the proper radio calls to flight and package comms.

Wingmen

  • Be there.
  • Do not hit #1.
  • Keep #1 in sight.
  • Be in position and on the proper radio frequency.
  • Clear for the formation and back up lead.

UOAF Communications

Before Initial

  • Lead briefs the preferred landing method to the flight.
  • Example: Flight, landing runway THREE-ZERO via initial.
  • Example: Flight, landing runway TWO-ONE via straight in, formation landing.
  • Example: Flight, landing runway ONE-FOUR via straight in, single ship.
  • Wingmen respond with their callsign.
  • Example: TWO, THREE, FOUR

At Initial

  • Flight lead announces on package comms that the flight is at initial and descending to pattern altitude.
  • Example: Snake 11, initial

At the Break Point

  • Lead calls the break.
  • Example: Lead, in the break
  • Wingmen stay on runway heading until their turn, then call their own break.
  • Example: TWO, in the break
  • Example: THREE, in the break
  • Example: FOUR, in the break

On the Downwind Leg

  • Lead may call airspeed as a courtesy.
  • Example: Lead is TWO-FIVE-ZERO knots, slowing to TWO-ZERO-ZERO.
  • Wingmen configure approximately abeam the runway midpoint.
  • Use judgment to preserve spacing while still reaching the proper configuration.

On Base Turn

  • Lead and wingmen call base turn to the package.
  • Example: Snake 11, base, runway THREE-ZERO
  • Example: Snake 12, base, runway THREE-ZERO

After Touchdown

  • Lead announces when off the active runway.
  • Example: Snake 11 is off runway THREE-ZERO at Bravo.
  • Example: Snake 12 is off runway THREE-ZERO at Bravo.

Tactical Recovery Procedure (TRP)

This page currently captures the overhead-break material used most often in UOAF event flow. TRP guidance is planned as a dedicated expansion rather than a placeholder summary.