Section 2. Data Recording and Retention

  1. Type or write the date on the console printout at the start of each operational day or as specified in a facility directive. The facility directive must require the time that the date must be entered daily.


The operational day for a 24-hour facility begins at 0000 local time. The operational day at a part time facility begins with the first operational shift in each calendar day.

  1. As a minimum, record on the console failure/error messages regarding Data Acquisition Subsystem (DAS), Data Entry and Display Subsystem (DEDS), and Interfacility (IF).


When a failure is known to exist, that particular failure printout may be inhibited to minimize its impact on the system.

  1. Facilities having continuous data recording capabilities must extract and record on tape or disc:
  1. Tracking messages, target reports, and sector time.
  2. Automatic functions and keyboard input data.
  3. Interfacility messages.
  4. MSAW and CA warning message data. Other data available in the extraction routine may be extracted.
  1. Air traffic facilities using a teletype emulator (TTYE) in lieu of a console printout (TTY) must store and retain data in accordance with paragraphs 12-2-1, Data Recording, and 12-2-2, Data Retention. However, the data may be retained on a disc or hard drive as specified in a facility directive.
  1. Write on each data extraction tape/disc:
  1. The tape/disc drive number.
  2. The date.
  3. The times (UTC) the extraction started and ended.
  4. The items listed in subparagraph 12-2-1c not extracted.
  5. The data extracted in addition to that required by subparagraph 12-2-1c.
  6. The initials of the person changing the recording.
  1. Retain data extraction recordings for 45 days except:
  1. Accidents: Retain data extraction recordings in accordance with FAA Order JO 8020.16, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting.
  2. Incidents: Retain data extraction recordings in accordance with FAA Order JO 8020.16.
  3. Tarmac Delay: When a facility is notified that an aircraft has or may have exceeded the “Three/Four-Hour Tarmac Rule,” retain data recordings relevant to the event for 1 year.
  1. If a request is received to retain data information following an accident or incident, the printout of the relative data will suffice. The tape/disc may then be returned to service through the normal established rotational program. The printout data are considered a permanent record and must be retained in accordance with aircraft accident/incident retention requirements. Reduction of the extracted data to hard-copy format will be made at the earliest time convenient to the facility involved without derogation of the ATC function and without prematurely taking the computer out of service. Do not make these data and printouts a part of the accident/incident package.
  2. If a request is received to retain a specific data recording and the data are available and contained on tape, the tape must be retained in its entirety. If the data are contained on disc, the facility may transfer all pertinent data to magnetic tape and label the tape a Duplicate Original. After successful transfer, the disc pack may be returned to service through the normal rotational cycle. However, if a specific request is received to retain the disc, the disc pack must be retained in its entirety.
  3. Treat data extraction recordings pertaining to hijack aircraft the same as voice recorder audio files.


FAA Order JO 7210.3, Para 3-4-4, Audio Data Retention.

  1. Whenever the computer fails during normal operations, all pertinent data must be recorded on the Fault Log. However, if the computer failure is the first of a particular nature and an operational requirement exists to resume normal computer operation as soon as possible, a Fault Log need not be recorded.
  2. When you anticipate the need for assistance from the National Field Support Group (NFSG), record the entire contents of memory before restarting the operational program.
  3. Retain the Fault Log and the memory dump until the cause of the fault has been determined or NFSG requests them.