曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
IFPS, operators should therefore specify the relevant NAT centre(s) using the IFPS "extra address"
feature. Note that flight plans for flights not entering the IFPS zone will not be accepted by IFPS and
should therefore be sent directly to the relevant centre(s).
3.2 General Message Content
The letter “O” and the digit “0” are not interchangeable. Inappropriate use of these characters will
prevent the correct processing of the flight plan.
NORTH ATLANTIC MNPSA OPERATIONS MANUAL ATTACHMENT 4
NAT MNPS 105 Edition 2009
The line length must not exceed 69 character columns. Lines exceeding the Annex 10 maximum of
69 columns are invariably broken at that position by intervening AFTN communication centres,
without any regard for content, causing the creation of unintelligible fragments.
3.3 Field 3: Message Type
To be completed when the responsibility for originating flight plan messages has been delegated.
For filing of subsequent flight plans use either the “modification” (CHG) or “cancellation” (CNL)
format as outlined in ICAO DOC 4444.
Common Error:
It is common for CNL messages to be received without a subsequent FPL message. This is
equivalent to having received no flight plan at all. If an Airline Operator still intends to operate the
flight, another FPL must be sent.
Also note that there is no guarantee messages are received in the same order they are transmitted. If a
CNL (referring to a previous FPL) is sent and immediately followed by a new FPL it is quite
possible that the FPL arrives first and is then immediately cancelled by the delayed CNL.
Creative use of time stamps does not help, it is the arrival sequence rather than the time stamp that
determines how messages are processed. It is therefore recommended that a few minutes be allowed
to elapse between the CNL and a subsequent FPL.
Another common error occurs when using CHG messages. Transmitting only those parts of a field
that have changed is not acceptable because the new field will replace the entire contents of that field
in the original message.
3.4 Field 7: Aircraft Identification (ACID)
One of the following ACIDs must be included:
(a) The registration marking of the aircraft (e.g. EIAKO, 4XBCD, N2567GA)
(b) The ICAO designator for the aircraft operating agency followed by the flight identification
(e.g. KLM511, NGA213).
(c) The call sign determined by the military authorities if this will be used to identify the aircraft
during flight.
Common Errors:
The ACID must not exceed 7 characters. An ACID of more than 7 characters will invalidate the
message. Furthermore it will be impossible to manually correct the data as computer systems are
only designed to handle the ICAO stipulated maximum of 7 digit aircraft identification strings.
The hyphen, often used in the graphical representation of aircraft registration, is also used as the field
separator in all flight related ICAO messages and so must not be used in the flight plan ACID.
All-numeric ACIDs must be avoided. Even when the registration of a military flight is all numeric it
is expected to be preceded by the operating agency descriptor assigned to the military operator in
question.
3.5 Field 8: Flight Rules and Type of Flight
Flight Rules
Insert one of the following letters to denote the category of flight rules with which the pilot intends
to comply:
I if IFR;
V if VFR;
NORTH ATLANTIC MNPSA OPERATIONS MANUAL ATTACHMENT 4
NAT MNPS 106 Edition 2009
Y if IFR first
Z if VFR first
Specify in item 15 the point(s) where the change of flight rules is planned.
Type of Flight
Insert one of the following letters to denote the type of flight:
S if Scheduled Air Service;
N if Non-scheduled Air Transport Operation;
G if General Aviation;
M if Military;
X if the type of flight does not match any of the predefined categories.
Common Error:
It is imperative that the letter „X‟ is used when the type of flight does not match any of the
predefined categories. Failure to do so causes the message to fail processing.
3.6 Field 9: Number and Type of Aircraft and Wake Turbulence category
Number of Aircraft
Insert the number of aircraft only when that number exceeds one, using two digits (e.g. 03).
Type of Aircraft
Insert the appropriate designator as specified in ICAO DOC 8643 – “Aircraft Type Designators”,
OR
If no designator has been allocated insert ZZZZ and specify in Item 18 the type of aircraft, using the
“TYP/…” sub-field and free text.
OR
In the case of flight plans covering more than one aircraft type, insert ZZZZ and specify in Item 18
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空翻译14(157)
