V AI:N1234 AT:C150 TS:90 DD
SM TM1800
AE:65 RTSM..OMA..LNK
AD
NK TE:0300 RM
FP KIKKYFYX
JO 7110.10T 2/14/08
6-2-5 Flight Plan Proposals
FB:0330 AA: PD:JOE PILOT
HBSM NB: CR:R/W TL:
OP:
CP:KFODYFYX
TA:2100
NOTE1. M1FC will autoaddress the CP field, automatically
extract the required items from the flight plan mask and
transmit a flight proposal to the departure tie-in
AFSS/FSS.
M1FC will automatically fill in the originator of the flight
plan in the RM field when the flight plan is transmitted.
2. For civil flight movement messages with remarks,
precede the remarks with a dollar symbol ($).
3. OASIS will autoaddress the Closure Points field,
automatically extract the required items from the flight
plan, insert the originator of the flight plan into the
Remarks field, and transmit a flight proposal to the
departure tie-in AFSS/FSS at a time determined by the
facility parameter.
6-2-3. ENTRY OF MILITARY IFR MULTI-
LEG STOPOVER FLIGHT PLAN
a. Complete all FP fields down through time en
route or remarks for the first leg. Use MI in the flight
rules field. This will hold the flight plan on the
proposed list for flight notification.
b. All subsequent legs shall be preceded by a slant
and recorded in the route field after the first leg:
DESTINATION, ETE, AIRSPEED, P-TIME, ALTI-
TUDE, ROUTE, and remarks for each leg.
c. After all legs have been recorded properly, the
FP should autoaddress the ARTCC of the first leg
departure point in the OP: field and all destination
BASOPS stations in the CP: field. GI will send the
first leg to the appropriate ARTCC and place the
flight plan on the proposed list.
EXAMPLE-
M1FC
FR:MI AI:BAT21 AT:F16/R TS:450 DDBQ TM1700
AE:280
RTBQ..TNU..OFF/FOE 0+15 450 P1800 270
OFF..FOE
AD:OFF TE:0030 RM:*REMARKS $VT012115
FB:0230 AA: PD:ON FILE BASOPS
HBBQ NB:1 CR:OD TL: OP:ZCG
CP:KOFFYXYX KFOEYXYX
TA:1730
d. To send the second leg of the flight plan to the
appropriate ARTCC, the original flight plan needs to
be altered.
1. Display the flight plan (FPC).
2. Change the MI to I. It is not necessary to hold
this leg for flight notification.
3. Make the necessary changes to indicate the
next leg of the flight plan.
EXAMPLE-
M1FC
FR:I AI:BAT21 AT:F16/R TS:450 DD:OFF TM1800
AE:270
RT:OFF..FOE
AD:FOE TE:0015 RM:*REMARKS
FB: AA: PD:ON FILE BASOPS
HB.DBQ NB:1 CR:OD TL: OP:ZCP
CP:
TA:1815
NOTE-
If there is an additional leg, it must be taken from the
original flight plan.
e. After all legs have been sent to their appropriate
ARTCC, construct a flight notification message.
1. Retrieve the original flight plan from the
proposal list.
2. Edit each leg preceded by a slant to indicate
the destination, ETE and pertinent remarks.
3. Delete all other information and restore to the
proposal list (STPM) and await activation.
EXAMPLE-
M1FC
FR:MI AI:BAT21 AT:F16/R TS:450 DDBQ TM1700
AE:280
RTBQ..TNU..OFF/FOE 0+15
AD:OFF TE:0030 RM:*REMARKS $VTO12115
FB:0230 AA: PD:ON FILE BASOPS
HBBQ NB:1 CR:OD TL:
OP:ZCG
CP:KOFFYXYX KFOEYXYX
TA:
NOTE-
OASIS. Transmit only the applicable inbound and
outbound flight notification information to intermediate
tie-in facilities. Remarks common to all flight segments
shall be entered in the Remarks text box for transmission.
These remarks shall include: departure point, all stops
and destination.
EXAMPLE-
DEPD TCM LNDG EDW DMA JAX ADW
7/31/08 JO 7110.10T CHG 1
JO 7110.10T 2/14/6-2-6 Flight Plan Proposals
NOTE-
OASIS. Detailed instructions for the processing of
Military IFR Multi-Leg Stopover Flight Plans are
contained in the WINGS online help and the WINGS
System Users Guide.
6-2-4. ENTRY OF MILITARY VFR
STOPOVER FLIGHT PLAN
a. File a military VFR stopover flight plan in the
same format as a military IFR stopover.
b. After the flight plan is filed on the proposal list,
display the flight plan (FP ACID). Use the CX
keyword to cancel the flight plan. The complete flight
plan is then on file for search and rescue.
EXAMPLE-
M1FC
FR:MV AI:G2034 AT:UH1/U TS:90 DD:FOD TM1800
AE:055
RT:FOD..DSM..OFF/MLC 3+10 90 P2100 045
OFF..MLC/SZL
2+10 90 P0100 055 MLC..SZL
AD:OFF TE:0200 RMVT010600
FB:0400 AA: PD:ON FILE BASOPS
HBBQ NB:1 CR:O/D TL:
OP:
CP:KOFFYXYX KMLCYFYX KSZLYXYX
TA:2000
c. After the flight plan is cancelled, use the FPC
keyword to display the flight plan on the screen.
Change the RT field to show only the destination,
ETE, and any pertinent remarks for all remaining
legs. File the revised version onto the proposal list to
await activation.
EXAMPLE-
M1FC
FR:MV AI:G2034 AT:UH1/U TS:90 DD:FOD TM1800
AE:055
RT:FOD..DSM..OFF/MLC 3+10/SZL 2+10
AD:OFF TE:0200 RMVT010600
FB:0400 AA: PD:ON FILE BASOPS
HB:DBQ NB:1 CR:OD TL:
OP:
CP:KOFFYXYX KMLCYFYX KSZLYXYX
TA:2000
NOTE-
OASIS. Transmit only the applicable inbound and
outbound flight notification information to intermediate
tie-in facilities. Remarks common to all flight segments
shall be entered in the Remarks text box for transmission.
These remarks shall include: departure point, all stops
and destination.
EXAMPLE-
DEPD TCM LNDG EDW DMA JAX ADW
NOTE-
OASIS. Detailed instructions for the processing of
Military VFR Stopover Flight Plans are contained in the
WINGS online help and the WINGS System Users Guide.
3/15/07 7110.65R CHG 2 JO 7110.10T CHG 1 7/31/08
JO 7110.10T 2/14/08
6-3-1 IFR Flight Plan Handling
Section 3. IFR Flight Plan Handling
6-3-1. DOMESTIC IFR FLIGHT PLANS
a. IFR flight plans should consist of items 1
through 15 of FAA Form 7233-1. Items 1 through 11
shall be transmitted to the ARTCC as part of the IFR
flight plan proposal. Items 12 through 15 shall be
retained in the FSS and be available upon request.
NOTE-
Part-time FSSs shall forward items 1 through 15 in
accordance with para 6-1-4.
b. M1FC. IFR flight plans should consist of the
following fields:
1. FR Type of Flight.
2. AI Aircraft Identification.
3. AT Number and Type of Aircraft.
4. TS True Airspeed or Mach Number.
5. DD Departure Point.
6. TM Departure Time.
7. AE Requested Altitude.
8. RT Route of Flight.
9. AD Destination.
10. TE Time En Route.
11. RM Remarks.
12. FB Fuel on Board.
13. AA Alternate Destination.
14. PD Pilot Data.
15. NB Number of Persons on Board.
16. CR Color of Aircraft.
17. OP ARTCC Address.
18. CP Addresses/Closure Point.
19. TA Estimated Time of Arrival.
NOTE-
OASIS. IFR flight plans should consist of the same fields
as shown for M1FC. Flight plan items are entered into
labeled text boxes in the Flight Plan dialog box.
c. M1FC. Items 1 through 11 shall be transmitted
to the ARTCC as part of the IFR flight plan proposal.
Items 12 through 19 shall be retained by the FSDPS
and be available upon request.
NOTE-
OASIS. Items 1 through 11 shall be transmitted to the
ARTCC as part of the IFR flight plan proposal. Items 12
through 19 will be retained in a history file and be
available upon request.
. Con-
sists of two-to-seven characters followed by a space
character. The first character of the identification
must be a letter.
(a) Phrases such as Flynet, Snow Time, etc.,
which do not identify specific aircraft, but are
supplemental data defining a special mission or
function, shall be contained in remarks (Field
11/RM.
(b) For foreign aircraft identifications with a
numeric as the first character, insert an X as the first
character and explain in the remarks section.
8. Aircraft Data (Field 03/AT. Consists of
two-to-nine characters followed by a space
character. Aircraft data within the field may vary
from one-to-three elements consisting of:
(a) Number of aircraft (when more than one)
and/or the heavy aircraft indicator. For heavy aircraft
the indicator is “H/”. This element contains a
maximum of two characters followed by a slash.
EXAMPLE2/F15
3H/B52
10/F18
(b) Type of Aircraft. This elem ent is
mandatory and contains two-to-four characters
consisting of the authorized aircraft designator as
contained in FAAO JO 7340.2, Contractions. Enter
military designators of aircraft, omitting prefixes and
suffixes pertaining to aircraft mission or model.
(c) Equipment Suffix. This elem ent is
optional and consists of a slash (/) followed by one
letter which is one of the approved designators
identifying transponder and/or navigation gear.
9. Airspeed (Field 05/TS. Consists of two-tofour characters followed by a space character. This
field shall indicate the filed true airspeed in knots or
Mach number.
7/31/08 JO 7110.10T CHG 1
JO 7110.10T 2/14/08
6-3-4 IFR Flight Plan Handling
EXAMPLE350
M075
10. Departure Point or Coordination Fix (Field
06/DD. Consists of two-to-twelve characters
followed by a space character. This field contains the
departure point or fix at which an aircraft will pick up
IFR. It must be a fix, not an airway. For proposed
departures, it must match the first element in the route
of flight; and for IFR pickups, it must match either the
first element in the route of flight or the third element
if the ./. or VFR is used as the second element.
11. Proposed Departure Time (Field 07/TM.
Consists of five or seven characters followed by a
space character. This field contains the letter P
followed by a four or six digit time group in UTC.
12. Requested Altitude (Field 09/AE. Con-
sists of two-to-seven characters followed by a space
character. Altitudes or flight levels, as appropriate,
shall be expressed in hundreds of feet, but without
leading zeros. The letters OTP shall be entered in this
field to indicate a requested altitude of VFR
conditions-on-top. Blocked altitudes are indicated
by entering the lower altitude of the requested block,
the letter B, and the higher altitude of the block; e.g.,
80B100, 240B270, with no intervening spaces.
13. End of Line (New Line Key) (Field E). The
first occurrence of Field E shall always follow Field
09/AE: of the message. Any time a subsequent end of
line becomes necessary, if used within Field 10/RT:,
it must be preceded by the appropriate element
separator (not a space). If used within Field 11/RM:,
Field E may be entered at any point within the
remarks sequence.
14. Route of Flight (Field 10/RT). The route of
flight consists of departure point or pickup point
(PUP), the route of flight, and normally a destination
followed by a space character.
(a) Field 10/RT: is a fixed sequence field and
must begin with a fix; e.g., fix, airway, fix, airway,
etc. The last element may be a fix or one of the route
elements VFR, DVFR, or XXX (incomplete route
indicator). An element is separated from another
element by a period character.
(b) When consecutive fix elements or route
elements are filed, the fixed sequence format is
maintained by inserting two period characters
between the filed Field 10/RT: elements; e.g., fix..fix
or airway..airway.
(c) When a pilot files an airway..airway com-
bination, obtain the point of transition and insert it in
the transmitted flight plan; e.g., SGF.J105..J24.
STL.J24. The foregoing does not apply if the first
encountered fix happens to be the next filed junction
point within the route.
NOTE-
OASIS. Airway..airway combinations in the route of
flight require a defined junction (either five-character
alphanumeric, LOCID, or pre-defined fix-radial-dis-
tance.)
(d) The slash character (/) is used to file a
latitude/longitude fix or in describing an ETE.
(e) The maximum number of filed field
elements for computer-addressed flight plans is 40.
Double period insertions do not count against the
40-element limitation. Transmit flight plans filed
exceeding the route element limitation to the
ARTCC, not its computer.
(f) Fix Descriptions. A fix must be filed in
one of the following ways:
(1) Fix Name. Domestic, Canadian, and
International identifiers of two-to-five alphanumer-
ic characters.
(2) Fix Radial Distance (FRD). Consists of
eight-to-eleven alphanumeric characters in the
following sequence: Two-to-five characters identi-
fying a navigational aid, three characters of azimuth
expressed in degrees magnetic, and three characters
of distance expressed in nautical miles from the
navigational aid. Zeros preceding a significant
character shall be entered before the azimuth and
distance components as required to assure the
transmission of three characters for each.
(3) Latitude/Longitude. Consists of nineto-twelve characters entered as follows: The latitude
shall appear as the first component as four numbers
(trailing zeros required) with an optional letter N or
S appended. If the optional letter is omitted, north is
understood. Latitude shall be separated from
longitude with a slash (/) elem ent separator.
Longitude shall appear as the second component as
four or five digits (trailing zeros required, leading
zero optional) with an optional letter W or E
appended. If the optional letter is omitted, west is
understood.
JO 7110.10T 2/14/08
6-3-5 IFR Flight Plan Handling
(4) Navigation Reference System (NRS)
Waypoints. NRS waypoints consist of five alphanu-
meric characters, which include the ICAO Flight
Information Region (FIR) identifier, followed by the
letter corresponding to the FIR subset (ARTCC area
for the contiguous U.S.), the latitude increment in
single digit or group form , and the longitude
increment.
EXAMPLE“KD34U”
(g) Route Descriptions. A route must be filed
in one of the following ways:
(1) Airway. The official airway designator
must be filed.
(2) Coded Routes. Coded routes are a
shorthand method of describing a route segment or
segments which may have an altitude profile
described, an adapted airspeed within the route,
reentry or loop routes as an option, or a time delay at
a fix within the route as an option. Some of the
principal uses of coded routes are as follows:
[a] Instrument Departures (DP). DP, if
used, must be filed by the computer code designator
as the second element of Field 10/RT and followed by
the transition or exit fix.
Standard Terminal Arrivals (STAR).
STAR, if used, must be filed by the computer code
designator as the next to last element of Field 10/RT:
and be immediately preceded by the entry or
transition fix.
[c] Published Radials. Published radials
(e.g., within a preferred route) are considered
airways. Do not file unpublished radials.
EXAMPLE.JFK053..DPK017
.RBV020
[d] Military Routes. Certain military
routes (e.g., Military Training Routes (MTR) and Air
Refueling Tracks/Anchors), are considered coded
routes. The route designator must be preceded and
followed by the entry and exit fixes in terms of
fix/radial/distance (FRD), and reentry information
may be suffixed to certain military coded routes as
follows:
[1] The entry and exit fix must be
associated with a fix on the route, and the entry fix
must be prior to the exit fix on the route.
EXAMPLE-
TNP355025..IR252
PKE107012
[2] Routes having reentries for a single
Strategic Training Range (STR) site shall contain the
entry of alternate entry fix in terms of FRD, the route
designator followed immediately by a plus sign (+),
either the letter R (1st STR site) or S (2nd STR site),
and a digit indicating the number of reentries.
EXAMPLE(FRD) IR240+R2 (FRD)
(FRD) IR240+S3 (FRD)
[3] Routes having reentries for two
STR sites shall contain the entry/alternate fix in terms
of FRD, the route designator followed immediately
by a plus sign (+), the letter R, and a digit indicating
the number of reentries on the first STR site,
immediately followed by second plus sign (+), the
letter S, and a digit indicating the number of reentries
on the second STR site.
EXAMPLE(FRD) IR240+R2+S3 (FRD)
[4] STR routes must be entered and
exited at the respective primary fix. Alternate STR
routes must be entered/exited at the alternate entry/
exit fix. The routes must be identified by an
individual name.
EXAMPLE(FRD) IR240+R2 (FRD) (Primary)
(FRD) IR240A+R2 (FRD) (Alternate)
[e] North American Routes (NAR).
NAR routes are numerically coded over existing
airways and route systems from and to specific
coastal fixes serving the North Atlantic.
EXAMPLE.NA9
.NA50
[f] Stereo Routes. A stereo route must
specify a prestored stereo tag. An FP message may be
entered with a stereo tag as the only Field 10/RT:
entry, which causes the Field 10/RT: data stored for
the stereo tag to be substituted for the stereo tag and
processed as the filed Field 10/RT: Additionally, the
filed departure point (Field 06/DD must agree with
the stored departure point.
[g] Incomplete Route Indicator (XXX).
When XXX, the incomplete route indicator, appears
in Field 10/RT, the element preceding the XXX
element must be a fix.
JO 7110.10T 2/14/08
6-3-6 IFR Flight Plan Handling
[h] Visual Flight Rules (VFR) or De-
fense Visual Flight Rules (DVFR) element. When
VFR or DVFR is the second element of Field 10/RT:,
the filed fix following VFR or DVFR must be internal
to the ARTCC's area to whom the flight plan was
initially submitted. When VFR or DVFR is other
than the second element in Field 10/RT:, the element
preceding the VFR or DVFR must be a filed fix.
(h) Fix Suffix.
(1) En Route Delay Suffix consists of an
element separator (/), followed by the letter D,
followed by the hours and minutes separated by a plus
sign (+). Must be appended to a fix.
EXAMPLE.STL/D1+30
.PKE107012/D2+05
Use of this suffix is limited to the following cases:
[a] Aerial Refueling Tracks and An-
chors. The suffix is appended to the entry fix.
EXAMPLE.ICT248055/D0+30.AR330
En route delays not involving a
change of altitude stratum and not involving a
stopover, terminal area delay, or special use airspace
delay unless specifically covered by a letter of
agreement with the receiving ARTCC.
(2) Estimated Time En Route (ETE)
Suffix. Consists of an element separator (/) and four
digits appended to the destination. Leading zeros are
required, and the time en route is expressed in hours
and minutes.
EXAMPLE.STL/0105
(i) A period is not required after the last
element of Field 10/RT:. If remarks (Field 11/RM
are present, a space is required after the last element
of Field 10/RM:. If remarks are not present, no space
is required and Field F (End of Message) should be
the next entry.
15. Remarks (Field 11/RM. Consists of the
appropriate remarks code character and the remarks.
Remarks are considered mandatory or optional and
should be limited to those pertinent to air traffic
control. Spaces are permitted within the remarks field
to separate words or contractions.
(a) Mandatory Remarks. These remarks shall
be transmitted in Field 11/RM: whenever a pilot files
the information on the flight plan. A mandatory
remark is required whenever there is a modification
to the flight plan by the specialist.
(1) If it is necessary to make modifications
to the filed route of flight for the purpose of achieving
computer acceptance of the input due, for example, to
correct a fix or an airway identification, “FRC,”
meaning “Full Route Clearance Necessary,” or
“FRC/(fix),” will be added to the remarks, “FRC” or
“F RC/(fix)” must always be the first item of
intra-center remarks. When “FRC” or “FRC/(fix)”
appears on a flight progress strip, the controller
issuing the ATC clearance to the aircraft shall issue a
full route clearance to the specified fix, or if no fix is
specified, for the entire route. “FRC” or “FRC/(fix)”
shall always be first in Remarks (Field 11/RM:).
NOTE-
INPUT OPERATORS ARE LIMITED TO MAKING ONLY
THOSE CHANGES REQUIRED FOR COMPUTER
ACCEPTANCE. Modifications, such as those to conform
with traffic flows and preferred/recommended routings,
shall only be made by the pilot or his/her operations office
or the controller responsible for initiating the clearance
to the aircraft.
(2) When a pilot files an FAA-assigned
three-letter company designator, the authorized
radiotelephony call sign must be included in the
remarks field.
(b) Optional Remarks. These remarks shall
be transmitted when pertinent to air traffic control
and can revert to mandatory status for some military
flight plans.
(1) In the case of applicable military
flights, NOPAR shall be the first item in Remarks
(Field 11/RM:).
(2) Remarks for military flight plans filing
an IR route must contain the IR route designator,
entry time prefaced by the letter E, exit time prefaced
by the letter X, and MARSA when applicable.
Remarks for flight plans filing a terminal area delay
must contain the airport identifier at which the delay
will occur, followed by the letter D, followed by the
duration of the delay in hours plus minutes, followed
by the destination airport. These should be the initial
item s in the rem arks field, unless subpara
6-3-3c15(a)(1) or (2) applies, and should be in order
of occurrence.
JO 7110.10T 2/14/08
6-3-7 IFR Flight Plan Handling
16. End of Message Function (Field F).
Consists of enter function.
d. Additional Messages. The following messages
are eligible for input to ARTCC computers via
Service B, in addition to the Flight Plan (FP)
message:
1. Remove Strips (RS). The purpose of the RS
message input is to advise the computer that data on
a particular flight is no longer valid and in effect
cancels the flight plan and removes it from computer
storage.
(a) Eligibility. RS messages may be entered
only for flight plans which:
(1) Are proposed flights.
(2) Have been previously entered by the
same source entering the RS message.
(3) The flight plan is inactive; e.g., a
departure strip must not yet have been printed.
Otherwise, the following rejection message is
returned: “REJECT--NOT YOUR CONTROL.”
(b) Format. Fields 01 (Message type) and
02/AI: (Aircraft Identification) are required.
EXAMPLE-
RS TWA138
2. Amendment Message (AM). The purpose of
the AM message is to change data previously stored
in the host computer.
(a) Eligibility. Same as for the Remove Strip
(RS) message (above).
(b) Format. AM messages sent to the host
computer must follow a specific format. First, the
field to be amended must be identified, then the
amended information given. The host computer
recognizes the following fields by either number or
name: (See para 6-3-2.)
TBL 6-3-2
Field Number and Name
Field Field Number
Field
Name
Aircraft Identification 02 AID
Aircraft Type 03 TYP
Speed 05 SPD
Departure/Coordination Pt. 06 FIX
Proposed Time 07 TIM
Altitude 09 RAL
Route of Flight 10 RTE
Remarks 11 RMK
(c) Restrictions.
3. If Field 02/AI: is to be amended, no other
field may be amended in the same message. If Field
02/AI: and other fields are to be amended, send an RS
message and reenter the entire corrected flight plan.
If an attempt is made to amend Field 02/AI: within a
multiple amendment message or to amend Field 02
to M, the following rejection message is returned:
“REJECT--INVALID AMENDMENT.”
NOTE-
Alternate procedure is to send two amendments - the first
amends field 2; the second amends the other field or fields.
4. Field 07/TM: Amendments. An attempt to
amend Field 07/TM: to anything other than a P-time
is not allowed. If such an amendment is attempted,
the following error message is returned:
“COFIE INVALID TIME PREFIX.”
5. Amendment to Fields 06/DD:, 07/TM:, and
10/RT: Where Fields 06/DD:, 07/TM:, and 10/RT:
are amended with a single AM message, the
following rules apply:
(a) The amended Field 06/DD: replaces the
previously stored coordination fix (Field 06/DD:).
(b) The amended Field 07/TM:, with ap-
propriate letter prefix, replaces the previously stored
coordination time (Field 07/TM:).
(c) The amended route data (Field 10/RT:)
may completely replace the previously filed Field
10/RT: or may be merged with the filed Field 10/RT:.
(d) If the last element of the amended route
data is followed by a destination indicator (e), this last
element becomes the new destination fix.
(e) When amended route data is merged with
filed data, it replaces all data between the departure
point and the first nonamended element remaining in
the field. The last element of the amended data must
match the first element of the remaining nonamended
data, otherwise the following rejection message is
returned: “REJECT--(last element) CANNOT
MERGE.”
6. Amendment to Field 10/RT: Only. Except as
permitted above, a Field 10/RT: amendment must be
the only field amended; no other field may be
amended with the same message. Otherwise, the
following is returned: “REJECT--INVALID
AMENDMENT.”
JO 7110.10T 2/14/08
6-3-8 IFR Flight Plan Handling
EXAMPLE-
Mes-
sage
Type
Aircraft
Identifica-
tion
Field
to be
Re-
vised
New Field
Data
Field
to be
Re-
vised
New
Field
Data
AM TWA179 07 P0800 08 350
AM UAL466 07 0300
AM AAL4355 10 ORD.J60
.DEN
7. Correction Message (CM). When the host
computer detects an error in a flight plan, an error
message is generated to the sender when the sender
is within the departure ARTCC's adapted boundaries.
NOTE-
These procedures do not apply to OASIS facilities.
(a) Eligibility. CM messages may be entered
only for the period for which the departure ARTCC's
program is adapted, normally 5 minutes. After that
time, the flight plan in error drops out to the ARTCC
Primary A position for reentry. The sender has
primary responsibility for corrective action.
NOTE-
Error messages are generated only on messages from
sending stations within the adaptation parameters of the
departure ARTCC and for only that portion of the route
within that ARTCC's adapted boundaries. Other flight
plans in error are referred to a Primary A position.
(b) Format. Responses to error messages
shall be transmitted in the form of a CM message
within the time parameters adapted for your ARTCC.
ARTCC-Generated Error Message:
EXAMPLE-
Sending
Facility
MSG
Type
MSG
NR
Field in
Error
Data in
Error
Reason
DCA Error 123 08 9A FORMAT
CM Format:
Field 00 MSG Type Correct Data
DCA 1820123 CM 090
(c) When a CM message in response to an
error message results in any change to a pilot-filed
Field 06/DD: (Departure Point) or Field 10/RT:
(Route of Flight) once the flight plan has been
accepted, an AM message shall be sent to add a field
11/RM: intra-ARTCC remark. In remarks, insert
“FRC PILOT FILED (original data).”
(d) Should a “NOT YOUR CONTROL”
response be received, do not retransmit the flight plan
or the AM. Confirm ARTCC receipt of the flight plan
or AM (FRC/REMARKS) via interphone with the
Primary A position. (See TBL 6-3-3.)
TBL 6-3-3
Computer Flight Data Input
COMPUTER FLIGHT DATA INPUT CHART
Field Element Example Requirements
A Start of
Message
(SOM code)
New Line
Key
Required for
SOM
recognition.
B Preamble
Line
FF
KZFWZQZ
X
Provides
priority, and
addressee.
C Originator DTG
KMLCYFY
X
Required for
ending the
message header.
D End of Line (New Line
Key)
EOL.
E End of
Message
(Enter
Function)
End of Message.
6-3-4. COORDINATE RNAV ROUTES
a. When accepting flight plans containing coor-
dinate RNAV routes, ensure that the route of flight
after the departure fix is defined by latitude/longitude
coordinates and a fix identifier.
b. The arrival fix must be identified by both the
latitude/longitude coordinates and the fix identifier.
EXAMPLE-
(1) (2) (3) (4) (4) (5)
MIA SRQ 3407/10615 3407/11546 TNP LAX
1. Departure airport.
2. Departure fix.
3. Intermediate fixes defined by latitude/longi-
tude coordinates.
4. Arrival fix for the destination airport in terms
of both the latitude/longitude coordinates and the fix
identifier.
5. Destination airport.
JO 7110.10T 2/14/08
6-4-1 Flight Plan Handling
Section 4. Flight Plan Handling
6-4-1. FLIGHT PLAN ACTIVATION
a. AISR. Handle departure reports as a routine
radio contact in accordance with para 4-3-5, Routine
Radio Contacts. If a departure report has not been
received within 1 hour of the proposed departure time
and specific arrangements have not been made to
activate the flight plan, cancel and file the proposed
flight plan.
b. AFSS. Handle departure reports as a routine
radio contact in accordance with para 4-3-5.
1. M1FC. If a departure report has not been
received or the pilot has not amended the P time, a
VFR flight plan will remain on the proposed list until
2_hours past the proposed time. At this time it is
automatically removed from the list and entered on
the Aircraft Data File (DD).
2. OASIS. If a departure report has not been
received or the pilot has not amended the ETD, a VFR
flight plan will remain on the Proposed List for a
predetermined facility parameter time interval. After
this time it is automatically removed from the
Proposed List and entered into a history file.
c. The AFSS Aircraft Data File (DD) is used for
statistical and historical purposes. Movement
messages, pilot briefs, and aircraft contacts are placed
on the list automatically and are retained for the
number of hours specified in the Aircraft Drop
Interval (ADDI) parameter.
NOTE-
OASIS. The OASIS history files are used for statistical and
historical purposes. Movement messages, pilot briefings
and aircraft contacts are recorded in these files
automatically and are retained for 15 days.VU
TM1203 AE:85
RTVU..SLC..TWF..BOI
AD:BOI TE:0145 RMASMD DEP
FB: AA: PD:
NB: CR: OP:
CP:KBOIYFYX TA:1348
NOTE1. M1FC will automatically extract the required items
from the flight plan mask and transmit the flight
notification message when a departure time is placed in
the TM: field and the GI keyword is entered.
2. OASIS will automatically extract the required items
from the Flight Plan, format and transmit the flight
notification message when the flight plan is activated.
b. When the proposed flight plan is received from
another AFSS/FSS, BASOPS, or DUAT vendor, and
the departure station has only partial flight plan data,
add a remark indicating the Service B address of the
station holding the complete flight plan.
NOTE1. M1FC will automatically add this to the RM: field of
the flight plan mask when it receives the proposal from
another facility.
2. OASIS will automatically add this to the Remarks text
box of the flight plan dialog box when it receives the
proposal from another facility.
EXAMPLE-
AISR
FF KBOIYFYX
DTG KCDCYFYX
VFR N12345 C182/U PVU BOI 1958 $FP
KIADXCLX
M1FC
FR:V AI:N1234 AT:C182/U TS:130 DDVU
TM1813 AE:85
RTVU..BOI
AD:BOI TE:0145 RMFP KIADXCLX
FB: AA: PD:
NB: CR: OP:
CP: KBOIYFYX TA:19581800
AE:095
RT:FOD..OMA
AD:OMA TE:0050 RMFIRIV FOD
FB:0200 AA: PD:JOE PILOT
NB:2 CR:R/W OP:
CP:KOLUYFYX KFODYFYX TA:1850
NOTE-
M1FC/OASIS will autoaddress to the tie-in AFSS/FSS.
Because the pilot elected to FIRIV with FOD, the message
must also be manually addressed to FOD.
d. The station with which the pilot elects to close
the flight plan shall forward a numbered closure
message to the designated tie-in AFSS/FSS.
e. On civil flight plans, if the pilot advises of
stopover points, show these in remarks.
EXAMPLE-
AISR
FF KBOIYFYX
DTG KCDCYFYX
VFR N12345 C182/U PVU BOI 1958 $LNDG
TWF
M1FC
FR:V AI:N1234 AT:C182/U TS:130 DDVU
TM1813 AE:85
RTVU..SLC..TWF..BOI
AD:BOI TE:0145 RMLNDG TWF
FB: AA: PD:
NB: CR: OP:
CP:KBOIYFYX TA:1958
JO 7110.10T 2/14/08
6-4-3 Flight Plan HandlingECAL1 AT:T43/R TS:400 DD:SMF
TM2205 AE:330
RT:SMF..FMG..SLC..DEN..RCA
AD:RCA TE:0330 RMAP3NP3 S
FB: AA: PD:
NB: CR: OP:ZCO
CP:KRCAYXYX TA:0135
AISR
FF KBOIYFYX
DTG KCDCYFYX
VFR R54321 2/UH1/U SLC BOI 1943 $N
M1FC
FR:MV AI:R54321 AT:2/UH1/U TS:100 DD:SLC
TM1813 AE:45
RT:SLC..TWF..BOI
AD:BOI TE:0130 RMN
FB: AA: PD:
NB: CR: OP:
CP:KBOIYFYX TA:1943BQ
TM1700 AE:280
RTBQ..TNU..OFF/FOE 0+15/MLC 0+45
AD:OFF TE:0030 RM:*REMARKS
FB:0230 AA: PD:ON FILE BASOPS
NB:1 CR:OD OP:ZCG
CP:KOFFYXYX KFOEYXYX KMLCYFYX TA:1730
NOTE1. M1FC will autoaddress the CP: field, automatically
extract the required items from the flight plan mask, and
transmit a flight notification message to the destination
BASOPS. MV is used in the FR field when sending a
military VFR flight notification.
JO 7110.10T 2/14/08
6-4-4 Flight Plan Handling
2. OASIS will autoaddress, automatically extract the
required items from the flight plan dialog box, and
transmit a flight notification message to all required
facilities.VU TM1900
AE:105
RT:SLC..TWF..MLD..LWS..GEG
AD:GEG TE:0330 RMOVR SLC 1900 ORIG
DESTN BOI
FB: AA: PD:
NB: CR: OP:
CP:KBOIYFYX KSEAYFYX TA:2230
IFR Change of Destination:
AISR
FF KRCAYXYX KTIKYXYX KRIUYFYX
DTG KCDCYFYX
IFR DECAL01 T43/R SMF TIK 0230 $AP3NP3S OVR
SLC 2330 ORIG DESTN RCA
M1FC
FR:MI AIECAL1 AT:T43/R TS:400 DD:SMF
TM2330 AE:310
RT:SMF..SLC..GJT..AMA..OKC
AD:TIK TE:0300 RMNP3 S OVR SLC 2330 ORIG
DESTN RCA
FB: AA: PD:
NB: CR: OP:
CP:KRCAYXYX KTIKYXYX KRIUYFYX TA:0230
NOTE1. M1FC. On VFR flight plans, M1FC will transmit and
file the flight plan with the TS: and AE: fields blank. On
IFR flight plans, these fields must be completed. If the TS:
and AE: are unknown, 2 or 3 zeros may be used instead.
2. OASIS. If the Flight Plan dialog box is used to transmit
VFR flight plans, OASIS will transmit and file the flight
plan with the airspeed and en route altitude text boxes
blank. For military IFR change of destination, use the
General Facility Message to transmit changes to the
closure points.VU
TM1940 AE:105
RT:SLC..TWF..MLD..LWS..GEG
AD:GEG TE:0330 RMCNLD IFR OVR TWF
FB: AA: PD:
NB: CR: OP:
CP:KSEAYFYX TA:2310
NOTE-
Obtaining the name of the original flight plan source may
provide additional information if the aircraft becomes
overdue.
c. Military Change from IFR to VFR or VFR to
IFR. When a military aircraft changes from IFR to
VFR, or VFR to IFR, or requests that other
significant information be forwarded, transmit this
information to the destination station.
EXAMPLE-
AISR
FF KTIKYXYX
DTG KDENYFYX
DECAL01 CHGD TO VFR RON
M1FC
ORIGINEN PRECEDENCE:FF TIME: ACK:N
ADDR:KTIKYXYX
TEXTECAL01 CHGD TO VFR RON
6-4-9. CHANGE IN ETA
When an aircraft wants to change its estimated time
en route (ETE), facilities shall secure a new estimated
time of arrival (ETA) and forward the information to
the destination tie-in station as a numbered message.
The destination tie-in station shall acknowledge and,
thereafter, use the new ETA as the standard for any
necessary follow-up action; e.g., QALQ message.
EXAMPLE-
AISR
FF KSEAYFYX
DTG KBOIYFYX
BOI001 SEA
N34567 E2140
M1FC
ORIGIN:BOI PRECEDENCE:FF TIME: ACK:Y
ADDR:SEA
TEXT:N34567 E2140
NOTE1. M1FC. M1FC will automatically acknowledge the
message, change the ETA on the flight plan and inbound
list, and store the message in the DD file without specialist
intervention.
2. OASIS. OASIS will automatically acknowledge the
message, update the ETA on the Inbound List, store the
message in the history file, and notify the specialist that
a Changed ETA message was received which matched an
active flight plan.
6-4-10. FLIGHT PLAN CLOSURE
Do not transmit arrival reports except under unusual
circumstances or in the following cases:
a. Transmit to any facility requested by the pilot,
arrival or any other information involving FAA or
Canadian MOT aircraft.
EXAMPLE-
AISR
FF KDCAYFYX
DTG KHHRYFYX
HHR002 DCA
N2 A0839 (Remarks, as appropriate)
M1FC
ORIGIN:HHR PRECEDENCE:FF TIME: ACK:Y
ADDRCA
TEXT:N2 A0839 (Remarks as appropriate)
b. For U.S. military aircraft, transmit arrival
reports to the departure station only when:
1. Requested by BASOPS.
2. Special military flights arrive.
c. When a pilot closes a flight plan with a station
that has not received a flight notification message,
obtain as a minimum, the departure point, the flight
planned destination point, and the station with which
the flight plan was filed.
1. If the station receiving the closure is the tie-in
station for the planned destination, transmit an arrival
message to the departure station with the remark
FPNO and the departure point and destination
identifiers. The departure station shall relay the
arrival information to the station holding the flight
notification message in the active file.
EXAMPLE-
AISR
FF KDCAYFYX
DTG KMIVYFYX
MIV001 DCA
N8567 A1745 FPNO PHF NMK
M1FC
JO 7110.10T 2/14/08
6-4-8 Flight Plan Handling
ORIGIN:MIV PRECEDENCE:FF TIME: ACK:Y
ADDRCA
TEXT:N8576 A1745 FPNO PHF NMK
2. If the station receiving the closure message is
not the destination tie-in station, transmit a closure
message to the destination tie-in station, including
the aircraft identification, the closure time, the
departure point, and destination. Remarks are
optional.
EXAMPLE-
AISR
FF KHUFYFYX
DTG KDAYYFYX
DAY003
N11ND C1217 LOU IND LNDD CMH
M1FC
ORIGINAY PRECEDENCE:FF TIME: ACK:Y
ADDR:HUF
TEXT:N11ND C1217 LOU IND LNDD CMH
NOTE1. M1FC. Closure and arrival messages do not process
automatically; manual intervention is required.
2. OASIS. OASIS automatically processes correctly
formatted closure and arrival messages. OASIS will
automatically remove the flight plan from the Inbound
List, store the message in the history file, and notify the
specialist that a Closed flight plan message was received
which matched an active flight plan.
6-4-11. MILITARY FLIGHTS TO/FROM U.S.
a. To U.S. If REQ ARR is in remarks, suspend the
flight plan until arrival information is received from
BASOPS and forward to the departure location.
b. From U.S. If requested by BASOPS, include
REQ ARR in remarks section of ICAO flight plan.
Terminate suspense action only after receipt of an
arrival message and delivery to BASOPS.
JO 7110.10T 2/14/08
6-5-1 Military Operations
Section 5. Military Operations
6-5-1. MILITARY TRAINING ACTIVITY
a. Military Training Routes (MTR).
1. Unless otherwise covered in a letter of
agreement, the tie-in AFSS/FSS/ARTCC/BASOPS
for an MTR-scheduling activity shall transmit an
unnumbered NADIN message. Use the assigned
group code KAWP YFYX and for Alaska, use
KFSSYFAK KAWPYFYX. Transmit as a single
message whenever possible.
EXAMPLE-
AISR
FF ADDRESSES
DTG KDCAYFYX
IR104 1400-1440 60 AND BELOW
IR104 021530-021625 60 AND BELOW
M1FC
ORIGIN:FOD PRECEDENCE:FF TIME: ACK:N
ADDR: ADDRESSES
TEXT: IR505 1400-1600 60 AND BELOW
2. Multiple activities should be combined
chronologically by use time(s) and transmitted (not
more than 24 hours in advance) as a single message
using only the format shown in the example below.
EXAMPLE-
AISR
FF ADDRESSES
DTG KDCAYFYX
VR066 1330-1440 100 AND BELOW
IR104 1400-1440 60 AND BELOW
IR104 1545-1630 50 AND BELOW
VR066 1600-1655 30 AND BELOW
M1FC
ORIGN:FOD PRECEDENCE:FF TIME: ACK:N
ADDR: ADDRESSES
TEXT: IR505 1440-1640 60 AND BELOW
IR507 1700-1800 60 AND BELOW
NOTE-
Slow-speed, low-altitude training routes are not to be
transmitted, briefed on, or posted. The contraction VLAR
is not an approved contraction.
b. Military Operations Area (MOA).
1. Transmit MOA messages only when the use
times are other than what has already been published
or otherwise covered in a letter of agreement. The
controlling agency (usually an ARTCC) shall
transmit an unnumbered NADIN message. Use the
assigned group code KAWPYFYX and for Alaska,
use KFSSYFAK KAWPYFYX. Use only approved
MOA names as depicted in FAAO 7400.8 (DO NOT
USE ABBREVIATIONS).
EXAMPLE-
AISR
FF ADDRESSES
DTG KZKCZRZX
BISON MOA 1345-1550 ALT 025B180
2. Activity schedules should be combined and
listed chronologically by use time(s) and transmitted
(not more than 24 hours in advance) as a single
NADIN message using only the format shown in the
following example:
EXAMPLE-
AISR
FF ADDRESSES
DTG KZKCZRZX
BISON MOA 1345-1550 ALT 025B180
BISON MOA 1600-1645 ALT 060B180
HILLTOP MOA 1600-1715 ALT 100B180
HOWARD MOA 1600-0200 ALT 090B180
REDHILLS MOA 1700-1800 ALT 080B100
c. A VR operation may be filed as a composite
flight, IFR-VFR-IFR. Unless the BASOPS has the
capability to do so, the tie-in AFSS/FSS shall
transmit the IFR proposals in separate messages to
the appropriate ARTCCs in accordance with paras
6-3-1, 6-3-2, 6-3-3, and 6-3-4.
d. Information received from either the AFSS/
FSS/ARTCC/military scheduling activity or control-
ling agency that modifies an MTR and MOA
schedule shall be transmitted by an unnumbered
message via Service B as defined in subparas 6-5-1a
and b.
e. Special Use Airspace (SUA).
1. M1FC. Properly formatted IRs, VRs, and
MOAs are automatically placed on the list and the
0_queue. Messages are deleted from the list by
automatic cancellation. The list is displayed by use of
the following keywords: VM MO (ALL MOAs), or
VM (MOA NAME) MO, IR, VM (STATE IDENT;
i.e., VA) MO or VM IR, VM VR (ALL IRs or VRs),
or VM 1756 VR (route specific). The route must be
JO 7110.10T 2/14/08
6-5-2 Military Operations
a four-digit character. Three-digit routes must be
preceded by a zero.
2. OASIS. Properly formatted IRs, VRs and
MOAs are automatically stored and are displayed
using the Briefing functions. Messages are deleted by
automatic cancellation.
NOTE-
The above procedures do not preclude a specialist from
exercising his/her own judgment in providing further
assistance when there is the slightest doubt about the
adequacy of data being furnished to alert a pilot to the
existence of an MTR or MOA.
6-5-2. AERIAL REFUELING TRACKS
Upon notification from the ARTCC or a scheduling
facility that a published refueling track will be
activated and all or part of the activity will take place
outside of restricted/warning areas or Class A
airspace, the tie-in AFSS/FSS shall issue a NOTAM
for the aerial refueling track.
6-5-3. SPECIAL MILITARY FLIGHTS
a. Advise the ARTCC of flight notification
messages, progress reports, changes en route, and
related messages concerning Presidential or Vice
Presidential flights.
b. Alaska. In addition to the above, give advance
notice to all RCCs along the route of flight.
Telephone SARCC (907) 752-0227 or (907)
752-0128. Initiate communications search proce-
dures if arrival is not received within 15 minutes after
ETA and immediately notify ANRCC (Alaskan
NORAD Region Control Center).
6-5-4. MILITARY FOREIGN FLIGHTS
Generally, all military foreign flights are required to
clear through specified military bases. Pilots
normally will not file flight plans directly with an
AFSS/FSS unless BASOPS is not available.
BASOPS with no Service B access will forward an
ICAO-type flight plan message via their tie-in
AFSS/FSS for relay through the AFTN. BASOPS
should specify all addressees, both ATC and
operational, in accordance with ICAO standards and
military regulations.
6-5-5. USAF/USN UNDERGRADUATE
PILOTS
To identify aircraft piloted by solo USAF/USN
undergraduate student pilots (who may occasionally
request revised clearances because they normally are
restricted to flight in VFR conditions), the aircraft
identification in the flight plan shall include the letter
Z as a suffix. Do not use this suffix in ground-to-air
communication.
NOTE-
USAF solo students who have passed an instrument
certification check may penetrate cloud layers in climb or
descent only. Requests for revised clearances to avoid
clouds in level flight can still be expected. This does not
change the requirement to use the letter Z as a suffix to the
aircraft identification.
6-5-6. MESSAGE HANDLING
Accept and forward messages from any military
authority that concern aircraft movement, national
defense, safety of flight, or emergencies. This
includes, but is not limited to, the following:
a. Flight Advisory Messages.
1. The tie-in AFSS/FSS originating the adviso-
ry or receiving it from the originating BASOPS shall
determine the AFSS/FSS nearest the aircraft's
estimated position for VFR flights, or the appropriate
ARTCC for IFR flights. Transmit a numbered
message only to the facility identified. Include in the
text, FLT ADVY, aircraft identification and type, and
route of flight in that order. The last item shall be the
identifier of the originating BASOPS or AFSS/FSS.
EXAMPLE-
AISR
FF KZIDZRZX
DTG KCOUYFYX
COU005 ZID
FLT ADVY A12345 T38 GVW J80 DAY
DAY WX BLO LNDG MIN. SUG PROCD CVG.
ADZ INTENTIONS DLVR 1625
GVW BASOPS
M1FC
ORIGIN:COU PRECEDENCE:FF TIME: ACK:Y
ADDR: KZIDZRZX
TEXT: A12345 FLT ADVY T38 GVW J80 DAY
DAY WX BLO LNDG MIN. SUG PROCD CVG.
ADZ INTENTIONS DLVR 1625 GVW BASOPS
2. Inform the originator if unable to deliver the
flight advisory within 15 minutes. File the message.
JO 7110.10T 2/14/08
6-5-3 Military Operations
b. Electronic Counter Measure (ECM) Alerts.
Transmit a numbered message via Service B to tie-in
stations serving the addressees. If acknowledgements
are not received within 1 hour, deliver via telephone.
c. REACH and SAM Flight Messages. Forward to
the airlift command post specified by the pilot if
message contains request PASS TO AMC ACP.
d. UNIDENTIFIED FLYING OBJECT (UFO)/
UNEXPLAINED PHENOMENA REPORTS.
1. Persons observing UFOs/Unexplained Phe-
nomena should contact an UFO/Unexplained
Phenomena Reporting Data Collection Center, such
as the National Institute for Discovery Science
(NIDS), the National UFO Reporting Center, etc.
2. If concern is expressed that life or property
might be endangered, also refer the individual to the
local police department.
JO 7110.10T 2/14/08
6-6-1 IFR/DVFR ADIZ Flight Plans
Section 6. IFR/DVFR ADIZ Flight Plans
6-6-1. AIRCRAFT MOVEMENT
INFORMATION SERVICES (AMIS) WITHIN
AN ADIZ-IFR
In addition to the normal handling of aircraft
operating in accordance with IFR, ADIZ penetration
information or position reports on IFR operations
outside of controlled airspace shall be forwarded
immediately to the appropriate ARTCC.
6-6-2. AMIS WITHIN AN ADIZ-DVFR
For security control of air traffic, specific information
contained in flight plans filed by a pilot operating or
proposing to operate in accordance with DVFR
within an ADIZ shall be forwarded to NORAD.
NOTE-
Other offices, military and civil, as well as pilots, may file
DVFR flight plans with an AFSS/FSS for forwarding to
NORAD.
6-6-3. FORWARDING DVFR INFORMATION
Except for Alaska, forward DVFR flight plan
information to NORAD via the Service B NORAD
address or by telephone as follows:
NOTE1. The following NORAD addresses are group addresses
that include all appropriate NORAD sectors and law
enforcement:
KZAMZQZX - the contiguous 48 states and San Juan.
PHIRAOCZ - Hawaii.
2. NORAD will not send an acknowledgement and must
be manually acknowledged from the suspense list by the
specialist. (NORAD Headquarters assumes responsibility
for receipt.)
a. VFR.
1. M1FC - DVFR flight plans shall be entered
into the M1FC Flight Plan mask with “V” in the FR:
field for processing purposes. The applicable
NORAD address must be manually entered into the
CP: field. If “NORIV,” delete AFSS closure point
address.
2. OASIS - DVFR flight plans shall be entered
into the OASIS Flight Plan dialog box with “VFR”
selected in the Flight Rules (FR) drop-down list box
for processing purposes. The applicable NORAD
address must be manually entered into the Closure
Points text box. If “NORIV,” delete AFSS closure
point address.
b. Aircraft call sign.
c. Number and type of aircraft.
d. Altitude (within ADIZ).
e. True airspeed.
f. Time of departure.
1. When the flight plan information is provided
before the aircraft's departure, enter as a proposal.
Depart the flight plan immediately upon receipt of the
actual departure time.
2. If arrangements cannot be made to obtain the
actual departure time, forward the estimated time of
departure (ETD).
g. Point of departure.
h. ETA.
i. Destination.
j. Remarks.
1. DVFR discrete transponder code.
2. True airspeed.
3. Estimated point of penetration of the ADIZ
(latitude/longitude or fix-radial-distance).
4. Estimated time of penetration of the ADIZ.
5. If no arrival report (NORIV) will be filed with
an appropriate aeronautical facility, include the
abbreviation NORIV. Do not pass “NORIV” to
NORAD. For Service B transmissions, precede
“NORIV” remark with the percent (%) symbol.
EXAMPLE1210 135 3442/9345 1446
NOTE-
On a proposed flight plan, a single “X” may replace the
DVFR discrete transponder code, true airspeed,
estimated point of penetration of ADIZ, or the estimated
time of penetration.
EXAMPLE-
Missing true airspeed:
1210 X 3442/9345 1446
Missing estimated point of ADIZ penetration and time
JO 7110.10T 2/14/08
6-6-2 IFR/DVFR ADIZ Flight Plans
with NORIV:
1210 135 XX %NORIV
6-6-4. STOPOVER DVFR FLIGHT PLANS
Accept stopover DVFR flight plans filed on those
aircraft planning one or more landings (within an
ADIZ) en route to the destination, provided the
information in para 6-6-3 is furnished for each
segment of flight. Remind the pilot that 14 CFR
Part_99 requires departure times to be made good and
that a written record should be retained of these times
at each departure point.
6-6-5. ADDRESSING DVFR FLIGHT PLAN
MESSAGES
Forward DVFR flight plan information (Reference
para 6-6-3) as follows:
a. Contiguous U.S. ADIZ. Forward DVFR flight
plan information to NORAD.
b. Alaskan ADIZ. Alaska ADIZ procedures are
contained in a Letter of Agreement with the affected
facility.
c. Hawaiian ADIZ. Forward all DVFR flight plan
information to NORAD.
1. M1FC - Enter “V” in the FR: field of the
Flight Plan mask.
2. OASIS - Select “VFR” in the Flight Rules
drop-down list of the Flight Plan dialog box.
d. Canada. Routing DVFR flight plan messages to
Canada. Compose DVFR messages pertaining to
aircraft operating on a DVFR flight into Canada
using the same procedure as for DVFR messages in
the contiguous 48 states, except add “DVFR” in
remarks. In addition, address and route to the
appropriate transborder tie-in station.
JO 7110.10T 2/14/08
6-7-1 Law Enforcement Messages
Section 7. Law Enforcement Messages
6-7-1. LAW ENFORCEMENT ALERT
MESSAGES (LEAM)
The El Paso Intelligence Center (EPIC ) is an
organization composed of 14 Federal agencies,
including the FAA. The principal mission of EPIC is
to facilitate the exchange of information and tactical
intelligence on illicit narcotic trafficking and to
support, through the intelligence process, Federal
investigations concerning violation of Federal
statutes as they apply to narcotics, aliens, currency,
and weapons. EPIC issues two types of Law
Enforcement Alert Messages (LEAM) that pertain to
aircraft: Aircraft Lookout Alerts and Stolen Aircraft
Alerts. Upon receipt of a LEAM from EPIC, take the
following actions:
a. Aircraft Lookout Alerts.
1. Keep active for 7 days, unless otherwise
specified, or until cancellation is received.
2. Do not disseminate Suspect Aircraft Look-
outs outside of official government facilities. As this
data is inherently sensitive, unauthorized disclosure
of information could compromise an investigation,
endanger lives, and could result in crim inal
prosecution or administrative action against the
offender.
REFERENCE-
FAAO 1600.29, Para 7c(7), Stolen Aircraft Alert Procedure.
NOTE-
Paragraph 6-7-1a applies only to FSS and AFSS
facilities in Alaska. AFSS facilities operating under
contract of a Service Provider are not considered official
government facilities and therefore will not receive
Aircraft Lookout Alerts.
b. Stolen Aircraft Alerts. Stolen Aircraft Alerts
request recipients to watch for and report on the
location and movement of an aircraft which has been
reported stolen.
1. M1FC.
(a) Keep active until included in a stolen
aircraft summary or until cancelled.
(b) Upon receipt, check local records for any
aircraft contact, beginning with the date the aircraft
was reported stolen. AFSSs shall notify their Flight
Service Data Processing System (FSDPS) personnel
to run the ENFORCE program as soon as practicable.
(c) Relay any information available to the
office listed on the alert.
2. OASIS. When OASIS receives a correctly
formatted stolen aircraft alert, it processes it as
follows: Checks the database for the past 15 days for
a match. If no match is found, the LEAM is added to
the Law Enforcement (LE) List with a green icon and
no alarm. If a match is found, a Law Enforcement
alarm is generated at designated workstations and the
LEAM is placed on the LE List with a red icon.
c. Stolen Aircraft Summaries.
1. Stolen Aircraft Summaries should be used to
displace and consolidate all the individual stolen
aircraft alerts received in the interim.
2. Monthly summaries are sent as soon as
possible after the end of the month. They include
aircraft registration numbers, aircraft type, and the
date/time stolen and/or recovered.
3. Biannual summaries are sent in January and
July. They list only those aircraft stolen in the past
2_years.
d. All LEAM.
1. Distribute the Stolen Aircraft Alerts and
Summaries, at the discretion of the Air Traffic
Manager, to all parties, fixed base operators, airport
managers, etc.
REFERENCE-
FAAO 1600.29, Para 7c(6), Stolen Aircraft Alert Procedure.
2. Check local records for the previous 24 hours.
3. Notify EPIC via Service B message
(KDEAYYYX) or by telephone (1-888-873-3742
[USE EPIC], 1-915-760-2227 for the Air Watch
Desk or 1-915-760-2200 for the General Watch
Desk) of any contact within the past 24 hours. Also,
notify your Regional duty officer for relay to the
cognizant Transportation Security Administration
Aviation Command Center.
4. Subsequent aircraft transactions shall be
monitored and require the same notification as
defined in subpara 6-7-1d3.
JO 7110.10T 2/14/08
6-7-2 Law Enforcement Messages
5. Take no action regarding the aircraft, crew, or
passengers other than normal air traffic job related
functions.
6. Cease all actions upon receipt of a
cancellation or a summary if the latter does not
include this aircraft's registration number.
6-7-2. INITIATING LEAMs
Any inquiries from airport managers, aircraft owners,
or law enforcement entities to initiate an alert
message shall be directed to EPIC. EPIC is interfaced
with the National Crime Information Center, which
gives them access to any stolen aircraft report entered
by law enforcement agencies. FAA facilities shall not
volunteer to relay this inform ation to EPIC .
Assistance shall be limited to providing EPIC phone
number(s) as specified in subpara 6-7-1d3 or
advising the inquiring party to go through normal law
enforcement channels.
6-7-3. FSDPS RESPONSIBILITIES
The FSDPS shall:
a. As a minimum, execute the ENFORCE
program every 8 hours. In addition, run the
ENFORCE program when requested.
b. Not accept requests to search for individual
aircraft from other than an FAA facility or office.
c. Immediately notify the requesting facility or
office when the program recognizes any aircraft
registration number in the history file that matches
one in the LEAM. Negative replies are required.
JO 7110.10T 2/14/08
6-8-1 Nonemergency Parachute Jumping
Section 8. Nonemergency Parachute Jumping
6-8-1. COORDINATION
All pertinent information received from pilots prior
to and during parachute jumping activity shall be
forwarded to other affected ATC facilities.
6-8-2. PREJUMP RADIO
COMMUNICATIONS
a. When a prejump radio call required by 14 CFR
Section 105.14 is received, contact the ARTCC
sector or terminal facility in whose airspace the jump
begins. If the controller has pertinent traffic, advise
the jump aircraft to contact the control facility on the
appropriate frequency for traffic information.
b. If the aircraft is unable to contact the control
facility direct, obtain traffic information and relay it
to the aircraft.
EXAMPLE“Cessna Four Zero Yankee, A-T-C advises traffic is a
Cessna Four Twenty-One passing the Sputs intersection
eastbound on Victor One Fifty-Seven at seven thousand.”
JO 7110.10T 2/14/08
7-1-1 Messages and Formats
Chapter 7. International Operations
Section 1. Messages and Formats
7-1-1. GENERAL
a. Title 14 of the U.S. Code of Federal Regulations
(14 CFR) and the International Civil Aviation
Organization (ICAO) require flight plans for all civil
aircraft operation between the United States and
foreign locations. Bureau of Customs and Border
Protection requirements, international flight plan
information, and Air Defense Identification Zone
(ADIZ) penetration requirements are listed in other
publications; e.g., the FAA International Flight
Information Manual (IFIM), the Bureau of Customs
and Border Protection Guide for Private Flyers, the
Aeronautical Information Manual (AIM), 14 CFR
Part 91, and 14 CFR Part 99. Designated airports of
first landing are listed in the IFIM and the
Airport/Facility Directory (A/FD).
b. This chapter provides guidance to AIFSS,
AFSS, FSS, and ARTCC facilities that transmit
international flight movement messages. It incorpo-
rates relevant information from ICAO and 14 CFR
docum ents. All personnel required to handle
international messages shall be familiar with ICAO
documents containing instructions for preparing and
transmitting communications for the AFTN circuits.
These documents should be retained at FAA facilities
which handle international messages. FAA personnel
shall not act as agents for any aircraft operating or
dispatching company.
NOTE-
International telecommunications instructions are found
in International Standards and Recommended Practices,
ICAO Annex 10 - Aeronautical Telecommunications,
Volume II, and Document 7946, Manual of Teletypewriter
Operating Practices. DOC 4444-RAC 501, Rule of the
Air and Air Traffic Services, lists various ATS movement
messages. Location indicators are contained in ICAO
Document 7910, and Designators for Aircraft Operating
Agencies Aeronautical Authorities and Services are
contained in ICAO DOC 8585. FAA policies concerning
acceptance of messages for international transmission
are contained in 14 CFR Part 189.
c. AFSSs and FSSs that transmit only occasional
international messages or are unable to determine the
correct addressing for all air traffic units concerned
may refer the pilot to the proper gateway facility or
address the message to the proper gateway facility for
handling. The gateway stations and their areas of
responsibilities are as follows:
1. New York AIFSS (ISP): Bermuda, Canada,
North Atlantic, Europe, and Africa.
2. Miami AIFSS (MIA): Caribbean, South
America, and Central America.
3. Kenai AIFSS (ENA): Alaska.
4. Oakland AIFSS (OAK): Pacific.
d. To ensure that the gateway facility understands
your request, include T (transmit) instructions in the
first line of text.
EXAMPLE-
AISR
FF KMIAYFYX
DTG KICTYFYX
MIA T ALL INTL ADDRESSEES
(Text)
M1
ORIGIN: PRECEDENCE.FF TIME: ACK:N
ADDR:KMIAYFYX
TEXT:MIA T ALL INTL ADDRESSEES
(TEXT)
7-1-2. AIR TRAFFIC SERVICE (ATS)
MESSAGES
ATS as used in this section, as opposed to the
meaning of the term within the FAA, is a generic term
meaning and including: flight information, alerting,
air traffic advisory, and air traffic control (ATC)
services.
7-1-3. CATEGORIES OF MESSAGES
The following ATS messages, with their normal
priority indicators, are authorized for transmission by
any means; i.e. , AFTN, NADIN, interphone,
computer-to-computer, or via the aeronautical
mobile service, as applicable.
a. Emergency Messages.
1. Distress messages and distress traffic,
including alerting (ALR) messages relating to
distress (DETRESFA) phase-SS.
JO 7110.10T 2/14/08
7-1-2 Messages and Formats
2. Urgency messages, including alerting mes-
sages relating to an alert (ALERFA) phase or to an
uncertainty (INCERFA) phase-SS.
3. Other messages concerning known or
suspected emergencies which do not fall under
subparas 7-1-3a1 and 2 and radio communications
failure (RCF) messages-FF or higher as required.
b. Movement and Control Messages.
1. Flight plan (FPL)-FF.
2. Amendment and coordination messages.
(a) Departure (DEP)-FF.
(b) Delay (DLA)-GG.
(c) Arrival (ARR)-GG.
(d) Boundary estimate (EST)-FF.*
(e) Modification (CHG)-FF.*
(f) Coordination (CDN)-FF.*
(g) Acceptance (ACP)-FF.*
3. Cancellation (CNL)-GG.*
4. Clearances, flow control (SPL, CHG,
CDN)-FF or DD.*
5. Transfer of control (TCX)-FF.*
6. Requests (RQS)-FF.*
7. Position reports (AIREP)-FF.*
c. Flight Information Messages.
1. Traffic information-FF.*
2. Meteorological information (MET)-FF or
GG.
3. Operation of aeronautical facilities and
essential airport information (NOTAM)-GG.
* Normally exchanged between ATC units via voice
circuits.
d. Technical Messages. Four categories of these
messages are specified for use on computer-to-com-
puter circuits only. They will not be sent on AFTN or
NADIN circuits.
7-1-4. SERVICE MESSAGES
a. NADIN will immediately generate a service
message to an originator when incorrect code or
routing indicators are detected.
EXAMPLE-
FF KZKCZQZX
031840 KSLCYTYX
SVC. ZKC121 QTA RPT
FF KZKCZQZX
031840 KSLCYTYX
SVC. ZKC122 QTA MSR
b. Assign the appropriate priority indicator to
international service messages. When service
messages refer to messages previously transmitted,
assign the same priority prefix. Identify a service
message by inserting SVC as the first item of the text.
EXAMPLE-
FF TJSJYFYX
DTG KSEAYFYX
SVC. RUMES 231015
(Text)
7-1-5. TRANSMISSION VIA NADIN
International messages are generally introduced on
NADIN for relay to AFTN circuits.
a. M1FC facilities use the ICAO flight plan mask
or TB mask. Addressee(s): Not to exceed 69
characters or seven addressees, each addressee
separated by a space.
b. AISR facilities handle international messages
on NADIN for relay to AFTN as follows:
1. Start of message. New Line Key.
2. Preamble (priority, space, addressee(s).
(a) Priority. Two-character precedence field.
(b) Addressee(s). Not to exceed 69 characters
or seven addressees, each addressee separated by a
space.
(c) End of Line (EOL) new line key.
(d) End of Text (EOT) (enter function).
c. OASIS facilities use the ICAO Flight Plan
dialog box or General Facility Message. A maximum
of 16_addressees can be entered.
7-1-6. TRANSMISSION OF ATS
MESSAGES
a. Air traffic service messages are interchanged in
the international air traffic control system in the
following modes:
JO 7110.10T 2/14/08
7-1-3 Messages and Formats
1. The preferred step-by-step mode wherein
each ACC/ARTCC sends forward the full current
(updated) flight plan information as the flight
progresses.
2. The simultaneous mode wherein information
extracted from the filed flight plan (FPL) is sent
simultaneously to all ATS units along the route of
flight. In this mode, only amendments to the FPL,
plus necessary control information, are forwarded
from center to center as the flight progresses.
b. Prepare and transmit ATS messages as set forth
in this Order. Address these messages as follows:
1. Include an eight-character addressee indica-
tor for each addressee. For M1FC and AIS R
facilities, there can be no more than one line
(69_characters including separating spaces) of
addressees. When more than the allowable number of
addressees are required, two or more transmissions of
the message (each with no more than the allowable
number of addresses) must be made. For OASIS
facilities, a maximum of 16 addressees can be
entered. The eight-letter combination addressee
indicators are composed as follows:
(a) The four-letter ICAO location indicator;
e.g., MPTO. Use only those listed in ICAO DOC
7910 (Location Indicators). Some ICAO eight-char-
acter addressees for Mexico and Canada are listed in
FAAO JO 7350.8, Location Identifiers.
(b) A four-letter designator for the facility
type/office, or if no designator has been assigned,
affix YXYX for military, ZZZX for aircraft in flight,
or YYYX for all other cases; e.g., MTPPYYYX. (See
Note.)
REFERENCE-
ICAO DOC 8585, Designators for Aircraft Operating Agencies,
Aeronautical Authorities and Services.
NOTE-
The most frequently used and authorized designators are:
YAYX Government Civil Aviation Authority (FAA
Regional Office or Headquarters).
YCYX Rescue Coordination Center (RCC).
YDYX Authority Supervising the Aerodrome.
YFYX Aeronautical Fixed Station (AFSS/FSS/IFSS/
IATSC).
YMYX Meteorological Office (NWS).
YNYX International NOTAM Office (NOF).
YTYX Telecommunications Authority.
YWYX Military Flight Operational Control Center
(ACP)
YXYX Military Organization (BASOPS).
YYYX Organization not allocated a two-letter
designator.
ZOZX Oceanic Air Traffic Control Center.
ZPZX Air Traffic Service Reporting Office.
ZQZX Computer Facility at ACC/ARTCC.
ZRZX ACC/ARTCC. (Center in charge of a FIR/UIR
when the message is relevant to a VFR flight (AMIS)).
ZTZX Aerodrome Control Tower.
ZZZX Aircraft in flight.
(c) A one-letter designator will appear
following an air carrier designator to indicate the
department or division of the organization addressed.
2. Filing time. A six-digit date/time group
indicating the time the message is filed with the
AIFSS/AFSS/FSS for transmission.
c. Originator Indicator. Consists of an eight-letter
sequence similar to an address indicator, identifying
the place of origin and the organization originating
the message.
d. Supplementary Address and Origin Informa-
tion. When the four-letter designators YXYX,
ZZZX, or YYYX are used, identify the aircraft
operator or organization at the beginning of the text
preceding the start-of-ATS data symbol ( - - ), in
the same order as in the addressee(s) and/or originator
indicator(s). Where there is more than one such
insertion, the last should be followed by the word
“stop.” Where there are one or more insertions in
respect to addressee indicators plus an insertion in
respect to the originator indicator, the word FROM is
to appear before that relating to the originator.
e. When addressing flight plan messages or
related amendments and flight plan cancellation
messages to centers, use one of the four-letter
designators as follows:
1. If message is relevant to IFR and:
(a) The ARTCC is computer-equipped
(U.S. ARTCCs), use ZQZX.
(b) The center is not computer-equipped, use
ZRZX.
(c) R elevant to oceanic operations, use
ZOZX.
NOTE-
Some centers may request specific addressing different
from above. ZTZX and ZPZX are used internationally, but
are not used in internal U.S. application.
2. If message is VFR (AMIS), use ZRZX.
3. If SVC or administrative, use ZRZX.
JO 7110.10T 2/14/08
7-1-4 Messages and Formats
7-1-7. ORIGINATING MESSAGES
a. Messages for ATS purposes may be originated
with ATS units by aircraft in flight, or, through local
arrangem ents, a pilot, the operator, or their
designated representative.
b. Accept air-filed flight plans or changes in
destination information from aircraft inbound from
foreign locations and, if requested by the pilot, enter
Customs notification service.
c. Do not accept round-robin flight plans to
international locations, other than Canada.
NOTE1. Only accept VFR round-robin flight plans to Canada
if the filer of the flight plan is in possession of a valid
numbered letter of authorization and adheres to the
provisions contained therein.
2. Individual requests for the temporary authorization
letter should be directed to the appropriate service area
office.
3. The temporary authorization letter mandates the pilot,
or responsible party, to provide the AFSS/FSS with a
name, telephone number and authorization number for
inclusion in the remarks section of the flight plan.
4. AFSS/FSS shall log a double (2) count for the
round-robin flight plan.
d. Do not accept assumed departure flight plans
when the destination is in a foreign country other than
Canada.
e. Aircraft movement, control, and flight informa-
tion messages for purposes other than ATS, such as
operational control, shall be originated by the pilot,
the operator, or their designated representative.
7-1-8. ADDRESSING MESSAGES
a. Addressing the flight plan is determined by the
point of departure, the destination, and the FIR
boundaries to be penetrated during the course of the
flight.
b. Address IFR FPL messages to the ARTCC
serving the airport of departure and to all ATS units
(including oceanic) providing air traffic control
service or concerned with flight along part or the
whole of the route to be flown except FAA ATCTs
and other conterminous U.S. ARTCCs.
NOTE-
Within the North Atlantic (NAT) Region, FPLs on turbojet
aircraft transiting the control areas of Gander Oceanic,
New York Oceanic, Reykjavik, Santa Maria Oceanic,
Shanwick Oceanic and Sondrestrom (south of 70 degrees)
within 90 nautical miles of the control area boundary,
shall be addressed to the adjacent ACC to provide lateral
separation. For all other aircraft, a 120 nautical mile
proximity limit shall apply.
c. Transmit all IFR FPLs to ARTCCs not less than
1 hour prior to the proposed departure time. Do not
hold FPLs until after departure time and transmit as
a combined FPL and DEP. Separate FPL and DEP
messages must be transmitted.
NOTE-
ICAO flight plans do not require an acknowledgment to
the transmitting facility.
d. Address aircraft movement messages only to
those ATS units responsible for the provision of
relevant service, except when requested by the
operator concerned, these messages, when
transmitted via the AFTN, may also be routed, as
specified by the operator or a representative to:
1. One addressee at the point of intended
landing or point of departure.
2. Not more than two operational control units
concerned.
e. The ARTCC serving the departure airport shall
transmit the DEP message on IFR aircraft to all
known recipients of the FPL message. Flights
between conterminous U.S. and Canada (excluding
Gander Oceanic), Alaska, Hawaii and Puerto Rico do
not require DEP messages. Discontinuance of DEP
messages affecting the route of flight can only be
accomplished by ICAO Regional Air Navigation
Agreement.
7-1-9. FLIGHT PLAN FORMS AND
INSTRUCTIONS
a. Use the International Flight Plan, FAA Form
7233-4 (see Appendix A), ICAO Model Flight Plan
Form displayed in DOC 4444, M1FC ICAO Flight
Plan Mask, or OASIS ICAO Flight Plan dialog box
and apply the procedures set forth in this section for
flight:
NOTE-
Exceptions apply for flights to Canada and Mexico, see
Section 4 and Section 5, for procedures.
1. Originating within conterminous U.S. and
Canada and destined nonstop to points beyond those
areas.
JO 7110.10T 2/14/08
7-1-5 Messages and Formats
2. Originating within or transiting Pacific Flight
Information Regions (FIR) and destined to or from
FIRs beyond the Pacific Region including the North
American (NAM) Region.
NOTE1. The NAM Region encompasses the conterminous U.S.,
Alaska, and Canada to the North Pole.
2. FAA Form 7233-1, or Military Form DD-175, and
domestic procedures are used for flights in the
conterminous U.S., Canada, and the Honolulu, Alaskan,
and San Juan domestic control areas.
3. AISR facilities record on the flight plan form
the time that a flight plan is filed. This time will
constitute evidence of the pilot's intention to comply
with Customs, Immigration, and Public Health
requirements and will be made available upon request
from these authorities.
7-1-10. ICAO ATS MESSAGE FORMAT
The following are examples of ICAO message types
most likely to appear on AFTN/NADIN circuits. The
number above the data corresponds to the field type
numbers on the flight plan form (FAA Form 7233-4)
and on the chart of Standard ATS Messages and Their
Composition, Appendix A.
a. Departure Message (DEP). ARTCCs are the
designated ATS unit responsible for originating and
transmitting DEP messages on all IFR aircraft
departing airports within their center boundaries. IFR
flight plans must be transmitted to ARTCCs at least
1 hour before departure. This allows ARTCCs to
determine recipients of DEP message when domestic
portions are transmitted to ARTCCs in M1 format.
Do not hold FPLs and combine with DEP into a
single message.
b. Delay Message (DLA). Transmitted when
departure of an aircraft, for which an FPL message
has been transmitted, is postponed or delayed more
than 30 minutes after the estimated time of departure
contained in the FPL.
c. Alerting Message (ALR). Relating to an
overdue situation on an aircraft.
d. Supplementary Flight Plan (SPL) information
shall be sent to ATS units requesting the information
(RQS).
RQS-N1234-SVMI-KMIA
1. INCERFA, ALERFA, DETRESFA, as ap-
propriate to the phase of the emergency.
2. Agency and person calling.
3. Nature of the emergency.
4. Significant information from the flight plan.
5. Unit which made last contact, time, and
frequency used.
6. Last position report and how determined.
7. Color and distinctive marks of aircraft.
8. Any action taken by reporting office.
9. Other pertinent remark.
EXAMPLE-
AISR (INCERFA)
SS MMMXYAYX
DTG KSANYFYX
(ALR-INCERFA/KSAN/OVERDUE
-N1234S-VG
-C172
-KRNO2000
-MMLP0130
-REQ ACK OR ARR ACFT OVERDUE YOUR
STN)
M1 (INCERFA)
ORIGIN:SAN PRECEDENCE:SS TIME: ACK:N
ADDR:MMMXYAYX
TEXTALR-INCERFA/KSANYFYX/OVERDUE
YOUR STATION
-N1234S-VG
-C172-SD/C
-KSAN2000
-N0160A105-DCT TIJ DCT
-MMLP2130 RMK/REQ ACK OR ARR)
AISR (ALERFA)
SS MMMXYAYX
TEXTALR-ALERFA/KSAN/OVERDUE)
(text remains same except for remarks information).
M1 (ALERFA)
ORIGIN: PRECEDENCE:SS TIME: ACK:Y
ADDR:MMMXYAYX
TEXTALR-ALERFA/KSANYFYX/OVERDUE
(text remains same except for remarks information).
AISR (DETRESFA)
SS MMMXYAYX
TEXTALR-DETRESFA/KSAN/OVERDUE
(text remains same except for remarks information).
M1 (DETRESFA)
ORIGIN: PRECEDENCE:SS TIME: ACK:Y
ADDR:MMMXYAYX
TEXTALR-DETRESFA/KSANYFYX/OVERDUE
(text remains same except for remarks information).
NOTE-
OASIS facilities shall transmit alerting messages using
the Transmit General Facility Message dialog box.
b. The cancellation of action initiated by the
rescue coordination center is the responsibility of that
center.
EXAMPLE-
AISR (CANCELLATION)
SS MMMXYAYX
020618 KMIAYFYX
(ALR-ALERFA/KMIAYFYX/CNL
N1234 LOCATED)
M1 (CANCELLATION)
ORIGIN:_PRECEDENCE:SS_TIME:
ACK:YADDR:MMMXYAYX
TEXTALR-ALERFA/KMIAYFYX/CNL
N1234 LOCATED
NOTE-
Transmit cancellation messages for INCERFA and
DETRESFA using same format as above.
JO 7110.10T 2/14/08
7-4-1 Canadian Movement and Control Messages (Transborder Flights Only)
Section 4. Canadian Movement and Control Messages
(Transborder Flights Only)
7-4-1. GENERAL
Except as indicated in this section, handle transborder
Canadian movem ent and control messages as
described in Sections 1, 2, and 3. Do not pass
ADCUS messages to NAV CANADA, as they no
longer alert Canadian Customs to inbound flights.
CANPASS authorizations are the obligation of the
pilot, at the number in subpara 7-4-3a.
7-4-2. INBOUNDS FROM CANADA
a. M1 will automatically acknowledge and
suspense a VFR flight notification message if
received in the proper format. Deliver VFR and IFR
ADCUS to the U.S. Customs and Border Protection.
File IFR messages after delivery.
b. AISR facilities acknowledge receipt of flight
notification messages as soon as practical by
transmitting the letter R followed by the full aircraft
identification; e.g., R N711VR. Suspense VFR flight
notification messages until arrival or closure
information is received. File IFR messages after
delivery.
7-4-3. OUTBOUNDS TO CANADA
a. When Customs notification service is requested
advise the pilot to contact Canada's Private Aircraft
Program for Customs (CANPASS) at 888-226-7277
and include CANPASS in the remarks section of the
flight plan. If the pilot has contacted CANPASS,
place CANPASS in the remarks section of the flight
plan. Process outbound flight plans in accordance
with Chapter 6 and subparas 7-4-3d and e.
b. Accept Customs notification requests from
inflight aircraft for relay via flight notification
message only for airports of entry where Customs
flight notification service is provided and when
proposed ETA is during Customs service hours. NAV
CANADA no longer passes ADCUS messages to
Canadian Customs.
c. Upon notification of departure of VFR flights,
transmit a flight notification message directly to the
destination Canadian relay facility. Include
CANPASS in the remarks.
NOTE1. M1 will format and address a flight notification
message to a Canadian destination airport if the proposed
flight plan was filed in accordance with subparas 7-4-3d
and 7-4-3e.
2. AISR facilities address messages to the destination
relay facility listed in FAAO JO 7350.8, Location
Identifiers. AISR facilities transmit flight notification
messages for VFR flights in accordance with para 6-4-4,
Flight Notification Messages. Flight notification mes-
sages included the type of flight plan as the first item of the
notification message. CANPASS is required in the
remarks, as appropriate.
3. OASIS facilities shall enter CANPASS in the Remarks
text box of the Flight Plan dialog box. OASIS will
automatically format and transmit a flight notification
message to the tie-in destination facility.
EXAMPLE-
AISR
FF CZYZZFZX
DTG KBUFYFYX
VFR N711VR C182 BUF YYZ 1735
CANPASS
d. IFR Flight Plans
1. CANPASS Flight Plans.
(a) M1FC. Insert an ampersand and the letter
C (&C) as the first two entries in the OP field of the
FP mask and use the four-letter Canadian location
identifier for the destination airport in the AD: field.
EXAMPLE-
M1- AIRFILED
FR:I AI:N1234 AT:C421/R TS:280
DDSM TM1800 AE:200
RTSM..CYYZ
AD:CYYZ TE:0300 RMCANPASS
FB:0400 AA:
PD:JOE PILOT
HBSM NB:2 CR:R/W TL:
OP:
CP:
TA:2100
EXAMPLE-
M1 - CANPASS
FR:I AI:N1234 AT:C421/R TS:280 DDSM TM1800
AE:200
RTSM..CYYZ
JO 7110.10T 2/14/08
7-4-2 Canadian Movement and Control Messages (Transborder Flights Only)
AD:CYYZ TE:0300 RMCANPASS
FB:0400 AA:
PD:JOE PILOT
HBSM NB:2 CR:R/W TL:
OP:&C
CP:CZYZZFZX
TA:2100
(b) OASIS. Enter $CANPASS %ADCUS in
the Remarks text box of a Canadian IFR flight plan.
NOTE-
The ADCUS remark is not transmitted but triggers the
autoaddressing in OASIS.
2. Send a flight notification message on airfile
IFR aircraft that has requested Customs notification.
Place CANPASS (if prior notification) in the remarks
section of the flight notification message. If the pilot
files a flight plan, but gives no indication that
CANPASS procedures have been implemented, or
prefers to leave the notification off of the flight plan,
leave the remarks section blank and allow the NAV
CANADA specialists to handle the situation upon
arrival.
e. VFR Flight Plans.
1. M1FC. ADCUS (if airfiled) and CANPASS:
Insert an ampersand and the letter C (&C) in the OP:
field and use the four-letter Canadian location
identifier for the destination airport in the AD: field.
EXAMPLE-
M1- AIRFILED
FR:V AI:N1234 AT:C150 TS:90 DD:BUF
TM1800 AE:045 RT:BUF..CYYZ
AD:CYYZ TE:0030 RMCANPASS 2 FB:0330 AA:
PD:JOE PILOT
HBSM NB:2 CR:5/W TL:
OP:&C
CP:CZYZZFZX
TA:1830
M1-CANPASS
FR:V AI:N1234 AT:C150 TS:90 DD:BUF
TM1800 AE:045 RT:BUF..CYYZ
AD:CYYZ TE:0030 RMCANPASS
FB:0330 AA:
PD:JOE PILOT
HBSM NB:2 CR:5/W TL:
OP:&C
CP:CZYZZFZX
TA:1830
2. OASIS. Enter CANPASS in the Remarks text
box. OASIS will automatically format and transmit
a flight notification message to the tie-in destination
facility.
f. Refer to the Canada and North Atlantic IFR and
VFR supplements to determine Customs hours of
service, availability of Customs flight notification
service (CANPASS), and the relay facility for
infrequently used Airports of Entry not listed in
FAAO JO 7350.8 Location Identifiers.
g. Suspense VFR message until acknowledgment
is received.
REFERENCE-
FAAO JO 7110.10, Para 8-5-2, Canadian Transborder.
1. If an acknowledgment is not received within
30 minutes after departure, M1 facilities retransmit
the message. AISR facilities transmit the contraction
REQ ACP (request acceptance) and the complete
aircraft identification.
EXAMPLE-
AISR
FF CZYZZFZX
DTG KBUFYFYX
REQ ACP N711VR
2. If acknowledgment is not received within
1_hour after departure, use interphone or telephone to
deliver. In any event, assure delivery prior to ETA.
3. Refer to Section B of the Canada and North
Atlantic IFR Supplements for Canadian FSS and
ACC telephone numbers.
h. When correcting or revising a message,
retransmit the complete message preceded by the
contraction CHG (change).
EXAMPLE-
AISR
FF CZYZZFZX
DTG KBUFYFYX
CHG VFR N711VR C182 BUF YYZ 1845
CANPASS
M1
ORIGIN: PRECEDENCE:FF TIME: ACK:Y
ADDR:CZYZZFZX
TEXT CHG VFR N711VR C182 BUF YYZ 1845
CANPASS
AISR
FF CZYZZFZX
DTG KBUFYFYX
CHG VFR N711VR C182 BUF YYZ 1845 CANPASS
M1
JO 7110.10T 2/14/08
7-4-3 Canadian Movement and Control Messages (Transborder Flights Only)
ORIGIN: PRECEDENCE:FF TIME: ACK:Y
ADDR:CZYZZFZX
TEXT: CHG VFR N711VR C182 BUF YYZ 1845
CANPASS
NOTE-
OASIS facilities use the Transmit General Facility
Message dialog box when transmitting change messages.
i. Do not transmit IFR flight notification messages
except for military aircraft or Customs notification
purposes.
NOTE-
Canada will not acknowledge receipt of these messages.
j. When available, use interphone or telephone for
flights of 30 minutes or less.
7-4-4. OUTBOUNDS TO CANADA
DEPARTING FROM OUTSIDE FLIGHT PLAN
AREA
Accept flight plans regardless of departure point. We
no longer forward ADCUS to CANADA; the current
terminology is CANPASS (See para 7-4-1 and
subpara 7-4-3a).
a. Forward VFR flight plan information for
aircraft proposing to depart from outside the facility's
flight plan area to the tie-in AFSS/FSS for the
departure point in the following format:
1. Aircraft identification.
2. Aircraft type.
3. Departure point.
4. Destination.
5. Proposed departure time/ETE.
6. Remarks.
EXAMPLE-
AISR
FF KBUFYFYX
DTG KCLEYFYX
N711VR C182 BUF YYZ P1630/0030 CANPASS
NOTE-
OASIS facilities use the Flight Plan dialog box. OASIS
will automatically format and transmit the proposal to the
departure tie-in facility.
b. Forward IFR flight plan information for aircraft
proposing to depart from outside the facility's flight
plan area in accordance with Para 6-3-1, Domestic
IFR Flight Plans. If Customs flight notification
service (ADCUS) is requested, advise the pilot to
contact CANPASS at 888-226-7277; include
CANPASS information as an intrafacility remark,
and transmit the proposal message to both the
ARTCC and the tie-in AFSS/FSS as follows:
1. M1 and OASIS facilities use procedures
depicted in subpara 6-2-1a2(g) and Notes.
2. Enter the ARTCC computer address last.
EXAMPLE-
AISR
FF KAOOYFYX KZOBZQZX
DTG KDCAYFYX
DCA2010001 FP N1234P P28R/A 150 PIT P0200
150 PIT..CIP..DKK..BUF..YYZ/0130 CANPASS
c. Identify the tie-in AFSS/FSS, and advise the
pilot to report departure time directly to that facility.
NOTE-
While the report may be relayed through another facility,
it is the pilot's responsibility to notify the tie-in AFSS/FSS
of the departure time.
d. Upon receipt of the departure report, the tie-in
AFSS/FSS is responsible for delivery of the flight
notification message to Canada.
1. M1 facilities, enter the departure time in the
TM: field of the proposed flight plan. Add &C to the
OP: field. M1 will automatically transmit the flight
notification message.
2. AISR facilities, transmit a flight notification
message in accordance with para 6-4-4.
NOTE-
AISR facilities, if a departure report has not been received
within 1 hour of the proposed departure time, cancel and
file the proposed flight plan.
3. OASIS facilities, enter the departure time in
the ETD text box of the Flight Plan dialog box.
OASIS will automatically transmit the flight
notification message.
e. Acknowledgment from the departure point
tie-in AFSS/FSS is required for both VFR and IFR
proposals.
7-4-5. IFR FLIGHT PLANS DEPARTING
CANADIAN AIRPORTS
a. Accept IFR flight plans departing from
Canadian airports and destined to the U.S. Transmit
a proposal message in ARTCC HOST computer
format to the associated Canadian ACC. Address
messages to the ACC listed in FAAO JO 7350.8
Location Identifiers.
JO 7110.10T 2/14/08
7-4-4 Canadian Movement and Control Messages (Transborder Flights Only)
NOTE-
FSSs and AFSSs in Alaska will still accept Canada to
Canada IFR flight plans.
b. Canada does not acknowledge for proposal
messages. Do not expect or request acknowledgment.
7-4-6. SEARCH AND RESCUE MESSAGES
Provide Search and Rescue, for flights inbound from
Canada, in accordance with Chapter 8.
JO 7110.10T 2/14/08
7-5-1 Mexican Movement and Control Messages (Transborder Flights Only)
Section 5. Mexican Movement and Control Messages
(Transborder Flights Only)
7-5-1. GENERAL
Except as outlined in this section, handle transborder
Mexican movem ent and control messages as
described in Sections 1, 2, and 3. Transborder flight
plans to Mexico with oceanic routing require the
ICAO flight plan while the domestic flight plan may
be used for flights with route over land.
7-5-2. INBOUNDS FROM MEXICO
a. Flight notification messages.
1. M1FC/OASIS. When received in the proper
form at, VFR flight notification messages are
automatically acknowledged and suspended. Deliver
VFR and IFR ADCUS messages to Customs and
Border Protection. Store IFR ADCUS messages in
the M1 DD file or OASIS History file, as appropriate.
2. AISR. Acknowledge receipt of a flight
notification message as soon as practical by
transmitting the letter R followed by the full ACID;
e.g., R N7llVR. Deliver VFR and IFR ADCUS
messages to Customs and Border Protection.
Suspense VFR flight notification messages until
arrival or closure information is received. File IFR
messages.
b. Search and Rescue. Provide search and rescue
service in accordance with standard format/time
increments listed in Section 3, Alerting Service, and
Chapter 8, Search and Rescue (SAR) Procedures for
VFR Aircraft. The departure station in Mexico is
responsible for initiating SAR action until an
acknowledgment of the flight notification message is
received.
7-5-3. OUTBOUNDS TO MEXICO
a. When customs notification service is requested
for an airport-of-entry, include ADCUS, the number
of persons on board, and the pilot's name in the
remarks section of the flight plan.
NOTE-
Mexican customs regulations require that only interna-
tional airports-of-entry may be used for first landing.
REFERENCE-
FAAO JO 7350.8, Location Identifiers.
1. If the pilot still intends to land at a destination
other than an airport-of-entry, advise the pilot that
the flight plan will not be used for Customs or search
and rescue service in Mexico.
2. Transmit the flight notification message to
the Regional Flight Dispatch Office, not the
destination tie-in station.
NOTE-
If the correct addressee cannot be determined, transmit to
the nearest border Regional Flight Dispatch Office.
b. When a pilot files an IFR flight plan and
Customs notification service is requested for an
airport-of-entry, include ADCUS and the informa-
tion listed in subpara 7-5-3a. Transmit to the
appropriate ARTCC.
NOTE-
Mexico requires notification of an inbound aircraft before
its arrival. The inclusion of ADCUS in the remarks section
of an IFR flight plan or flight notification message
satisfies this requirement.
c. VFR Flight Plans.
1. Upon notification of departure of VFR
flights, transmit a flight notification message. When
Customs notification service is requested for an
airport-of-entry include ADCUS and the informa-
tion listed in subpara 7-5-3a. Address messages to
the ICAO addressee for the appropriate destination
location.
2. If a VFR flight plan is filed with a destination
other than an airport-of-entry, transmit the flight
notification message to the Regional Flight Dispatch
Office, not the destination tie-in station. If the correct
addressee cannot be determined, transmit to the
nearest border Regional Flight Dispatch Office.
NOTE-
Facilities with interphone/telephone capability may relay
flight notification messages by this method.
REFERENCE-
FAAO JO 7350.8, Location Identifiers.
3. M1FC. For automatic addressing and
formatting, use V in the flight rules of the domestic
flight plan mask. For automatic addressing, use &M
in the OP: field. Use the four-letter (ICAO) location
identifier for the destination airport. Manually
JO 7110.10T 2/14/7-5-2 Mexican Movement and Control Messages (Transborder Flights Only)
address the message to the designated Regional
Flight Dispatch Office.
EXAMPLE-
M1FC
FR:V AI:N1234S AT:C182/A TS:120 DD:SAT TM1200
AE:65
RT:SJT..DRT..MMCU
AD:MMCU TE:0400 RMADCUS 4 ZUCHERMANN
FB:0800 AA: PD: A. ZUCHERMANN
HB:SAT NB:4 CR:R/B TL: OP:&M
CP:MMCUXMXO TA:1600
M1FC will automatically address the CP: field if the
4-letter ICAO address is used in the AD: field, &M is used
in the OP: field and the destination is an airport-of-entry.
Only the tie-in facility will be addressed.
4. AIS R. Address messages to the ICAO
addressee for the appropriate destination location.
Transmit the following information:
(a) Type of flight.
(b) Aircraft identification.
(c) Aircraft type.
(d) Departure point.
(e) Destination.
(f) ETA.
(g) Remarks.
EXAMPLE-
AISR
FF MMCUXMXO
DTG KSJTYFYX
VFR N1234S C182 SJT MMCU 1400 $ADCUS
4ZUCHERMANN
5. OASIS . For automatic addressing and
formatting, select VFR in the Flight Rules text box of
the Flight Plan dialog box, and enter ADCUS in
Remarks.
d. If acknowledgment is not received within
30_minutes after departure, transmit a “request
acceptance” message to the destination station tie-in
addressee and to the Regional Flight Dispatch Office.
Manually address the message to the designated
Regional Flight Dispatch Office.
REFERENCE-
FAAO JO 7350.8, Location Identifiers.
EXAMPLE-
AISR
FF MMCUXMXO MMMYXMXO
REQ ACP N1234S
M1FC
ORIGIN:SJT PRECEDENCE:FF TIME:1130
ACK:Y
ADDR:MMCUXMXO MMMYXMXO
REQ ACP N1234S
NOTE-
OASIS facilities, use the Transmit General Facility
Message dialog box to transmit “request acceptance”
messages.
e. The Regional Flight Dispatch Office involved
will then normally send an acknowledgment to the
departure station and assume responsibility for the
flight notification message.
f. If acknowledgment/acceptance is not received
within 1 hour of the departure, use interphone/tele-
phone or other available means to deliver the message
to the appropriate Regional Flight Dispatch Office.
g. Do not accept round-robin flight plans to
Mexico.
7-5-4. MEXICAN REGIONAL FLIGHT
DISPATCH OFFICE TELEPHONE NUMBERS
(See Table 7-5-1.)
TBL 7-5-1
Dispatch Office Phone Numbers
Mexican Regional Flight Dispatch Office Telephone Numbers
REGION IDENTIFIER TELEPHONE NUMBER
CENTRO (CENTRAL) MMMX 01152 5 762-7062
01152 5 784-40-99 ext. 153
01152 5 762-58-77 ext. 153
NORESTE (NORTHEAST) MMMY 01152 83 454-020 ext. 141
NOROESTE (NORTHWEST) MMMZ 01152 67 23-114
01152 67 22-075 ext. 140
OCCIDENTE (WEST) MMGL 01152 36 890-121 ext. 32 and 167
SURESTE (SOUTHEAST) MMMD 01152 99 231-186 ext. 149
3/15/07 7110.65R CHG 2 JO 7110.10T CHG 1 7/31/08
JO 7110.10T 2/14/08
8-1-1 General
Chapter 8. Search and Rescue (SAR) Procedures for
VFR Aircraft
Section 1. General
8-1-1. RESPONSIBILITY FOR SAR
ACTION
a. The departure station is responsible for SAR
action until receipt of the destination station's
acknowledgment for the flight notification message.
This responsibility is then transferred to the
destination station.
b. The National SAR Plan assigns search and
rescue responsibilities as follows:
1. To the military agencies for conducting
physical search and rescue operations.
2. To the FAA for:
(a) Providing emergency service to aircraft in
distress.
(b) Assuring that SAR procedures will be
initiated if an aircraft becomes overdue or unreported.
This is accomplished through the ATC system for
IFR aircraft and the flight plan program and/or
reports of overdue aircraft received at air traffic
facilities for VFR aircraft.
(c) Attempting to locate overdue or unre-
ported aircraft by INREQ and ALNOT communica-
tions search.
(d) Cooperating in the physical search by
making all possible facilities available for use of the
searching agencies.
c. Flight service stations serve as the central point
for collecting and disseminating information on
overdue or missing aircraft which are not on an IFR
flight plan.
d. ARTCCs serve as the central points for
collecting information, coordinating with SAR, and
conducting a communications search by distributing
any necessary ALNOTs concerning:
1. Overdue or missing IFR aircraft.
2. Aircraft in an emergency situation occurring
in their respective areas.
3. Aircraft on a combined VFR/IFR or an
airfiled IFR flight plan, and 30 minutes have passed
since the pilot requested IFR clearance, and neither
communications nor radar contact can be established.
4. Overdue or missing aircraft which have been
authorized to operate in accordance with a SVFR
clearance.
e. The ARTCC serves as the contact point for
collecting information and coordinating with the
RCC on all ELT signals.
8-1-2. OVERDUE AIRCRAFT ON FLIGHT
PLAN
Consider an aircraft on a VFR or DVFR flight plan
overdue when it fails to arrive 30 minutes after its
ETA and communications or location cannot be
established.
8-1-3. OVERDUE AIRCRAFT NOT ON
FLIGHT PLAN
Consider an aircraft not on a flight plan as overdue at
the actual time a reliable source reports it to be at least
1 hour late at destination. Based on this overdue time,
apply the same procedures and action times as for
aircraft on a flight plan. When such a report is
received, verify (if possible) that the aircraft actually
departed and that the request is for a missing aircraft
rather than a person. Refer missing person reports to
the appropriate authorities.
REFERENCE-
FAAO JO 7110.10, Para 8-2-1, Initial Action/QALQ; Para 8-3-1,
INREQ; Para 8-4-1, ALNOT.
JO 7110.10T 2/14/08
8-2-1 Overdue Aircraft Action
Section 2. Overdue Aircraft Action
8-2-1. INITIAL ACTION/QALQ
a. As soon as a VFR/DVFR aircraft (military or
civil) becomes overdue, the destination station
(including intermediate destination tie-in station for
military aircraft) shall attempt to locate the aircraft by
checking the destination airport and all adjacent
airports that could accommodate the aircraft. Also,
check appropriate ATCT facilities and ARTCC
sectors through the area manager. If this communica-
tions search does not locate the aircraft, transmit a
QALQ to the departure location tie-in AFSS/FSS
and when appropriate the DUAT vendor or
AFSS/FSS where the flight plan information is on
file.
EXAMPLE-
AISR
FF KICTYFYX
DTG KHONYFYX
QALQ N12345
M1FC
ORIGIN:ICT PRECEDENCE:FF TIME: ACK:N
ADDR:MKL
TEXT
ALQ Nl2345
NOTE1. OASIS facilities, use the Transmit Search and Rescue
dialog box to transmit the QALQ.
2. If it is determined by the flight service specialist that
the local field search cannot be completed before the
INREQ transmission time, the QALQ shall be transmitted
in time to receive the information for the INREQ message.
The local field search shall continue without reference to
time until completed.
b. Use of long distance telephone in carrying out
SAR responsibilities is authorized when appropriate.
c. In the case of a U.S. registered aircraft, or any
aircraft known to be piloted by or transporting U.S.
citizens and en route within a foreign country or
between two foreign countries, if the overdue report
is received either from someone directly concerned or
from aviation authorities of a foreign country, notify
the Washington Communications Control Center
immediately via Service B message addressed to
RWA.
d. Alaska. In addition to subparas 8-2-1a and c,
address QALQ, INREQ, or ALNOT messages and
replies to PANCYAYX and PAEDYCYX.
NOTE-
RCCs other than Elmendorf AFB (PAEDYCYX) are not on
Service B and must be notified by telephone.ALQ Nl2345 C1255
b. If unable to obtain additional information
transmit a message to the destination station
containing all information not previously sent.
Include any verbal or written remarks made by the
pilot which may be pertinent to the search. The data
transmitted may be obtained from the flight plan
information or any other pertinent information
located in the DD file. This information can be
transmitted using the SV 1, TB, and RV 1 format.
Before transmitting, the message will require the
correct header to be added to ensure the QALQ reply
message is placed on the SAR list.
EXAMPLE-
AISR
FF KLOUYFYX
DTG KJBRYFYX
QALQ N12345 C150/X 110 PBF D1235 85
LIT PAH 0130/0400 CLARENCE NEWBERN
601 E 12TH MKC 555-123-4567 2 POB
WHITE/RED
M1FC
ORIGIN:RDU PRECEDENCE:FF TIME: ACK:N
ADDRIE
TEXTALQ N12345 FR:V AT:C182/T TS:120
DD:EQY TM291445 AE:035 RT:EQY..CAE
..ALD..CRG..DAB..ORL..ISM AD:ISM TE:
0400 RMREFUEL CRG FB:0430 AA: PD:
MIKE T. BROWN DQY 704-555-1212 NB:2
CR:W/R/B OP: CP:KPIEYFYX TA:291845
A/C ID TIME DEP DESTN
INFLT BRFG: N12345 14:50 EQY ISM
RMKS:AVFP
A/C ID TIME DEP DESTN
INFLT BRFG: N12345 14:00 EQY ISM
RMKS:VNR
NOTE-
OASIS facilities, retrieve data from the history files using
the SAR Search dialog box, format the message and
transmit using the Transmit Search and Rescue dialog
box.
8-2-3. CANCELLATION OF THE QALQ
If the aircraft is located by the destination station after
the QALQ is sent, transmit a cancellation message
addressed to all recipients of the QALQ.
EXAMPLE-
AISR
FF KSTLYFYX
DTG KHONYFYX
QALQ N12345 CNLD
M1FC
ORIGIN:JBR PRECEDENCE:FF TIME: ACK:N
ADDR:FOD
TEXTALQ Nl2345 CNLD
NOTE-
OASIS facilities, transmit the QALQ cancellation using
the Transmit Search and Rescue dialog box.
JO 7110.10T 2/14/08
8-3-1 Information Requests (INREQs)
Section 3. Information Requests (INREQs)
8-3-1. INREQ
If the reply to the QALQ is negative or the aircraft has
not been located within 30 minutes after it becomes
overdue:
a. The destination station shall transmit a
numbered INREQ message to the departure station,
flight watch control stations with communication
outlets along the route, and other AFSS/FSSs and
ARTCCs along the route. In addition, address RCC
and DUAT vendors using the collective address
KSARYCYX.
1. If the departure airport, route of flight,
destination airport or alternate airports are within
50_miles of the Great Lakes, include Cleveland AFSS
as an addressee. They will relay to Cleveland RCC.
2. Hawaiian stations shall give preliminary
notification to Honolulu SARCC as follows:
(a) Hilo by long distance telephone.
(b) Honolulu AFSS shall use local telephone.
(c) Secondary means for Hilo shall be Service
B to Honolulu AFSS and then by telephone between
Honolulu AFSS and the SARCC.
b. Include all information in the INREQ message
that will assist in search activities.
NOTE-
The National Search and Rescue Plan is outlined in the
AIM, para 6-2-7.
EXAMPLE1. AISR
DD (appropriate eight-character
identifiers and KSARYCYX)
DTG KJBRYFYX
JBR001 (appropriate three-character identifiers)
INREQ N12345 BE36/R 150 PAH D1235
85 PAH LIT FEXHA 1635 DALE CARNINE
601 E. 12TH ST. MKC 555-765-4321 2 POB
BROWN/WHITE (any other information available)
M1FC
ORIGIN:RDU PRECEDENCED TIME:ACK:Y
ADDRAppropriate three-character identifiers and
KSARYCYX
TEXT:INREQ N12345 FR:V AT:C152/T TS:100
DD:EQY TM291445 AE:035 RT:EQY..CAE..
ALD..CRG..DAB..ORL..ISM AD:ISM TE:0400
RMREFUEL CRG FB:0430 AA: PDAVE
JOHNSON DQY 704-555-1212 NB:1 CR:W/R/B
OP: CP:KPIEYFYX TA:291845
A/C ID TIME DEP DESTN
INFLT BRFG: N12345 14:50 EQY ISM
RMKS:AVFP
A/C ID TIME DEP DESTN
INFLT BRFG: N12345 14:00 EQY ISM
RMKS:VNR
2. AISR
DD (appropriate eight-character
identifiers and KSARYCYX)
DTG KJBRYFYX
JBR001 (appropriate three-character
identifiers)
INREQ N12345 BE36/R 150 PAH LIT
DALE CARNINE 601 E. 12TH ST MKC
WIFE REPORTS ETA 1230
M1FC
ORIGIN:OLU PRECEDENCED TIME:ACK:Y
ADDRappropriate three-character
identifiers and KSARYCYX)
TEXT:INREQ N12345 BE36/R GRI LBF
DALE CARNINE 601 E. 12TH ST MKC
WIFE REPORTS ETA 1230
NOTE-
OASIS facilities, retrieve data from the history files using
the SAR Search dialog box, format the message and
transmit using the Transmit Search and Rescue dialog
box.
c. RCC does not have transmit capability.
Acknowledgement is not required for messages to
RCC.
8-3-2. ACTION UPON RECEIPT OF INREQ
Stations receiving an INREQ shall take the following
action:
a. Seek information about the aircraft by checking
facility records and all flight plan area airports along
the proposed route of flight that could accommodate
the aircraft. Notify appropriate ATCT facilities.
Reply to the INREQ with a numbered message within
1 hour. If unable to complete the search within 1 hour,
forward a status report followed by a final report
when the search is complete. If the reply contains
JO 7110.10T 2/14/08
8-3-2 Information Requests (INREQs)
pertinent information such as aircraft location or
position report, transmit to the destination station.
EXAMPLE-
AISR
DD KLANYFYX
DTG KHONYFYX
HON001 LAN
INREQ N1234A NO SVCS PROVIDED. FPA
SRCH INCOMP
AISR
DD KLANYFYX
DTG KHONYFYX
HON002 KLANYFYX
INREQ N1234A NEG INFO
M1FC
ORIGINAN PRECEDENCED TIME: ACK:Y
ADDR:HON
TEXT:INREQ Nl234A NO SVCS PROVIDED.
FPA SRCH INCOMP
ORIGINAN PRECEDENCED TIME: ACK:Y
ADDR:HON
TEXT:INREQ N1234A NEG INFO
NOTE-
Upon receipt of INREQs and ALNOTs, ATCTs and
ARTCCs are required to check facility records, report
findings to AFSS/FSS that alerted them within 1 hour, and
retain in an active status until canceled.
REFERENCE-
FAAO JO 7110.65, Para 10-3-4, ALNOT.
b. The destination station shall retransmit the
information, as necessary, to all original addressees.
c. Cleveland AFSS. When addressed, shall notify
Cleveland U.S. Coast Guard RCC.
d. Hawaiian stations, notify Honolulu SARCC by
telephone.
e. Facilities served by the expanded 800 system
that have any portion of their incoming calls and/or
Service B diverted to another facility shall notify that
facility of the INREQ. The facility receiving diverted
calls or Service B traffic shall check their records and
advise of any information or contact with the aircraft.
8-3-3. CANCELLATION OF INREQ
The INREQ originator shall transmit a numbered
cancellation message containing the location of the
aircraft to all INREQ addressees when the aircraft is
located. Notify associated ATCT facilities.
EXAMPLE-
AISR
DD (appropriate eight-character
identifiers including KSARYCYX)
DTG KLOUYFYX
LOU001 (appropriate three-character identifiers)
INREQ N1234A CNLD LCTD BWG
M1FC
ORIGIN:FOD PRECEDENCED TIME: ACK:Y
ADDRappropriate three-character
identifiers and KSARYCYX)TEXT:INREQ Nl234A CNLD
LCTD DSM
NOTE-
OASIS facilities, transmit the INREQ cancellation using
the Transmit Search and Rescue dialog box.
JO 7110.10T 2/14/08
8-4-1 Alert Notices (ALNOTs)
Section 4. Alert Notices (ALNOTs)
8-4-1. ALNOT
If the replies to the INREQ are negative, or if the
aircraft is not located within 1 hour after transmission
of the INREQ, whichever occurs first, the destination
station shall transmit an ALNOT.
a. Address ALNOT messages to your Regional
Operations Center and those facilities within the
search area. In addition, address the DUAT vendors
and RCC using the collective address KSARYCYX.
The search area is normally that area extending
50_miles on either side of the proposed route of flight
from the last reported position to the destination. The
search area may be expanded to the maximum range
of the aircraft at the request of the RCC or by the
destination station. If the departure airport, route of
flight, destination airport, or alternate airports are
within 50 miles of the Great Lakes, include Cleveland
AFSS as an addressee. They will relay to the
Cleveland RCC.
b. Alaska. Address to PANCYGYX, PANCY-
AYX, and KSARYCYX. (Only AFSSs/FSSs in the
ALNOT search area are required to acknowledge.)
c. Include all information in the ALNOT message
that will assist in search activities (same as INREQ
plus any additional information received).
EXAMPLE-
AISR
SS (appropriate ARTCC circuit codes as identified in
subpara 10-1-4c, other addresses as identified in
subpara 8-4-1a and KSARYCYX)
DTG KRDUYFYX
ALNOT N12345 BE36/R 150 RDU D1840 75
RDU EWN FEXHA 2140
CLARENCE E. NEWBERN
601 E 12TH MKC 555-123-4567 2 POB
BROWN/TAN (any other information available)
M1FC
ORIGIN:RDU PRECEDENCE:SS TIME: ACK:N
ADDRappropriate ARTCC circuit code as identified in
subpara 10-1-4c, other addresses as identified in
subpara 8-4-1a and KSARYCYX
TEXT:ALNOT N12345 FR:V AT:C172/T TS:100
DD:EQY TM291445 AE:035 RT:EQY..CAE..
ALD..CRG..DAB..ORL..ISM AD:ISM TE:0400
RMREFUEL CRG FB:0430 AA: PD:JOHN M.
BROWN DQY 704-555-1212 NB:3 CR:W/R/B
OP: CP:KPIEYFYX TA:291845
A/C ID TIME DEP DESTN
INFLT BRFG: N12345 14:50 EQY ISM
RMKS:AVFP
A/C ID TIME DEP DESTN
INFLT BRFG: N12345 14:00 EQY ISM
RMKS:VNR
NOTE-
OASIS facilities, retrieve data from the history files using
the SAR Search dialog box, format the message and
transmit using the Transmit Search and Rescue dialog
box.
d. Ten minutes after issuance of the ALNOT, call
Tyndall AFB to ensure delivery of the ALNOT and
to answer any inquiries. (Alaska: Call Fort
Richardson, 11th RCC at (907) 428-7230,
800-420-7230, or DSN 317-384-6726.)
NOTE-
RCC (Tyndall AFB) phone numbers are:
800-851-3051 or 850-283-5955.
Defense Switching Network 523-5955.
8-4-2. ACTION UPON RECEIPT OF ALNOT
Upon receipt of an ALNOT, each station whose flight
plan area extends into the ALNOT search area shall:
a. Immediately conduct a communications search
of those flight plan area airports which fall within the
ALNOT search area that could accommodate the
aircraft and which were not checked during the
INREQ search. Notify the appropriate ATCT
facilities. Request the appropriate law enforcement
agency to check airports which cannot be contacted
otherwise. Stations that have any portion of their
incoming calls and/or Service B diverted to another
facility shall notify that facility of the ALNOT. The
facility receiving diverted traffic shall check their
records and advise of any information or contact with
the aircraft.
b. Within 1 hour after receipt of the ALNOT,
notify the originator of the results or status of the
communications search. If the reply contains
pertinent information, such as aircraft location or
position report, transmit to the destination station.
The destination station shall retransmit the informa-
tion, as necessary, to all original addresses.
EXAMPLE-
AISR
JO 7110.10T 2/14/08
8-4-2 Alert Notices (ALNOTs)
SS KFODYFYX
DTG KANBYFYX
ALNOT N12345 FLD CK INCOMP
AISR
SS KFODYFYX
DTG KANBYFYX
ALNOT N12345 ACFT LCTD OG DHN
M1FC
ORIGIN:GFK PRECEDENCE:SS TIME: ACK:N
ADDR:COU
TEXT:ALNOT N12345 FLD CK
COMPL NEG INFO
ORIGIN:GFK PRECEDENCE:SS TIME: ACK:N
ADDR:COU
TEXT:ALNOT N12345 ACFT LCTD OG DIK
c. Stations within the ALNOT search area shall
record the ALNOT. (See Para 2-2-2j, Phraseology.)
d. Request search assistance from aircraft travers-
ing the search area.
8-4-3. REPORTING ALNOT STATUS TO
RCC
If the extended communications search fails to locate
the aircraft or if 1 hour has elapsed since ALNOT
transmission, whichever occurs first, the destination
station shall call the RCC and, if appropriate, the
Cleveland AFSS, which notifies the Cleveland RCC.
Provide all pertinent available information about the
overdue aircraft not already provided in the ALNOT
to include:
a. Agency and the person calling.
b. Details of the flight plan. If the aircraft was not
on a flight plan, include all the facts about the source
of the report.
c. Time the last radio transmission was received,
by whom, and the frequency used.
d. Last position report.
e. Whether an ELT signal was heard or reported
along the route of flight.
f. Action taken and the proposed action by the
reporting station.
g. Upon request, furnish positions of other aircraft
known to be along or near the route of flight of the
missing aircraft.
8-4-4. CANCELLATION OF ALNOT
The ALNOT remains current until the aircraft is
located or the search is suspended by the RCC. The
ALNOT originator shall then transmit a cancellation
message with the location of the aircraft, if
appropriate, addressed to all recipients of the
ALNOT. Each facility shall notify all previously
alerted facilities and agencies of the cancellation.
EXAMPLE-
AISR
SS (appropriate ARTCC circuit codes
as identified in subpara 10-1-4c, other
addresses as identified in
subpara 8-4-1a and KSARYCYX)
DTG KEWNYFYX
ALNOT N12345 CNLD ACFT LCTD JAX
AISR
SS (appropriate ARTCC circuit codes
as identified in para 10-1-4c, other
addresses as identified in
subpara 8-4-1a and KSARYCYX)
DTG KEWNYFYX
ALNOT N1513B CNLD SEARCH SUSPENDED
M1FC
ORIGIN:OLU PRECEDENCE:SS TIME:ACK:N
ADDRappropriate ARTCC circuit
codes as identified in subpara 10-1-4c,
other addressees as identified in
subpara 8-4-1a and KSARYCYX)
TEXT:ALNOT Nl5l3B CNLD ACFT LCTD MCK
NOTE-
OASIS facilities, transmit the ALNOT cancellation using
the Transmit Search and Rescue dialog box.
JO 7110.10T 2/14/08
8-5-1 Other SAR Actions
Section 5. Other SAR Actions
8-5-1. CONTACT WITH AIRCRAFT
CROSSING HAZARDOUS AREA
When Lake, Island, Mountain, or Swamp Reporting
Service programs have been established and a pilot
requests the service, establish radio contact every
10_minutes (or at designated position checkpoints)
with the aircraft while it is crossing the hazardous
area. If contact with the aircraft is lost for more than
15_minutes, alert Search and Rescue.
NOTE-
Hazardous Area Reporting Service and chart depictions
are published in the AIM, para 4-1-20.
8-5-2. CANADIAN TRANSBORDER
a. Assume responsibility for initiating SAR action
on transborder aircraft upon acknowledgment for the
inbound flight notification message.
b. When SAR action is initiated, the destination
and departure facilities are responsible for all
communications search actions within their respec-
tive countries and for alerting their respective RCC.
c. Canadian communications search procedures
and action times are similar to U.S. procedures. They
will address all SAR messages to the U.S. departure
AFSS/FSS, which is then responsible for initiating
SAR action for the U.S. portion of the route of flight.
d. For inbounds from Canada, apply standard U.S.
SAR procedures contained in this chapter for the U.S.
portion of the route. Include the Canadian departure
facility as an addressee on all SAR messages since
that facility is responsible for initiating SAR action
for the Canadian portion of the route of flight.
e. Upon receipt of a Canadian QALQ, the
departure AFSS/FSS shall take the following
actions:
1. Check locally for any information about the
aircraft.
2. If unable to obtain additional information, or
within 15 minutes after receipt of the QALQ, transmit
a message to the destination facility containing all
flight plan information not previously sent.
f. Upon receipt of a Canadian INREQ, the
departure AFSS/FSS shall transmit an INREQ for the
U.S. portion of the route of flight and reply to Canada
within 1 hour in accordance with standard INREQ
procedures.
g. Upon receipt of a Canadian ALNOT, the
departure AFSS/FSS shall transmit an ALNOT for
the U.S. portion of the route and reply to Canada
within 1 hour in accordance with standard ALNOT
procedures.
JO 7110.10T 2/14/08
9-1-1 General
Chapter 9. FAA Weather Services
Section 1. General
9-1-1. PURPOSE
Surface meteorological observations are filed at
scheduled and unscheduled intervals with stations
having sending capability to WMSC for dissemina-
tion on the Service A domestic aviation weather
system. These reports are aviation routine weather
reports (METAR) and aviation selected special
weather (SPECI). All reports will include a report
type and the six-digit time of the observation.
Computer sorting and validation requires exact
adherence to format and procedure at all times.
9-1-2. SCHEDULED TRANSMISSION
TIMES
a. METAR REPORTS. Prepare and code METAR
reports for transmission between H+55 and H+00.
1. M1FC entry, use TA mask and specify H in
the time field.
2. AISR entry, use /T procedures between H+46
and H+54. Use /D procedure between H+55 and
H+00.
3. OASIS entry, use the Transmit Weather
Observation dialog box. If the Hold box is checked,
OASIS will hold the METAR report(s) until the listed
METAR Transmit Time parameter.
b. SPECI AND DELAYED OR CORRECTED
REPORTS. Transmit SPECI, delayed or corrected
reports as soon as possible after H+00.
1. M1FC entry, use TA mask and leave the time
field blank.
2. AISR entry, use /D procedure.
3. OASIS entry, use the Transmit Weather
Observation dialog box, leaving the Hold box
unchecked.
9-1-3. DISTRIBUTION
Most meteorological and NOTAM data exchanged
outside of the facility is dependent on the Weather
Message Switching Center Replacement (WMSCR).
It is important to adhere to strict form at and
procedures during normal operations, as well as
during system interruption periods.
a. Circuit interruption. Notify your tie-in facility,
the AISR Customer Service Center, WMSCR and, if
appropriate, the GS-200 Host facility of all outages.
The M1FC AFSS facility should notify their FSDPS,
AWP, and the appropriate telco servicing company.
The OASIS AFSS facility should notify WMSCR
and/or NADIN and the appropriate telco servicing
company.
b. All outage reports should refer to the correct
circuit and/or equipment identification numbers.
Facilities should obtain and record ticket numbers
provided by AISR or the telco authority.
c. AISR and WMSCR telephone numbers are as
follows:
1. AISR HELPDESK 866-466-1336.
2. WMSCR (KNKAWMSC):
Atlanta 770-210-7931.
Salt Lake City 801-320-2045.
JO 7110.10T 2/14/08
9-2-1 Pilot Weather Report (UA/UUA)
Section 2. Pilot Weather Report (UA/UUA)
9-2-1. GENERAL
Pilot Weather Reports (PIR EPs) are filed at
unscheduled times with stations having sending
capability to WMSCR for dissemination on the
Service A domestic aviation weather system. These
reports shall be entered into the system as individual
reports, not appended to a surface observation. Entry
shall only be between H+00 and H+55.
9-2-2. PREPARATION FOR
TRANSMISSION
a. M1FC entry, use WY mask. (See para 4-2-4.)
b. AISR entry, use /D procedures.
c. OASIS entry, use the Transmit PIREP dialog
box.
9-2-3. RESPONSIBILITY
AFSS/FSS specialists shall actively solicit PIREPs
in conjunction with preflight and inflight communi-
cations with pilots and assure timely dissemination of
the PIREP information. Each facility should make
special efforts to obtain PIREPs on departure and
arrival weather conditions at airports within their
flight plan area.
9-2-4. PIREP DISPLAY
Maintain a PIREP display to conform with the
particular requirements of your facility. If it is posted
for internal use only, symbology may be used at the
facility's discretion. If it is displayed as a pilot
self-briefing aid, the use of contractions, such as
OVC, shall be applicable.
9-2-5. SOLICITING PIREPs
a. Solicit PIREPs for the affected area(s) when one
or more of the following weather conditions exist, are
reported, or forecast to occur:
1. Ceilings at or below 5,000 feet.
2. Visibility reported on the surface or aloft is
5_miles or less.
3. Thunderstorms and related phenomenon.
4. Turbulence of moderate degree or greater.
5. Icing of light degree or greater.
6. Wind shear.
7. Volcanic ash clouds are reported or forecast.
NOTE-
Pilots may forward PIREPs regarding volcanic activity
using the format described in the Volcanic Activity
Reporting Form (VAR) as depicted in the Aeronautical
Information Manual, Appendix 2.
b. Also, solicit PIREPs regardless of weather
conditions when:
1. An NWS or ATC facility indicates a need
because of a specific weather or flight assistance
situation.
2. Necessary to determine flying conditions
pertinent to natural hazards (mountain passes, ridges,
peaks) between the weather reporting stations.
3. The station is designated as responsible for
PIREPs in an offshore coastal area.
c. Flight watch specialists shall solicit sufficient
PIREPs to remain aware of flight conditions.
d. To solicit PIREPs within a specific area,
broadcast a request on NAVAIDs, transcribed
broadcast facilities, or a selected communications
frequency.
PHRASEOLOGY-
PILOT WEATHER REPORTS ARE REQUESTED
(location/area). CONTACT (name) RADIO/FLIGHT
WATCH ON (frequency) TO REPORT THESE
CONDITIONS.
9-2-6. RECORDING OF PIREP DATA
Record PIREP data directly into M1FC or OASIS, or
on FAA Form 7110-2, or on other material deemed
appropriate; e.g., 5'' x 8'' plain paper.
9-2-7. DATA TO BE INCLUDED IN PIREPs
Include the following reports of flight conditions, as
appropriate:
a. Height and coverage of cloud bases, tops, and
layers.
b. Flight visibility.
JO 7110.10T 2/14/08
9-2-2 Pilot Weather Report (UA/UUA)
c. Restrictions to visibility and weather occurring
at altitude.
d. Air temperature and changes to temperature
with altitude or range.
e. Direction and speed of wind aloft.
f. Extent and intensity of turbulence.
REFERENCE-
FAAO JO 7110.10, Para 9-2-8.
g. Extent, type, and intensity of icing.
REFERENCE-
FAAO JO 7110.10, Para 9-2-9.
h. Weather conditions and cloud cover through
mountain passes and over ridges and peaks.
i. Location, extent, and movement of thunder-
storms and/or tornadic activity.
j. Excessive winds aloft, LLWS , and other
phenomena bearing on safety and efficiency of flight.
9-2-8. REPORTING TURBULENCE IN
PIREPs
a. Turbulence reports should include location,
altitude, or range of altitudes, and aircraft type, and
should include whether in clouds or clear air. The
degree of turbulence, intensity, and duration
(occasional, intermittent, and continuous) is deter-
mined by the pilot. It is essential that the report is
obtained and dissem inated when possible in
conformance with the U.S. Standard Turbulence
Criteria Table as follows:
1. Light. Loose objects in aircraft remain at rest.
2. Moderate. Unsecured objects are dislodged.
Occupants feel definite strains against seat belts and
shoulder straps.
3. Severe. Occupants thrown violently against
seat belts. Momentary loss of aircraft control.
Unsecured objects tossed about.
4. Extreme. Aircraft is tossed violently about,
impossible to control. May cause structural damage.
b. Report CAT or CHOP if used by the pilot to
describe the type of turbulence.
9-2-9. REPORTING ICING CONDITIONS IN
PIREPs
a. Icing reports shall include location, altitude or
range of altitudes, type aircraft, air temperature,
intensity, and type of icing.
b. Icing types.
1. Rime. Rough, milky, opaque ice formed by
the instantaneous freezing of small super-cooled
water droplets.
2. Clear. A glossy, clear or translucent ice
formed by the relatively slow freezing of large
super-cooled water droplets.
3. Mixed. A combination of rime and clear.
c. Icing intensity.
1. Trace. Ice becomes perceptible. Rate of
accumulation slightly greater than sublimation.
Deicing/anti-icing equipment is not utilized unless
encountered for an extended period of time (over
1_hour).
2. Light. The rate of accumulation may create a
problem if flight is prolonged in this environment
(over 1 hour). Occasional use of deicing/anti-icing
equipment removes/prevents accumulation. It does
not present a problem if deicing/anti-icing is used.
3. Moderate. The rate of accumulation is such
that even short encounters become potentially
hazardous, and use of deicing/anti-icing equipment
or diversion is necessary.
4. Severe. The rate of accumulation is such that
deicing/anti-icing equipment fails to reduce or
control the hazard. Immediate diversion is necessary.
9-2-10. MEANS USED TO SOLICIT PIREPs
Inform pilots of a need for PIREPs. The following
methods may be used to collect PIREPs:
a. During preflight weather briefings.
b. On post-flight contacts.
c. During regular air-ground contacts.
d. Broadcast a request on NAVAID frequencies.
e. Append a request on HIWAS, TIBS, VOR-
TWEB, or TWEB broadcasts.
f. Request PIREPs from air carrier and military
operations offices, military pilot-to-forecaster units,
and local aircraft operators.
JO 7110.10T 2/14/08
9-2-3 Pilot Weather Report (UA/UUA)
g. Solicit from other air traffic facilities.
9-2-11. PIREP CLASSIFICATION
Categorize PIREPs as follows:
a. URGENT. The following weather phenomena
shall be classified as an URGENT (UUA) PIREP:
1. Tornadoes, funnel clouds, or waterspouts.
2. Severe or extreme turbulence (including clear
air turbulence).
3. Severe icing.
4. Hail.
5. Low level wind shear. Classify LLWS
PIR EPs as UUA if the pilot reports air speed
fluctuations of 10 knots or more. Classify reports of
LLWS with air speed fluctuations less than 10 knots
as routine. If air speed fluctuation is not reported,
classify PIREP as UUA.
NOTE-
LLWS defined as windshear within 2,000 feet of the
surface.
6. Volcanic ash clouds.
7. Any other weather phenomena reported
which are considered by the specialist as being
hazardous, or potentially hazardous, to flight
operations.
b. ROUTINE. Classify as ROUTINE (UA) all
PIREPs received except those listed above.
9-2-12. PIREP HANDLING
Upon receipt of a PIREP, accomplish the following:
a. Urgent.
1. Deliver to the ARTCC Weather Coordinator
as soon as possible.
2. Deliver to the associated WSO as soon as
possible.
3. Enter on Service A at the first opportunity.
4. Use in weather briefings, as appropriate.
b. Routine.
1. Transmit on Service A as soon as practical.
2. Broadcast in accordance with established
procedures in Chapter 2.
3. Use in weather briefings, as appropriate.
9-2-13. OFFSHORE COASTAL ROUTES
When your station has been given responsibility for
collecting offshore coastal route PIREPs:
a. Include the coastal water area when soliciting
PIREPs. At least one PIREP is required hourly
regardless of weather conditions.
b. Pacific. Hawaiian Island station areas coincide
with the Honolulu ARTCC sectors and the entire
Hawaiian area is designated as offshore areas for
PIREP purposes.
NOTE-
The Flight Services Operations Area Office assigns
PIREP responsibility for an offshore coastal area, route,
or route segment to a specific station. The area assigned
will be within the same ARTCC area as the station, and the
station shall have adequate air-ground communications
coverage over its assigned offshore area.
9-2-14. PIREP PREPARATION
To assure proper dissemination of PIREPs to all
system users, the encoding procedures listed below
shall be followed:
a. Identify each element by a Text Element
Indicator (TEI).
b. Ensure each report includes TEIs for message
type, location, time, altitude/flight level, type
aircraft, and at least one other to describe the reported
phenomena.
c. Precede each TEI, except message type, with a
space and a solidus (/).
d. Follow each TEI, except altitude/flight level,
with a space.
e. Insert zeros in reported values when the number
of digits in the report is less than the number required
by the format.
f. Use only authorized aircraft designators and
contractions.
g. In the location TEI, include any three-letter
identifier to describe locations or routes.
h. Omit entries of TEIs, except as listed in
subpara_9-2-14b, for which no data was reported.
JO 7110.10T 2/14/08
9-2-4 Pilot Weather Report (UA/UUA)
9-2-15. PIREP FORMAT
Using TEIs as described below, prepare PIREPs for
system entry in the following format:
NOTE-
OASIS. If using the “Folded” Transmit PIREP
dialog box, each TEI must be specified and can be
entered in any order. OASIS will automatically
format the message before transmission.
a. UUA or UA. Message type - Urgent or Routine
PIREP.
b. /OV.
1. Location in reference to a VHF NAVAID or
an airport, using the three or four letter identifier. If
appropriate, encode the identifier, then three digits to
define a radial and three digits to define the distance
in nautical miles.
EXAMPLE/OV KJFK
/OV KJFK107080
/OV KFMG233016/RM RNO 10SW| 欢迎光临 航空论坛_航空翻译_民航英语翻译_飞行翻译 (http://bbs.aero.cn/) | Powered by Discuz! X2 |