Section 2. User Coordination/Conferences/Publicity

  1. LOCAL CONFERENCES
  1. Facility air traffic managers must call local conferences, as often as important local problems warrant, for discussing and clarifying facility operational matters. Use discretion before making any policy commitments.
  1. Following these conferences, take appropriate action within your jurisdiction.
  2. Send two copies of the minutes, or a summary, of each local conference to the appropriate Service Area office and one to each conference member.
  1. If a general conference is needed to discuss problems and subjects of a broader nature than those suitable for a local conference, forward such recommendation to the appropriate Service Area office.
  1. PILOT/CONTROLLER OUTREACH: OPERATION RAIN CHECK

The need to expand pilot and controller operational perspectives is very important; therefore, air traffic facilities should maintain effective pilot/controller outreach efforts, such as Operation Rain Check. Conducting seminars, briefings and familiarization experiences remain a great way to enhance pilot awareness of National Airspace System (NAS) functions, safety, and airspace procedures. Emphasis should be placed on operations within Class B, Class C, Class D and Terminal Radar Service Area (TRSA) airspace and, where applicable, on runway safety.

  1. Operation Rain Check must.
  1. Be performed as an additional duty and must not adversely impact facility resources.
  2. Be conducted in an atmosphere that fosters mutual understanding, cooperation and a free exchange of information.
  3. Demonstrate a desire to help pilots make use of FAA services, and reflect a spirit of service to NAS operators, while also benefitting controllers.
  1. Important success factors to consider for Operation Rain Check:
  1. Facility access and security. Use good judgment and proper security measures while planning, setting up and conducting local programs.

REFERENCE-

http://www.faasafety.gov/.
FAA Advisory AC 61-91J WINGS - Pilot Proficiency Program.
FAA Order 8900.1. Flight Standards Information Management System, Volume 15, FAAS Team Policies and Procedures (https://fsims.faa.gov/).
FAA Order JO 7200.21, Partnership for Safety Program.

  1. Continuous and extensive publicity may be vital to a successful program. FAA Public Affairs may provide guidance on local media relations activities. Also, consider collaborating program agendas and events with the FAA WINGS program representatives.
  2. Distribute program announcements and/or information to airport authorities, flight schools, fixed base operators, military airfield managers, and neighboring facilities, including Flight Standards District Offices (FSDO) and Airport District Offices (ADOs).
  3. Consider presenting Letters of Appreciation to key program participants.
  4. Facility Managers should:
  1. Determine what program materials, resources and other safety organizations would add value to implementing local Operation Rain Check programs.

NOTE-

At locations where more than one air traffic facility exists, consider cooperative efforts.

  1. Ensure locally adopted indoctrination materials comply with Privacy Act stipulations.
  2. Offer participation to Runway Safety Action Teams, FSDOs, and Airport Authorities.
  3. Be emphatic about Runway Safety and should include the following on the agenda:
  1. Runway incursion/excursion prevention.
  2. Airport signage and markings.
  3. Local runway safety related issues.
  4. Pilot/controller communications and read backs.

NOTE-

  1. Runway Safety Action Team meetings are required at all towered airports (FAA Order 7050.1, Chapter 4) and may be included to provide a positive venue for controllers, pilots and airport personnel to address surface safety.
  2. Additional runway safety information is available through FAA National and Service Area Runway Safety Offices and Runway Safety Program Managers.
  1. Facility sponsored pilot/controller forums.
  1. PUBLISHED ITEMS

Items of publicity, either commendable or critical of FAA facilities, should be forwarded to the Service Area office. This includes newspaper clippings, magazine articles, photographs, or copies of letters.

  1. COORDINATION OF ATC PROCEDURES
  1. Coordination must be carried out with the appropriate users prior to implementing or changing procedures which may have a significant effect on them or flight information publications. Users means the operators of aircraft; organizations representing aircraft owners, operators, or pilots; individuals; the DOD; aviation authorities; or other government agencies concerned with the safe, efficient operation of aircraft in the NAS.
  2. Procedures which will have a significant effect on the users will be coordinated with them by means of correspondence, individual contacts, or a presentation at a meeting for the purpose of soliciting individual comments. When deemed appropriate, the advice and viewpoint of individual users will be obtained prior to the development of a proposed change. When safety is not a factor, a minimum of 45 days should be afforded those responding to a request for comments.
  3. No joint user meeting will be conducted for the purpose of seeking user consensus or agreement on an issue. Coordination does not mean or imply that unanimity of opinion must be reached nor does it mean that user concurrence is required.
  4. Interfacility coordination must be carried out, as appropriate, prior to coordination with the users. In addition, all other concerned FAA facilities and offices must be informed prior to implementing these changes.
  5. The final decision on whether a change is adopted as proposed, changed in light of the individual replies received, or not adopted rests with the initiating office and will be based on an evaluation of all pertinent factors. If significant objections to a change are received, advise the Service Area office which will inform the Manager of Airspace and Rules, if deemed appropriate.
  6. When a change is adopted, users will be afforded sufficient time to prepare for the change prior to its implementation. If a proposed change is not adopted, an explanation of the decision will be forwarded to the users.