3-10-1. LANDING INFORMATION

  • Views Views: 6
  • Last updated Last updated:
  • 3-10-1. LANDING INFORMATION

    Provide current landing information, as appropriate, to arriving aircraft. Landing information contained in the ATIS broadcast may be omitted if the pilot states the appropriate ATIS code. Runway, wind, and altimeter may be omitted if a pilot uses the phrase “have numbers.” Issue landing information by including the following:

    NOTE: Pilot use of “have numbers” does not indicate receipt of the ATIS broadcast.

    1. Specific traffic pattern information (may be omitted if the aircraft is to circle the airport to the left).
      • PHRASEOLOGY
      • ENTER LEFT/RIGHT BASE.
      • STRAIGHT-IN.
      • MAKE STRAIGHT-IN.
      • STRAIGHT-IN APPROVED.
      • RIGHT TRAFFIC.
      • MAKE RIGHT TRAFFIC.
      • RIGHT TRAFFIC APPROVED.
      • CONTINUE.

      NOTE: Additional information should normally be issued with instructions to continue. Example: “continue, report one mile final”; “continue, expect landing clearance two mile final”; etc.

    2. Runway in use.
    3. Surface wind.
    4. Altimeter setting.
    5. Any supplementary information.
    6. Clearance to land.
    7. Requests for additional position reports. Use prominent geographical fixes which can be easily recognized from the air, preferably those depicted on sectional charts. This does not preclude the use of the legs of the traffic pattern as reporting points.

      NOTE: At some locations, VFR checkpoints are depicted on sectional aeronautical and terminal area charts. In selecting geographical fixes, depicted VFR checkpoints are preferred unless the pilot exhibits a familiarity with the local area.

    8. Ceiling and visibility if either is below basic VFR minima.
    9. Low level wind shear or microburst advisories when available.
    10. Issue braking action for the runway in use as received from pilots when braking action advisories are in effect.
    11. Runway Condition Codes. Furnish RwyCC, as received from the Airport Operator, to aircraft via the ATIS.
    12. For opposite direction arrival operations, controllers may verbally issue the RwyCC, as identified in the FICON NOTAM, in reverse order. Controllers must not include reversed RwyCC on the ATIS broadcast.
    13. If the pilot does not indicate the appropriate ATIS code, and when a runway has been shortened, controllers must ensure that pilots receive the runway number combined with a shortened announcement for all arriving aircraft.
Top