General

The initiation and completion of SAR for aircraft on overdue VFR flights (see Chapter 3, Section 4) and assisting other ATC facilities as needed for SAR involving overdue IFR flights.

Conducting intra‐facility and inter‐facility coordination.

Forwarding departures, progress reports, and arrival reports to ATC upon request.

Compilation, evaluation, recording, and dissemination of data.

Managing outbound traffic as required.

Revising flight data as necessary.

Correctly formatting and editing flight data messages.

Record all actions taken in the provision of flight data services in the operational system.

Flight plans and related messages.

Service A/B messages.

ATC clearances.

Weather and flight data messages.

NOTAMs.

Other operationally significant actions.

Locally approved procedures may be used to manually record data during heavy traffic periods or system outages and should be logged in the operational system as soon as practicable.

Use control/clearance symbols, abbreviations, location identifiers, and contractions for recording position reports, traffic clearances, and other data.

When recording data you may use:

Plain language to supplement data when it will aid in understanding the recorded information.

Locally approved contractions and identifiers for frequently used terms and local fixes not listed in FAA Order JO 7340.2, Contractions, or accessible through FAA Order JO 7350.9, Location Identifiers. Use only within your facility, not on data or interphone circuits. All locally approved contractions and identifiers must be placed in facility files for record and reference purposes.

When recording data manually, use the standard hand-printed characters shown in TBL 4-1-3 to prevent misinterpretation.

To correct or update data, draw a horizontal line through it and write the correct information adjacent to it.

Do not erase any item.

Inbound flights - all information.

Outbound flights - VFR and IFR flight plan data when proposed departure time and/or ETA is within the period from one hour prior to closing until one hour after opening.

All other pertinent information (for example, NOTAMs and pending outages).

When a telephone request for an ATC clearance is received, positively verify the departure location by airport name or location identifier, and the city name and state.

Pilots departing from a non-towered airport on an IFR flight plan in the CONUS should be directed to consult the Chart Supplement U.S. to determine the frequency or telephone number to use to contact clearance delivery.

Pilots of MEDEVAC flights in the CONUS may obtain a clearance by calling (877) 543-4733.

In Alaska, pilots may obtain a clearance via telephone.

Refer to FAA Order JO 7110.10, paragraph 4-2-7, ATC Clearances, Advisories, or Requests, for guidance on relaying ATC clearances.

Circuit interruption notifications should be as follows:

Consult your operational system handbook and standard operating procedures for detailed instructions regarding circuit interruption notification procedures.

Notify any guarding facility/sector, the AISR customer service center, and NADIN.

All outage reports should refer to the correct circuit and/or equipment identification numbers. Facilities should obtain and record ticket numbers provided by AISR or the TELCO authority.

WMSCR and NADIN: contact the FAA NEMC at (855) 322-6362 (FAA-NEMC).

For ATLANTA (KATLYTYX), press 1;

For SALT LAKE CITY (KSLCYTYX), press 2.

AISR help desk: (866) 466-1336.

Distress messages.

Messages concerning safety to human life.

Flight movement/control/safety messages.

Aviation meteorological observations/forecasts/warnings.

Administrative messages which pertain to FAA personnel, facilities, or property.

NOTAM data.

NADIN has established group codes to allow message originators to input a single address, which will result in dissemination to a selected number of facilities.

System‐wide group codes have been established for the primary use of RWA/KRWAYAYX and the ATCSCC (KCFCZDZX). These codes are KDOMYFYX and KDOMYYYX respectively.

A group code has also been established for each regional office and ARTCC primarily for the issuance of regional office notices (RENOT) and all ARTCC instructions. They are as follows for regional offices in TBL 6-1-2 and ARTCCs in TBL 6-1-3.

In addition, a group code, KFSSYFYX, was established for the CONUS.

Using a group code, the operational system automatically transmits all VFR flight plans to the Drug Enforcement Administration in addition to the destination at the time of activation.

The group code KSARYCYX has been established to assist in the processing of INREQs and ALNOTs.

Specialists should follow the transmit formats defined for the operational system in use. Failure to comply can result in the message being rejected by either NADIN or WMSCR. This may result in non‐delivery to the intended recipients.

Full keyboard punctuation is allowed on all messages destined for internal FAA, DoD, and NWS dissemination. For international dissemination, punctuation should be limited to those characters identified in pertinent ICAO documents.

Contractions and abbreviations should be used to shorten data transmissions to the extent possible. In no case should one be used that is not documented in FAA Order JO 7340.2, Contractions. For international communications, be aware that the foreign correspondent may not understand all FAA contractions and may not have a full command of the English language. Care should be exercised in international communications to avoid slang phrases and non‐ICAO approved abbreviations.

The operational system can obtain weather or aeronautical information, including WMO collectives, by request/reply for data not stored in the system. Specific examples can be found in each operational system user guide.

WMSCR automatically generates a negative response to request/reply inputs for which it cannot deliver.

NO REPORT AVBL. This response means the current data has not been received by WMSCR.

NOT IN SYSTEM. This response means WMSCR does not receive and store the requested data.

INVALID FORMAT. This response means the computer cannot process the request because of an input error.

WMSCR will generate only one negative response message to a request/reply transmission that requests multiple reports and only when none of the data requested can be delivered.