(
13
Message Type, Number
Aircraft Identification and SSR
Departure Aerodrome
– –
and Reference Data Mode and Code and Time
16
– Destination Aerodrome and Total Estimated Elapsed Time, Alternate Aerodrome(s)
)
2.3.5.2 Example
The following is an example of a departure message sent from a departure aerodrome, or from a parent unit handling
communications for a departure aerodrome, to each addressee of a filed flight plan message.
(DEP-CSA4311-EGPD1923-ENZV)
2.3.5.2.1 Meaning Departure message — aircraft identification CSA4311 — departed from Aberdeen at 1923 UTC — destination Stavanger.
2.3.6 Arrival (ARR) message
2.3.6.1 Composition
3 7
(
13
Message Type, Number
Aircraft Identification and SSR
Departure Aerodrome
– –
and Reference Data Mode and Code and Time
– 17 Arrival Aerodrome and Time
)
2.3.6.2 Example 1 The following is an example of an arrival message sent from the arrival aerodrome (= destination) to the departure aerodrome. (ARR-CSA406-LHBP-LKPR0913)
2.3.6.2.1 Meaning
Arrival message — aircraft identification CSA406 — departed from Budapest/Ferihegy — landed at Prague/Ruzyne Airport at 0913 UTC.
2.3.6.3 Example 2
The following is an example of an arrival message sent for an aircraft which has landed at an aerodrome for which no ICAO
location indicator has been allocated. The SSR Code would not be meaningful.
(ARR-HELI13-EHAM-ZZZZ1030 DEN HELDER)
2.3.6.3.1 Meaning Arrival message aircraft identification HELI13 — departed from Amsterdam — landed at Den Helder heliport at 1030 UTC.
2.4 Co-ordination messages
2.4.1 Current flight plan (CPL) message
2.4.1.1 Composition
3 7
(
8
Message Type, Number
Aircraft Identification and SSR
Flight Rules and
– –
and Reference Data Mode and Code Type of Flight
9
10
Type of Aircraft and
Equipment
–
–
Wake Turbulence Category
13
14
Departure Aerodrome
Estimate Data
–
–
and Time –
16
Destination Aerodrome and Total Estimated Elapsed Time, Alternate Aerodrome(s)
2.4.1.2 Example 1
The following is an example of a current flight plan message sent from Boston Centre to New York Centre on a flight which is en route from Boston to La Guardia Airport.
(CPL-UAL621/A5120-IS –DC9/M-S/CD –KBOS-HFD/1341A220A200A –N0420A220 V3 AGL V445 –KLGA –0)
2.4.1.3 Example 2
The following is an example of the same current flight plan message, but in this case the message is exchanged between ATC computers.
(CPLBOS/LGA052-UAL621/A5120-IS –DC9/M-S/CD –KBOS-HFD/1341A220A200A –N0420A220 V3 AGL V445 –KLGA –0)
Note.— The messages in Examples 1 and 2 are identical except that the Message Number of Example 2 does not appear in Example 1.
2.4.1.4 Meaning
Current flight plan message [with sending unit identity (BOS) and receiving unit identity (LGA), followed by the serial number of this message (052)] — aircraft identification UAL621, last assigned SSR Code 5120 in Mode A — IFR, scheduled flight — one DC9, medium wake turbulence category, equipped with standard communications, navigation and approach aid equipment for the route and SSR transponder with Modes A (4 096 code capability) and C — ADS capability — departed Boston — the flight is estimated to cross the Boston/New York “boundary” at point HFD at 1341 UTC, cleared by the Boston Centre at altitude 22 000 feet but to be at or above altitude 20 000 feet at HFD — TAS is 420 knots, requested cruising level is altitude 22 000 feet — the flight will proceed on airway V3 to reporting point AGL thence on airway V445 — destination is La Guardia Airport 中国航空网 www.aero.cn 航空翻译 www.aviation.cn 本文链接地址：Rules of the Air and Air Traffic Services(154)
