Section 6. FSS Printing of Lists and Tallies
(Model 1 Full Capacity)

16-6-1. PRINTING OF LISTS

a.  Every hour on the minute specified by the Inbound List Print Interval (ILPI) system parameter, the Suspense List and the Inbound List must be printed at the appropriate FSS on the flight plan (FP) printer. For each list and FSS, this function must:

1. Retrieve the list data from the data base.

2. Format the title and the column headings.

3. List the entries in chronological order.

b. The Inbound List hourly printout consists of:

1. Time.

2. ACID.

3. Type of Flight.

4. A/C Type.

5. Departure.

c. The Suspense List hourly printouts consist of:

1. Time.

2. Message ID and/or ACID.

3. Type.

4. Addresses.

d. The Inbound List and the Suspense List printouts must be retained for l5 days.

16-6-2. PRINTING OF TRANSACTIONS INVOLVING LIST UPDATES

Transactions involving updates must be printed at the time of the transaction at the affected FSS on the flight movement printer.

a. The conditions for this function are a Flight Data List being updated by:

1. Acknowledging a general Service B message.

2. Not acknowledging the last address of a flight plan.

3. Receipt of an inbound flight plan.

4. Receipt of a change ETA message.

5. Receipt of a Roger message.

b. The List Update printouts must be retained for l5 days.

16-6-3. FLIGHT PLAN LOG PRINTING

The Flight Plan Log must be printed on the FP printer for the appropriate FSS once a day at the Log/Tally Print Time (LOGT) for that FSS. The entries in the log must be printed in chronological order.

a. The Flight Plan Log must consist of:

1. Date/Time.

2. ACID.

3. Types of Flight.

4. Departure Point.

5. Destination.

6. Position Number.

b. Should the log buffer for an FSS become full (l00,000 characters) before the LGOT, the data will be printed.

c. The Flight Plan Log printout must be retained for l5 days.

16-6-4. PREFLIGHT BRIEFING LOG PRINTING

The Preflight Briefing Log must be printed on the FP printer for the appropriate FSS once a day at the LOGT for the FSS. The entries in the log must be printed in chronological order.

a. The Preflight Briefing Log must consist of:

1. Time.

2. ACID.

3. Departure Point.

4. Destination.

5. Position Number.

6. Remarks.

b. Should the log buffer for an FSS become full (l00,000 characters) before the LOGT, the data will be printed.

c. The Preflight Briefing Log printout must be retained for l5 days.

16-6-5. IN-FLIGHT CONTACT LOG PRINTING

The In-Flight Contact Log print function must be printed on the FP printer for the appropriate FSS once a day at the LOGT for the FSS. The entries in the log must be printed in chronological order.

a. The In-Flight Contact Log must:

1. Retrieve the data from the In-Flight Contact Log.

2. Format the title and the column headings.

3. Sum the tallies.

4. List the entries in chronological order.

b. Should the log buffer for a FSS become full (l00,000 characters) before the LGOT, the data will be printed.

c. The In-Flight Contact Log printout must be retained for l5 days.

16-6-6. TALLIES PRINTING

The tally print function must print the tallies on the FP printer or to a personal computer (PC) assigned to collect the data once a day at the LOGT for the FSS.

a. The Terminal Daily Tally and the Summary of Daily Tallies must be printed or sent to a PC assigned to collect the data. The tallies for the Terminal Daily Tally are summed from the log entries for each of the terminal entries. The following type of logging must be done by the system:

1. From the In-Flight Contact Log:

(a) Radio contacts.

(b) Aircraft contacted.

(c) Pilot briefs.

2. From the Preflight Briefing Log, pilot briefs.

3. From the Flight Plan Log:

(a) International.

(b) Military.

(c) Civil.

(d) IFR.

(e) VFR.

4. Flight services.

b. The tallies for the Summary of Daily Tallies are the sums of the terminal tallies for a FSS plus any modifications to the tallies made by the Facility Supervisor's Terminal (FST). The tally section labeled “Aircraft Contacted - International,” must be omitted if there are no entries for the terminal and the FSS. Tallies are printed or sent to a PC assigned to collect the data at the scheduled time, even if interim printing of logs has occurred due to a full buffer.

c. Use the Summary of Daily Tallies to complete FAA Form 7230-l3.

REFERENCE-
FAAO JO 7210.3, Para 16-5-3, Distribution and Amendment.

d. The Summary of Daily Tallies printout or computer records must be retained for l5 days.

16-6-7. FLIGHT PLAN PRINTING

The FP print function prints the fields associated with the flight plan when it is modified, is deleted, remains on the Proposed List longer than the Flight Plan Drop Interval (FPDI), or is the recycle of a Roger message (when acknowledging the last address of a flight plan.)

a. The data must be formatted with a title indicating what action is being performed (modified or deleted) and which list is affected. The formatted data must be printed on the flight movement printer at the affected FSS. The printing will be done after completion of the transaction.

b. The FP printout must be retained for l5 days.

16-6-8. DISABLED SYSTEM COMPONENT PRINTING

a. The Disabled System Component printing function will print the Failed Component Message at the affected FSS printer and on the display processor printer for the FSS COTC.

b. The Disabled System Component printout must be retained for l5 days.