Amss Ops Pli PDF

Document No.
AAI/CATC/CNS-11
Edition: FEBRUARY 2017
Ukkxj foekuu Áf'k{k.k dkyst
bykgkckn, Òkjr
Civil Aviation Training College
Allahabad, India
Training Quality Policy
“To develop the

human resources for
the aviation industry,
ensuring conformity of
the processes, by
adapting the best
practices within
industry and building
higher skills and
standards in
training.”
PREFACE
The AMSS Operations (ECIL) PLI Courseware is developed at Civil Aviation Training
College, Allahabad, India with the purpose to equip the CNS Maintenance Personnel with the
conceptual knowledge on AFTN, AFTN Message Format, Supervision of traffic and channel,
Preparation of ATS & NOTAM messages, AFTN routing & retention of record and practical
skill on ECIL AMSS, including ECIL AMSS configuration, Frontend application, Supervisor
control functions & chart flow of message in AMSS and complete flight plan which is being
used in Airports Authority of India (AAI).
CNS directorate is committed to strive for EXCELLENCE. In line with this, efforts are being
put in to improve the quality of training and courseware.
The CATC team on its part has analyzed and considered to bring in improvement in
presentation of Handout/courseware. For this following steps have been taken.
i) To print the handout in two colors to break the monotone in study.
ii) To introduce summary after every chapter for easy recapitulation and for lasting
impression.
iii) The binding of the handout/courseware is also being improved.
I am sure the trainees will find this handout /courseware with a real difference.
To improve it further, suggestion and comments may be forwarded to the undersigned so that
we can continue to march towards excellence.
CHIEF INSTRUCTOR (CNS),

Civil Aviation Training College,
Airports Authority of India,
P.O. - Bamrauli,
Allahabad – 211 012, INDIA.
We are Committed to Achieve Excellence

Table of Content
Chapter Chapter Name Page

No. No.
1 Introduction 1
2 Aeronautical Fixed Telecommunication Network 4
3 AFTN Message Format 14
4 Supervision of Traffic & Channel 26
5 ATS Messages 36
6 NOTAM & MET Messages 48
7 AFTN Routing & Retention of Record 53
8 ECIL AMSS Configuration – Basic Concept 59
9 ECIL AMSS Frontend Application 72
10 Supervisor – AMSS Control Function 76
11 Introduction to AMHS/ATN 80
12 Practical Exercises 88
Chapter – 01 Introduction
CHAPTER – 01
INTRODUCTION

1.0. Overview

The process of getting an aircraft safely and efficiently to its destination depends largely on an
efficient communiction system besides navigation and surveillance systems. The
communication system must be able to provide an accurate and speedy exchange of
Aeronautical Information between stations to enable them to control the air space and
movement of air traffic to ensure highest standards of safety and quality in air traffic services.

In earlier days of Civil Aviation, the aircrafts were slow moving and hence
communication links by means of wireless telegraphy circuits and manual tele‐typewriter
circuits, generally known as Aeronautical Fixed Circuit were able to provide Aeronautical Fixed
Service (AFS) between two fixed points.

With the advent of high speed aircrafts, increasing number of flight in the airspace
across the continent, it was the need of that time to form a Global network of aeronautical
fixed circuits for the exchange of messages and/or digital data between aeronautical fixed
stations. The concept of Aeronautical Fixed Telecommunication Network (AFTN) was introduced
(refer Annex‐10, Vol.II) which became the media of communication of AFTN messages as per
ICAO standards.

India plays a key role in the international AFTN, bridging the gap between the eastern
and western parts of the world. Messages originating in the western countries are routed
through India to the eastern countries and vice‐versa.

In order to meet the growing demand for air traffic across the air space, India was
needed to upgrade and update the communication facilities like AFTN. The Automatic Message
Switching System (AMSS) was introduced in India in the year 1986‐87 in two major stations
Mumbai and Delhi. As on date, 18 major stations are having ECIL AMSS and other non‐AMSS
stations are connected with AMSS station over dialup circuit or working as remote client of
AMSS, known as RWS.

1.1. Automatic Message Switching System (AMSS)

The AMSS is a computer based system, centered on the AFTN for exchange of Aeronautical
messages by means of auto switching for distribution of messages to its destination(s), which
works on store and forward principle.

Civil Aviation Training College, Allahabad, India Page 1

AMSS (Automatic Messages Switching System) has four major areas :

- System
- Switching
- Messages
- Automation

a) System : AMSS is a dual architecture computer based system consisting of few servers
and workstations which are linked with each other over a local area network as well as with
other equipments/ devices for data communication.

b) Messages : AMSS is mainly for exchange of AFTN messages , but at the same time AMSS
can handle some Non‐AFTN messages like AMS messages ( formally known as HFRT/Radio
messages).

c) Switching : AMSS receives the messages from terminals directly connected to it and
terminals connected via other switches, and after analysis, it stores the messages and
automatically routes the messages to its destination(s). During the above process it uses
switching system, which allows on demand basis the connection of any combination of source
and sink stations. AFTN switching system can be classified into 3(three) major categories –

Line swithing
Message switching
Packet switching

d) Automation : So far automation is concerned for any system, it could be achieved by
means of mechanical devices like relay etc and/or application software designed as per
requirement. In ECIL AMSS, maximum features of automation like message switching,
analyzing, storing, periodical statistics etc are taken care by AMSS software and few by means
of mechanical system.

1.2. AMSS Operation Handout

This handout is designed to provide all the essential information one will need to get the most
from AMSS, while at the same time inviting one to explore the even greater depths and wider
coverage of material in the reference books/manuals.


1.2.1. Users of this Handout

It is designed to meet the needs of a wide range of AMSS users –

Beginners : Even if AMSS is new to you, this will get you up and running both AMSS Workstation
and Servers.

Intermediate Users : Chances are, you already know how to perform routine operation with
AMSS. This handout will facilitate you to improve further.

Advanced Users : If you have worked extensively with AMSS, you will appreciate this handout as
a reference and as a guide to further work with AMSS Operation.

1.2.2. Organization of this Handout

This Handout has 12 Chapters, which is classified in four parts.

PART‐1 : Chapters 2 to 7 covers AFTN, AFTN Message Format, AFTN Routing, Retention of AFTN
Records , Service Messages, ATS Message Format and in brief the concept on NOTAM and MET
messages in the light of ICAO Annex‐10, Volume‐II.

PART‐2 : Chapter 8 covers the ECIL AMSS Hardware and Software Configuration, Frontend and
Backend Datafiles as well as areas of automation implemented in AFTN message format.
Chapters 9 and 10 covers different functions of Frontend Application like booking, supervisor
and supervisory function in details.

PART‐3 : Chapter 11 covers the basic concepts on AMHS/ATN

PART‐4 : The Chapter 12 gives guidelines on practical exercises.


Chapter – 02 AFTN
CHAPTER – 02
Aeronautical Fixed Telecommunication Network (AFTN)

2.0. Overview

The objective of International Telecommunication Service is to ensure the telecommunication
and radio aids to air navigation necessary for the safety, regularity and efficiency of
international air navigation.

The Procedures for the International Aeronautical Telecommunication Service are documented
by ICAO in Annex‐10 (Volume‐II) for worldwide use. It is also recognized that supplementary
procedures may be required in certain cases in order to meet particular requirement of the
ICAO regions. Such supplementary procedures must not be contained in, nor conflict with, any
worldwide procedure of ICAO.

The International Aeronautical Telecommunication Service is divided into four parts : (1)
Aeronautical Fixed Service (AFS), (2) Aeronautical Mobile Service (AMS), (3) Radio Navigation
service and (4) Aeronautical broadcasting service.

2.1. Aeronautical Fixed Service (AFS)

It is a telecom service between specified fixed points provided primarily for the safety of air
navigation and for the regular, efficient and economical operation of air services.

The AFS has the following systems and applications that are used for ground‐to‐ground (i.e.,
point to point and /or point to multi‐points) communication in the aeronautical
telecommunication service.

o ATS direct speech circuits and network
o Meteorological operation circuits, networks & broadcast system
o Aeronautical Fixed Telecommunication Network (AFTN)
o Common ICAO data interchange network (CIDIN)
o ATS message handling services (ATSMHS)
o Inter‐centre communication (ICC)

2.2. Aeronautical Fixed Telecommunication Network (AFTN)

It is a world wide system of aeronautical fixed circuits provided, as a part of the AFS, for the
exchange of messages and/or digital data between Aeronautical fixed stations having the same

Chapter – 02 AFTN
or compatible communication characteristics. A station forming part of the AFTN and operating
as such under the authority of control of a state is known as AFTN Station.

2.2.1. Acceptance of Messages

The responsibility for determining the acceptability of a message shall rest with the station
where the message is filed for transmission. Once a message is deemed acceptable, it shall be
transmitted. The station(s) shall be responsible for delivery of messages to the addressee(s)
located within the boundaries of the aerodrome(s) served by that station and beyond those
boundaries only to such addressee(s) as may be agreed by special arrangement with the
administration concerned. (Ref : Annex‐10, Vol‐II, 3.3)

2.2.2. Categories of Messages

Subject to the provision of Annex‐10, Vol‐II, 3.3, the following categories of messages shall be
handled by the AFTN :

a) Distress messages b) Urgency messages c) Flight Safety Messages
d) Meteorological Messages e) Flight Regularity Messages
f) Aeronautical Information Service Messages
g) Aeronautical Administrative services messages h) Service messages.

2.2.2.1. Priority of Messages

Depending on the category of messages/type of messages, each message carry a priority
indicator (viz SS, DD, FF, GG, KK) to indicate the priority classification for transmission/handling
over AFTN.

‘SS’ is the top most priority, then ‘DD’ & ‘FF’, and ‘GG’ / ‘KK’ are the lowest priority of messages.

2.2.2.2. DISTRESS MESSAGES (Priority Indicator SS)

This message category shall comprise those messages sent by mobile stations reporting
grave and imminent danger and all other messages relating to the immediate assistance
required by the mobile station in distress threaten them.

2.2.2.3. URGENCY MESSAGES : ( Priority indicator DD )
This category of messages shall comprise messages concerning the safety of ship, aircraft,
or other vehicles, or of some person on board or within sight.


Chapter – 02 AFTN
2.2.2.4. FLIGHT SAFETY MESSAGES. (Priority indicator FF)
This category of messages shall comprise the following:
• Movement and control messages as defined in PANS‐ATM (DOC4444), Part VIII
• Messages originated by aircraft operating agency of immediate concern to an aircraft in
flight or about to depart.
• Meteorological messages restricted to information, special air‐reports, AIRMET
messages, volcanic ash and tropical cyclone advisory information and amended
forecasts.

2.2.2.5. METEOROLOGICAL MESSAGES (priority indicator GG)
This category of messages shall comprise of:
• Messages concerning forecast e.g. terminal aerodrome forecasts (TAFs), area and route
forecasts.
• Messages concerning observations and reports e.g. METAR, SPECI.

2.2.2.6. FLIGHT REGULARITY MESSAGES (Priority indicator‐GG)
This category of messages shall comprise of:
• Aircraft load messages.
• Messages concerning change in aircraft operating schedule.
• Messages concerning aircraft servicing.
• Messages concerning changes in collective requirement of passengers, crew and cargo
covered by deviation from normal operating schedule.
• Messages concerning non‐routine landings.
• Parts and material urgently required for the operation of aircraft.
• Pre flight arrangement of air‐navigation service and operational servicing for non‐
schedule aircraft operations, e.g. over flight clearance requests.
• Originated by aircraft operating agency‐reporting time of arrival and departure from
aerodrome.

2.2.2.7. AERONAUTICAL ADMINISTRATIVE MESSAGES
This category of messages shall comprise the following:
• Operation and maintenance of facilities essential for safety or regularity of aircraft
operation.
• Essential to efficient functioning of aeronautical telecommunication service.
• Exchanged between government civil aviation authorities relating to aircraft operation

2.2.2.8. AERONAUTICAL INFORMATION SERVICE messages: (Priority indicator GG)
This category of messages are concerning NOTAM and SNOWTAM.


Chapter – 02 AFTN
2.2.2.9. SERVICE MESSAGES: (Priority indicator as appropriate)
Originated by aeronautical fixed station to obtain information or verification concerning other
messages which appear to have been transmitted incorrectly by the aeronautical fixed service,
confirming the channel sequence numbers etc.
Service message shall be prepared in the format, addressed to aeronautical fixed station identified
only by a location indicator, immediately followed by the ICAO 3 letter designator YFY, followed by
an appropriate 8th letter.
When service messages refer to messages previously transmitted, the priority indicator
assigned should be that used for message(s) to which they refer.
A service message, other than one acknowledging receipt of SS messages, shall be further
identified by the use of abbreviation SVC as the first item in the text.
2.3. ADDRESSEE INDICATOR of AFTN Messages
Each AFTN message has two address information :
• Who has originated the message (Source)
• To whom it is addressed or to whom it will be distributed (Sink)
In order to maintain uniformity, pattern and ease for routing of messages, an 8(eight)‐letter
code group, known as addressee indicator, are formulated in accordance with the rules
prescribed by ICAO to define the Origin Indicators (OIs) and Distribution Indicators (DIs).
Addressee Indicator has two parts: first 4 letter code groups is assigned to a location of an
aeronautical fixed station and next 4 letters code group to identify the addressee (Organisation
/unit/ person addressed) of that station.
2.3.1 LOCATION INDICATOR (L.I.)
Four letter location indicator formulated and assigned to a geographical location where there is
situated a station forming a part of aeronautical fixed service.
ICAO DOC7910 contains a list of four‐letter code group location indicator for use in aviation only as
a location of an aeronautical fixed station in address, originator text etc
Example : VABB for Mumbai , VEAB for Allahabad

Chapter – 02 AFTN
2.3.1.1. FORMATION OF LOCATION INDICATOR

The world is divided into 22 non‐over‐lapping AFS routing areas, each of which is assigned a
separate identifying letter from A to Z excluding letters I, J, Q and X.

The boundaries of these areas need not necessarily coincide with the boundaries of any state,
territory or FIR but are decided solely from a consideration of the requirements of the AFS, so
as to assist message traffic routing processes to the maximum possible extent

a) Assignment of the first letter of a location indicator:

The first letter of the location indicator shall be the letter assigned to the AFS routing area
within which the location is situated except that where the location is served only by a single
communication centre situated in another AFS routing area, the first letter shall be that
assigned to the area in which that communication centre is situated.
(NOTE: An AFS Routing area can consist of a single state).

Example : 1st letter of L.I. of Delhi, Kolkata, Nagpur etc, are ‘V’

b) Assignment of the second letter of a location indicator:

Each separate state or territory is assigned a separate identifying letter to permit differentiation
between that state or territory and other states or territories in the same AFS routing areas.

Example : Bangkok and Kathmandu both comes under the same AFS routing area ‘V’, they have
been allotted separate letter ‘T’ and ‘N’ respectively to differtiate the states.

Separate identifying letters are also assigned to part of a state (or territory) where a separate
state or territory is itself an AFS routing area, by doing so AFTN routing uncertainties (if any) can
be removed or alleviated.

Unallocated letters within each AFS routing area may be assigned as additional letters, by ICAO,
at the request of a state having jurisdiction at location(s) within such area, in instances where
additional assignment will facilitate the processes of message routing.

Example : Western, Southern and Eastern part of India (AFSRA – V, 2nd letter I) having ‘A’, ‘O’ &
‘E’ as separate additional identifying letter respectively instead of ‘I’.

Delhi : VI Mumbai : VA Chennai : VO Kolkata : VE

Hence, the second letter of the location indicator shall be letter assigned to the state or territory
(or portion there of) within which the location is situated, except that where the location is served

Chapter – 02 AFTN
only by a single communication centre situated in another state or territory in which that
communication centre is situated.

c) Assignment of the third and fourth letter of a location indicator:

The state concerned shall assign the 3rd and 4th letters, as desired in such a way that the 4‐letter
code group location indicator is unique.

Example : VAAU : L.I. of Aurangabad (AU), Western part (A) of India (V)

Note :

Where the location is connected to a com centre, the 3rd letter of the L.I. should be so
assigned as to assists in the process of routing to that com centre.
‘NNN’ should not be used as 2nd, 3rd & 4th letters of L.I.
In exceptional cases, geographical location of the than those served by the AFS may be
given a L.I. of the discretion of the state having jurisdiction over the location concerned.
The letter ‘ZZ’ as 3rd an 4th letters of L.I. indicates a requirement of special distribution.

2.3.1.2. CHANGES IN THE ASSIGNMENT OF LOCATION INDICATORS

Location indicator once assigned should only be amended after paying due regard to the
worldwide repercussions of such changes upon all users of the communication services.

A location indicator should not be reassigned to another location for a period of at least six
months after cancellation of its previous assignment.

Changes in the assignment of location indicators should be promulgated by NOTAM or AIP as
far in advance of the effective date as practicable.

2.3.2. ICAO THREE LETTER DESIGNATOR

A location indicator alone does not constitute an addressee indicator or originator indicator in
AFTN messages. The aeronautical authority, service, unit or aircraft operating agency
originating the message, or to whom the message is addressed, should be identified by adding
to the L.I. the appropriate ICAO three letter designator and one letter either ‘X’ or any letter
assigned by state to form the 8‐letters addressee indicator.

Example : VABBYTYX

VABB – Location Indicator of MUMBAI
YTY – Three Letters Designator of Telecommunication AUTHORITY

Chapter – 02 AFTN
X – Filler Letter to form 8‐letters Addressee Indicator

Three‐letter designator is registered only for:

(a) Aircraft operating agency engaged in air transport operation, which in the opinion of the
state of jurisdiction have a need for an exclusive designator.
(b) Government authority and services, which use and/or provide air navigation,
communication and other facility and services for international civil aviation.
(c) Organisation other than government organisation, which provide service for
international civil aviation.

2.3.2.1. General Rules

The general rules governing the registration or change of three letter designators are as follow :

(a) Requests for the registration of (or change in) a three‐letter designator will only be
recognized by ICAO when received from the state having jurisdiction over the aircraft‐operating
agency, aeronautical authority or service concerned. Such requests should be addressed to the
Secretary General ICAO.
(b) The same designator will not be registered for more than one aircraft agency, aeronautical
authority or service.
(c) Not more than one three‐letter designator will be registered for each aircraft operating
agency, aeronautical authority or service.
(d) When a designator is no longer required, ICAO should be informed immediately. Any such
designator so released will not be reassigned until a period of at least 60 days elapsed.
(e) Each contracting state should review, at least annually, all of the designators and
associated information in DOC8585 for which it is responsible and advice ICAO of any changes
which should be made to this document in order to bring up to date.
(f) Reservation in three letter Designators :
9 Designators for government organisations, which provide civil aviation facilities and
services, are allocated only in the Y series.
9 Designators for government organisations, which provide air traffic services, are
allocated only in the Z series except ZXA to ZXZ.
9 The following three letter designators are reserved for national allocation by contracting
states to national authorities and services and will not be used for other assignment by ICAO.
The state may select and use any of these without referring the matter to ICAO.

YEY YGY YHY YIY YJY YKY YQY YRY YUY YVY & ZXA to ZXZ groups.

9 The following three letter designator when appearing in the address, origin parts of an
AFTN message must be complemented with further identification of the aircraft operating
agency, aeronautical authority or service concerned in the beginning of the text part of the
message.
o YXY ‐ Military service or organisation

Chapter – 02 AFTN
o YYY ‐ Aircraft operating agency or organisation that has not allocated
ICAO 3 letter designator on an exclusive basis.
o ZZZ ‐ Aircraft in flight.

(g) Restriction in the registration of three letter designator:
9 Combination of ZC or CZ to avoid conflict with the start of message signal.
9 Combination of NN to avoid conflict with the end of message signal.
9 PAN SOS UNO will not be used.
9 QTA, SVC shall not be used to avoid confusion with communication service codes.

(h) Limitations to avoid potential AFTN routing problems :
9 No further allocation of aircraft operating agency designator will be included in the Y
and Z series
9 No further allocation of any designator will be included in the Y series and ZAA to ZIZ,
ZOA TO ZUZ AND ZYA TO ZZY groups.

2.3.2.2. Three‐Letter /Four letter Designators commonly in use :

YAY GOVERNMENT CIVIL AVIATION AUTHORITY/ DGCA
YFY AERONAUTICAL FIXED STATION
YLY AIRCRAFT ACCIDENT AUTHORITY
YMY METEOROLOGICAL OFFICE
YNY INTERNATIONAL NOTAM OFFICE
YOY AERONAUTICAL INFORMATION SERVICE UNIT
YPY ROBEX COLLECTION CENTRE
YSY AERONAUTICAL STATION
YTY TELECOMMUNICATION AUTHORITY
YXA AIRPORTS AUTHORITY OF INDIA
ZAZ AERODROME CONTROL OFFICE
ZBZ REPETITIVE FLIGHT PLAN OFFICE
ZFZ CENTRE IN CHARGE OF A FLIGHT INFORMATION REGION
OR AN UPPER FLIGHT INFORMATION "WHETHER ACC OR
FIC" WHEN THE MESSAGE IS RELEVANT TO VIP FLIGHT.
ZGZ AIR TRAFFIC CONTROL
ZIZ FLIGHT INFORMATION CENTRE
ZPZ AIR TRAFFIC SERVICES REPORTING OFFICE
ZQZ CENTRE IN CHARGE OF FLIGHT INFORMATION REGION
ZRZ AREA CONTROL CENTRE
ZTZ AERODROME CONTROL TOWER
ZUZ UPPER AREA CONTROL CENTRE
ZYZ AERODROME SECURITY SERVICES
ZZZ AIRCRAFT IN FLIGHT


Chapter – 02 AFTN
In Airports Authority of India :

YXAC CHAIRMAN,AAI YXAO MEMBER (OPS)
YXAE MEMBER (ENGG.) YXAP MEMBER (PERS)
YXAF MEMBER (FINANCE) YXAK ED(CNS), AAI HQ
YXAN GM(COM), AAI HQ YXAM GM(N&S), AAI HQ
YUYU RED/ED –Region YVYX PRINCIPAL C.A.T.C.
YUYC RCC/GM(CNS) – Region YUYA RCA/GM(ATM)‐Region
YHYX APD – Station YTYX GM(CNS) – Station
YDYX GM(ATM) ‐ Station YFYX AMSS/AFS Supervisor


Chapter – 02 AFTN
Note :

..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..............................


Chapter – 03 AFTN Message Format
CHAPTER – 03
AFTN MESSAGE FORMAT

3.0. Overview

The two major International codes are used for the transmission of data between terminal and
computers are :
- International Telegraph Alphabet no.2 (ITA‐2) code, and
- International Alphabet no.5 (IA‐5) code.

In India, mostly ITA‐2 is used for exchange of data on AFTN. However, IA‐5 is also used for data
transmission from one system (computerized) to another system (computerized) for interfacing
high‐speed communication.

The AFTN messages are prepared using printable and non‐printable characters as well as some
of them are constant and some are variable. The AFTN message preparation input‐terminal has
undergone revolutionary changes from manual teletypewriter machine to electronic typewriter
machine, then present intelligent computer terminal. However, explanations of AFTN message
format remains constant in ICAO Document – Annex‐10, Volume‐II. For better understanding of
AFTN message types and its format with respect to present computerized environment, the
overall discussion on the subject has been simplified. However, it is recommended that ICAO
Annex‐10, Volume‐II, Chapter 4 should be referred for further details.

3.1. Message Format – ITA‐2

In general, all messages excluding AFTN channels test messages and channel check messages
(discussed in para 4.4.1. and para 4.4.3.) shall have the following components :

1) Heading 2) Address 3) Origin 4) Text 5) Ending

In relation to message format following symbols have been used in making reference to the
mechanical functions assigned to certain signals in the International Telegraph Alphabet No. 2
(ITA‐2) code.

< Carriage return
≡ Line feed
↓ Letter shift
↑ Figure shift
→ Space
<Enter> CR + LF (in computer)



3.1.1. Heading

The heading shall comprises:

a) Start‐of‐message signal, the characters ZCZC;
b) Transmission identification comprising :
1) Circuit identification;
2) Channel‐sequence number.
c) Additional service information (optional) comprising:
1) One SPACE;
2) Maximum ten characters
d) Spacing signal

3.1.1.1. Circuit Identification:

The circuit identification shall consist of three letters selected and assigned by the transmitting
station; the first letter identifying the transmitting terminal, the second letter the receiving end
of the circuit and the third letter to identify the channel; where there is only one channel
between the transmitting and receiving stations, channel letter A shall be assigned, where more
than one channels between the stations is provided the channels shall be identified as A, B, C
etc. in respective order.

Example : IAA for Delhi‐to‐Mumbai on 1st channel
IAX for Delhi‐to‐Mumbai on High Speed Circuit (in India)
IAD for Delhi‐to‐Mumbai on Dial‐up Circuit (in India)

3.1.1.2. Channel‐sequence Number:

It shall consists of three digit channel sequence numbers from 001 to 000 (representing 1000)
shall be assigned sequentially by telecommunication station to all messages transmitted
directly from one station to another. A separate series of these numbers shall be assigned for
each channel and a new series shall be started daily at 0000 hrs.

Recommendation:‐ The use of the 4 digit Channel sequence number, to preclude the
duplication of the same numbers during the 24 hours period, is permitted subject to agreement
between the authorities responsible for the operation of the circuit. In India, 4‐digit channel‐
sequence numbers are in use in AMSS.



3.1.1.3. Additional Service Information :

In India, it contains the time of transmission/distribution (TOT/TOD) of message ; comprises 6‐
digit date‐time in the format of ddhhmm (e.g. 240230) preceded by one space.

3.1.1.4. Spacing Signal:

In teletypewriter operation, the spacing signal consists of 5 SPACEs followed by 1 LETTER SHIFT.
This torn‐tape practice has no importance in today’s’ automatic system.

3.1.1.5 Example of Heading:

ZCZC→AOX↑0239→240230→→→→→↓

3.1.1.6. Uses and Reason of ZCZC:

In teletypewriter operation, the characters ZCZC have been chosen as a first part of heading of
message because Z and C are complementary to each other in the sense that one has a
MARKING impulse where the other has a SPACING impulse. Their transmission in combination
provides a convenient means by which the teletypewriter equipment at the next station can be
made to check both its own adjustments and the distortion in the incoming signal. If the ZCZC is
received without error, it is probable that the rest of the message will also be received
correctly.

3.1.2. Address

The address shall comprise:

o Alignment Function [<≡]
o Priority Indicator
o Addressee Indicator(s)
o Alignment Function [<≡]

3.1.2.1. Priority Indicator:

The priority indicator shall consist of the appropriate two‐letter group assigned by the
originator in accordance with the category of the message.


3.1.2.2. Addressee Indicator:

9 An addressee indicator (Ref. Ch‐2, Para‐ 2.3) shall immediately preceded by a space [→].

9 Where a message is to be addressed to an organization that has not been allocated an
ICAO 3‐letter designator, the location indicator of the destination shall be followed by the ICAO
3‐letter designator YYY (or the ICAO 3‐letter designator YXY in the case of military
service/organization) and 8th letter as filer letter X. The name of the addressee organization
shall then be included as the first item of the text of the message.
9 Where a message is to be addressed to an aircraft in flight and, therefore, requires
handling over the AFTN for part of its routing before retransmission over the Aeronautical
mobile Service, the location indicator of the Aeronautical station which is to relay the message
to aircraft shall be followed by the ICAO 3‐letter designator ZZZ and filler letter X. The
identification of the aircraft shall then be included as the first item of the TEXT of the message.

9 The complete addressee shall be restricted to three lines of page copy and a separate
addressee indicator shall be used for each addressee whether at the same or at different
locations. Application of the foregoing standard will result in message addressee indicators
being restricted to not more than seven in each line, accommodating maximum of twenty‐one
addressee indicators in each message.

9 Whenever the messages are offered in page‐copy form for transmission and contain
more addressee indicators that can be accommodated on a three line of page‐copy, such
messages shall be converted, before transmission, into two or more message, each of which
shall conform to the provisions given in the previous para. During such conversions, the
addressee indicator shall, in so for as practicable be positioned in the sequence which will
ensure that the minimum number of retransmission will be required at subsequent Comm.
centre.

9 The completion of each line of the addressee indicator group(s) in the address of a
message shall be immediately followed by the alignment function.

Examples:

VABBZRZX Area Control Centre (ZR) at Mumbai.

VABBYMYC Section (C) of Meteorological office at Mumbai.

VABBKLMN Department (N) of the aircraft operating agency KLM at Mumbai

VABBYYYX The aircraft operating agency whose name appears in the beginning
of the message TEXT whose office location is served by Mumbai.


VABBZZZX The aeronautical station Mumbai is required to relay this message
in the Aeronautical Mobile Service to the Aircraft whose identification
appears in the beginning of the message TEXT.

3.1.3. Origin

The Origin shall comprise:
o Filing Time
o Originator indicator
o Priority Alarm (if necessary)
o Alignment Function

3.1.3.1. Filing Time (THI)

It shall comprise the 6 digit date time group indicating the date and time for filing the message
for transmission. In teletypewriter operation the filling time shall be followed by one letter
shift (↓).

3.1.3.2. Originator indicator

9 The originator indicator shall comprise the location indicator of the place at which the
message is originated, followed immediately by ICAO 3‐letter designator identifying the
organization (aeronautical authority, service or aircraft operating agency, immediately by 8th
letter X unless 8th letter is specified by the organization which originated the message. In
teletypewriter operation, the originator indicator shall be immediately preceded by a space
(→).

9 Where a message is originated by an organization that has not been allocated in ICAO 3‐
letter designator, the location indicator of the place at which the message is originated shall be
followed immediately by the ICAO 3‐letter designator YYY or the ICAO 3‐letter designator YXY
(in the case of military service). The name of the originating organization or Military service
shall then be included in the first item in the text of the message.

9 Where a message originated by an aircraft in flight requires handling on the AFTN for
part of its routing before delivery, the originator indicator shall comprise of the Aeronautical
station responsible for transferring the message to the AFTN followed immediately by the ICAO
3‐letter designator ZZZ immediately followed by 8th letter X. The identification of the aircraft
shall then be included as the first item in the TEXT of the message.



Example : A message from aircraft AIC132 addressed to the area control centre at Mumbai,
the message being handled via aeronautical station Chennai. (Heading and Ending of the
message are not shown in this example of teletypewriter page copy form).

ADDRESS FF VABBZRZX

ORIGIN 150712 VOMMZZZX

TEXT AIC132 … (Rest of the text received from
aircraft)

3.1.3.3. Priority Alarm

The priority alarm shall be used only for distress messages, (Messages with SS priority). When
used, it shall consist of the following, in the order stated below.
Figure shift ( ↑ )
Five transmissions of signal No. 10 (Figure case)
Letter shift ( ↓ )

Use of priority alarm will actuate a bell (attention) signal at the receiving teletypewriter station,
other than at those fully automatic stations which may provide a similar alarm on receipt of
priority indicator SS, there by alerting supervisory personnel at relay centres and operators at
tributary stations, so that immediate attention may be given to the message. Priority alarm is
not required in AMSS.

The originator indicator group, or if a priority alarm has been used then that component part in
the origin of a message, shall be immediately followed by the alignment function (<≡)

3.1.4. Text

9 The following characters are allowed in text messages :

Letters : A B C D .........X Y Z
Figures: 1 2 3 4 5 6 7 8 9 0
Other signs : ‐ ? : ( ) . , ‘ = / +

Characters other than those listed above shall not be used in message unless absolutely
necessary for understanding of the text. When used, they shall be spelled out in full.



9 Roman numerals shall not be employed. If used, the same shall be preceded by the
word ROMAN.

9 Any uninterrupted sequence of ITA‐2 signal Nos. 26, 3 (ZCZC in letter case or figure case)

9 Any uninterrupted sequence of FOUR times ITA‐2 signal No.14 (NNNN in letter case or
figure case)

9 The text of the message shall be drafted in plain language or in abbreviations and codes.
The originator shall avoid the use of plain language when reduction in the length of the text by
appropriate abbreviations and codes is practicable.

9 Words and phrases, which are not essential, such as expressions of politeness, shall not
be used.

9 If the originator of the message wishes Alignment function (<≡) to be transmitted at
specific places in the text part of such message, the sequence shall be written on each of those
places.

9 When an originator reference is used, it shall appear at the beginning of the text, except
where the designator YXY, YYY, ZZZ comprises the second element of the addressee indicator
and/or originator indicator in a message. In such message the originators reference shall follow
the identification of the organization or the aircraft.

9 When the ICAO 3‐letter designator YXY, YYY, ZZZ comprises the second element of the
addressee indicator and it, therefore, becomes necessary to identify in the text the specific
addressees of the message, such identification group will precede the originators reference (if
used) and become the first item of the text.

9 When the ICAO 3‐letter designator YXY, YYY, ZZZ comprises the second element of the
originator indicator and it thus becomes necessary to identify in the text, the name of the
organization (or Military service or the aircraft) who originated the message, such identification
shall be inserted as the first item of the text of the message.

9 Where the ICAO 3‐letter designator YXY, YYY, ZZZ is/are used to refer to TWO or MORE
different organization (or Military Service), the sequence of further identification in the text
shall correspond. In such instances, each address identification shall be followed immediately
by an alignment function (<≡). The name of the (YXY, YYY, ZZZ) organization originating the
message shall then be preceded and followed by the word "FROM" and "STOP" followed by an
alignment function shall then be included in the TEXT at the end of these identifications to
precede the remainder of the text wording.


9 An alignment function (<≡) shall be transmitted at the end of each printed line of the
text except for the last.

9 When it is desired to CONFIRM a portion of the text of a message (excepting ATS
messages intended for the use in ATC computer) such confirmations shall be separated from
the last text group by the abbreviation CFM followed by the portion being confirmed.

9 When it has been discovered that an error has been made in the text of a message
(excepting ATS message intended for the use in ATC computer), the correction shall be
separated from the last text group by confirmation, if any, by an alignment function (<≡). This
shall be followed by the abbreviation COR and the correction.

9 In message containing ATS DATA intended for use in ATC computer, is the message field
identified as FIELD TYPE 5 and 18 TO 21, the confirmation and correction (as provided above) if
used, shall be performed prior to transmission of the END‐OF‐ATS‐DATA signal.

9 At the end of the text the following END‐OF‐TEXT signal shall be transmitted.

3.1.4.1. Long Text of Message

As per the provision of AFTN message, the text of messages entered by the AFTN origin station
shall not exceed 1800 characters in length. When a text is exceeding 1800 characters, the
messages have to be divided into two or more parts for transmission over AFTN.

Each message part should carry the same address and origin with the sequence of each part
indicated on the last line of text as follows :

( End of first message ) / / END PART 01 / /

(End of second message) / / END PART 02 / /

(End of last message) / / END PART XX/XX / /

The following example illustrates the application of the above procedure, for a three part
message. The message part sequence information is included in the Text character count.

First message :
(Address) GG VABBYNYX
(Origin) 011030 VIDPYNYX
(Text) text
/ / END PART 01 / /
(Ending) NNNN



Second message :
(Address ) GG VABBYNYX
(Text) text continued
/ / END PART 02 / /
(Ending ) NNNN

Third and last message :
(Address) GG VABBYNYX
(Text) remainder of the text
/ / END PART 03/03 / /
(Ending ) NNNN

3.1.5. Ending

The ending of AFTN message shall comprises :

9 The PAGE FEED SEQUENCE consisting of 7 LINE FEEDS (≡≡≡≡≡≡≡)

9 NOTE: This together with the 1 line feed of the preceding Alignment function will
provide sufficient separation between messages when appearing in page copy form.

9 The END‐OF‐MESSAGE‐SIGNAL, consisting of the letter N (letter case of signal No.14),
appearing FOUR TIMES in UNDIVIDED sequence.

This component, transmitted intact from the moment of the first transmission of the message
until ultimate delivery, is required so that the connections set up for cross‐office transmission, at
a semi automatic or fully automatic relay installation, can be cleared for following message
traffic and in addition on message traffic transmitted to torn‐tape relay station only.

9 The message‐separation signal, consisting of a letter shift (↓) transmitted 12 times in
uninterrupted sequence. It has importance for torn‐tape manual system only.

3.1.5.1. The AFTN messages entered by the AFTN origin station shall not exceed 2100
characters in length. The character count includes all printing and non‐printing characters in the
message from the start‐of‐message signal (ZCZC) to the end‐of‐message signal (NNNN).



3.2. Message Format – IA‐5

All messages, using IA‐5, shall have the following major components:

1) Heading 2) Text 3) Ending

3.2.1. Heading

It has three sub‐components :

a) Heading line b) Address c) Origin

3.2.1.1 Heading line

It shall comprises of
(1) Start‐of‐Heading Character (SOH), one character (0/1)
(2) Transmission identification, same as ITA‐2
(3) Additional Service Information (optional), same as ITA‐2

3.2.1.2. Address

Same as ITA‐2, refer para. 3.1.2.

3.2.1.3. Origin

Same as ITA‐2 (refer para 3.1.3). In addition, it has Start‐of‐text character STX), one character
(0/2) at the end of origin.

3.2.2. Text

Same as ITA‐2 (refer para 3.1.4) except end‐of‐text signal.

3.2.3. Ending

It comprises of – (1) Alignment function, one CR and one LF, (2) Page‐feed sequence, one
character (0/11), VT and (3) End‐of‐text character, one character (0/3), ETX.


3.2.3. Restriction
Message using IA‐5 shall not contain:
o Character 0/1 (SOH) other than the one in the heading
o Character 0/2 (STX) other than the one in the origin
o Character 0/3 (ETX) other than the one in the ending
o Any uninterrupted sequence of characters 5/10, 4/3, 5/10, 4/3 in this order (ZCZC)
o Any uninterrupted sequence of characters 2/11, 3 /10, 2/11, 3/10 in this order (+:+:)
o Any uninterrupted sequence of four times characters 4/14 (NNNN) and
o Any uninterrupted sequence of four times characters 2/12 (,,,,)
Example : IA‐5 Message
[SOH (0/1)] VEX0234 240400 GG
VEABYFYX
240400 VEBNYFYX [STX(0/2)]
SVC TEST MESSAGE .......
[CR+LF, PFS(0/11)]
[ETX(0/3)]


Note :
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
....................................................................................................


Chapter – 04 Supervision of Traffic & Channel
CHAPTER – 04
SUPERVISION OF TRAFFIC & CHANNEL

4.0. Overview

An AFTN station whose primary function is the relay or retransmission of AFTN traffic from (or
to) a number of other AFTN stations over the established AFTN circuits, is also responsible for :

a) Continuity of message traffic,
b) Re‐establishing of circuit(s) and action, in case of failure of communication,
c) Action on mutilated or improperly formatted messages, etc.

All of the above is achieved by means of sending suitable service (SVC) message(s) to the
concerned station and/or by transmitting channel test messages and channel check messages
etc. in the specified format.

4.1. Continuity of Message Traffic

The receiving station shall check the transmission identification of incoming transmission to
ensure the correct sequence of channel sequence number of all messages received over that
channel.

When the receiving station detects that one or more channel‐sequence numbers are missing, it
shall send a complete service (SVC) message to the previous station rejecting receipt of any
message that may have been transmitted with such missing number(s). The text of this service
message shall comprise the signal QTA, the procedure signal MIS followed by the missing
transmission identification and the end‐of‐text signal.

The following examples illustrate application of the above‐mentioned procedure. In example, 4‐
digits channel sequence numbers has been used, as in practice in India.

A) When one channel sequence number is missing

SVC→QTA→MIS→EAA↑0123↓<≡

B) When several channel sequence numbers are missing

SVC→QTA→MIS→EAA↑0126‐0129↓<≡

When the above provisions are applied, the station notified of the missing message condition
by the service message shall resume its responsibility for transmission of the message (or
messages) that it had previously transmitted with the transmission identification concerned,
and shall retransmit that message (or messages) with a new (correct in sequence) transmission
identification.

The receiving station shall synchronize such that the next expected channel‐sequence number
is the last received channel sequence number plus one.

When the receiving station detects that a message has a channel sequence number less than that
expected, it should advise the previous station using a service message with a text comprising

the abbreviation SVC
the procedure signal LR followed by transmission identification of the received message.
the procedure signal EXP followed by transmission identification expected.
the end‐of‐text signal

Example :

SVC→LR→AIA↑0123↓→EXP→AIA↑0135↓<≡

When the above provisions are applied, the station receiving the out of sequence message should
synchronize such that the next expected channel sequence number is the last received channel
sequence number plus one. The previous station should check its outgoing channel sequence
number and, if necessary, correct the sequence.

4.2. Misrouted Messages

A message is considered to have been misrouted when it contains no relaying instructions,
expressed or implied, on which the receiving station can take action.

When the receiving station detects that a message has been misrouted to it, it shall either.

1) Send a service message to the previous station rejecting receipt of the misrouted
message; or
2) Itself resumes responsibility for transmission of message to all the addressee indicators.

NOTE: The procedure of Para (1) is preferable at remote stations , having only one circuit with
main AMSS station and working as RWS or Dial‐up Station. The procedure in Para (2) may be
preferred at stations using AMSS .

When the provisions of Para (1) are applied, the text of the service message shall comprise the
abbreviation SVC, the signal QTA, the procedure signal MSR followed by the transmission
identification of the misrouted message and the end‐of‐text signal.


Example: SVC→QTA→MSR→AIA↑0129↓<≡
When, as a result of provisions contained in Para (1), a sending station is notified of the
misrouted message condition by service message, it shall resume responsibility for the message
and shall retransmit as necessary on the correct outgoing channel or channels.

4.3. Circuit Interruption

When a circuit becomes interrupted and alternative facilities exist, the last channel sequence
number sent and received shall be exchanged between the stations concerned. Such exchanges
shall take the form of complete service message with the text comprising the abbreviation SVC
the procedure signal LR and LS Followed by the transmission identification of the relevant
channel and the end‐of‐text signal.

Example: SVC→LR→AIA↑0132↓→LS→IAA↑0321↓<≡

Note : AMSS have the provision of exchanging LR/LS at every H+00 hours.

AAI CHQ Instruction : It is essential to exchange LR/LS of previous day at the time of watch‐
open and LR/LS of date at the time of watch‐closing to protect the loss of traffic. As a result of
such provision, the respective station shall be responsible to retransmit its own traffic, if any, to
ensure that all traffic has been received by the other station.

4.4. Failure of Communication

In case of failure of communication on any fixed service circuit, the station concerned shall
attempt to re‐establish circuit and communication as soon as possible.

If contact can not be reestablished within a reasonable period on the normal fixed service circuit,
an appropriate alternative circuit should be used. If possible, attempt should be made to establish
communication on any authorized fixed service circuit available.

If these attempts fail, use of any available air‐ground frequency shall be permitted only as
exceptional and temporary measure when no interference to aircraft in flight is ensured.

A station experiencing a circuit or equipment failure shall promptly notify other stations with
which it is in direct communication, if the failure will affect traffic routing by those stations.
Restoration to normal shall also be notified to the same stations.



4.4.1. Test Procedure:

In order to re‐establish communication and/or for the purpose of testing and repairing lines
test messages are transmitted over AFTN channels and consists of the following:

1) The start‐of‐message signal,
2) The procedure signal QJH,
3) The originator indicator,
4) Three page‐copy lines of sequence of characters RY in ITA‐2 or U(5/5) *(2/10) in IA‐5,
and
5) The end‐of‐message signal

Example :

ZCZC QJH VABBYFYX
RYRYRYRYRYRYRYRYRYRY...........................(contd. 1st line)
RYRYRYRYRYRYRYRYRYRY...........................(contd. 2nd line)
RYRYRYRYRYRYRYRYRYRY...........................(contd. 3rd line)
NNNN

4.4.2. Routing Diversion:

When diverted traffic will not be accepted automatically or where a predetermined diversion
routing has not been agreed, a temporary diversion routing shall be established by the
exchange of service messages.

The text of such service massages shall comprises:
9 the abbreviation SVC
9 the procedure signal QSP.
9 if required, the procedure signal RQ, NO or CNL to request, refuse or cancel a diversion
9 identification of routing areas, states, locations or station for which the diversion applies
9 the end‐of‐text signal

Example :

a) to request a diversion:

SVC→QSP→RQ→VT→VG↓<≡

b) to accept a diversion:

SVC→QSP→VT→VG↓<≡



c) to refuse a diversion:

SVC→QSP→NO→VT→VG↓<≡

d) to cancel a diversion:

SVC→QSP→CNL→VT→VG↓<≡

4.4.3. Channel Continuity Check:

In order to provide some measure of assurance that channel continuity is maintained, the
following periodic channel check transmission shall be sent on a circuit when it is unoccupied
and should be sent at H+00, H+20, H+40.

heading ZCZC ANA0020 240400
AF(<≡), procedure signal, AF(<≡) CH
end‐of‐message signal NNNN

If a periodic channel check transmission is not received within a tolerance agreed for that
channel and channel was unoccupied, a station shall send a service message to that from which
the transmission was expected.

The following example illustrates application of above procedure:

SVC→MIS→CH→[↑2240↓]→LR→IAA↑0761↓<≡

Note : When channel is unoccupied and periodic channel check transmission is not received
within a tolerance for that channel, the communication on that channel is uncertain. In such
case, the channel shall be put on test transmission and LR/LS should be communicated via
alternate circuit, if any.

4.5. Mutilated or Improperly Formatted Message

4.5.1. Mutilated Message – Case Study: 1

If, before retransmission is commenced, a relay station detects that a message has been
mutilated at some point ahead of the END OF MESSAGE SIGNAL, and it has reason to believe
that this mutilation had occurred before the message has been received by the previous
station, it shall send a service message to the originator as identified by the originator indicator
in the origin of the mutilated message requesting repetition of the incorrectly received
message.

Example: <≡GG→VABBYFYX<≡
↑140436↓→VECCYFYX<≡ SVC→QTA→RPT→↑140430↓→VABBZRZX↓<≡

NOTE: These circumstances of detection of a mutilation may only be possible at non‐automatic
relay station or on manual intervention.

9 When the above procedure is applied, the originator as identified by the originator
indicator in the origin of the mutilated message shall resume responsibility for the mutilated
message, and shall comply with the provisions described below.

9 Reprocess the message before transmitting the un‐mutilated version of the message to the
same addressee in the following manner.

Insert a new heading
Remove the ending of the message
Insert in lieu thereof the procedure signal DUPE, preceded by at least a letter shift and
followed by 1 carriage returns, 8 LINE FEEDS, END OF MESSAGE SIGNAL and, if necessary the
LETTER SHIFTS of the message separation signal and tape feed.


If, before retransmission is commenced, a relay station detects that one or more messages have
been mutilated at some point ahead of the END OF MESSAGE SIGNAL, and has reason to believe
that this mutilation had occurred during or subsequent to its transmission from the previous
station rejecting the mutilated transmission and requesting a repetition of the incorrectly received
message(s).

Example:

(i) In respect of a single mutilated message ‐

SVC→QTA→RPT→AIA↑0245↓<≡

(ii) In respect of a several mutilated message ‐

SVC→QTA→RPT→AIA↑0261‐0265↓<≡


NOTE: These circumstances of detection of a mutilation may only be possible at non‐automatic
relay station or on manual intervention.

9 The station receiving the service message shall reassume responsibility for the referenced
message.
9 Retransmit the un‐mutilated copy of the referenced message with a new (correct in
sequence) transmission identification.
9 If the station receiving the service message is not in possession of an un‐mutilated copy
of the original message it shall then send a service message to the originator of the message
requesting repetition of the incorrectly received message.


If, before retransmission is commenced, a relay station detects that a received message has a
recognizable but mutilated END OF MESSAGE SIGNAL, it shall, where necessary repair this
mutilated before retransmission.

NOTE: These circumstances of detection of a mutilation is normally taken care by semi‐automatic
or fully automatic station like AMSS.

If, after a message has been transmitted in TOTO, a station detects that the text or the origin of
the message was mutilated or incomplete; it shall transmit to all addressee concerned a service
message with the following text if an un‐mutilated copy of the message is available in the station.

SVC CORRECTION (the origin of the incorrect message) STOP
(Followed by the correct message text).


If, after transmission of the text material of a message, a relay station can detect that there is
no complete END OF MESSAGE SIGNAL but has no practicable means of discovering either the
irregularity has affected only the END OF MESSAGE SIGNAL or whether it may have also caused
the part of the original text to have been lost shall insert into the channel as mentioned below.

↓<≡CHECK≡TEXT≡NEW→ENDING→ADDED
Its own station identification (e.g. VABBYFYX)
Alignment Function (↓<≡)
Followed by normal ending

9 On page copy, this insertion will appear as follows
CHECK

TEXT
NEW ENDING ADDED VABBYFYX
(Followed by normal ending).

9 The staggered presentation on copy is prescribed to ensure that the attention of the
addressee is drawn immediately to the insertion.

NOTE: These circumstances of detection of mutilation may only be relevant to fully automatic
station and it is implemented in AMSS.


If, a relay station detects that a message was received with a completely mutilated address line,
it shall send a service message to the previous station rejecting the mutilated transmission as
shown below:

Example:

SVC→QTA→ADS→AIA↑0623↓→CORRUPT↓<≡

9 The station receiving such a message shall reassume responsibility for the referenced
message with a corrected address line, and new transmission identification.
If a relay station detects that a message was received with an invalid (i.e. length other than 8
letters) or UNKNOWN addressee indicator it shall relay the message to those valid addressees
for which it has relay responsibility using the stripped address (discussed later on) procedure.

In addition, (except the procedure of sending SVC message direct to the originator under the
same circumstances) the station shall send a service message to the previous station requesting
correction of the error.

Example :

i) for the invalid address indicator
SVC→ADS→AIA↑0723↓<≡
GG→VIDPYMYX→VILKYMYX→VIJPYMY<≡
CHECK→VIJPYMY↓<≡

ii) for the unknown address indicator
SVC→ADS→AIA↑0724↓<≡
FF→VIJOZTZX→VISRZTZX→VIOPZRZX<≡
UNKNOWN→VIOPZRZX↓<≡


9 A station receiving such a service message shall obtain a correct addressee indicator and
shall repeat the message to the addressee using the stripped address procedure.


When the first relay station detects that a message was received with a mutilated origin line or
without any origin it shall

o Stop processing the message, and
o Send a service message to the station from which the message was received.
Example :

SVC→QTA→OGN→AIA↑0825↓→CORRUPT↓<≡

When the first relay station detects that a message was received with an incorrect originator
indicator, it shall:
o Stop processing the message, and
o Send a service message to the station from which the message was received.

Example:

SVC→QTA→OGN→AIA↑0827↓→INCORRECT↓<≡

9 The station receiving the above service message shall resume responsibility for the
referenced message and shall retransmit the message with a correct originator indicator and if
applicable, a new transmission identification.


Note :
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................

Chapter – 05 ATS Messages
CHAPTER– 5
ATS MESSAGES
5.0 Overview
The Air Traffic Service (ATS) messages, in general, includes those messages concerning the
emergency situation / safety of an aircraft, e.g., alerting phase – aircraft not in contact, radio
communication failure with aircraft etc., and messages concerning the flight movement and
control. All such messages shall be exchanged between service users over the AFTN.
Note : The ATS message service of the ATS message handling service (ATSMHS) application
shall be used to exchange ATS message between users over the ATN internet as per the
provision in ICAO Doc.9705.
This chapter includes the Amendment No:- 1 to the Doc4444,effective from 15th
Nov’2012.
The ATS messages have been standardized with element of data grouped into FIELDs and field
contains single element or group of related elements. The standard ATS messages shall be
composed as per the sequence of fields of data explained in this chapter.
In computerized ATS system, ATS messages with error(s) are rejected by the system. Hence,
where the standard ATS messages are transmitted in areas where ATC computer are known to
be in use, the formats and data conventions shall be adhered to rigorously.
Though the provision of correction in ATS messages is there, but it may be taken into practice
that correction in ATS messages is not permitted.
5.1. Structuring and Punctuation in ATS Message
Symbols Signal Name Remarks

Field 3 shall always be
1. ( Start-of-ATS-Data signal preceded by this signal
All Fields except Field 3 shall

2. - Start-of-ATS-Field signal always preceded by this signal
Separation of elements within

3. / or Space the field
Last Field of ATS message

4. ) End-of-ATS-Data signal immediately followed by this
signal

5.2. ATS Message Category – Type – Designator – Fields
S.No. Category Type of Message Designator Field Type Numbers

3, 5, (7), 8, (9), 10, (13), (15),
1 Alerting Message ALR
(16), (18), (19), (20)
Emergency
Radio
2 Communication RCF 3, 7, (21)
Failure Message
Field Flight Plan 3, 7, 8, (9), 10, (13), (15), (16),
3 FPL
message (18)
4 Delay Message DLA 3, 7, 13, 16,18
Modification
5 CHG 3, 7, 13, 16, {22},18
Message
and associated update
Flight Plan
6 Cancellation CNL 3, 7, 13, 16,18
Filed Flight Plan
Message
Departure
7 DEP 3, 7, 13, 16,18
Message
8 Arrival Message ARR 3, 7, 13, 16, 17
Current Flight Plan 3, 7, 8, (9), 10, (13), (14), (15),
9 CPL
Message (16), (18)
10 Estimate Message EST 3, 7, 13, 14, 16
Co-ordination
11 CDN 3, 7, 13, 16, {22}
Message
Acceptance
12 ACP 3, 7, 13, 16
Co-ordination
Message
Logical
13 Acknowledgement LAM 3
Message
Request Flight
14 RQP 3, 7, 13, 16,18
Plan Message
Request Suppl
15 Flight Plan RQS 3, 7, 13, 16,18
Supplementary
Message
Supplementary
16 Flight Plan SPL 3, 7, 13, (16), (18), (19)
Message

( ) - This field begins a new line when the message is printed in page
{ } - This field is repeated as necessary
5.3. Field Type and Data
Field Type Data

1 Not currently used
3 Message type, number and reference data
5 Description of emergency
7 Aircraft Identification and SSR Mode and code
8 Flight Rules and Type of flight
9 Number and type of aircraft and wake turbulence Category
10 Equipment and capabilities
13 Departure aerodrome and Time
14 Estimate Data
15 Route
16 Destination aerodrome and total estimated elapsed

time, Destination alternate aerodrome(s)
17 Arrival aerodrome and time
18 Other information
19 Supplementary information
20 Alerting search and rescue information
21 Radio failure information
22 Amendment
Submission of the Flight Plan:-

Flight plan shall not be submitted more than 120 hours before the estimated off-block time of
a flight. Fpl message should be transmitted immediately after the filling of the flight plan .If a
flight plan is filed more than 24 hours in advance of the estimated off-block time of the flight
to which it refers the date of the flight departure shall be inserted in item 18 of the flight
plan.
5.4. Description of Fields
5.4.1. Field Type 3 (MESSAGE TYPE, NUMBER & REFERENCE DATA)
 A) Message type : Three letters.

 B) Message Number : Letter(s) identifying the sending ATS unit (maximum 4
letters). , Oblique Stroke (/)
Letter(s) identifying the receiving ATS Unit (Maximum 4 letters) followed by 3 decimal Numeric
giving the serial number of this message in the sequence of messages transmitted by this unit
to the indicated receiving ATS Unit.
 C) Reference Data : 1 to 4 letter(s) followed by OBLIQUE STROKE (/)
followed by 1 to 4 letter(s) followed by 3 decimal numeric, giving the message number
contained in element (b) of the operational message which began the sequence of messages of
which this message is a part.
Note : Element (A) is mandatory. Computers generate element (B) (C) when used for messages
exchanged between the computer systems of ATS units.
Examples : (FPL
(CHGA/B234A/B231
(CPLA/B002
5.4.2. Field Type 5 (DESCRIPTION OF EMERGENCY)
 Phase of Emergency : One of the following words INCERFA or

ALERFA or DETRESFA, OBLIQUE STROKE
 Originator of Message : 8 letters, OBLIQUE STROKE
 Nature of Emergency : Short plain language text.
Example : -ALERFA/VABFBZQZX/REPORT OVERDUE
5.4.3. Field Type 7 (AIRCRAFT IDENTIFICATION AND SSR MODE AND CODE)
 Aircraft Identification : Not more than 7 alphanumeric characters without hyphens or

symbol , OBLIQUE STROKE
 SSR Mode : 1 letter.
 SSR Code : 4 numeric.

This field may be terminated after element after aircraft identification
Example : -AIC102 or -AIC102/A3001
5.4.4. Field Type 8 (FLIGHT RULES AND TYPE OF FLIGHT)
 Flight Rules : 1 letter ( I V Y Z )
I If it is intended that the entire flight will be operated under the

IFR
V If it is intended that the entire flight will be operated under the
VFR
Y if the flight initially will be operated under the IFR ,followed by
one or more subsequent changes of flight rules *
Z if the flight initially will be operated under the VFR ,followed by
one or more subsequent changes of flight rules*
*Specify in the field No.15, the point or points at which a change of flight rules is planned.
 Type of Flight :1 letter ( S N G M X )
S -Scheduled Air Services

N -Non-Scheduled air transport operation
G -General Aviation
M -Military
X -if other than any of the defined categories above.
Example : -IN -IS
Specify status of a flight following the indicator STS in item 18, or when necessary to denote
other reasons for specific handling by ATS, indicate the reason following the indicator RMK in
Item 18.
5.4.5. Field Type 9 (NUMBER AND TYPE OF AIRCRAFT AND WAKE TURBULENCE CATEGORY)
 (a) Number of Aircraft ( if more than one ) : Maximum 2 numeric

 (b) Type of Aircraft : 2 to 4 characters or ZZZZ, then ‘/’
 (c) Wake Turbulence Category : 1 letter ( H M L )
H-Heavy : Take-off mass > 1,36,000Kgs
M-Medium: Take-off mass < 1,36,000Kg but > 7000kg
L-Light: Take-off mass < 7000Kgs.
When ZZZZ used in (b), the type of aircraft(s) to be shown in field 18.

Examples : -B707/H
-2FK27/M
-ZZZZ/L
5.4.6. Field Type 10 (EQUIPMENT AND CAPABILITIES)
a) Radio Communication, Navigation and Approach Aid Equipment and capabilities:

INSERT one letter as follows:
N if no COM/NAV /approach aid equipment for the route to be flown is carried
,or the equipment is unserviceable,
OR S if standard COM/NAV /approach aid equipment for the route to be flown is
Carried and serviceable,
AND/OR
INSERT one or more of the following letters to indicate the serviceable COM / NAV /
approach aid equipment and capabilities available
A GBAS landing system J7 CPDLC FANS1/A SATCOM(Iridium)

B LPV(APV with SBAS) K MLS
C LORAN C L ILS
D DME M1 ATC RTF SATCOM (INMARSAT)
E1 FMC WPR ACARS M2 ATC RTF (MTSAT)
E2 D-FIS ACARS M3 ATC RTF (Iridium)
E3 PDC ACARS O VOR
F ADF P1 – P9 Reserved for RCP
G GNSS
H HF RTF R PBN approved
I INERTIAL NAVIGATION T TACAN
J1 CPDLC ATN VDL Mode2 U UHF RTF
J2 CPDLC FANS 1/A HFDL V VHF RTF
J3 CPDLC FANS 1/A VDL Mode4 W RVSM approved
J4 CPDLC FANS 1/A VDL Mode2 X MNPS approved
J5 CPDLC FANS 1/A SATCOM Y VHF with 8.33 khz channel spacing
(INMARSAT) capability
J6 CPDLC FANS 1/A SATCOM (MTSAT) Z Other equipment carried or other
capabilities
Note 1. If the letter S is used,standard equipment is considered to be VHF RTF, VOR and ILS.
Note 2. If the letter G is used,the types of external GNSS augmentation ,if any ,are specified in
item 18 following the indicator NAV/ and separated by a space.
Note 4. Letter R:- Specify PBN levels in field no:- 18 ,indicator:- PBN/.
Note 5. If the letter Z is used , specify in Item 18 the other equipment carried or other
capabilities , preceded by COM/ ,NAV/ and/or DAT, as appropriate.
Note 6. Information on navigation capabilities is provided to ATC for clearance and routing
purpose.

then oblique stroke ‘/’
b) Surveillance equipment and capabilities:-
i) INSERT N if no surveillance equipment for the route to be flown is carried ,or the
equipment is unserviceable,
OR
INSERT one or more of the following descriptors ,to a maximum of 20 characters ,to
describe the serviceable surveillance equipment and/or capabilities on board:
ii) SSR Modes A , C and S
A Transponder- Mode A (4 digits) | Maximum of one entry
C Transponder- Mode A (4 digits) and Mode C |
S Letters used :- E,H,I,L,P,S.X |
iii) ADS–B Letters used :- B1,B2,U1,U2,V1,V2 (B1 or B2 and/or U1 or U2 and/or VI or V2)
iv) ADS-C Letters used:- D1,G1 (D1 and/or G1)
Alphanumeric characters not indicated above are reserved.
Additional surveillance application should be listed in item 18 following the indicator SUR/ .
Examples : -S/A
-SCH/CB1
-ADE3RV/HB2U2V2G1
5.4.7. Field Type 13 (DEPATURE AERODROME AND TIME)
 (a) Departure Aerodrome :Four letter Location Indicator or ZZZZ or AFIL

 (b) Time : 4 numeric.
This filed shall be terminated after element (a) in message types CPL, EST, CDN , ACP and RQP(if
the estimated off block time is not known)
In element (a) if ZZZZ or AFIL (Flight plan filed in Air) is used the name and location of the
departure aerodrome or ATS unit form which supplementary flight data can be obtained is to
be shown in field 18,preceded by DEP/ .
Examples : -VABB0030 (EOBT)

-AFIL1625 (actual or estimated time of departure from the first
point shown in the Route Field(Field Type 15)
5.4.8. Field Type 14 (ESTIMATE DATA)
 (a) Boundary Point : 2 to 5 characters.

 (b) Time at Boundary point : 4 numeric
 (c) Cleared level : letter F or A followed by 3 numeric or S or M
followed by 4 numeric.
 (d) Supplementary Crossing Data : as expressed in (c).

 (e) Crossing Condition : 1 letter ( A or B )
This field may be terminated after ( c )
5.4.9. Field Type 15 (ROUTE)

a) Cruising Speed or Mach Number(Maximum 5 characters) : letter K or N or M
K-Kilometres per hours followed by 4 figures(e.g. K0830)
N-Knots followed by 4 figures (e.g. N0485)
M-True Mach Number followed by 3 figures (e.g. M082)
b) Requested Cruising Level : letter F or A followed by 3 numeric or letter S or M followed by 4

numeric or VFR., followed by SPACE
c) Route (including changes of speed, level and/or flight rules)
(Following 5 sub-items separated by a space)
1. ATS route (2 to 7 characters)
2.Significant points (2 to 11 chracters)
3.Change of speed or level (maximum 21 characters)
4. Change of flight rules(maximum 3 characters)
5. Cruise climb(maximum 28 characters)
Examples : -K0410S1500 A4 CCV 411
-N0420F310 R10 UB19 CGC UA25 DIN/N0420F330 UR14
IBY UR1 MID
5.4.10. Field Type 16 (DESTINATION AND TOTAL EET, DESTINATION ALTN AERODROMEs)
 Destination Aerodrome : Four letter Location Indicator or ZZZZ

 Total Estimated Elapsed Time : 4 numeric
 SPACE , if next element present
 Alternate Aerodrome(s) : Four letter location indicator or ZZZZ
If ZZZZ is used ,SPECIFY destination/alternate aerodrome name and location in the field type 18
,preceded by DEST/ and ALTN/ respectively.
Examples : -VABB0630
-VABB0730 VAAH
-VABB0730 VAAH VANP
5.4.11 Field Type 17 ( ARRIVAL AERODROME AND TIME)
a) Arrival Aerodrome :- 4 LETTERS ,being the ICAO four-letter location indicator to the
arrival aerodrome as specified in Doc 7910 or
ZZZZ if no ICAO location indicator has been allocated.
b) Time of Arrival :- 4 NUMERICS, giving the actual time of arrival.
SPACE
c) Arrival Aerodrome :- Name of arrival aerodrome ,if ZZZZ IS INSERTED IN a).

5.4.12. Field Type 18 (OTHER INFORMATION)
NOTE:- use of indicators not included under this items may result in data being rejected ,
processed incorrectly or lost.
Hyphens or oblique strokes should only be used as prescribed.
INSERT 0 (zero) if no other information,
OR other necessary information. Appropriate Indicators in the following order :
 STS/ reason for special handling by ATS,e.g. search
and rescue mission
 PBN/ indication of RNAV and/or RNP capabilities.
 NAV/ significant data related to navigation equipment
 COM/ communication applications or capabilities not
specified in Item 10a
 DAT/ data applications or capabilities not specified in
Item 10a
 SUR/ surveillance applications or capabilities not
specified in Item 10b
 DEP/ name and location of departure aerodrome
 DEST/ name and location of destination aerodrome
 DOF/ date of flight departure(in YYMMDD format)
 REG/ nationality or common mark and registration mark
of the aircraft
 EET/ estimated elapse time
 SEL/ SELCAL Code
 TYP/ type of aircraft
 CODE/aircraft address (e.g. F00001)
 DLE/ en-route delay
 OPR/ ICAO designator or name of the aircraft operating
agency
 ORGN/originator
 PER/ aircraft performance data
 ALTN/ name of destination alternate aerodrome
 RALT/ ICAO four letter indicator(s) for en-route alternate(s)
 TALT/ ICAO four letter indicator(s) for take-off alternate(s)
 RIF/ route details to the revised destination aerodrome
 RMK/ any other plain language remarks
Examples : -0
-PBN/A1B1D1O1S1 DOF/121224 REG/VTINV EET/VGFR0006

VEGF0030 VGFR0035 VEGF0036 SEL/DQBJ RMK/RT DESIGNATOR
I FLY

5.5. Example of ATS Type of Messages
 ALERTING (ALR)
(ALR-ALERFA/VECCZQZX/REPORT OVERDUE
-BAW664/A5045-IS
-B747/H-S/N
-VECCO605
-N0495F320 G450
-VABB0320 OPKC
-REG/GABCD SEL/ABEK RMK/NO POSITION REPORT SINCE DEP
-E/0530 P/135 R/VE S/MJ/L D/8 150 C YELLOW A/SILVER C/SMITH
-BAW VECCZRZX 0610 126.7 JS 0610 POLOT REPORTED OVER NDB ATS
UNITS CALCUTTA FIR ALERTED NIL)
 RADIO COMMUNICATION FAILURE (RCF)
(RCF-IAC175
-0532 121.3 ALPHA 0532 TRANSMITTING ONLY 126.7
LAST POSITION CONFIRMED BY RADAR)
_________________________________________________________________
 FILED FLIGHT PLAN (FPL)
(FPL-IGO358-IS
-A320/M-SDFGE1HIRWY/S
-VECC0705
-N0384F230 B593
-VEAT0043 VEGT
-PBN/A1B1D1O1S1 DOF/130211 REG/VTINV EET/VGFR0006 VEGF0030 VGFR0035
VEGF0036 SEL/DQBJ RMK/RT DESIGNATOR I FLY)
 MODIFICATION (CHG)
(CHG-AIC103/A4500-VABB0430-VECC-DOF/130215-14/NIPAD/1730F290F270A)
 CANCELLATION (CNL)
(CNL-VTEAH-VIDP0230-VILK-DOF/130221)
 DELAY (DLA)

(DLA-ALK342-VOMM1940-VCBI-0) {1940 IS REVISED EOBT CHENNAI}

(DLA-ALK342-VOMM1940-VCBI-DOF/130221)
 DEPARTURE (DEP)
(DEP-AFR182-VIDP0135-VTBD-0)
(DEP-AFR182-VIDP0135-VTBD-DOF/130221)
 ARRIVAL (ARR)
(ARR-AIC765-VECC1300-VOMM1450)
(ARR-VTDNT-VECC0130-ZZZZ0532 GRASS MORE)
CURRENT FLIGHT PLAN (CPL)
(CPL-KLM182/A5045-IS
-A320/H-S/C
-VABB-NIPAD/0610F290F330B
-N0450F330 G450
-0)
 ESTIMATE (EST)
(EST-RNA212/A5150-VIDP-KUSMI/0450F330F290A-VNKT)
 CO-ORDINATION (CDN)
(CDNP/D075P/D039-JAL345/A0506-VIDP-0PKC 14/TIGERO145F290)
 ACCEPTANCE (ACP)
(ACP-ILVUAVA-VOCC-VOBG)
 LOGICAL ACKNOWLEDGEMENT (LAM)
(LAMA/B124)
___________________________________________________________
 REQUEST FLIGHT PLAN (RQP)
(RQP-DLH801-OAKB2145-VIDP-0)
(RQP-DLH801-OAKB2145-VIDP-DOF/130221)
 REQUEST SUPPLIMENTARY FLIGHT PLAN (RQS)

(RQS-BBC301/A5100-VGZR-VECC-0)
(RQS-BBC301/A5100-VGZR-VECC-DOF/130221)
 SUPPLEMENTARY FLIGHT PLAN (SPL)
(SPL-DLH665/A4100-VTBD
-VECC0315 VEPH
-EET/VECCF0135 REG/DABYP SEL/FMEL
-E/0745 P/315 R/VU S/M J/L D/S 280 C YELLOW A/SILVER BLUE TAIL
LUFTHANSA C/MATSCHKE)

Chapter – 06 NOTAM & MET Messages
Chapter – 06
NOTAM & MET MESSAGES
6.0. Overview
The objective of this chapter is to provide a ready reference of NOTAM and MET message
format in brief. The detail discussion on the subject is beyond the scope of AMSS Operation.
However, one can refer the following Course Handouts for details :
• Ab‐initio JET – Aeronautical Information Service (AIS)
• Automated Self‐Briefing System (ASBS)
• Basic AIS
• Ab‐initio JET – Meteorological (MET)
6.1. NOTAM Format
The NOTAM format aims at standardizing the presentation of the different type of information
promulgated by NOTAM in order to facilitate the understanding of the message by the
addressee.
6.1.1. NOTAM Numbering/Identification
Each NOTAM shall be allocated a series identified by a letter (in India – letter
A,B,C,D,G only) and a four digit number (must be consecutive and based on the calendar year)
followed by a stroke (/) and a two‐digit number of the year.
Example : A0127/09, C0534/09
6.1.2. NOTAM Type/Identifier
The appropriate identifier has to be used for each NOTAM, e.g. N/R/C.
NOTAMN – New Information
NOTAMC – Canceling a previous NOTAM
NOTAMR – replacing a previous NOTAM

6.1.3. Qualifier (Q‐line)
Q‐line is divided into eight fields, each separated by a stroke. If no entry is to be made in a field,
it is not necessary to transmit blanks between the strokes. Always refer ICAO Doc.8126 for
filling the Q‐line.
6.1.3.1. FIR :
VECF ‐ Location Indicator of affected FIR
VIXX – if more than one FIR of India affected
VEXX – if more than one FIR in a group of States affected
6.1.3.2. NOTAM Code
All NOTAM code group contain a total of five letters and the first letter is always the letter Q.
The second and third letters identify the subject, and the fourth and fifth letters denote the
status of the subject reported upon.
Always refer the ICAO Doc.8126 to get the codes (nc23/nc45).
6.1.3.3. TRAFFIC
I IFR
V VFR
K Notam Checklist
6.1.3.4. PURPOSE
N Immediate attention of aircraft operators
B for PIB entry
O Operationally significant
M Miscellaneous (not for briefing)
K Notam Checklist

6.1.3.5. SCOPE
A Aerodrome
E Enroute
W Navigational Warning
K Notam Checklist
6.1.3.6. LOWER & UPPER Limits
Lower and Upper limits shall always be filled and shall be expressed in flight level (FL). Default
value : 000/999
6.1.3.7. COORDINATES‐RADIUS
The latitude and longitude accurate to one minute, as well as three‐digit distance figure giving
the radius of influence in NM.
Example : 4712N02315E025
6.1.4. Item A – Location
The ICAO location indicator of the aerodrome or of the FIR, in which the facility, airspace or
condition being reported on is located. Maximum 7‐location indicators are permitted.
6.1.5. Item B , C and D – Period of Validity
Item B : 10‐digit date‐time group, e.g., 0906240730 (Start‐time)
Item C : 10‐digit date‐time group, e.g., 0906241330 (End‐time)
or 0906241330 EST (Estimated End‐time)
or PERM (Permanent)
This field is not required for NOTAMC
Item D : Specific time an date schedule between the date‐time included in items B) and
C). This field is optional.

6.1.6. Item E – Text of NOTAM
Uses decoded NOTAM code, complemented where necessary by ICAO abbreviation, indicators,
identifier, designators, call sign, frequencies and figures, and plain language.
6.1.7. Item F & G – Lower and Upper limit
The actual lower limit or upper limit as it is received.
Example : 6500 FT AMSL
FL100
1200 M AMSL
GND
SFC
6.1.8 EXAMPLE OF NOTAM
(A0123/09 NOTAMN
Q)VECF/QNVAS/IV/NBO/AE/000/999/
A)VEPT B)0902230400 C)0902231330
E)DVOR PPT xxxMHZ NOT AVAILABLE)
(A0256/09 NOTAMC A0251/09
A)VIDF/QMRAK/IV/NM/A/000/999/
A)VIJP B)0903240500
E)RWY09 AVAILABLE)
(A0233/09 NOTAMR A0230/09
Q)VABF/QWMLW/IV/BO/000/050/2312N05633E002
A)VABF B)0907040500 C)0907060800
D)JUL 05 06 0500‐0800
E)PJE WI THE AREA CENTRED AT 2312N05633E WITH A
RADIUS OF 2 NM
F) SFC G) 5000FT AMSL)
6.2. MET Message
In all metro station, MET messages are originated by and at AMSS (MET Centre). However, in
small stations, the MET messages are supplied by MET Centre and submitted through ECIL
AMSS. For more details on MET messages refer to Meteorological Course Handout.

Example :
MEATR VILK 0420 23005 6000 SKC 1002 NOSIG=
Indicates :
MET REPORT OF VILK, TIME OF OBSERVATION 0400, SURFACE WIND 230 DEG 05 KT, VISIBILITY
6 KM, SKY CLEAR, QNH 1002 HPA, NOSIGNIFICANT CHANGE.
Few words & abbreviation of MET messages:
SPECI Special Met Report
RA Rain
TS Thunderstorm
TREND Trend
- Light
+ Heavy
FU Smoke

Chapter – 07 AFTN Routing & Retention of Record
CHAPTER – 07
AFTN ROUTING & RETENTION OF RECORD
Overview
A collection of individual circuits becomes a network when it is agreed mutually that traffic can
flow from circuit to circuit. The network works very well when routings are determined for the
normal flow of traffic and in case of interruption due to circuit failure.
Message shall be routed in accordance with predetermined responsibility for onward relay as
agreed between the administrations responsible for the operation of directly connected stations.
A station experiencing circuit or equipment failure shall notify other stations with which it is in
direct communication if the failure will affect traffic routing by those stations. Restoration to
normal shall also be notified to the same stations.
In order to route traffic in accordance with ICAO procedures, the elements of the routing
directory used by a communication centre are:
Normal routing list, which indicates the correct outgoing, circuit to be used for every
addressee indicator.
Alternate routing list, which indicates the outgoing circuit when normal route is lost.
7.1. Normal Routing
This section looks at the normal routing procedures for single and multi‐address traffic.
7.1.1. SINGLE ADDRESS TRAFFIC
For single‐address traffic, a communication centre accepts the responsibility of relay of this
message through circuits shown on normal routing list.
7.1.2. MULTI‐ADDRESS TRAFFIC
In the case of multi‐address traffic, a communication centre attempts to relay the message to
every address. Once the message is delivered to one of the addressees, that addressee
indicator is removed from any other copy going in another direction to prevent against
duplication of delivery. The method known as 'Addressing Stripping', is used to ensure that
correct action is taken.

7.2. Address Stripping
This material is intended to provide information, guidance and clarification related to the
application of address stripping to the AFTN. These provisions recommend the application of
address stripping to those elements of the AFTN other than CIDIN.
Address stripping applied to messages in AFTN format is the process performed by an AFTN
communication centre in removing from the address those addressee indicators not required
for:
relay by the AFTN communication centre to which the message is transmitted;
processing or delivery to addressee(s) by AFTN destination station to which the message
is transmitted, and
Processing or delivery to addressee(s) served by AFTN destination station on a multi‐
point circuit to which the message is transmitted.
The advantage of address stripping includes:
9 Elimination of definition, storage and maintenance of incoming circuit responsibility lists
and associated processing on the basis that all addressee indicators are to be processed for
onward routing action, i.e. none to ignore.
9 Elimination of the VVV diversion indicator
9 Elimination of multiple delivery or non‐delivery caused by erroneous or mis‐applied
incoming circuit responsibility list:
9 Reduction of overhead by progressively removing addressee indicators as messages
transits the network;
9 Simplification of implementation; and
9 Simplification of the preparation, co‐ordination, maintenance and application of routing
directories.
Figure : 7.1

Figure shows the method of address stripping on the conventional AFTN, reflecting point‐to‐
point and multipoint environments.
Say, a Message is originated at VEAB and addressed to VEGT VAAH VANP VOHY VOTP ( for
simplicity of explanation addressee indicators are abbreviated as L.I. only). Now let see the
steps :
Step 1 : Varanasi (VEBN) AFTN Centre received the message as
it is from VEABorigin station, then retain addresses as below and forward toward next relay
station(s)
9 VEGT to Kolkata (VECC) AFTN centre serving VEGT
9 VAAH VANP VOHY VOTP to Delhi AFTN centre
Step 2 : at Delhi (VIDP) AFTN Centre
9 VAAH to Ahmedabad (VAAH) AFTN centre
9 VANP VOHY VOTP to Nagpur (VANP) AFTN centre
Step 3 : at Nagpur (VANP) AFTN Centre
9 VOHY to Hyderabad (VOHY) AFTN centre
9 VOTP to Chennai (VOMM) AFTN centre
Step 4 : at Chennai (VOMM) AFTN Centre
9 VOTP to Tirupati (VOTP) AFTN centre
In stripped addressing, a communication centre receives messages addressed to those addressee
indicators for which that centre can take any action. Hence a communication centre accepts relay
responsibilities for all messages transmitted to it. Whenever a normal circuit fails, messages meant
for that circuit is diverted by the communication centre via available alternate circuits.
7.3. Predetermined Distribution System
When it has been agreed between the Administrations concerned to make use of a
predetermined distribution system for AFTN messages, the system described below shall be
used.

The Predetermined Distribution Addressee Indicator (PDAI) shall be constructed as follows:‐
The first and second letter:
The first two letters of the Location Indicator of the communications centre of the State which
has agreed to implement the system and which receives messages over a circuit for which it has
a predetermined routing responsibility.
The third and fourth letter :
The letters ZZ, indicating a requirement for special distribution;
The fifth, sixth and seventh letter :
The fifth, sixth and seventh letters taken from the series A to Z and denoting the national and/or
international distribution list(s) to be used by the receiving AFTN centre;
"N" , “S” and "V", as the fifth letter, are reserved for NOTAM , SNOWTAM and ASHTAM
respectively.
The eighth letter
Either the filler letter "X" or a letter taken from the series A to Z to further define the national
and/or international distribution list(s) to be used by the receiving AFTN centre.
9 To avoid conflict with the AFTN start‐of‐ message signal, combinations with ZC or CZ will
not be used.
9 To avoid conflict with the AFTN end ‐of‐ message signal, combinations with NN will not be
used.
PANS: ‐ Predetermined Distribution Addressee Indicators (PDAIs) should be used whenever possible
on AFTN messages between States which have agreed to make use of predetermined distribution
system.
AFTN messages carrying Predetermined Distribution Addressee Indicator allocated by the State
receiving the message shall be routed to the addressee listed on the associated list of Addressee
Indicators described below.
States shall send their list of selected Predetermined Distribution Addressee Indicators together
with the associated lists of Addressee Indicators to:
a) The states from which they will receive AFTN messages for predetermined distribution, to
assure correct routing; and
b) The states, which will originate AFTN message for, predetermined distribution to facilitate the
treatment of requests for retransmission and to assist originators in using the predetermined
Distribution Addressee Indicators correctly.

The list of Addressee Indicators associated with a Predetermined Distribution Addressee
Indicator shall include either:
Addressee Indicators for national distribution; or
Addressee Indicators for international distribution; or
Predetermined Distribution Addressee Indicators for international distribution; or
Any combination of above three
7.4. Retention of AFTN Traffic Record
7.4.1. LONG TERM RETENTION OF AFTN TRAFFIC RECORD
Copies of all messages in their entirety, transmitted by an AFTN ORIGIN station shall be
retained for a period of AT LEAST 30 days.
AFTN destination stations shall retain for a period of at least 30 days a record containing the
information necessary to identify all messages received and the action taken there on.
AFTN communication Centre shall retain for a period of at least 30 days, a record containing the
information necessary to identify all messages relayed or retransmitted and the action taken
there on.
NOTE :The provisions for identification of messages mentioned above may be obtained by
recording the heading, address and origin parts of the messages.
7.4.2. SHORT TERM RETENTION OF AFTN RECORD
AFTN communication centers shall retain, for a period of at least one hour, a copy of all
messages in their entirety, retransmitted or relayed by that communication Centre.
In case where acknowledgement is made between AFTN communication Centre, a relay Centre
shall be considered as having no further responsibility for retransmission or repetition of a
message.

Note :
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
..........................................................................................................................................................
....................................................................................

Chapter – 08 ECIL AMSS ConfigurationBasic Concept
CHAPTER – 08
ECIL AMSS CONFIGURATION – Basic Concept
8.0. Overview
The ECIL AMSS was introduced in India in the year 1997 at Delhi and Mumbai initially, then to
other metro and major stations. Within a period of last ten year, it has undergone lots of
changes by mean of incorporating high‐speed circuits over TCP/IP protocol, DSCN circuit,
Remote Workstation, Remote ASBS terminals with remote replication of Database server etc,
even AMSS at Mumbai and Delhi are further upgraded by ECIL. However, the basic structure of
AMSS remains same. It is not to far that these will be replaced by new generation system,
known as AMHS.
Taking into consideration all of these, the basic configuration of ECIL AMSS has been discussed in a
modular form for better understanding of the subject concerned.
8.1. ECIL AMSS Hardware Configuration
AMSS consists of 3 (three) major components:
• Core System
• Recording System
• Users’ Terminals
Core System : It incorporates communication adapters, protocol/suites, routing and gateway
facilities. The core system is composed of two identical computer machines (known as AMSS
Main Servers) which are operated in an operational/hot standby combination. Both units
supervise each other’s software and hardware. In case of software/hardware failure of the
operational unit, the hot standby unit is activated automatically so that it can take over
immediately without loss of data. The core system also includes remote communication
adaptors, Multiplexer and one/two computer machine(s), known as communication server, to
avail the communication gateway facilities (if any)
Recording system : It has two identical mass data storage devices for storing all incoming and
outgoing AFTN messages. It has also two identical mirrored Database servers, which are
operated in parallel. The mirroring between the two database servers is performed in the
background to store specified type of messages like NOTAM, MET, ATC, HFRT, with no effect on
the regular operation.
Users’ Terminals : It is the interface between user and the system with capability for uniform
administration and monitoring facilities for all system component, networks and data as well as
exchange of data as per requirement of users vide different type application software. Any

number of users’ terminals (maximum 60), formally known as Workstation, can be installed and
used simultaneously.
ECIL AMSS is mainly working within a local area network and which is further extended to
connect other remote station for data communication. For better understanding, AMSS
Hardware Configuration will be discussed in modular fashion.
Any network works either as Domain based network and/or Non‐domain based network. In
ECIL AMSS, we have both types of networks within the same LAN.
8.1.1 Non‐Domain Network :
Basically, all the computers are in same Workgroup ( say, NAA in AMSS ). Each computer of the
network can share their resources with each other, if required.
In ECIL AMSS, all users terminals (formally known as AMSS Workstation like Supervisor,
Booking, Notam, HFRT, AREA, MLU etc.) are working under the same workgroup and they are
inter connected with each other by means of NIC, UTP Cable and Ethernet Hub/Switch.
Any computer, including present days Intel Dual Core or Core to Duo or Xeon processor can
work as a user terminal (AMSS Workstation) of AMSS. Only each computer should have built‐in
network interface RJ‐45 port or additional NIC.

AMSS Workstations are ready to

work on any version of Microsoft
Windows OS like, Windows NT,
Windows 98, Windows ME,
Windows XP (even Server version
OS ).
8.1.2. Domain Network :
ECIL AMSS Main Application Servers (Operational Server and Hot Standby Server – amss1 and
amss2) act as domain servers in AMSS LAN and overall control the main functions of AMSS like
message routing/switching and server‐client integrity by mean of software.
The Hardware configuration of AMSS Main Servers has some limitation to use next generation
machines. Original ECIL AMSS came with Intel‐440 GX motherboard based P‐3 Server machine
(at present the same motherboard is hardly available in the market).
As per the requirement of ECIL AMSS Application software, the servers should have one
ISA/EISA slot (excluding ECIL AMSS upgraded version at Mumbai, Delhi). Moreover, it should
have SCSI Interface, support of communication adapter etc.
AMSS Server works on UNIX platform. AMSS Servers has mainly three additional hardware
components for different purpose :
• To be on LAN :
Both the servers has their own NIC ( in AMSS server, normally two nos. NIC are available) which
are connected with Ethernet Switch by means of RJ‐45 ports and UTP Cat‐V cables.

• Dual Architecture :
a) Health Monitoring : Each server has one SOLC (Switch over logic control card) card
which has two serial ports. Both the Servers are interconnected over one port of each SOLC.
Each servers are monitoring each other health status through this SOLC card. In case of failure
of Online Server, the hot standby server take over the charge and acts as Online server.
b) Common Data Storage System : Two nos. of SCSI Hard disks are connected with both the
server in a daisy chain fashion, so that both the server has a common area to store messages
and system information as Online server as well as to use the same for recovery during auto
change over from one server to other.
c) Remote Communication Adapter : Each server has one Stallion Card as communication
control module to serve multiple numbers of channels.
Both the AMSS Servers are individually connected to parallel printer, known as Server Console
Printer for printing of system generated health/activity information.
8.1.3. Message Storing :
ECIL AMSS is designed to store information in three areas :
• Server IDE Hard disk for Unix OS and Application Softwares.

• SCSI Disks for storing only AFTN messages (In/Out). The disks are referred as Disk‐0 and
Disk‐1. Each SCSI disk and its corresponding connector are housed in a single cabinet with SMPS
to provide external power supply to disk.
• Database servers to store specified type of messages like ATC, Notam, MET and HFRT.
This machine may be a standalone PC on Windows platform, connected with LAN as common
workgroup ‘NAA’ and having SQL 2000 server version Database Management software.
8.1.4. Remote Data Communication :
AMSS is mainly designed for exchange of messages with different stations over different type of
communication media/remote lines. AMSS is capable to handle mainly following types of
remote communication lines:
• Remote Printers : (1) Report Printer , (2) Reject Printer and (3) Drop Printers. All the
printers are Dot Matrix Serial printers.
• TP Lines : Low speed (50 baud) Teleprinter line provided by DOT
• Dial‐up Lines : Over telephone line connected through Modem.
• Other Network System : Serial communication over two pair of lines connected through
Line drivers to exchange messages with other networks like ADS at Chennai and Kolkata.
• High Speed Lines : 1) 64kbps leased line over X.25/TCP/IP protocol and/or DSCN
connectivity over TCP/IP protocol.
8.1.5. LTU :
Except the High speed lines, rest all lines are terminated in a single unit, known as LTU (Line
Termination Unit) in ECIL AMSS.
The LTU has main two parts : (1) DC Power Supply Modules and (2) three types of line
termination units – LTU‐B, LTU‐C and LTU‐M cards
The LTU B/C/M card is basically a communication interface cards. The LTU‐B card is used to
interface TP lines and LTU‐C for RS‐232 interface. The LTU‐M card not in use in present AMSS.
Both the servers are physically connected with the LTU units for Rx/Tx of messages. The system
is designed in such a way that only the Online server can transmit messages through LTU
whereas both the server can receive the messages through same LTU ( but the Online server is
responsible for routing action on received messages).
In order to allow the ‘Online’ server to transmit messages, there is another card known as LTU‐
D. The SOLC cards of both the AMSS servers provide the SOLC logic signals to LTU‐D card so that
the LTU‐D card has the information which server is online (Sys‐A or Sys‐B). Accordingly it passes

the information to all LTU cards which in turn established the physical line connection between
online system Tx lines and LTU Tx lines.
8.1.5.1. Multi‐channels support between Server and LTU :
Each server has one Stallion Card which works as Communication Control Module in
coordination with CCM Adaptors for multiplexing of messages through different channels.
8.1.6. High Speed Connection :
The high‐speed 64kbps lines are connected through a Machine, known as Communication
Server (X.25) which has one additional Communication Card – Eicon Card. Each Eicon card can
support maximum two lines. The high‐speed lines are connected through MLLN Modem over
DOT X.25 clouds. However, now‐a‐days, one Router has introduced in between Comm. Server
and MLLN to accommodate VOIP (Voice Over Internet Protocol) communication over the same
line.
The DSCN Connectivity are get through another Communication Server (TCP) which has one
additional NIC card to accommodate DSCN Memotech router connectivity. All the
communication servers are in same LAN workgroup (NAA).

8.1.7. The Audio Visual Alarm (AVA)
AVA software monitors and displays the status of the entire message switching system
including its various allied sub‐systems. The AVA displays
o Switch status‐ MS1 and MS2
o Device Status‐Disks and Tapes
o Power Supply status
o Real time
o Channel status
The AVA obtains all the status information from the ONLINE AMSS system through LAN and
displays them graphically. The graphical representation enables quicker and easier
interpretation of current status of the entire network. The status of all systems and sub‐
systems are displayed in the form of rectangular blocks. The background color of a block
indicates the current status of the system/sub‐system concerned. The date and time of failure
are shown wherever they are relevant.
In case of failure of AMSS Server(s) [MS‐1/MS‐2] or disk(s) [D0/D1] which are critical, the
software:
- Comes to the foreground if it had been minimized
- Gives visual effect to the block concerned (in red color)
- Generates alarm sound
The AVA software can also be run in any WS running Windows NT. The AVA terminal will have
special hardware to monitor LTU power status. If it is run on a WS other than AVA terminal,
then the status of all systems/sub‐systems except LTU power status can be monitored.

8.1.8. System Report & Reject Printer (SRP/SRJ)
SRP‐ This printer is used for auto printing of various reports generated by the system.
For example hourly report half hourly report. Further other reports like 23rd day Statistics, AFTN
circuit loading statistics by supervisory commands. This printer is connected directly from LTU.
SRJ‐ This printer is used for printing logging details of rejected messages by the system. Also it
logs the header summary of the messages transacted through LTU.
Functional Block Diagram of AMSS
8.2. ECIL AMSS Software Configuration
The ECIL AMSS has mainly three type application softwares, namely,
AMSS application software, built under SCOUnix OS environment,
AMSS Backend application software for Windows OS platform
AMSS Backend application software for Windows OS platform

8.2.1. Architecture of AMSS application Software
The software is designed in very modular structure and is written in C language. The message
switching application software is a machine independent and is easily portable. Application
software is divided into three tasks.
Task 1: receives messages from LAN and remote lines, keeps into the shared memory.
Task 2: transmit messages from shared memory to LAN nodes and remote lines.
Task 3: divides into several modules controlled by an application oriented base
sequencer. The main modules of this task are as follows:
8.2.1.1. Input Processing (IP)
This module provides an interface to receive messages from shared memory, MCCM ports and
fills up into a queue after preprocessing. It acts as a transport for messages to the next module
Message Parsing.
8.2.1.2. Message Parsing (MP)
This module receives preprocessed messages from IP and analyses them to pick up different
fields, finds the error in them, keeps them in the message control packet (MCP), and puts the
MCPs in queue for Message Routing (MR).
8.2.1.3. Message Routing (MR)
This module is responsible to find out the route for transmission depending on the route picked
up signaled by the MP. This module stores the messages in mirror disks with suitable index and
stores the messages in memory blocks for transmission and other activities.
8.2.1.4. Output Scheduler (OS)
This module is responsible for scheduling the transmission based on priority and availability of
circuits. It also stores the outgoing details of messages in transaction file on the disk. It prepares
journals and monitors line conditions.
8.2.1.5. Output Processing (OP)
This module is responsible for header generation, code conversion and transmission function of
message.
8.2.1.6. There are various other modules, which helps in supervision and control. Some
of these modules are:
- Command Analyzer and Processor
- Report Generator

- Application like delayed message, half‐hourly reports, message retrieval etc.
- Recovery, Ledgering and Reconfiguration.
8.2.2. AMSS Backend Application Software
The application which is not directly involved in a particular application of a workstation for
running and execution of file management but certain specified task are being executed by the
backend application. The backend application is a support service to the workstation or front‐
end applications. Normally it runs on Database Machines. ( Software for X.25 Server and TCP
Server is not included for discussion).
The Back‐end Application needs the following data files, beside its own executable file , e.g,
AppSer.Exe.
The file Path (RootDirectory)=C:\\Naa\\BackEnd\\DataFiles\\
The following lists of DataFiles are required for BackEnd application
config.dat – It contains all important files information such as Channel prefix, root dir,
Origin Indicator etc. for backend application
NotamSup.dat – includes the name of NOTAM Error‐Q Terminal (say,NOB)
AtcSup.dat – includes the name of FPL Error‐Q Terminal (say, BKB)
MetSup.dat – includes the name of Met Error‐Q Terminal (say, MTA)
In addition the backend application contains the following file folder:
ErrorATC – contains ATS messages rejected due text format error
ErrorMet – contains MET messages rejected due text format error
ErrorNotam – contains NOTAM messages rejected due text format error etc.
8.2.3. AMSS Front‐end Application Software
The front‐end application supports a workstation’s hardware and the LAN System in the AMSS
environment. The front‐end supports different AFTN message preparation features and queries
at workstations viz. NOTAM, BOOKING, HFRT.
THE ECIL customized the following execution files (.exe files) according to the requirement of

individual workstation.
1 SUPERVISOR AMSS Supervisor
2 BOOKING For Message Booking and Error‐Q handling
3 NOTAM For AIS/NOTAM/ASBS purpose
4 HFRT For HFRT/RADIO communication
5 ASBS For Flight Information Bulletin, open to all users
6 BRIEFING Used by ATC for YA numbers etc
7 ADC/FIC Used by ATC for FIC/ADC numbers etc.
8 AREA Used by ATC Area Control for HFRT and AFTN
messages monitoring
9 MLU Used by MLU for monitoring HFRT/AFTN FPL
messages and ADC numbers etc.
8.2.3.1. Files of Front‐end Application
Each Front‐end Application needs the following data files, beside its own executable file , e.g,
booking.exe, notam.exe etc. to run the execution files on defined Workstation.
The file Path—C:\\Naa\\FrontEnd\\DataFiles\\ (in general)
login.dat—It contains the username and password of the users.
config.dat – It contains all important files information such as Channel prefix, root dir,
Hfrt position etc.
basedet.dat – This is used to read address list in any message preparation.
pry.dat – It contains Priority to be assigned to a message.
freqId.dat – It contains frequencies and its corresponding frequency designators. (for
HFRT Application only)
nc23.dat – It contains Notam 2nd and 3rd letter code and code details. (For NOTAM
Application only)
nc45.dat – It contains Notam 4th and 5th letter code and code details. (For NOTAM
Application only)
8.2.3.2. Scope of Automation for AFTN Message and Utilization in AMSS
The ITA‐2 format has five parts namely, Heading, Address, Origin, Text and Ending. The AFTN

messages are prepared using printable and non‐printable characters. Some are constant and
some are variable. With the help of intelligent terminal almost all the constant components can
be automated and in case of variable components some validation can be designed in order to
avoid human errors.
• Automation of Heading :
The heading of an AFTN message is totally automated. The Channel Prefix and sequence
number with start‐of‐message signal etc generated by system automatically.

• Automation of Address :
The system prevents wrong entry by validating the priority indicator against prefixed value of it
available in pry.dat file. Operator can type or select the priority through drop down menu as
per category of message. For addressee indicators, the system allows entry of any number of
addressee indicators validating the 8 characters for each addressee but it transmits by splitting
those addresses into multiples of 21 addresses in a message.
• Automation of Origin :
System validates the entry for valid date time group and 8 alphabetic characters for originator
indicator. The system prompts for filing time as current time, which may be edited by the
operator also. Again, the originator indicator is prompted by the system from file config.dat
that is editable by the operator as well.
The priority alarm is automatically added if priority indicator is ‘SS’.
• Automation of Text :
The text of ATFN message has free format however certain elements of the text are
automated.
The system checks the maximum length in terms of characters (1800 characters including
printable and non‐printable characters) of the text. However operator is allowed to enter any
number of characters in the text but system automatically splits into parts by making 2100
characters for a complete AFTN message length.
The system prevents the use of ZCZC and NNNN in the text part.
In text of NOTAM and Air Traffic Services (ATS) messages the entry of the text in various fields is
restricted as per the specified characters, which are validated by the system.
The text of certain SERVICE messages have been automated e.g. QTA MIS, LR/LS, CHANNEL
CHECK, CORRUPT etc.
It is to be noted that, the TEXT part of AFTN message cannot be automated completely but with
the help of intelligent terminal generation of message become faster.
• Automation of Ending :
The ENDING comprises of the page feed sequence, end‐of‐message signal and message
separation signal. The ending is fully automated.

8.3. AMSS Switch‐on Procedure
The system power ON sequence always starts from :
LTU Rack, Disk Switch(es), ONL MS(1/2), HSB MS(2/1), and
Power OFF sequence always starts with
HSB MS(1/2), ONL MS(2/1), Disk Switch(es), LTU Rack
8.3.1. Switch‐on AMSS Main Server (MS‐1/2)
After power‐on AMSS Main Unix Server, press <Enter> key at prompt “boot:” for normal booting
of Unix system. On asking by system, press <Ctrl>+d for normal mode startup and confirm the time
of the system by entering new time or press <Enter> key. Enter System User Name and Password.
The system is ready on prompt “#” to accept user’s command.
To run the system as Online Server or Hot standby Server, follow as below:
# ./r <Enter> for recovery mode and online
# ./h <Enter> for standby
(Running the system on new mode as online is reserved with Administrator)
8.3.2. Switch‐on AMSS Workstation or Database Server
After power‐on the Workstation/Server CPU with Monitor, the system will load Microsoft
Windows (NT/XP) Operating Software automatically.
Press “Ctrl+Alt+Del” at a time to log in the Network, the LOGON Information screen will appear.
Enter or Accept: it by pressing OK if the username and password as below
Username : Administrator
Password : (blank)
From the Desktop Screen, run the appropriate shortcut of desire application for functioning of
AMSS Backend or Front‐end application, as the case may be.

Chapter – 09 ECIL AMSS Frontend Application
CHAPTER – 09
ECIL AMSS FRONTEND APPLICATION
9.0. Overview
The ECIL AMSS has different front‐end application e.g., booking, supervisor, notam etc.
customized according to the requirement of specified jobs of the workstation concerned.
However, most similarity of different application is its main screen with the difference that
some of menu, submenu or popup menus are active or deactive as per the requirement of
individual application.
In this section, only few menu/submenu of main screen will be discussed in brief as per the
basic requirement of AMSS Operation (Level‐1). However, details of the same will be covered in
practical session.
9.1. AMSS Front‐end Main Screen
The main screen of front‐end application has the provision of 14‐menus and each menu has few
sub‐menus to carry out different functions.
9.1.1. Menu – Adm
This is administrative in nature and contains the following sub‐menus:
Sub‐menu Purpose Remarks

Login User to logged in with login ‘sa’ is reserved for supervisor
name and password login name and password
Logout To log out from application
New Login Used to create new login Only by Supervisor

name
Drop Login To enable login name Only by Supervisor
Change To change password of Supervisor has full right for all

Password user own login login
User Manager Logged in time against user
Login Statistics Only for NOTAM/HFRT For System Administration

statistics
Exit To close application

9.1.2. Menu – Mpu
This is only for Message Preparation. It has two sub‐menus :
• AFTN Document Preparation for saving of standard messages as document which could be
used anytime as a text of message.
• AFTN Message Preparation – an AFTN Format template with automation in different areas
, used for generation of AFTN message .
9.1.3. Menu – Ntm
This area is specially customized for creation of Notam messages, Maintenance of Notam
Database, Notam Briefing and different statistics on Notam & Bulletin. This area is mainly for AIS
Personnel and beyond the scope of discussion in AMSS Operation. (Details in ASBS course
materials).
Only one user on the specified NOTAM Workstation can prepare a NOTAM message with the help
of Notam Preparation template under ‘Notam’ submenu of this section. It generates the Notam
number automatically.
9.1.4. Menu – NQry & InactiveNotams
These two menu provides Notam Query screen with different options to display active or inactive
notams in respect of a Notam series (e.g. A, B, C etc) of a Notam Office (e.g., VECCYNYX, VIDPYNYX
etc.) which will be retrieved by the system from Notam Database.
9.1.5. Menu – Atc
This menu provides appropriate ATS message template for all type of ATS messages ( ref. Chapter‐
5, Para.5.2) like FPL, DEP, ARR, CHG, DLA, ALR, RCF etc.
The Flight Plan Template has the provisions to query the plan from the Database also. One can use
this facility to query the plan from database and then modify it (normally, Dep time, Regn and
Selcal ) before submit.

9.1.6. Menu – Mlu, Met, MQry
All these three menus are hardly use by CNS personnel. Only ‘YA’ sub‐menu of ‘Mlu’ is used by
HFRT personnel for preparing flight progress strip and sometime ‘Mqry’ is used to provide Met
observation (METAR/SPECI) to aircraft operating agency on request. The menu ‘Met’ is not in use
to prepare MET messages.
9.1.7. Menu – Hfrt
This menu provides HFRT message preparation screen, used by HFRT personnel to record the air‐
ground /ground‐ground communication messages and forwards the same to ATC & MLU
Computers. The HFRT/FIC/MET and YA query can be executed by using HFRT message screen.
9.1.8. Menu – Tbl
This menu has different sub‐menus to store/edit different information in table. The GI_TBL
facilitate to store a number of address lists under a group indicator. This facility is helpful for
transmission of Notam, FPL etc messages where a single message is sent to a large number of
addressees.
9.1.9. Menu – Stat
This menu brings the AMSS Statistics screen (also called AMSS Control Screen) to display all the
messages received, transmitted and some of statistical data. It also provides lists of commands and
allows executing any command by the supervisor.
The following items are available in the AMSS Statistics table. The user can select and click and
execute the following tasks.
LCLRx Displays all the local received messages.
SVC Displays all the Service messages received.
LCLTx Displays all the local transmitted messages
LCLPnD Displays all the messages which are pending for transmission from the local
Workstation
SUSQ Displays all the messages suspended by AMSS
REJQ Displays all the messages rejected by AMSS
TxQ Displays the transmit queue messages (route wise) which are pending for transmission
LCLRxPrv Displays all the previous days received messages by the local WS
PrevSvcMsg Displays all the service messages received on previous day
LCLTxPrv Displays all the previous day transmitted messages by local WS

SSPtyMsg Displays all the SS priority messages received by local WS
Tester Displays the tester screen, which is used to generate a test message on any given
channel
HMSR Displays the message retrieval screen
Cmd Provides list of commands and allows to issue any command by the Supervisor
RejMsgs Displays all the rejected message by the local WS
Miscellaneous The result of some commands and some miscellaneous messages are displayed.
Sys LR/LS Displays the latest LR/LS report of the AMSS system.
Monitor Displays the online data being received and transmitted on a Channel
TRAK Provides Message transaction details.
RetMsgs Displays the latest retrieved messages for further reference.
CmdResp Displays the latest command response.
9.1.10. Menu – Messenger
This menu provides the facility to broadcast some messages to all nodes of AMSS Network,
normally, used by Supervisor or System Administrator concerning system shut‐
down/maintenance/problems etc.

Chapter – 10 AMSS Control Function
CHAPTER – 10
SUPERVISOR ‐ AMSS CONTROL FUNCTION
10.0. Overview
The AMSS Control screen can be activated by clicking of popup menu key “Ac” or by clicking on
menu “Stats”. It has several functions and all the options buttons are active in ‘Supervisor’
application. Basically, this control is used to monitor incoming/outgoing messages, monitoring
system’s different Queues on rejected/suspended/transmission messages as well as total
software control on AFTN channels and routes etc.
10.1. Message Monitoring
All received (incoming) or transmitted (outgoing) messages can be monitored with help of
following functions:
LCLRx : all received messages of current date on self machine
(Local)
LCLRxPrv : all received messages of previous day on self machine
(Local)
LCLTx : all transmitted messages of current date on self
machine (Local)
LCLTxPrv : all transmitted messages of previous day on self
machine (Local)
HMSR : all incoming / outgoing messages within last 30 days
All the function has the option to view and transmit the messages under new CSN. The
incoming or outgoing messages are always counted as In/Out with respect to AMSS Main
Server only.
10.1.1. Service Message Monitoring
All the service messages, i.e, message text is having SVC as first element, addressed to that
machine can be monitored by clicking the ‘SVC’ button. In general, all service messages
addressed to XXXXYFYX, where XXXX is L.I. of the Station concerned, are available under ‘SVC’
function of Supervisor terminal and the same local service message are not available under
‘LCLRx’ function.
In some service messages like SVC QTA RPT, ADS CORRUPT, OGN CORRUPT, supervisor has to
take manual action (system will display at the end part of the text of that message – ‘MANUAL
ATTENTION REQD’). Supervisor will retrieve those messages through HMSR command and
retransmit accordingly.

For the message, system has taken action automatically, system displays ‘AUTO ACTIONED’ at
the end part of the text.
All the service message of the previous day’s received can be displayed by clicking on the
button ‘PrevSvcMsg’. The care should be taken to take suitable action on all service messages 5
minutes before the change over of day (2355 GMT).
10.1.2. SS Priority Message Monitoring
As soon as a SS priority message has been received by the system a hooter tone will generate to
draw the attention of the user. A dialog box for SS priority message will appear on the
concerned workstation screen.
Acknowledge it by Clicking OK button of dialog box. The dialog box will disappear and hooter
sound will stop. The SS priority message received can be displayed by clicking ‘SsptyMsg’
button.
10.2. Message Tracking
The message(s) transaction details can be seen by clicking ‘Track’ button and filling the channel
Prefix, Message number(s) and date. Results are as below (Example):
EAA0123 240230 GG XMT VEGT 240231 EGA0067
EAA0123 240230 GG PDG VEAT
10.3. Message Retrieval
All the messages of last 30 days can be retrieved by ‘HMSR’ button. The following message
Retrieval Dialog box will appear. In this screen Date, Channel Prefix and Msg fields are
mandatory and rest is optional.

10.4. Test Transmission
In case of failure of circuits due to line or any circuit uncertainty or other reasons, test
messages can be transmitted or test messages can be stopped over any channel(s) with the
help of ‘Tester’ button.
To run the Tester, User has to enter Channel identification (three letters), type of tester 1, 2 or
3 and number of test times. (for continuous transmission of test message enter zero) and then
submit.
10.5. Transmit –Reject Queue Monitoring
The ‘TxQ’ button of AMSS Control function enable the supervisor to access route status report
of the circuits (LAN, Remote etc) of the station such as: pending messages route wise, the
message status etc., number of messages in transmit queue route‐wise etc.
The ‘RejQ’ button enables the supervisor to monitor the messages rejected by the system due
to format error and to take suitable action on that.
In the both cases, the supervisor has the option to ‘Kill’ the message or ‘Froce routing’ of
messages. The priority jumping of message(s) can also be done.
10.6. Supervisory Commands
The supervisory commands are used to control the operation of AMSS System exclusively from
Supervisor terminal. These commands are listed under a group of commands (CMD GROUP).
Under each group of the command group there are number of sub commands for system
operation, verification, manipulation, monitoring and corrections, switch control etc.
All such commands are available under ‘Cmd’ button of AMSS Control/Stats Screen. The
following type of command groups are mainly used by AMSS Supervisor to control the efficient
flow of incoming/outgoing AFTN traffic through AMSS :
• Circuit Control Commands
• Route Control Commands
(A) The Circuit Control commands are used to :
– Get the channel status in details (CCST)
– Close the incoming or outgoing of a channel (CCLS)
– Open the incoming or outgoing of a channel (COPO)
– Disable / Enable a channel (CDIS/CENB)
– Monitor incoming/outgoing channel (CMNI/CMNO)

– Self line status, currently monitored channel (LINE)
– Get the list of address for a channel (ADRS)
– To enable line for giving command (ECMD)
– and more .............
In all of the above commands, one has to define the parameters(s), e.g., channel as three letter
prefix etc., to execute the commands. A guideline on the command is available on the bottom
line of the screen.
(B) The Route Control commands are executed by filling up parameters of route name (define
in four letters) to :
– Auto divert traffic from one to another route (ADVT)
– Divert traffic from one to another route (ALRT)
– Block a route (BLCK)
– Unblock a route (UBLK)
– Stop diversion (NRML) in case of route diversion
– Get the route status (RSTA)
– Normalize the route ( ADVN) in case of auto‐route diversion
The Journal Commands –‘MSGD’ is used to take backup of data on a tape with the use of online
AMSS main server. The System Status commands – ‘QRPT’ is used to take cumulative report of
23‐day message transaction statistic channel‐wise. The rest commands or command groups are
used by the AMSS System Administrator only.

Chapter – 11 Introduction to AMHS/ATN
CHAPTER – 11
INTRODUCTION TO AMHS / ATN
11.0. Overview
The process of getting an aircraft safely and efficiently to its destination depends on three
functions – Communication (C), Navigation (N) and Surveillance (S). ICAO calls the three
functions as the CNS system and regards them as forming the basic support services of air
traffic management. While the functions are not new in aviation, both aircraft and their
avionics have become more sophisticated. Rapidly improving satellite and digital technologies
now make even more revolutionary advances possible.
The increasing use of data communications between aircraft and the various ground system
require a communication system that gives users close control over the routing of data and
enables different computer systems to communicate with each other without human
intervention. The Aeronautical Communication Panel (ACP) has designed the Aeronautical
Telecommunication Network (ATN) as a seamless network to distribute ATC messages among
ICAO members (Ground to Ground) including Air to Ground messages.
The ATN is a private inter‐networking infrastructure for global network, which is collection of
interconnected aeronautical End‐System (ES), Intermediate System (IS) and Sub‐Network (SN)
elements for exchange of digital data between a wide variety of end‐system applications
supporting end users. The End‐system attached to ATN sub‐networks communicate with the
end‐systems on the other sub‐networks by using ATN router. The ATN routers can be either
mobile (Aircraft‐based) or fixed (Ground‐based).
The ATN is based on :
OSI (ATN/OSI – X.400) model ( Ref. ICAO Doc.9705 )
OSI (ATN/OSI – TCP/IP) model (Ref. ICAO Doc.9880)
OSI (ATN/ISP – X.500) model (Ref. ICAO Doc.9896)
The ATN has mainly two types of applications –
Air‐Ground Applications
Ground‐Ground Applications

Figure 11.1 : ATN Architecture
The ATS (Air Traffic Service) message handling services (ATSMHS) is a part of ground to ground
application and centered on the AFTN using Aeronautical Message Handling System (AMHS) for
exchange of ATC messages between service users over ATN internet communication services
(ICS). (Ref.: Annex‐10, Vol‐II, Ch‐4)
11.1. AMHS
The AMHS is a message handling system that allows exchange of ATS messages between its
service users. It is based on ISO/IEC10021 or ITU‐T X.400.
The AMHS message service provides Basic Service and Extended Service. Extended Service is a
superset of Basic Service, supports more complex message structures, use of Directory service
and support Security.
It has three major components :
ATS Message Server
AFTN/AMHS Gateway
ATS Message User Agent
which collectively work on store and forward principle through the message handling system
(MHS) prescribed by the ISO.

11.2. AMHS Architecture:
• MTA (Message Transfer Agent) Send out/Receive ATN Message
• MS (Message Store)
• AFTN (Aeronautical Fixed Telecommunication Network)
• MTCU (Message Transfer and Control Unit) provides interface between the ATN and
AFTN components.
• UA (User Agent) provide interface for user sends or gets mail
The ATS Message Server should perform the following:
Routing : Sending / Receiving
Encoding / Decoding
Store and retrieve received messages
Long term logging of all messages passing through MTA and store at least for 30 days
The ATS Message User Agent provides the input mechanism and protocol for users to send and
receive messages. It interfaces with the MTA or/and MS normally through the LAN or IP
network over dedicated circuits or VPN.
The AFTN/AMHS Gateway is to convert the AFTN messages to AMHS messages or vice‐versa.
The AFTN components handles the message format using ITA‐2, it shall convert the messages
to/from IA‐5. The ATN component ensures all AMHS information‐passing MTCU compiled with
base standard of ATS message server. The MTCU provides bi‐directional conversion facility
between AFTN component and ATN component using IA‐5 internally.
11.3. Comsoft’s AMHS ‐ India
The AMHS, supplied by M/s. Comsoft, Germany, fulfils all international aeronautical
interoperability standards (AMHS, AFTN, CIDIN, and SITA) and provides fully integrated and
uniform message handling facilities. The System is compliance with standards and ICAO SARPs,
such as AMHS, X.400 P1/P3/P7, ATN.

The AMHS system, installed in Mumbai, India is known as AIDA‐NG (Aeronautical Integrated
Data‐exchange Agent – Next Generation).
AIDA‐NG consists of three major components :
– Communication Core System (CSS)
– Recording Sub‐System (RSS)
– Operator Working Position (OWP)
All system components are interconnected through a redundant Fast‐Ethernet LAN. All system
parts are based on high scaleable COTS equipment and are independent of each‐other so that
they can be extended and enhanced individually.
11.3.1. Communication Core System (CCS) :
It has incorporated communication adapters, protocol suites, routing and gateway facilities.
The Core system is composed of two identical communication units, which are run in an
operational/hot standby combination. Both units supervise each other’s software and
hardware. In case of software/hardware failure of the operational unit, the hot standby unit is
activated automatically so that it can takeover immediately without loss of data within 5
seconds.
Technical Data
- two Intel processor-based servers
-Red Hat Linux fedora OS

-up to 130 serial WAN interface
(V.24/V.11)
-up to 8 serial LAN interface

(Fast/Gigabyte Ethernet)
Main Functions :
– Performs message handling and central routing tasks

– Houses duplicated physical LAN/WAN interfaces for the
connection to external communication partners
– Executes LAN/WAN protocol stacks for the communication with
all partner systems
11.3.2. Recording Sub‐System (RSS) :
It has two identical redundant database servers which are operated in parallel and works in the
background with no effect on the regular operation.
Technical Data :
– Two Intel processor‐based servers
– Each server equipped with high‐volume storage systems in RAID1 and RAID5
configuration
– Red Hat Linux Fedora Operating System
Main Functions :
– Fully redundant database system
– Holds the traffic, statistical and technical event databases (storage period configurable
by database type)
– Maintain static databases (system configuration, templates, archives and other data)
– Allows operators and applications to access all databases and archives directly and
simultaneously.

11.3.3. Operator Working Position (OWP) :
It is the interface between user and system that provide, uniform administration and
monitoring facilities for all system components, networks and data. All operator‐working
positions are identical in hardware and software and therefore provide the full functional
scope. Any number of working positions can be connected (upto 99, however Mumbai system
has two OWPs) and used simultaneously.
Technical Data :
– Intel processor‐based workstations
– Red Hat Linux Fedora OS
– X‐Window system, KDE Window Manager, Java based GUI
Main Functions :
– Provide an user‐friendly HMI to access system resources, configuration, messages and

queues.
– Support teamwork by means of a sophisticated resource‐sharing concept
– Allow efficient access control by individually configurable user profile
– Provide all system resources with simultaneous read access.
– Perform online check on all data entered
System control and operation
11.3.4. Connectivity :
AIDA‐NG (AMHS) supports all kind of protocols and network type, i.e., not only the primary
standard networks AFTN, CIDIN & AMHS, but also their variations such as SMTP, AFTN/X.25,
AFTN/TCP/IP, CIDIN TCP/IP, SITA‐B etc. The system has interoperability with ATN and AMHS
networks.

11.3.5. System Architecture :
11.3.6. AMHS User Terminal (CADAS):
The Comsoft’s Aeronautical Data Access System –CADAS, used as AMHS User Agent , is a web‐
based ATS user terminal system for AMHS that provides access facilities to all services related
to ATC and aeronautical data.
The CADAS AMHS user agent provides a full set of ICAO message forms for FPL and associated
messages, NOTAM messages as well as Meteorological messages. A built‐in field wizard assists
the user with message creation with online error check facility to ensure that no erroneous
message leave the AMHS UA. It also supports AMHS free text formats in line.
In addition to text messaging, the CADAS AMHS UA allows to send, receive, display file
attachments, such as documents and charts, which is of great benefit for daily operations
dealing with meteorological charts and AIP documents, Pre‐flight Information bulletins and
other ATS‐related information. It supports the daily work of an operator with both an address
book facility and access to national and international director services.
Total 25 nos. of AMHS User Agent terminal have been used in Mumbai AMHS at different
position, e.g., Notam, Briefing, ATS etc for daily work with different functionality.
The CADAS AMHS user agent runs on standard Windows and Linux PCs with several terminal
applications connected over X.400/P3/P7.
Terminal Access : One has to use the IE or Web browser to access CADAS home page address
(e.g. http://192.168.101.1, http://cadas.comsoft.de), and then choose the right terminal and
enter Username and Password for access to the terminal application.

11.3.7. Redundancy :
The system avoids shared hardware components as typically used in standard cluster solution,
rather major components are duplicated which gives the advantage of exclusion of single points
of failure. Power supply, disks and network adapters are also redundant.

Chapter – 12 Practical Exercise
CHAPTER – 12
PRACTICAL EXERCISE
The Exercises are designed in such a fashion that one can easily understand the subject instead
of playing with keyboard to access the different options of AMSS application by trial‐error
method.
DON’Ts :
Switch‐on or Switch‐off or works‐on the AMSS Server(s) and Database Server(s) without
the supervision of Instructor(s).
Switch‐off or use the AMSS TCP Server for exercise purposes.
Exploring the unwanted area(s) on workstation, which is not part of practical exercises
or not instructed by Instructor(s) to do so.
Submitting messages addressed to AAI Hqr (VIDD) and/or to YUYU/YUYC/YTYX
DOs :
• Shutdown the Workstation(s), following the shutdown procedures, before leaving the
AMSS Lab.
• Keep the desk, room clean as far as possible and keep the keyboard, mouse, books, and
chairs in order in right position before leaving the room.
12.1. Exercises
1. Familiarization with AMSS Setup
Go through the block diagram of AMSS and identify the Servers, Workstations, Switches etc and
their connectivity.
2. Switch‐off & Switch‐on Workstation
Before power‐off, close all the application(s) running, if any and shutdown the system.
Power‐on the system, it will boot the OS automatically, then press
<Ctrl>+<Alt>+<Delete>
to get into log‐in information, then check ‘User Name’ as ‘Administrator’ with blank password
and press OK.

3. Booking Application and Functions
Click the ‘Shortcut of Booking’ application on the desktop to run it.
a) Observe the main screen minutely‐ see the main menu, popup menu, left/right
windows, status bar etc.
b) Menu – ‘Adm’
Use it’s submenu to login, logout, create new login, change password etc.
CAUTION : Don’t change the password of Super‐user ‘sa’
c) Menu – ‘Mpu’
- Use submenu to save document
- Try few messages through AFTN Msg preparation template
d) Menu – ‘Stats’
Click on it, and check ONLY Local Rx/TX , SVC and SSPty to monitor incoming/ outgoing
messages, service messages etc. if any.
4. Practice on Service Messages
Create and submit different types of Service messages.
5. Practice on ATS Messages
Create and submit ATS messages like FPL, DEP, ARR etc through ‘Af’ free‐text format mode
ONLY
6. Practice on NOTAM Messages
Create and submit Notam messages through ‘Af’ mode only.
Use ICAO Doc.8126, if required.
7. Menu – ATC
Get familiar with sub‐menus and submit FPL through Flight Plan Message template in ‘F’ mode
etc.
8. Menu – Tbl
Create group address for lists of addressees
To activate, restart the application
Use ‘Af’ mode to sent message with the use of GI address created

9. Menu‐ NQry & InactiveNotam
Use it to display active Notams or inactive Notams etc.
10. Menu – Mqry
Use it to display METAR of a specified station, if available in Database.
11. Menu – Ntm
Use ‘N’ to prepare Notam through Notam Template.
NOTE : Only one machine will be available on ‘N’ mode.
12. Menu – Stats/Ac‐ TRACK
Use ‘Track’ to see details of distribution action taken by system on specified message(s).
13. Supervisory Functions (Ac)
HMSR – Display in/out messages
SysLRLS – LR/LS i.r.o. all channels on that time
TxnQ /RejQ – Display Messages in Queue.
Cmd – Commands on Circuit / Route Control
CAUTION : Don’t use any command of other CMD Group without the guidance of Instructor(s).
14. Printer
To set serial printer: Run – mode com1 9600,n,8,1 etc.

Paper feeding in printer
Taking print‐out of desire message
15. Others as per requirements, if any
END

Digrams

Amss Ops Pli PDF

Uploaded by

Amss Ops Pli PDF

Uploaded by

Document No.

“To develop the

CHIEF INSTRUCTOR (CNS),

We are Committed to Achieve Excellence

Chapter Chapter Name Page

Civil Aviation Training College, Allahabad, India Page 1

Civil Aviation Training College, Allahabad, India Page 2

Civil Aviation Training College, Allahabad, India Page 3

Civil Aviation Training College, Allahabad, India Page 4

Civil Aviation Training College, Allahabad, India Page 5

Civil Aviation Training College, Allahabad, India Page 6

Civil Aviation Training College, Allahabad, India Page 7

Civil Aviation Training College, Allahabad, India Page 8

Civil Aviation Training College, Allahabad, India Page 9

Civil Aviation Training College, Allahabad, India Page 10

Civil Aviation Training College, Allahabad, India Page 11

Civil Aviation Training College, Allahabad, India Page 12

Civil Aviation Training College, Allahabad, India Page 13

Civil Aviation Training College, Allahabad, India Page 14

Civil Aviation Training College, Allahabad, India Page 15

Civil Aviation Training College, Allahabad, India Page 16

Civil Aviation Training College, Allahabad, India Page 17

Civil Aviation Training College, Allahabad, India Page 18

Civil Aviation Training College, Allahabad, India Page 19

Civil Aviation Training College, Allahabad, India Page 20

Civil Aviation Training College, Allahabad, India Page 21

Civil Aviation Training College, Allahabad, India Page 22

Civil Aviation Training College, Allahabad, India Page 23

Civil Aviation Training College, Allahabad, India Page 24

Civil Aviation Training College, Allahabad, India Page 25

Civil Aviation Training College, Allahabad, India Page 27

Civil Aviation Training College, Allahabad, India Page 28

Civil Aviation Training College, Allahabad, India Page 29

Civil Aviation Training College, Allahabad, India Page 31

Civil Aviation Training College, Allahabad, India Page 32

Civil Aviation Training College, Allahabad, India Page 33

Civil Aviation Training College, Allahabad, India Page 34

Civil Aviation Training College, Allahabad, India Page 35

5.1. Structuring and Punctuation in ATS Message

Symbols Signal Name Remarks

All Fields except Field 3 shall

Separation of elements within

Last Field of ATS message

Civil Aviation Training College, Allahabad, India Page 36

5.2. ATS Message Category – Type – Designator – Fields

S.No. Category Type of Message Designator Field Type Numbers

10 Estimate Message EST 3, 7, 13, 14, 16

Civil Aviation Training College, Allahabad, India Page 37

5.3. Field Type and Data

Field Type Data

2 Not currently used

3 Message type, number and reference data

4 Not currently used

6 Not currently used

7 Aircraft Identification and SSR Mode and code

8 Flight Rules and Type of flight

9 Number and type of aircraft and wake turbulence Category

10 Equipment and capabilities

11 Not currently used

12 Not currently used

13 Departure aerodrome and Time

16 Destination aerodrome and total estimated elapsed

17 Arrival aerodrome and time

20 Alerting search and rescue information

21 Radio failure information

Submission of the Flight Plan:-

Civil Aviation Training College, Allahabad, India Page 38

5.4. Description of Fields

5.4.1. Field Type 3 (MESSAGE TYPE, NUMBER & REFERENCE DATA)

 A) Message type : Three letters.

5.4.2. Field Type 5 (DESCRIPTION OF EMERGENCY)

 Phase of Emergency : One of the following words INCERFA or

Example : -ALERFA/VABFBZQZX/REPORT OVERDUE

 Aircraft Identification : Not more than 7 alphanumeric characters without hyphens or

Civil Aviation Training College, Allahabad, India Page 39

This field may be terminated after element after aircraft identification