曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
element in the field. The rules for the inclusion or omission of
conditional elements are indicated in the field tables.
1.5 Structuring and punctuation
1.5.1 The beginning of the ATS data shall be indicated
on page copy by an Open Bracket ‘(’, which constitutes the
Message
category Message type
Message
type
designator
Emergency Alerting
Radio communication
failure
ALR
RCF
Filed flight plan
and associated
update
Filed flight plan
Modification
Cancellation
Delay
Departure
Arrival
FPL
CHG
CNL
DLA
DEP
ARR
Coordination Current flight plan
Estimate
Coordination
Acceptance
Logical acknowledgement
CPL
EST
CDN
ACP
LAM
Supplementary Request flight plan
Request supplementary
flight plan
Supplementary flight plan
RQP
RQS
SPL
Field
type Data
3 Message type, number and reference data
5 Description of emergency
7
8
9
10
Aircraft identification and SSR Mode and Code
Flight rules and type of flight
Number and type of aircraft and wake
turbulence category
Equipment
13
14
15
16
17
18
19
20
21
22
Departure aerodrome and time
Estimate data
Route
Destination aerodrome and total estimated
elapsed time, alternate aerodrome(s)
Arrival aerodrome and time
Other information
Supplementary information
Alerting search and rescue information
Radio failure information
Amendment
Appendix 3 A3-3
1/11/01
Start-of-ATS-Data Signal. This signal shall be used only as
the printed character immediately preceding the Message
Type Designator.
Note.— In teletypewriter operation using International
Telegraph Alphabet No. 2, the open bracket is transmitted as
the Figures Case of Signal No. 11. On some teletypewriter
machines, this will print as a symbol other than ‘(’, but this
variation will be local and of no consequence. Where higher
level codes are employed, the character printing as ‘(’ is
used.
1.5.2 The beginning of each field, other than the first,
shall be indicated by a single hyphen ‘–’, which constitutes the
Start-of-Field Signal. This signal shall be used only as the
printed character preceding the first element of ATS data in
each field.
Note.— In teletypewriter operation using International
Telegraph Alphabet No. 2, the single hyphen is transmitted as
the Figures Case of Signal No. 1. On some teletypewriter
machines, this will print as a symbol other than ‘–’, but this
variation will be local and of no consequence. Where higher
level codes are employed, the character printing as ‘–’ is
used.
1.5.3 Elements within a field shall be separated by an
oblique stroke ‘/’ (see Note 1), or a space (sp.) (see Note 2)
only where so prescribed in the field tables on pages A3-5 to
A3-29.
Note 1.— In teletypewriter operation using International
Telegraph Alphabet No. 2, the oblique stroke is transmitted as
the Figures Case of Signal No. 24. On some teletypewriter
machines, this will print as a symbol other than ‘/’, but this
variation will be local and of no consequence. Where higher
level codes are employed, the character printing as ‘/’ is
used.
Note 2.— In teletypewriter operation using International
Telegraph Alphabet No. 2, the space is transmitted as Signal
No. 31. Where higher level codes are employed, the character
which causes a space on page copy is to be used.
1.5.4 The end of the ATS data shall be indicated by a
close bracket ‘)’, which constitutes the End-of-ATS-Data
Signal. This signal shall be used only as the printed character
immediately following the last field in the message.
Note.— In teletypewriter operation using International
Telegraph Alphabet No. 2, the close bracket is transmitted as
Signal No. 12. On some teletypewriter machines, this will
print as a symbol other than ‘)’, but this variation will be
local and of no consequence. Where higher level codes are
employed, the character printing as ‘)’ is to be used.
1.5.5 When the standard ATS messages are prepared in
teletypewriter form, an Alignment Function (two Carriage
Returns followed by one Line Feed) shall be inserted:
a) prior to each of the fields so annotated in the reference
table on page A3-30;
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
Air Traffic Management 下(49)
