7754 Vol 2 Flyleaf - ICAO Public Maps

) provide advance boundary information and
revisions thereto for the next ATC unit;
c) update the basic flight plan data in the receiving ATC
unit with the most recent information; and
d) pre-activation of the flight plan in the next ATC
unit where the flight time from the departure aerodrome
to the COP is less than that which would be required
to comply with the agreed time parameters for
ACT message transmission.
Message format
ATS field Description
3 Message type and serial number — elements
(a) and (b)
7 Aircraft identification — elements (a), (b)
and (c)
13 Departure aerodrome — element (a)
14 Boundary estimate data — elements (a), (b)
and (c)
16 Destination aerodrome — element (a)
22* Amendment
* Field Type 22 will contain the following fields:
8 1 Flight rules and type of flight
9 Number, type of aircraft and wake turbulence
category — elements (b) and (c) and, if
required, element (a)
10 1 Equipment
15 1,2 Route
18 1 Other information
1. Optional fields to be included in Field Type 22 as agreed
2. If Field Type 15 is included in an PAC message, it shall, as a
f Agreement, one route element after the COP which are known to both ATC
located within the area of responsibility of the transmitting ATC unit.
Example
(PACN/ZLM012-NAF30/A4610-EHTW-RKN/1002F050-
EDDL-8/IM-9/FK50/M-15/NO270F050 RKN DCT DUS)
Revision (REV)
Purpose
20. The REV message shall be used to transmit
changes to previously sent and acknowledged transfer
conditions which had been sent in an ACT message.
Operational requirement
21. The REV message shall provide for revision of
previously sent and acknowledged ACT messages.
Message format
ATS field
Example
Description
3 Message type and serial number — elements
(a), (b) and, if bilaterally agreed, (c)
7 Aircraft identification — element (a)
13 Departure aerodrome — element (a)
14 Boundary estimate data — elements (a), (b)
and (c) and may include elements (d) and (e)
if bilaterally agreed
16 Destination aerodrome — element (a)
(REVAM/ZLC033AM/ZLC032-KL221/A2104-
EHAM-ARKON/0752F170-EDDL)
Application status messages
Logical acknowledgement message (LAM)
Purpose
22. A LAM, which is mandatory, shall be generated
and transmitted as an acknowledgment for each message
received and correctly processed. The creation and transmission
of a LAM shall mean unequivocally that the corresponding
message has been received correctly and processed
successfully and that the appropriate working position will
be provided with the results of the processing. A LAM shall
not be acknowledged.
Operational requirement
23. In respect of coordination messages, the LAM