Chapter 8. NAS En Route Automation
8-1-1. TRANSITION PROCEDURES
must develop and maintain current detailed procedures for
transition to and from the various automated and nonautomated
modes of operation.
transition plans must include as a minimum:
decision authority; i.e., the individual responsible for
making the transition decision.
checklists specifying the duties and the responsibilities for
the OMIC, STMCIC, FLM, Radar Position (R), and other
appropriate positions. The checklist must include, as a
minimum, the following information/procedures:
procedures (intra- and interfacility).
duties/responsibilities (including detection and resolution of
Whenever possible, coordination/notification procedures and
duties/responsibilities should be listed in the order in which
they are to be accomplished.
air traffic manager must not cause or permit the operational
use of the Direct Access Radar Channel (DARC) solely for
purposes of training when the primary operational system is
FLIGHT DATA PROCESSING
must process ALTRV flight plans as follows:
ALTRV data, stationary and/or flight plan information, must
not be entered into the computer, processed, stored, or
transmitted by the computer unless specific declassification
data is provided; for example, “declassified for NOTAM/computer
flight plan processing 24 hours in advance.” In the absence of
declassified data, process this information manually and pass
to only those personnel with a need to know. All data must be
marked with the appropriate level of security classification,
collected when notification to all applicable parties is
completed, and destroyed according to security guidelines.
The use of a mission plan message is not authorized for
processing classified ALTRV flight plans.
military operations specialist at the departure ARTCC or where
the ALTRV begins must ensure that unclassified ALTRV missions
are entered into the NAS computer to destination or to ALTRV
Base operations within Anchorage ARTCC's jurisdiction may
enter ALTRV flight plans into the NAS computer.
flight plans for military aircraft (including ALTRVs) to or
through the Anchorage FIRs must be given normal addressing
plus PAZAZQZX and PAZNZQZX.
ALTRV flight plans that have a block altitude change must be
entered to the destination airport or ALTRV end point. An
“XXX” must be entered into the route of flight immediately
after each fix where a block altitude change is to occur to
prevent the production of flight progress strips containing
erroneous altitude information. The air traffic specialist
working the area where the “XXX” has been entered must change
the mission block altitude to what was previously coordinated
and remove the “XXX” so that the correct block altitude will
be processed to subsequent facilities.
Flight Plan Entries for MARSA and
For domestic flight plans (not leaving
U.S. domestic airspace), include “MARSA”
and/or “ALTRV” in Field 11.
For international flight plans, include
the word(s) “MARSA” and/or “ALTRV” in
Reasons for Special Handling (STS/). Do not
include additional/supplemental information in
STS/. Include any additional/supplemental
information in Remarks (RMK/).
IR101E1802X1845 MARSA BAKER23
facility officer who has been designated military liaison and
security duties is responsible for the development and
implementation of methods for assuring the accuracy and the
completeness of ALTRV flight plan and control information.
and revisions of ALTRV flight plans not processed online must
be forwarded via the Aeronautical Information System from
facility to facility.
8-1-3. COMPUTER DATA RETENTION
SAR/CDR computer and DLOG (if recorded) recordings and data
communications/console typewriter printouts for 15 days unless
they are related to an accident/incident as defined in FAAO 8020.11,
Aircraft Accident and Incident Notification, Investigation,
and Reporting. Retention of the latter must be in accordance
with FAAO 1350.15, Records, Organization, Transfer, and
Destruction Standards, Chapter 14, subparas 8020(1), (a), (b),
(c), (d), and (exception).
a request is received to retain computer data following an
accident, the printout of the relative data will suffice, and
the recording tape/disc may then be returned to service
through the normal rotational cycle. The printout data are
considered a permanent record and must be retained in
accordance with aircraft accident/incident retention
requirements. Reduction of the SAR/CDR and DLOG (if recorded)
tapes/discs to hard-copy format must be made at the earliest
time convenient to the facility involved without derogating
the ATC function and without prematurely taking the computer
out of ATC service. Do not make these data and printouts a
part of the accident/incident package.
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.
SAR/CDR and DLOG (if recorded) tapes/discs/duplicate and/or
originals and data communications/console typewriter
printouts related to hijack aircraft the same as voice
recorder tapes. (See para 3-4-4, Handling Recorder Tapes or