4.1.1 The various circumstances surrounding each known or suspected emergency situation preclude the specifi-cation of standard message types to provide for emergency communications, except as described in 4.1.2 and 4.1.3 below.
4.1.2 Alerting (ALR) messages
4.1.2.1 When an air traffic services unit considers that an aircraft is in a state of emergency as defined in Annex 11, Chapter 5, an alerting message shall be transmitted to any air traffic services unit that may be concerned with the flight and to the associated rescue co-ordination centres, containing such of the information specified in Appendix 3, Section 1, as is available or can be obtained.
4.1.2.2 When so agreed between the air traffic services units concerned, a communication relating to an emergency phase and originated by a unit employing automatic data-processing equipment may take the form of a modification message (as in 4.2.2.4), supplemented by a verbal message giving the additional details prescribed for inclusion in an alerting message.
4.1.3 Radiocommunication failure (RCF) messages
Note.— Provisions governing the action to be taken in the event of radiocommunication failure are set forth in Annex 2, 3.6.5.2, and in Part III, Section 17 of this document.
4.1.3.1 When an air traffic services unit is aware that an aircraft in its area is experiencing radiocommunication failure, an RCF message shall be transmitted to all subsequent ATS units along the route of flight which have already received basic flight plan data (FPL or RPL) and to the aerodrome control tower at the destination aerodrome, if basic flight plan data has been previously sent.
4.1.3.2 If the next ATS unit has not yet received basic flight plan data because it would receive a current flight plan message in the co-ordination process, then an RCF message and a CPL message shall be transmitted to this ATS unit. In turn, this ATS unit shall transmit an RCF message and a CPL message to the next ATS unit. The above process shall be repeated progressively from centre to centre up to the first ATS unit along the remaining route of flight to which basic flight plan data has already been sent.
4.2 Movement and control messages
4.2.1 Messages concerning the intended or actual movement of aircraft shall be based on the latest information furnished to air traffic services units by the pilot, the operator or his designated representative, or derived from ground-based radar.
4.2.2 Filed flight plan messages and associated update messages
4.2.2.1 Filed flight plan messages and associated update messages comprise:
—
filed flight plan messages (4.2.2.2)
—
delay messages (4.2.2.3)
—
modification messages (4.2.2.4)
—
flight plan cancellation messages (4.2.2.5)
—
departure messages (4.2.2.6)
—
arrival messages (4.2.2.7).
4.2.2.2 Filed flight plan (FPL) messages
Note.— Instructions for the transmission of an FPL message are contained in Appendix 2.
4.2.2.2.1 Unless repetitive flight plan procedures are being applied or current flight plan messages are being employed, filed flight plan messages shall be transmitted for all flights for which a flight plan has been submitted with the object of being provided with air traffic control service, flight information service or alerting service along part or the whole of the route of flight.
4.2.2.2.2 A filed flight plan message shall be originated and addressed as follows by the air traffic services unit serving the departure aerodrome or, when applicable, by the air traffic services unit receiving a flight plan from an aircraft in flight:
a) an FPL message shall be sent to the area control centre or flight information centre serving the control area or flight information region within which the departure aerodrome is situated;
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：Rules of the Air and Air Traffic Services(102)
