曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
conterminous U.S. ARTCC; e.g., for a proposed
flight from Sitka to Houston, address PAZAZQZX,
CZVRZQZX, and KZSEZQZX.
REFERENCEFAAO
JO 7110.65, Para 2-2-2, Forwarding Information.
6-3-3. IFR FLIGHT PLAN CONTROL
MESSAGES
(Pacific: Pacific Supplement.)
Transmit all proposed IFR flight plan messages to the
ARTCC within whose control area IFR flight is
proposed to begin.
a. Communications Functions. Flight plan data
messages shall be addressed to the computer only. All
other types of messages for ARTCC attention shall be
addressed to the Flight Data position only.
Acknowledgements for all numbered messages will
be received from the computer or the Flight Data
position indicating receipt by the ARTCC, but not
necessarily computer acceptance. (See TBL 6-3-1.)
b. Format.
1. Adhere to a fixed order of data. Do not exceed
the stated maximum number of characters or
elements allowed for each field in messages
addressed to an ARTCC computer. Flight plans filed
containing more than the stated character maximums
should be sent using the ARTCC flight data address.
2. AISR. One space character must be entered
at the end of each data field. The following
clarifications are presented:
(a) The first data field of a message need not
be preceded by a space.
TBL 6-3-1
ARTCC ID & Computer Flight Data
ARTCC ID Computer Flight Data
Albuquerque ZAB KZABZQZX KZABZRZX
Atlanta ZTL KZTLZQZX KZTLZRZX
Boston ZBW KZBWZQZX KZBWZRZX
Chicago ZAU KZAUZQZX KZAUZRZX
Cleveland ZOB KZOBZQZX KZOBZRZX
Denver ZDV KZDVZQZX KZDVZRZX
Fort Worth ZFW KZFWZQZX KZFWZRZX
Houston ZHU KZHUZQZX KZHUZRZX
Indianapolis ZID KZIDZQZX KZIDZRZX
Jacksonville ZJX KZJXZQZX KZJXZRZX
Kansas City ZKC KZKCZQZX KZKCZRZX
Los Angeles ZLA KZLAZQZX KZLAZRZX
Memphis ZME KZMEZQZX KZMEZRZX
Miami ZMA KZMAZQZX KZMAZRZX
Minneapolis ZMP KZMPZQZX KZMPZRZX
New York ZNY KZNYZQZX KZNYZRZX
Oakland ZOA KZ0AZQZX KZOAZRZX
Salt Lake ZLC KZLCZQZX KZLCZRZX
Seattle ZSE KZSEZQZX KZSEZRZX
Washington ZDC KZDCZQZX KZDCZRZX
(b) The last data field of a message need not
be followed by a space.
3. Each field of data is composed of one or more
elements. Discrete elements of information within a
field are separated by delimiters, generally slashes
(oblique strokes) or periods.
4. Messages addressed using an ARTCC flight
data address (KZRZX) are not processed by the
HOST computer. Response and/or interpretation of
these messages are dependent on flight data
personnel action. The prime consideration of these
types of messages, shall be the readability of the
transmitted data. The second, third, and fourth
character of the address shall be the same as the
ARTCC flight data address.
5. All domestic flight data processing computers
have the capability to return acknowledgments to
the source and, depending on local adaption, return
error messages and accept amendments. Notify the
2/14/08 JO 7110.10T
IFR Flight Plan Handling 6-3-3
appropriate ARTCC Data Systems Specialist or
Primary A position when it is suspected that a flight
plan has been erroneously rejected by the computer.
6. IFR flight plans specifying stopovers or
terminal area delays require separate messages be
sent to the appropriate ARTCCs for each segment.
Unless otherwise covered by a letter of agreement,
treat flight plans proposing special use airspace
delays in the same manner. Separate messages are
also required for any other en route delays if a change
of altitude stratum is proposed at the delay point. See
subpara 6-3-3c14(h)(1)[b] for delays not involving
a change of altitude stratum.
7. Some fields contain the necessary functions
to operate the computer data terminal adapters and are
designated by alpha characters. Do not separate these
fields with spaces.
c. For EAS FDP acceptance, the complete
message contents, the order of data, the number of
characters allowed within any data field or element,
and any associated operational procedures or
restrictions are as follows (as used here, field refers
to EAS FDP field and/xx refers to M1FC field):
NOTEOASIS.
Detailed operating instructions for processing
IFR Flight Plans are contained in the WINGS online help
and the WINGS System Users Guide.
1. Start of Message Code (Field A). No entry
requirement for AISR equipment. (New Line Key)
2. Preamble Line (Field B). Consists of
originator, priority, and addressee(s).
3. Originator Line (Field C). Consists of a
six-digit date-time group and the eight-character
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
FSS飞行服务站1(60)
