7754 Vol 2 Flyleaf - ICAO Public Maps

Level and speed information
10. All level information shall be specified as flight
level(s) or altitude(s) expressed in hundreds of feet. Speed
information shall be expressed as true airspeed in knots or
as a Mach number.
a) provide for acquisition of missing flight plan data;
b) provide advance boundary information and revisions
thereto for the next ATC unit;
c) update the basic flight plan;
d) facilitate early correlation of radar tracks; and
MESSAGE REFERENCE
Message numbering
11. All messages shall contain a 3-digit serial number
in field type 3. This number will run from 001 to 000
(representing 1 000) inclusive and will reset to 001 on
passing 000.
12. All data processing systems should be capable of
checking the continuity of numbers on a per interface basis
and of initiating notification of discrepancies.
Direction indicators
13. All messages shall contain direction indicators
immediately preceding the serial number. The list of unit
identifiers to be used is contained in Supplement B to Part
VI of the EUR ANP.
MESSAGES
Notification messages
Advanced boundary information (ABI)
Purpose
14. The ABI message, which is mandatory, shall
systematically precede an ACT message and shall be used
to give advance information on flights. It shall be
transmitted at a bilaterally agreed time or position before
the common boundary. Significant changes to a previously
transmitted ABI shall be carried out using another ABI.
e) allow accurate short-term sector load assessment.
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
bilaterally.
2. If Field Type 15 is included in an ABI message, it shall, as a
minimum, include the COP as agreed in the Letter of
Agreement, one route element before the COP and one route
element after the COP which are known to both ATC systems.
Normally the route point before the COP is located within the
area of responsibility of the transmitting ATC unit.
Operational requirement
15. The ABI message shall satisfy the following
operational requirements during the flight notification phase
and before the ATC coordination phase:
Coordination messages
Example
(ABIAM/ZLC031-KL221/A2104-EHAM-
ARKON/O740F190-EDDL-8/IS-9/B737/M-10/S/C)