Chapter 6. Flight Data

Section 1. General

6-1-1. COMMUNICATIONS SERVICE

Most flight movement data exchanged outside of the facility is processed by automated systems such as the National Airspace Data Interchange Network (NADIN). It is important to adhere to strict format and procedures during normal operations as well as system interruption periods.

a.Circuit interruption notifications should be as follows:

1.AFSS.

(a)M1FC. Notify their FSDPS and appropriate telco servicing company of all outages.

(b)OASIS. Notify NADIN or WMSCR, (as appropriate), the Harris Help Desk, and appropriate telco servicing company of all outages.

NOTE-
The FSDPS notifies NADIN for Service B outages or AWP for Service A outages, as well as the ARTCC Systems Engineer (SE).

2.FSS. Notify their guard facility, the AISR Customer Service Center, and NADIN.

b.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.

NOTE-
OASIS facilities should obtain and record ticket numbers provided by Harris or the telco servicing company.

c.AISR and NADIN telephone numbers are as follows:

1.NADIN/ATLANTA (KATLYTYX)
(770) 210-7675.

2.NADIN/SALT LAKE CITY (KSLCYTYX) (801) 320-2172.

3.AISR HELPDESK 866-466-1336.

d.OASIS telephone numbers are as follows:

1.WMSCR/ATLANTA 770-210-7931.

2.WMSCR/SALT LAKE CITY
801-320-2045.

3.HARRIS HELPDESK 877-373-0110.

6-1-2. FLIGHT PLANS

The filing of VFR flight plans is recommended. Brief pilots, as appropriate, on the following:

a.Identify the tie-in station for the departure point, and advise the pilot to report departure time directly to that facility.

b.When a departure report is unlikely because of inadequate communications capability, advise the pilot that the flight plan will be activated immediately, using the proposed departure time as the actual departure time. Include "ASMD DEP" in remarks. The pilot is responsible for cancelling or extending the flight plan if the flight is cancelled or delayed.

c.Determine the flight plan area in which the destination is located. Request the pilot close the flight plan with the tie-in station. Provide the pilot the tie-in station's phone number, upon request.

d.Recommend that a separate flight plan be filed for each leg of a VFR flight.

e.Request the pilot inform an AFSS/FSS whenever the filed time en route changes more than 30 minutes.

f.On return flights from remote areas, such as a fishing site, establish a mutually acceptable date/time with the pilot for alerting search and rescue.

g.On a single flight to be conducted under both IFR/VFR flight rules, confirm whether the VFR portion is by flight plan and, if so, with whom the pilot will close. File two separate flight plans.

h.If a pilot indicates the flight will penetrate Class A airspace, advise the pilot of the Class A requirements.

i.When a pilot files to an airport served by a part-time FSS and the ETA is during the period the facility is closed, ask the pilot to close with the associated AFSS/FSS, identified in FAAO JO 7350.8, Location Identifiers and the Airport/Facility Directory.

j. Upon request, inform pilots filing IFR flight plans of the appropriate and most effective means of obtaining IFR departure clearances.

k.When a pilot files a DVFR flight plan, advise the pilot to activate with Flight Service. Also advise the pilot that a discrete beacon code will be assigned upon activation.

NOTE-
1.A discrete beacon code may be assigned when the flight plan is filed, as necessary. If the pilot wants to file a DVFR flight plan that departs outside the facility's flight plan area, provide the applicable toll-free number for the departure FSS.

2.Discrete beacon codes are assigned to facilities in accordance with FAAO 7110.66, National Beacon Code Allocation Plan.

6-1-3. FLIGHT PLAN DATA

Handle flight plan data as follows:

a.AISR.

1.Record flight plan data received from an operations office on FAA Form 7233-1 or a flight progress strip. The operations office must obtain complete information on the flight, but need forward to the FAA only those items necessary for control or VFR flight plan purposes.

2.Accept military flight plan proposals, cancellations, and closures from any source including collect telephone calls.

3.Pass the FAA Form 7233-1 to the appropriate operating position for delivery of the flight notification message.

b.M1FC/OASIS.

1.Record flight plan data on domestic or ICAO flight plan mask or dialog box as appropriate. Flight plan data received from an operations office may be limited to only those items necessary for control or VFR flight plan purposes, provided the operations office obtains complete information on the flight.

2.Accept military flight plan proposals, cancellations, and closures from any source, including collect telephone calls.

3.Transmit flight notification messages as follows:

(a)M1FC. From a flight plan mask in order for M1FC to place the message in the aircraft data file and provide automatic log and tally.

(b)OASIS. From a flight plan dialog box in order for OASIS to place the message in the history file and provide automatic log and tally.

NOTE-
Part-time operations offices must provide complete information in the event it is needed for SAR purposes.

6-1-4. PART-TIME FSS CLOSURE ACTION

Part-time facilities shall forward the following information to the designated guard AFSS/FSS.

a.Inbound flights - all information.

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

c.All other pertinent information; e.g., NOTAM, pending outages.