AIM DECODED

4-3-5. Unexpected Maneuvers in the Airport Traffic Pattern

AIM Text

There have been several incidents in the vicinity of controlled airports that were caused primarily by aircraft executing unexpected maneuvers. ATC service is based upon observed or known traffic and airport conditions. Controllers establish the sequence of arriving and departing aircraft by requiring them to adjust flight as necessary to achieve proper spacing. These adjustments can only be based on observed traffic, accurate pilot reports, and anticipated aircraft maneuvers. Pilots are expected to cooperate so as to preclude disrupting traffic flows or creating conflicting patterns. The pilot-in-command of an aircraft is directly responsible for and is the final authority as to the operation of the aircraft. On occasion it may be necessary for pilots to maneuver their aircraft to maintain spacing with the traffic they have been sequenced to follow. The controller can anticipate minor maneuvering such as shallow “S” turns. The controller cannot, however, anticipate a major maneuver such as a 360 degree turn. If a pilot makes a 360 degree turn after obtaining a landing sequence, the result is usually a gap in the landing interval and, more importantly, it causes a chain reaction which may result in a conflict with following traffic and an interruption of the sequence established by the tower or approach controller. Should a pilot decide to make maneuvering turns to maintain spacing behind a preceding aircraft, the pilot should always advise the controller if at all possible. Except when requested by the controller or in emergency situations, a 360 degree turn should never be executed in the traffic pattern or when receiving radar service without first advising the controller.

4-3-6. Use of Runways/Declared Distances

  1. Runways are identified by numbers that indicate the nearest 10-degree increment of the azimuth of the runway centerline. For example, where the magnetic azimuth is 183 degrees, the runway designation would be 18; for a magnetic azimuth of 87 degrees, the runway designation would be 9. For a magnetic azimuth ending in the number 5, such as 185, the runway designation could be either 18 or 19. Wind direction issued by the tower is also magnetic and wind velocity is in knots.
  2. Airport proprietors are responsible for taking the lead in local aviation noise control. Accordingly, they may propose specific noise abatement plans to the FAA. If approved, these plans are applied in the form of Formal or Informal Runway Use Programs for noise abatement purposes.
    1. ATC will assign the runway/s most nearly aligned with the wind when 5 knots or more, or the “calm wind” runway when less than 5 knots unless:
      1. Use of another runway is operationally advantageous, or
      2. A Runway Use Program is in effect.
  3. If a pilot prefers to use a runway different from that specified, the pilot is expected to advise ATC. ATC may honor such requests as soon as is operationally practicable. ATC will advise pilots when the requested runway is noise sensitive. When use of a runway other than the one assigned is requested, pilot cooperation is encouraged to preclude disruption of traffic flows or the creation of conflicting patterns.
  4. Declared Distances.
    1. Declared distances for a runway represent the maximum distances available and suitable for meeting takeoff and landing distance performance requirements. These distances are determined in accordance with FAA runway design standards by adding to the physical length of paved runway any clearway or stopway and subtracting from that sum any lengths necessary to obtain the standard runway safety areas, runway object free areas, or runway protection zones. As a result of these additions and subtractions, the declared distances for a runway may be more or less than the physical length of the runway as depicted on aeronautical charts and related publications, or available in electronic navigation databases provided by either the U.S. Government or commercial companies.
    2. All 14 CFR part 139 airports report declared distances for each runway. Other airports may also report declared distances for a runway if necessary to meet runway design standards or to indicate the presence of a clearway or stopway. Where reported, declared distances for each runway end are published in the Chart Supplement. For runways without published declared distances, the declared distances may be assumed to be equal to the physical length of the runway unless there is a displaced landing threshold, in which case the Landing Distance Available (LDA) is shortened by the amount of the threshold displacement.
      1. The FAA uses the following definitions for runway declared distances (See FIG 4-3-5):
        1. Takeoff Run Available (TORA) – The runway length declared available and suitable for the ground run of an airplane taking off.

          The TORA is typically the physical length of the runway, but it may be shorter than the runway length if necessary to satisfy runway design standards. For example, the TORA may be shorter than the runway length if a portion of the runway must be used to satisfy runway protection zone requirements.

        2. Takeoff Distance Available (TODA) – The takeoff run available plus the length of any remaining runway or clearway beyond the far end of the takeoff run available.

          The TODA is the distance declared available for satisfying takeoff distance requirements for airplanes where the certification and operating rules and available performance data allow for the consideration of a clearway in takeoff performance computations.

        3. Accelerate-Stop Distance Available (ASDA) – The runway plus stopway length declared available and suitable for the acceleration and deceleration of an airplane aborting a takeoff.

          The ASDA may be longer than the physical length of the runway when a stopway has been designated available by the airport operator, or it may be shorter than the physical length of the runway if necessary to use a portion of the runway to satisfy runway design standards; for example, where the airport operator uses a portion of the runway to achieve the runway safety area requirement. ASDA is the distance used to satisfy the airplane accelerate-stop distance performance requirements where the certification and operating rules require accelerate-stop distance computations.

        4. Landing Distance Available (LDA) - The runway length declared available and suitable for a landing airplane.

          The LDA may be less than the physical length of the runway or the length of the runway remaining beyond a displaced threshold if necessary to satisfy runway design standards;for example, where the airport operator uses a portion of the runway to achieve the runway safety area requirement.

          Although some runway elements (such as stopway length and clearway length) may be available information, pilots must use the declared distances determined by the airport operator and not attempt to independently calculate declared distances by adding those elements to the reported physical length of the runway.

      2. The airplane operating rules and/or the airplane operating limitations establish minimum distance requirements for takeoff and landing and are based on performance data supplied in the Airplane Flight Manual or Pilot's Operating Handbook. The minimum distances required for takeoff and landing obtained either in planning prior to takeoff or in performance assessments conducted at the time of landing must fall within the applicable declared distances before the pilot can accept that runway for takeoff or landing.
      3. Runway design standards may impose restrictions on the amount of runway available for use in takeoff and landing that are not apparent from the reported physical length of the runway or from runway markings and lighting. The runway elements of Runway Safety Area (RSA), Runway Object Free Area (ROFA), and Runway Protection Zone (RPZ) may reduce a runway's declared distances to less than the physical length of the runway at geographically constrained airports (See FIG 4-3-6). When considering the amount of runway available for use in takeoff or landing performance calculations, the declared distances published for a runway must always be used in lieu of the runway's physical length.
      4. While some runway elements associated with declared distances may be identifiable through runway markings or lighting (for example, a displaced threshold or a stopway), the individual declared distance limits are not marked or otherwise identified on the runway. An aircraft is not prohibited from operating beyond a declared distance limit during the takeoff, landing, or taxi operation provided the runway surface is appropriately marked as usable runway (See FIG 4-3-6). The following examples clarify the intent of this paragraph.

        FIG 4-3-5
        Declared Distances with Full-Standard Runway Safety Areas, Runway Object Free Areas, and Runway Protection Zones

        aim0403_Auto8

        FIG 4-3-6
        Effects of a Geographical Constraint on a Runway's Declared Distances

        aim0403_Auto7

Source: FAA Aeronautical Information Manual · current edition · paragraph 4-3-5.

Research Notes

AIM 4-3-5 covers approach lighting systems — the runway-end lighting that guides instrument approaches to landing in low visibility conditions.

Major systems:

  • ALSF-II: Cat II/III approach with sequenced flashing lights and centerline. Required for the lowest minimums.
  • ALSF-I: Approach lights with sequenced flashing. Slightly less capable than ALSF-II.
  • SSALR / SSALF: Simplified Short Approach Lighting with sequenced flashing and runway alignment indicator.
  • MALSR: Medium-Intensity Approach Lighting System with RAIL (runway alignment indicator lights). Common at GA airports with ILS approaches.
  • ODALS: Omnidirectional Approach Light System. Used for circling and non-precision approaches.
  • REIL: Runway End Identifier Lights — two synchronized white strobes at the threshold. Help pilots identify the runway at night.

Connection to § 91.175: Per § 91.175(c), the pilot may descend below DH/MDA only when the approach lights (or other specified visual references like the threshold or REIL) are distinctly visible. Approach lighting is the single most-cited visual reference for the descent-below-DH decision.

Light intensity: Pilot-controllable at many GA airports via the radio (typically 122.95 or the CTAF). The pilot clicks the mic 5 times for low intensity, 7 for medium, 9 for high. Check the Chart Supplement for the specific click count and frequency at each airport.

Reference: § 91.175 (instrument approaches); AIM 2-1 (Airport Lighting); AIM 4-3-5.