LESSON PLAN DATA SHEET

COURSE NAME: ASSISTANT CONTROLLER TRAINING, STAGE 2

COURSE NUMBER: 55053

LESSON TITLE: COMPUTER COMMAND COMPOSITION AND ENTRY

DATE REVISED: 2014-04

VERSION: V.1.02

REFERENCES: TI 6110.101, En Route Automation Modernization (ERAM) Air Traffic

Manual (ATM): RA-Position User Manual; TI 6110.100 En Route Automation
Modernization (ERAM) Air Traffic Manual (ATM): R-Position Manual; ERAM
EDSM SRS 210.04 V1B1, En Route Automation Modernization (ERAM) En
Route Display Management (EDSM) R-Position and General EDSM
Requirements Volume 1, Book 1; ERAM EDSM SRS 210.04 V1B2, En
Route Automation Modernization (ERAM) En Route Display Management
(EDSM) Appendices for R-Position and General EDSM Requirements
Volume 1, Book 2; ERAM EDSM SRS 210.04 V2B1, En Route Automation
Modernization (ERAM) En Route Display Management (EDSM) D-Position,
A-Position, and AT Specialist Requirements Volume 2, Book 1; ERAM IFPA
SRS 210.15, En Route Automation Modernization (ERAM) Interface Proxies
Set A (IFPA); ERAM FDP SSS 200.04, En Route Automation Modernization
(ERAM) Flight Data Processing (FDP); ERAM SIG 884, Hold View Issues
Part 1; ERAM SIG 1380, Hold View Issues Part 2

HANDOUTS: 55053-HO6, PRACTICE EXERCISES

EXERCISES: YES

END-OF-LESSON YES
TEST:

PERFORMANCE NO
TEST:

MATERIALS: NONE

OTHER PERTINENT THIS LESSON IS BASED ON ERAM BUILD EAC1500. THE LESSON HAS
INFORMATION: BEEN REVIEWED AND REFLECTS CURRENT ORDERS AND MANUALS
AS OF APRIL 2014.
INTRODUCTION

The National Airspace System (NAS) is a computerized network that passes

air traffic information from controller to controller. To function effectively in
that network, you must gain a thorough knowledge of the required command
composition and entry procedures.

Review The previous lessons covered the location and functions of the sector
equipment and of Command Fields 01 through 11.

Combining that knowledge with the information in this lesson, you will be able
to compose commands.

Purpose This lesson will cover command types associated with the A- and RA-
Positions. These are the command types you will use most in the control of
air traffic. The lesson also covers the remaining command fields used by the
Certified Professional Controller (CPC).

You will complete practice exercises on command composition and computer

entry.

55053-LP06 / V.1.02 1
INTRODUCTION (Continued)

Objectives

55053-LP06 / V.1.02 2
COMMAND COMPOSITION

Command ID  All commands must begin with a Command ID:

ERAM EDSM SRS
210.04 V1B2,  Two-letter designator
Appendix C,
Section C.1
 Hard-labeled function keys

 The two-letter designator is automatically inserted.

Command
Composition
Order
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.1

 A command starts with Field 01.

 The remaining fields are entered in a specified order depending on

command type.

 Command fields are separated by spaces.

55053-LP06 / V.1.02 3
COMMAND COMPOSITION (Continued)

Command
Composition
Area
TI 6110.101,
par. 1.2.6.2

 The RA-Position MCA View is accessed through the MCA button on the
RA-Position toolbar or by beginning to type a command.

 The view includes Preview and Feedback Areas.

 When a command is sent, the cursor changes to a busy cursor (hour-

glass symbol).

 If a command is accepted, a green check mark displays in the Feedback

Area.

 If a command is rejected, a red X displays in the Feedback Area.

 If a message in the Feedback Area is longer than four lines, the view
expands.

55053-LP06 / V.1.02 4
COMMAND ACCEPTANCE CHECKS

Command
Processing
TI 6110.100,
par. 1.4.1;
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.9;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.8

 Commands are checked for:

 Syntax and format

 Source legality

 Semantics

 If a command is rejected, an error or reject message will display in the

Feedback Area.

55053-LP06 / V.1.02 5
COMMAND ACCEPTANCE CHECKS (Continued)

Syntax and
Format
Checking
TI 6110.100,
par. 1.4.2;
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.2;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.8

 Format checking verifies that:

 All required fields are present.

 If the number of fields is incorrect, you may see one of two error
messages: MESSAGE TOO SHORT or MESSAGE TOO LONG.

 Example: In the DM command, fields 01 and 02 are required and

field 08 is optional. If you entered just field 01, you would get
MESSAGE TOO SHORT. If you entered fields 01, 02, 08, and 09,
you would get MESSAGE TOO LONG.

 Fields are in the correct sequence.

 Values entered are within the required range.

NOTE: Field 01 is always checked to verify it is a valid, two-letter

Command ID. If not, you will receive the error message, INVALID
MESSAGE TYPE.

 Syntax checking detects illegal characters.

Continued on next page

55053-LP06 / V.1.02 6
COMMAND ACCEPTANCE CHECKS (Continued)

Syntax and  Error messages display in the Feedback Area.

Format
Checking  System stops error checking as soon as it detects the first error in a
(Cont'd) command.
TI 6110.100,
par. 1.4.2;  Command is not retained in the Preview Area.
ERAM EDSM SRS
210.04 V1B2,
Appendix C,  Press RECALL key to display the command in the Preview Area to
Sections C.1, C.2, correct and resubmit it.
C.8

Syntax and
Format
Checking -
Example 1

 Field 02 has a limit of 7 characters.

55053-LP06 / V.1.02 7
COMMAND ACCEPTANCE CHECKS (Continued)

Syntax and
Format
Checking -
Example 2

 The sample command contains two errors: incorrect routing (W30 should
be W3, an AT Specialist position) and incorrect syntax (typing the letter O
instead of the clear weather symbol). As demonstrated here, the system
stops processing at the first error it encounters in the command.

Source  A source legality error is generated when the system detects that the
Legality controller is not authorized to enter the command.
ERAM EDSM SRS
210.04 V1B1,  Error message displayed in the Feedback Area: ILLEGAL SOURCE
par. 3.2.3.2.3.2.4

 Original command not retained in the Preview Area

Example: CP (Change Parameter) command cannot be entered from the

RA-Position.

55053-LP06 / V.1.02 8
COMMAND ACCEPTANCE CHECKS (Continued)

Semantic
Checking
TI 6110.100,
par. 1.4.4;
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.35

 Semantic checking determines whether the current state of the system

allows the command to be performed.

 If not, system generates semantic error

Example: (R-Position) Attempt to See All a sector that is also

performing a See All.

 Error message displayed in the Feedback Area

 Original command not retained in the Preview Area

55053-LP06 / V.1.02 9
COMMAND ACCEPTANCE CHECKS (Continued)

Review QUESTION: What acceptability checks are performed by the computer?

QUESTION What error message is displayed in the Feedback Area
when the system detects that the controller is not authorized to enter the
command?

55053-LP06 / V.1.02 10
SYSTEM RESPONSE

Types of  After format, syntax, source legality, and semantic checks have been
Responses performed, the computer will respond to your input by one of the
ERAM EDSM SRS following:
210.04 V1B1,
par. 3.2.3.2.3.2.1
 Accept

 Reject

 Error

Accept  If input passes all checks, one of the following occurs:

ERAM FDP SSS
200.04, par 3.3.2;  Data is displayed on MCA Feedback Area, Flight Strip Printer (FSP),
ERAM EDSM SRS
210.04 V1B1, par. Situation Display, or
3.2.3.2.1.2.1.6.3
 If immediate display is NOT required, response statement is
displayed on MCA Feedback Area, or

 Combination of the first two options occur together.

55053-LP06 / V.1.02 11
SYSTEM RESPONSE (Continued)

Error or Reject
TI 6110.101,
par 1.2.6.2;
TI 6110.100,
par 6.1.2;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.8

 If a command is rejected, you will receive an ERROR or REJECT

message in the Feedback Area.

NOTE: Both the REJECT and ERROR messages are indicated by a red X.
The controller won’t normally get feedback on which type of response they
have received.

 The Feedback Area messages will typically contain information to help

the controller troubleshoot the mistake.

55053-LP06 / V.1.02 12
SYSTEM RESPONSE (Continued)

Error
Response
Example
TI 6110.101,
par 1.2.6.2;
TI 6110.100,
par 6.1.2;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.8

NOTE: RAL is the adapted abbreviation that should have been used.

Continued on next page

55053-LP06 / V.1.02 13
SYSTEM RESPONSE (Continued)

Error
Response
Example
(Cont'd)
TI 6110.101,
par 1.2.6.2;
TI 6110.100,
par 6.1.2;
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.5;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.8

NOTE: This is the response to the command input, since Field 11 is not
permitted in the DM.

55053-LP06 / V.1.02 14
CONTROLLER RESPONSE TO ERROR MESSAGES

Canceling  Used in lieu of correction

Entire
Command  CXX
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.35
 Cancels entire command

Taking No  Command will cancel after an adapted number of minutes.

Action
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.35

Editing  To edit a command:

Command
ERAM EDSM SRS  Recall the command via the RECALL key.
210.04 V1B1,
par. 3.2.1.2.1.5.6
 Use text-editing capabilities to correct the command.

55053-LP06 / V.1.02 15
COMMAND ENTRY ELIGIBILITY

Two Kinds of  Flight Data commands

Input
Commands  Eligibility is required.
ERAM EDSM SRS
210.04 V1B2,  Sector Information Display commands
Appendix C,
Section C.3  Eligibility is NOT required.

Sector  Sector is eligible to enter a command affecting the flight plan database if:
Eligibility
ERAM EDSM SRS  For proposed flight plans, the sector has or will receive a:
210.04 V1B2,
Appendix C,  Departure strip, or
Section C.3
 Departure coordination strip.

 Sector has control of that flight.

 Logic override (/OK) is entered.

Termination  Eligibility terminates when control of the flight is transferred to another

ERAM FDP SSS sector or facility.
200.04,
par. 3.3.1.3

55053-LP06 / V.1.02 16
COMMAND TYPES

Flight Data
Commands
ERAM FDP SSS
200.4, par. 3.3.2;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.2, C.3

 Purpose: Establish and update flight plan data.

 Command types include:

 Flight Plan (FP)

 Stereo Flight Plan (SP)

 Remove Strip Command (RS)

 Departure Command (DM)

 Hold Command (HM)

 Amendment Command (AM)

NOTE: There are other flight data commands that are not taught in this
lesson.

55053-LP06 / V.1.02 17
COMMAND TYPES (Continued)

Flight Plan
(FP)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.2

 Purpose: Establish a database for active or proposed flight plans.

 Required fields

 01, 02, 03, 05, 06, 07, 08 or 09, 10

 Optional fields

 04 and 11

NOTE: If a beacon code is not entered in a Flight Plan command, then the
computer will assign one. If you enter a beacon code that is already in use by
another aircraft, then the computer will assign another code.

55053-LP06 / V.1.02 18
COMMAND TYPES (Continued)

Stereo Flight
Plan (SP)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.2

 Purpose: Establish a database for abbreviated FPs that are repeated

many times, day after day.

 Required fields:

 01 – Message Type

 02 – AID

 07 – TIM

 10 – RTE

 Optional fields:

 03 – TYP

 05 – SPD

 08 or 09 – ALT or RAL

 11 – RMK

55053-LP06 / V.1.02 19
COMMAND TYPES (Continued)

Remove Strip
(RS)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.34;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.2

 Purpose: Remove any stored information on:

 Tentative or active flight

 Associated track

 Required fields:

 01 – Message Type

 02 – FLID

 Confirm by entering Y.

NOTE: This logic check is to ensure that you have entered the RS command
on the correct AID.

55053-LP06 / V.1.02 20
COMMAND TYPES (Continued)

Departure
Command
(DM)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.2

 Purpose: Activate a proposed FP.

 Required fields

 01 – Message Type

 02 – AID

 Optional Fields

 07 – TIM

 If omitted, computer will use present clock time.

 08 – Assigned Altitude

 If omitted, computer will use requested altitude for processing.

Continued on next page

55053-LP06 / V.1.02 21
COMMAND TYPES (Continued)

Departure  Special entries

Command
(DM) (Cont’d)  Logic Check Override (/OK)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
 Forces eligibility
Sections C.1, C.2
 Asterisk (*) suffixed to FLID

 Suppresses an Adapted Departure Route (ADR)

 An optional asterisk (*) or optional overcast weather symbol () may be

suffixed to Field 02.

 Entry of the asterisk inhibits the use of preferred routes.

 Entry of the overcast symbol inhibits the use of ICAO Equipment

Restricted Routes (IERRs).

 If the /OK is also suffixed, the asterisk or overcast symbol must

appear first.

Review

55053-LP06 / V.1.02 22
COMMAND TYPES (Continued)

Hold
Command
(HM)
EDSM V1B2
Appendix C,
Sections C.1, C.2;
SIG884; SIG1380

 Purpose: The HM command is used to place an aircraft in hold.

 Required fields

 01 – Message Type

 02 – AID

 21 – Hold Data

 Optional Fields

 310 – Holding Instructions

Continued on next page

55053-LP06 / V.1.02 23
COMMAND TYPES (Continued)

Hold  Use HOLD function key or type HM in the MCA.

Command
(HM)  Type the FLID (Field 02).
EDSM V1B2
Appendix C,  Hold Data can include:
Sections C.1, C.2;
SIG884; SIG1380
 The holding fix

 P for present position hold

 EFC

 C to cancel the hold

 To include the EFC time, enter the fix (or P) followed by a forward slash
[ / ] and the four-digit time.

 If you want to include Holding Instructions, they must ALL be entered.

 Direction is referenced by the eight cardinal compass points, such as

NW.

 Turns are RT or LT for right or left turn.

 Leg lengths are nautical miles, with NM after the number, or in

minutes, with MIN after the number.

 If no direction, turns, or leg lengths are entered, default information is

used.

Continued on next page

55053-LP06 / V.1.02 24
COMMAND TYPES (Continued)

Hold
Command
(HM)
EDSM V1B2
Appendix C,
Sections C.1, C.2;
SIG884; SIG1380

 As soon as the HM command is entered, you will observe HOLD

indications on the Aircraft List (ACL) and the aircraft will be entered into
the R-Position Hold View.

NOTE: If the holding fix is in a downstream sector, the aircraft will also be
entered into that sector’s Hold View.

 The HOLD key or HM command can be used to cancel a hold.

 The hold is canceled and HOLD indications on the ACL and R-Position
are grayed out.

NOTE: Entering a route amendment will also cancel a hold for an aircraft.

55053-LP06 / V.1.02 25
COMMAND TYPES (Continued)

Amendment
Command
(AM)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.16;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.8

NOTE: The program has restrictions when amending Fields 02, 06, 07, and
10. The restrictions are discussed later in this lesson.

 Purpose: Change, add to, or delete FP data.

 Required fields:

 01

 02

 Field Reference

 Amendment Data

NOTE: One set of Field Reference and Amendment Data is required.

Additional sets are optional. These fields are shown on the slide in
parentheses.

Continued on next page

55053-LP06 / V.1.02 26
COMMAND TYPES (Continued)

Amendment
Command
(AM) (Cont’d)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.16;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.8

55053-LP06 / V.1.02 27
COMMAND TYPES (Continued)

Review QUESTION: What are the six types of Flight Data commands taught in
this lesson?

QUESTION: An Amendment Command (AM) contains what fields?

55053-LP06 / V.1.02 28
COMPOSITION OF FIELD AMENDMENTS

Fields 02
Through 09
ERAM FDP SSS
200.04, par 3.3.2;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.2

 Field 02 (AID)

 Field 02 amendments cannot be combined with any other field

amendments.

 Cannot be used if duplicate exists

 Field 03 (TYP)

 Amended if aircraft data changes

 Field 04 (BCN)

 Cannot be used if duplicate

 Field 05 (SPD)

 Amended for any speed change

Continued on next page

55053-LP06 / V.1.02 29
COMPOSITION OF FIELD AMENDMENTS (Continued)

Fields 02  Field 06 (FIX)

Through 09
(Cont’d)  Cannot be used for proposed flights by itself
ERAM FDP SSS
200.04, par 3.3.2;
ERAM EDSM SRS
 Amendments to proposed flights must include Fields 06 and 10.
210.04 V1B2,
Appendix C,  Field 07 (TIM)
Sections C.1, C.2
 Coordination time

 Proposed time (P)

 Departure time (D)

 Estimated time (E)

 Field 08 (ALT)

 Assigned altitude in active FP

 Cannot be used in proposed FP

 Field 09 (RAL)

 Requested altitude in proposed FP

 Cannot be used in active FP

55053-LP06 / V.1.02 30
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 10 (RTE)
ERAM FDP SSS
200.04, par 3.3.2;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.1

 Unless Field 10 is the only field being amended, Field 06 must be

included.

 Amendments to Field 10 use merge elements.

 Fix or route that appears only once in Field 10

 Unambiguous element

Continued on next page

55053-LP06 / V.1.02 31
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 10 (RTE)
(Cont’d)
ERAM FDP SSS
200.04, par 3.3.2;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.1

NOTE: Data entered must either merge with two elements of the filed route
or merge with one element and indicate the new destination.

Continued on next page

55053-LP06 / V.1.02 32
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 10 (RTE)
(Cont’d)
ERAM FDP SSS
200.04, par 3.3.2;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.1

 Delay data is suffixed to the fix name, Fix-Radial-Distance (FRD), or

latitude/longitude.

 Estimated Time En Route (ETE)/Estimated Time of Arrival (ETA) must be

suffixed to the last filed element when the element is a fix.

Continued on next page

55053-LP06 / V.1.02 33
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 10 (RTE)
(Cont’d)
ERAM FDP SSS
200.04, par 3.3.2;
ERAM EDSM SRS
210.04 V1B1,
pars.
3.2.3.2.3.2.14,
3.2.3.2.3.2.32

 When amending a departure fix:

 For active flights, amend only the first element of Field 10 and append
an ↑.

 For proposals, enter a Field 06 and Field 10 amendment and append

an ↑.

 Amendments to the departure fix on proposed FPs require Field

06.

 When amending a departure point:

 If the second element of the route is an airway or SID, the new

departure point has to merge correctly with the airway or SID.
Otherwise, the amendment will be rejected.

 Reject message: X FIX NOT ON ROUTE

Continued on next page

55053-LP06 / V.1.02 34
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 10 (RTE)
(Cont’d)
ERAM FDP SSS
200.04, par 3.3.2;
ERAM EDSM SRS
210.04 V1B1,
pars.
3.2.3.2.3.2.14,
3.2.3.2.3.2.32

 When amending a proposal:

 For proposals, enter a Field 06 and Field 10 amendment and append

an ↑.

 Amendments to the departure fix on proposed FPs require Field

06.

 If the second element of the route is an airway or SID, the new

departure point has to merge correctly with the airway or SID.
Otherwise, the amendment will be rejected.

 Reject message: X FIX NOT ON ROUTE

55053-LP06 / V.1.02 35
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 06/10
Combination
ERAM FDP SSS
200.04, par 3.3.2;
ERAM EDSM SRS
210.04 V1B1,
pars. 3.2.9.2.5.8,
3.2.9.2.6,
3.2.9.2.7.1;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.1

 When suppressing an Adapted Departure Route (ADR)/Adapted Arrival

Route (AAR)/Adapted Departure Arrival Route (ADAR):

 An asterisk (*) is suffixed to the departure/destination fix.

 If used with a time element suffix, it must precede the data.

Continued on next page

55053-LP06 / V.1.02 36
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 06/10
Combination
(Cont'd)
ERAM FDP SSS
200.04, par 3.3.2;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.1

 Active flight plan:

 Command format is the same as for a proposed flight plan.

 Departure fix is retained.

 Tailoring symbol (./.) is inserted.

 New route follows.

 Field 06 replaces the previously stored coordination fix.

NOTE: In the example on the slide, new coordination fix processing starts at
GHI. Caution must be exercised since all sectors with unexpired fix postings
will receive a Remove Strip message.

 If a new destination fix is used, it must be followed by  or *.

 The entered route data will completely replace the filed Field 10.

 If the entered route data is to be merged with the filed Field 10, the
last element of the entered route data must match an element of the
filed Field 10.

55053-LP06 / V.1.02 37
COMPOSITION OF FIELD AMENDMENTS (Continued)

Fields 06, 07,

and 10
ERAM FDP SSS
200.04,
par 3.3.2.1.2;
ERAM EDSM SRS
210.04 V1B1,
pars 3.2.9.2.6,
3.2.9.2.7.1;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.1

 Permit amendment of the following:

 Fix

 Time

 Full or partial route

Continued on next page

55053-LP06 / V.1.02 38
COMPOSITION OF FIELD AMENDMENTS (Continued)

Fields 06, 07,

and 10 (Cont'd)
ERAM FDP SSS
200.04,
par 3.3.2.1.2;
ERAM EDSM SRS
210.04
pars 3.2.9.2.6,
3.2.9.2.7.1;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.1

55053-LP06 / V.1.02 39
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 10 Using
Route Readout
Request
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.32

 The route readout request is displayed in the Response Area.

 Each item in the route readout request is numbered in the sequence it

occurs.

Continued on next page

55053-LP06 / V.1.02 40
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 10 Using
Route Readout
Request
(Cont'd)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.32

 The response to a Route Readout request is handled as a Route

Amendment Correction to Field 10.

 The Route Readout request sequence numbers may be used as

replacement for the elements in the correction response.

Continued on next page

55053-LP06 / V.1.02 41
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 10 Using
Route Readout
Request
(Cont'd)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.32

55053-LP06 / V.1.02 42
COMPOSITION OF FIELD AMENDMENTS (Continued)

Field 11 (RMK)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.28

 Contains plain language remarks or general information

 Must start with:

 Clear weather symbol (O)

 Interfacility

 Overcast symbol ()

 Intrafacility

55053-LP06 / V.1.02 43
COMPOSITION OF FIELD AMENDMENTS (Continued)

Review

55053-LP06 / V.1.02 44
COMPOSITION OF FIELD AMENDMENTS (Continued)

Review
(Cont’d)

55053-LP06 / V.1.02 45
COMPOSITION OF FIELD AMENDMENTS (Continued)

Review
(Cont’d)

55053-LP06 / V.1.02 46
ORAL EXERCISE: ROUTE READOUT AMENDMENTS

Route
Amendment
Correction
Exercise

 Oral Exercise: Route Amendment Correction is located in Appendix A at

the end of the lesson plan.

55053-LP06 / V.1.02 47
PRACTICE EXERCISE 1

Practice  Practice Exercise 1: Using Proper Computer Sequences and Format is

Exercise 1
located in 55053-HO6.

55053-LP06 / V.1.02 48
MULTIPLE FLIGHT IDs OPTION

Multiple FLIDs
TI 6110.100,
par. 7.1.1;
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.3.2.3.2.7;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.1

 Some commands allow multiple Flight IDs (FLIDs).

 FLIDs are separated by a slash (/).

 Up to 15 FLIDs may be specified in a single command entry.

55053-LP06 / V.1.02 49
INFORMATION REQUEST COMMANDS

Uses  Information request commands include:

ERAM EDSM SRS
210.04 V1B1,  Altimeter Request (AR or QD)
pars. 2.4.4.2.2.11,
3.2.4.5.2.2.14,
3.2.9.2.5;  AR command maximum of four altimeters at a time
ERAM EDSM SRS
210.04 V1B2,
 QD command maximum of six altimeters at a time
Appendix C,
Section C.1
 Weather Request (WR)

 Strip Request (SR)

 Flight Plan Readout (FR)

NOTE: There are other Information Request commands that are not taught in
this lesson.

 Used to request:

 A display

 Printout of data from an established database

55053-LP06 / V.1.02 50
INFORMATION REQUEST COMMANDS (Continued)

Altimeter
Request
(AR or QD)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.2

 Purpose: Request/suppress altimeter settings (printing from A-Position

only).

 Required fields: 01 and 13

 Optional field: 13

 Shown in parentheses, ( ), in slide above

 Field 13 - Location Identifier (LOCID)

 Used to designate a location for entry of altimeter requests, altimeter

settings, upper wind requests, and upper wind entry

 Must be an adapted altimeter reporting station

Continued on next page

55053-LP06 / V.1.02 51
INFORMATION REQUEST COMMANDS (Continued)

Altimeter
Request
(AR or QD)
(Cont'd)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.2

Continued on next page

55053-LP06 / V.1.02 52
INFORMATION REQUEST COMMANDS (Continued)

Altimeter
Request
(AR or QD)
(Cont’d)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.4.4.2.2.11;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.1, C.2;
TI 6110.101,
Section 12

 Entry from A-Position

 If Fields 01 (AR or QD) and 13 (LOCID) are entered:

 Prints all altimeters selected on the FSP (at least one, maximum
of 24)

 Entry from RA-Position

 If Fields 01 (AR or QD) and 13 (LOCID) are entered:

 Adds the LOCID altimeter to the RA Altimeter Settings View

 Deletes the LOCID altimeter if station is already in RA Altimeter

Settings View

Continued on next page

55053-LP06 / V.1.02 53
INFORMATION REQUEST COMMANDS (Continued)

Altimeter
Request
(AR or QD)
(Cont’d)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.4.4.2.2.11;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2;
TI 6110.101,
Section 12

 Entry from RA Altimeter Settings View Template

 A maximum of twenty-four (24) entry boxes is allowed.

 Maximum columns four (4)

 Maximum rows twenty-four (24)

 Select desired box for entry.

 Type LOCID into box

 Keyboard Enter

 Exit template menu by either Keyboard Enter again or use the close
feature of the template.

Continued on next page

55053-LP06 / V.1.02 54
INFORMATION REQUEST COMMANDS (Continued)

Altimeter
Request
(AR or QD)
(Cont’d)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.4.4.2.2.11;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2;
TI 6110.101,
Section 12

 Removal from RA Altimeter Settings View Template

 Select desired box for removal.

 Select Delete pop-up.

 Close template.

Continued on next page

55053-LP06 / V.1.02 55
INFORMATION REQUEST COMMANDS (Continued)

Altimeter
Request
(AR or QD)
(Cont’d)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.4.4.2.2.11;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2;
TI 6110.101,
Section 12

 Altimeter Settings View Coding

 Time of the altimeter reading follows the station name. Time is

underlined if the entry is more than 1 hour old.

 Altimeter setting is underlined if it is below 2992. The letter -M-

appears if the reporting station is missing altimeter data.

55053-LP06 / V.1.02 56
INFORMATION REQUEST COMMANDS (Continued)

Weather
Request (WR)
ERAM EDSM SRS
210.04 V1B1,
pars. 3.2.4.5.2.2.14
and 3.2.4.5.2.3.13;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2

 Purpose: Display/suppress/print (from A-Position only) stored weather

data on the FSP or EDST.

 Required fields: 01 and 13

 Optional field: 13

 Shown in parentheses, ( ), in slide above

Continued on next page

55053-LP06 / V.1.02 57
INFORMATION REQUEST COMMANDS (Continued)

Weather
Request (WR)
(Cont'd)
ERAM EDSM SRS
210.04 V1B1, par.
3.2.4.5.2.3.15.8;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2
TI 6110.101,
Section 11

 Entry from A-Position

 Must use Field 13

 Maximum of three adapted stations

 Data printed on the FSP

 Entry from RA-Position keyboard

 Fields 01 and 13 are entered:

 Requested weather sequence is displayed on the RA Weather

Station Report View

 Maximum of three adapted stations

 Automatically expands and contracts vertically when entry is

added or deleted

 Number of lines available is 3 to 21+

Continued on next page

55053-LP06 / V.1.02 58
INFORMATION REQUEST COMMANDS (Continued)

Weather
Request (WR)
(Cont’d)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2
TI 6110.101,
Section 11

 Removal from the RA Weather Station Report View

 Via EDST:

 Select desired weather sequence for removal.

 Select delete pop up.

 Via keyboard:

 Enter LOCID of the station already in the list.

55053-LP06 / V.1.02 59
INFORMATION REQUEST COMMANDS (Continued)

Strip Request
(SR)
ERAM EDSM SRS
210.04 V1B1,
par. 3.2.9.2.5;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2

NOTE: BNAT signifies Nashville Tower.

 Purpose: Request printing of desired flight progress strip(s) at:

 Your sector

 Another sector within your facility

 Another facility

 Required fields: 01, 02, 13, and 16

 Time/fix parameters:

 If the departure time is:

 NOT within the Departure Strip Printing Interval (DSPI), use the
departure point

 Within the DSPI, use the current stored fix

 For active flights, use a current strip number or an unexpired fix on

the converted route.

55053-LP06 / V.1.02 60
INFORMATION REQUEST COMMANDS (Continued)

Flight Plan
Readout (FR)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2;
TI 6110.101,
Section 1.2.6.3

 Purpose: Display entire flight plan on the A- or RA-Position Response

Area or FSP.

 Required fields: 01 and 02

 Optional fields

 16

 Shown in parentheses, ( ), in the slide above

 Can only be the letter P

 42

 ICAO data

 Displayed in the A or RA Response Area unless optional Field 16 is

entered. In this case, the flight plan readout is printed on an associated
FSP.

55053-LP06 / V.1.02 61
INFORMATION REQUEST COMMANDS (Continued)

Review QUESTION: What command type is entered to obtain a flight plan

readout?
QUESTION: What does P entered in Field 16 of an FR command
signify?

55053-LP06 / V.1.02 62
MISCELLANEOUS COMMANDS

Uses
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.2, C.3

NOTE: GI and RF are the only miscellaneous commands taught in this

lesson.

 Used to:

 Enter data that is not flight plan related

 Transmit information of a general nature

Continued on next page

55053-LP06 / V.1.02 63
MISCELLANEOUS COMMANDS (Continued)

General
Information
(GI)
ERAM EDSM SRS
210.04 V1B1,
pars, 3.2.9.2.6 and
3.2.9.2.7.1;
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2

 Sends plain language commands to address(es) specified

 Required fields: 01, 16, and 11

 Optional field: 16

 Shown in parentheses, ( ), in the slide above

 Maximum of 48 destinations

Continued on next page

55053-LP06 / V.1.02 64
MISCELLANEOUS COMMANDS (Continued)

General
Information
(GI) (Cont’d)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Sections C.2, C.3

NOTE: There are many other routings not taught in this lesson.

 These examples are the most common commands.

 Field 11, when used in a GI command, must contain a clear weather

symbol (O).

Continued on next page

55053-LP06 / V.1.02 65
MISCELLANEOUS COMMANDS (Continued)

General
Information
(GI) (Cont’d)
TI 6110.101,
Section 9

 When a new GI arrives, the GI button will turn yellow.

 Click the button to open the GI View.

 Acknowledge the message.

 Three possible pop-up menu choices are provided: Forward, Delete,

and Print.

Review QUESTION: How would you expect to receive a GI message from an

adjacent sector?

55053-LP06 / V.1.02 66
MISCELLANEOUS COMMANDS (Continued)

Request Flight
Plan Transfer
(RF)
ERAM EDSM SRS
210.04 V1B2,
Appendix C,
Section C.2; ERAM
IFPA SRS 210.15,
par. 3.2.4.2.1.8

 The RF command is used to transfer flight data to a neighbor facility

(ARTS/STARS, neighboring centers, CAATS, ATOP, etc.).
 The forced flight plan does not appear on the facility's situation display or
in views; but the plan data is entered in their computer.

 Type RF, space, CID, space, facility ID (e.g., ZSE, ZMP, PPP, ABQ).

55053-LP06 / V.1.02 67
CONCLUSION

Summary
 Computer command entry

 Error checking

 Flight data command format

 Information request command format

 Information views on the RA system

Practice  Practice Exercise 2: Composing Field Amendments is located in 55053-

Exercise 2 HO6.

 You will complete this exercise in the lab.

Continued on next page

55053-LP06 / V.1.02 68
CONCLUSION (Continued)

Practice  Practice Exercise 3: Command Composition and Entry is located in

Exercise 3 55053-HO6.

 You will complete this exercise in the lab.

Practice  Practice Exercise 4: Entering Miscellaneous and Information Request

Exercise 4 Commands is located in 55053-HO6.

 You will complete this exercise in the lab.

End-of-
 Your instructor will now administer the End-of-Lesson Test.
Lesson Test

55053-LP06 / V.1.02 69
APPENDIX A: ROUTE AMENDMENT CORRECTION

Oral Exercise DATA RESULTS NEW FIELD 10 DATA

ENTRY

2.5

3..9

5.J81.PQR..9

5.V17..7

5/D1+00

9/1430

9*/1530

FXX

8..KFBO

55053-LP06 / V.1.02 70