4-7-12. AIRPORT CONDITIONS

  • Views Views: 905
  • Last updated Last updated:
Page

  • 4-7-12. AIRPORT CONDITIONS

    1. EN ROUTE. Before issuing an approach clearance, and subsequently as changes occur, inform an aircraft of any abnormal operation of approach and landing aids and of destination airport conditions that you know of which might restrict an approach or landing. This information may be omitted if it is contained in the ATIS broadcast and the pilot states that he/she has received the appropriate ATIS code.
      • NOTE:
      • 1. Airport conditions information, in the provision of en route approach control service, does not include the following:
        • a. The airport surface environment other than the landing area(s) (e.g. TAXIWAY, APRON or SERVICE keyword NOTAMs).
        • b. Obstruction information (e.g. OBST NOTAMs) for aircraft that will be cleared for an instrument approach.
        • c. Information pertaining to cold temperature compensation.
      • 2. When advised of special use airspace (SUA) or military training route (MTR) activation, appropriate action is taken to separate nonparticipating IFR aircraft from those activities when required, and/or to issue applicable advisories as warranted. When meeting this requirement, there is no requirement for controllers to additionally issue the associated D NOTAM activating that SUA or MTR to the pilot. Accordingly, D NOTAMs for SUA that contain the accountability codes SUAE, SUAC, and SUAW are not required to be issued.
      • 3. Although a pilot may have obtained NOTAM information during pre-flight briefings, airport conditions may have changed in flight. Therefore a pilot stating, or a controller asking, if they “have the NOTAMS” does not relieve the controller of the responsibility of issuing airport conditions that might restrict an approach or landing. Additionally, controller instructions to contact FSS to obtain the NOTAMs does not relieve the controller of their responsibilities specified in this paragraph.
    2. TERMINAL. On first contact or as soon as possible thereafter, and subsequently as changes occur, inform an aircraft of any abnormal operation of approach and landing aids and of destination airport conditions that you know of which might restrict an approach or landing. This information may be omitted if it is contained in the ATIS broadcast and the pilot states the appropriate ATIS code.
    3. Issue RwyCC contained in a FICON NOTAM to aircraft in accordance with one of the following:
      1. Before or when an approach clearance is issued.
      2. Before an en route descent clearance is issued.
      3. TERMINAL. Prior to departure.
      4. As soon as possible after receipt of any subsequent changes in previously issued RwyCC information.
    4. RwyCC may be issued in lieu of the complete FICON NOTAM. Issue the complete FICON NOTAM upon pilot request, workload permitting.
      • EXAMPLE
      • Boston Runway Two Seven, field condition, three, three, three, one hundred percent, two inches dry snow over compacted snow. Observed at one five three zero zulu.

      NOTE: RwyCC may be transmitted via the ATIS as prescribed in Paragraphs 2-9-3, Content; 3-3-1, Landing Area Condition; 3-9-1, Departure Information; and 3-10-1, Landing Information.

    5. TERMINAL. Where RCRs are provided, transmit this information to USAF and ANG aircraft. Issue the RCR to other aircraft upon pilot request.

      NOTE: USAF offices furnish RCR information at airports serving USAF and ANG aircraft.

Back
Top Bottom