6. After acknowledgment has been received,
advise the pilot to set the ADF function switch to the
ADF position and report the reading.
PHRASEOLOGY-
IF YOU HAVE A ROTATING COMPASS CARD (ROSE)
ON YOUR A-D-F INDICATOR, MAKE CERTAIN
NORTH IS AT THE TOP OF THE DIAL. TURN THE
FUNCTION SWITCH TO THE A-D-F POSITION.
WHEN THE NEEDLE STABILIZES, ADVISE THE
A-D-F NEEDLE READING.
REFERENCE-
The Instrument Flying Handbook. North may mean “north, N, zero (0) or
360.”
7. Compute the magnetic bearing.
NOTE-
Relative Bearing (RB) + Magnetic Heading (MH) =
Magnetic Bearing (MB)
If the MB exceeds 360 degrees, subtract 360 to determine
MB; i.e., 480 degrees - 360 degrees = 120 degrees MB.
8. Advise the pilot of direction from the NDB.
PHRASEOLOGY-
YOU ARE (direction) OF THE (name) RADIO BEACON.
b. Orientation.
1. Turn the aircraft inbound to the NDB being
used. Provide the direction of the turn and the heading
to be flown. Advise the pilot to report when
established on that heading.
PHRASEOLOGY-
FOR A-D-F ORIENTATION, TURN LEFT/RIGHT
HEADING (degrees). REPORT ESTABLISHED
HEADING (degrees).
2. Notify the appropriate control facility.
Provide all required information including the
aircraft's position and heading.
JO 7110.10T 2/14/08
5-4-2 ADF/VOR Orientation
3. Verify that the aircraft is established on a line
of position to the NDB.
PHRASEOLOGY-
WHAT IS YOUR A-D-F NEEDLE READING?
4. Provide heading adjustments as needed for
the aircraft to continue inbound to the NDB.
(a) If the pilot indicates an ADF reading other
than 3-6-0, compute the new heading and advise the
aircraft.
PHRASEOLOGY-
TURN LEFT/RIGHT HEADING (degrees). REPORT
ESTABLISHED HEADING (degrees).
(b) After pilot reports established and needle
is on 3-6-0, heading adjustments are not necessary.
PHRASEOLOGY-
CONTINUE HEADING (degrees).
c. Crossfixing. After the aircraft is established
inbound to the NDB, use the following procedures:
1. Advise the pilot to tune the ADF receiver to
the NDB to be used for crossfixing. Provide the NDB
name, identifier, and frequency.
PHRASEOLOGY-
TUNE YOUR A-D-F RECEIVER TO THE (name)
RADIO BEACON, FREQUENCY (frequency),
IDENTIFICATION (identification). CHECK VOLUME
UP AND IDENTIFY THE STATION. ADVISE WHEN
YOU HAVE DONE THIS.
2. After acknowledgment has been received,
request ADF reading.
PHRASEOLOGY-
WHEN THE NEEDLE STABILIZES, ADVISE THE
A-D-F NEEDLE READING.
3. Compute and plot the second line of position.
NOTE-
The intersection of the two lines of position is the aircraft's
position at the time of the second ADF reading.
4. Advise the pilot of the aircraft's position and
the safe altitude for orientation in that area.
PHRASEOLOGY-
YOU ARE (miles)(direction) OF THE (name) RADIO
BEACON. THE SAFE ALTITUDE FOR ORIENTATIONS
IN THAT AREA IS (feet).
5. Request pilot's intentions and provide
assistance, as requested.
PHRASEOLOGY-
WHAT ARE YOUR INTENTIONS?
5-4-3. VOR ORIENTATION/VOR CROSSFIX
When using VOR orientation and/or crossfix
procedures, determine the aircraft's position as
follows:
a. Position Fixing.
1. Advise the pilot to remain VFR and provide
the local altimeter setting.
PHRASEOLOGY-
MAINTAIN V-F-R AT ALL TIMES. ADVISE IF
HEADING OR ALTITUDE CHANGE IS NECESSARY TO
REMAIN V-F-R. (Location) ALTIMETER (setting).
2. Obtain heading and altitude. Advise the pilot
to maintain straight and level flight and to align the
heading indicator to agree with the magnetic
compass.
PHRASEOLOGY-
MAINTAIN STRAIGHT AND LEVEL FLIGHT. RESET
YOUR HEADING INDICATOR TO AGREE WITH YOUR
MAGNETIC COMPASS. AFTER YOU HAVE DONE
THIS, SAY YOUR HEADING AND ALTITUDE.
3. Determine the weather conditions and the
fuel status.
PHRASEOLOGY-
WHAT IS THE WEATHER AT YOUR ALTITUDE AND
FUEL REMAINING IN TIME.
4. Advise the pilot to maintain the sam e
heading, verify the aircraft has VOR equipment, and
determine the airspeed.
PHRASEOLOGY-
CONTINUE HEADING (degrees). WHAT TYPE OF
NAVIGATIONAL EQUIPMENT DO YOU HAVE ON
BOARD, AND WHAT IS YOUR AIRSPEED?
5. If the pilot calls on a simplex frequency, such
as 122.2, advise the pilot to tune the receiver to the
VOR you have selected. Provide the VOR name,
frequency, and communication procedures.
PHRASEOLOGY-
CONTINUE TRANSMITTING THIS FREQUENCY.
TUNE YOUR V-O-R RECEIVER TO THE (name)
V-O-R, FREQUENCY (frequency) IDENTIFICATION
(identification). CHECK VOLUME UP AND IDENTIFY
THE STATION. ADVISE WHEN YOU HAVE DONE
THIS.
NOTE-
If the pilot calls on duplex (122.1), use the VOR the pilot
is tuned as the initial VOR.
JO 7110.10T 2/14/08
5-4-3 ADF/VOR Orientation
6. Determine the aircraft's course selector
reading.
PHRASEOLOGY-
ROTATE YOUR COURSE SELECTOR SLOWLY UNTIL
THE LEFT/RIGHT NEEDLE CENTERS WITH A “TO”
INDICATION. ADVISE YOUR COURSE SELECTOR
READING.
7. Advise the pilot of the aircraft's position.
PHRASEOLOGY-
YOU ARE (direction) OF THE (name) V-O-R.
b. Orientation.
1. Turn the aircraft inbound to the VOR being
used. Provide the direction of turn and the heading to
be flown. Advise the pilot to report when established
on that heading.
PHRASEOLOGY-
FOR V-O-R ORIENTATION, TURN LEFT/RIGHT
HEADING (degrees). REPORT ESTABLISHED
HEADING (degrees).
2. Notify the appropriate control facility.
Provide all the required information including the
aircraft's position and heading.
3. Verify that the aircraft is established on a line
of position to the VOR.
PHRASEOLOGY-
WHAT IS THE POSITION OF YOUR LEFT/RIGHT
NEEDLE?
4. Provide heading adjustments as needed for
the aircraft to continue inbound to the VOR.
(a) When the pilot indicates the left/right
needle is not centered, advise the pilot to recenter
needle with a “TO” indication and report the course
selector reading.
PHRASEOLOGY-
Pilot response indicates needle not centered.
ROTATE YOUR COURSE SELECTOR SLOWLY UNTIL
THE LEFT/RIGHT NEEDLE CENTERS WITH A “TO”
INDICATION. ADVISE YOUR COURSE SELECTOR
READING. (If appropriate) TURN LEFT/RIGHT
HEADING (degrees). REPORT ESTABLISHED
(degrees).
(b) After the aircraft is established on the
inbound radial, advise the aircraft to continue on the
inbound heading.
PHRASEOLOGY-
CONTINUE HEADING (degrees).
5. _Plot line of position.
c. Crossfixing. After the aircraft is established
inbound to the VOR, use the following procedures:
1. Advise the pilot to tune the receiver to the
VOR you have selected for crossfixing. Provide VOR
name, frequency, and lost communications proce-
dures.
PHRASEOLOGY-
CONTINUE TRANSMITTING THIS FREQUENCY.
TUNE YOUR V-O-R RECEIVER TO THE (name)
V-O-R, FREQUENCY (frequency), IDENTIFICATION
(identification). CHECK VOLUME UP. IF
COMMUNICATION IS NOT ESTABLISHED
IMMEDIATELY, RETURN TO THIS FREQUENCY.
2. Using only the voice feature of the second
VOR, establish positive communication with the
aircraft.
PHRASEOLOGY(Name) RADIO TRANSMITTING ON THE (name)
V-O-R. HOW DO YOU HEAR? OVER.
NOTE-
Transmit only on the frequency of the VOR being used for
crossfixing, if available.
3. After communication has been reestablished,
advise the pilot to recenter the VOR left/right needle
and advise the reading.
PHRASEOLOGY-
ROTATE YOUR COURSE SELECTOR SLOWLY UNTIL
THE LEFT/RIGHT NEEDLE CENTERS WITH A “TO”
INDICATION. ADVISE YOUR COURSE SELECTOR
READING.
4. If the pilot is transmitting on duplex (122.1)
and the cross fix VOR has no voice capability provide
the following instructions.
PHRASEOLOGY-
CONTINUE TRANSMITTING THIS FREQUENCY.
TUNE YOUR VOR RECEIVER TO THE (name) VOR,
FREQUENCY (frequency), IDENTIFICATION (ident).
CHECK VOLUME UP AND IDENTIFY THE STATION.
ROTATE YOUR COURSE SELECTOR SLOWLY UNTIL
THE LEFT/RIGHT NEEDLE CENTERS WITH A “TO”
INDICATION. ADVISE YOUR COURSE SELECTOR
READING (PAUSE).
RETUNE YOUR VOR RECEIVER TO THE (name) VOR,
FREQUENCY (frequency), IDENTIFICATION
(identification). SAY YOUR AIRCRAFT
IDENTIFICATION AND THE (name) VOR COURSE
SELECTOR READING.
JO 7110.10T 2/14/08
5-4-4 ADF/VOR Orientation
5. Advise the pilot to continue the inbound
heading.
PHRASEOLOGY-
CONTINUE HEADING (degrees).
6. Plot the new line of position from the second
VOR, advise the pilot of the aircraft's position, and
the safe altitude for orientation in that area.
PHRASEOLOGY-
YOU ARE (miles) (direction) OF THE (name) V-O-R.
THE SAFE ALTITUDE FOR ORIENTATIONS IN THAT
AREA IS (feet).
NOTE-
The intersection of the two lines of position is the aircraft's
position at the time of the second VOR reading.
7. Request the pilot's intentions.
PHRASEOLOGY-
WHAT ARE YOUR INTENTIONS?
5-4-4. GUIDANCE TO AIRPORT
After establishing the aircraft's position and if the
pilot requests guidance to the airport:
a. Plot the course to the airport.
b. Provide the course guidance information to the
pilot.
1. Advise the pilot of the direction of the turn
and the heading to the airport.
PHRASEOLOGY-
FOR A HEADING TO THE (name) AIRPORT, TURN
LEFT/RIGHT HEADING (degrees). REPORT
ESTABLISHED HEADING (degrees).
2. After the pilot reports established on the
heading to the airport, advise the pilot of the position
in relation to the airport.
PHRASEOLOGY-
YOU ARE (miles) (direction) OF THE (name) AIRPORT.
CONTINUE HEADING (degrees).
3. Continue to provide assistance in the form of
pilotage and airport information as necessary.
PHRASEOLOGY-
DO YOU SEE ANY PROMINENT LANDMARKS?
ARE YOU FAMILIAR WITH THE (name) AIRPORT?
(Name) AIRPORT FIELD ELEVATION (feet). IT HAS
(number and surface type) RUNWAYS. THE RUNWAY/S
RUN (direction). THE AIRPORT IS LOCATED
(direction/distance) FROM (landmark visible to the
aircraft).
4. Advise the pilot to report the landing airport
in sight.
PHRASEOLOGY-
REPORT AIRPORT IN SIGHT.
5. Determine when the pilot no longer needs
assistance.
PHRASEOLOGY-
DO YOU REQUIRE FURTHER ASSISTANCE?
6. When the pilot indicates assistance is no
longer required, terminate the service. Provide the
CTAF frequency, if appropriate, and the local
altimeter setting.
PHRASEOLOGY(VOR/ADF) ORIENTATION SERVICE TERMINATED.
COMMON TRAFFIC ADVISORY FREQUENCY
(frequency). ALTIMETER (setting).
NOTE-
CTAF is defined as a UNICOM, Multicom, AFSS/FSS, or
ATCT frequency.
7. Notify appropriate control facility of the
aircraft's position, termination of services, and the
pilot's intentions.
JO 7110.10T 2/14/08
6-1-1 General
Chapter 6. Flight Data
Section 1. General
6-1-1. COMMUNICATIONS SERVICE
Most flight movement data exchanged outside of the
facility is processed by automated systems such as
the National Airspace Data Interchange Network
(NADIN). It is important to adhere to strict format
and procedures during normal operations as well as
system interruption periods.
a. Circuit interruption notifications should be as
follows:
1. AFSS.
(a) M1FC. Notify their FSDPS and ap-
propriate telco servicing company of all outages.
(b) OASIS. Notify NADIN or WMSCR, (as
appropriate), the Harris Help Desk, and appropriate
telco servicing company of all outages.
NOTE-
The FSDPS notifies NADIN for Service B outages or AWP
for Service A outages, as well as the ARTCC Systems
Engineer (SE).
2. FSS. Notify their guard facility, the AISR
Customer Service Center, and NADIN.
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.
NOTE-
OASIS facilities should obtain and record ticket numbers
provided by Harris or the telco servicing company.
c. AISR and NADIN telephone numbers are as
follows:
1. NADIN/ATLANTA (KATLYTYX)
(770) 210-7675.
2. NADIN/SALT LAKE CITY (KSLCYTYX)
(801) 320-2172.
3. AISR HELPDESK 866-466-1336.
d. OASIS telephone numbers are as follows:
1. WMSCR/ATLANTA 770-210-7931.
2. WMSCR/SALT LAKE CITY
801-320-2045.
3. HARRIS HELPDESK 877-373-0110.
6-1-2. FLIGHT PLANS
The filing of VFR flight plans is recommended. Brief
pilots, as appropriate, on the following:
a. Identify the tie-in station for the departure
point, and advise the pilot to report departure time
directly to that facility.
b. When a departure report is unlikely because of
inadequate communications capability, advise the
pilot that the flight plan will be activated
immediately, using the proposed departure time as
the actual departure time. Include “ASMD DEP” in
remarks. The pilot is responsible for cancelling or
extending the flight plan if the flight is cancelled or
delayed.
c. Determine the flight plan area in which the
destination is located. Request the pilot close the
flight plan with the tie-in station. Provide the pilot
the tie-in station's phone number, upon request.
d. Recommend that a separate flight plan be filed
for each leg of a VFR flight.
e. Request the pilot inform an AFSS/FSS
whenever the filed time en route changes more than
30_minutes.
f. On return flights from remote areas, such as a
fishing site, establish a mutually acceptable date/time
with the pilot for alerting search and rescue.
g. On a single flight to be conducted under both
IFR/VFR flight rules, confirm whether the VFR
portion is by flight plan and, if so, with whom the
pilot will close. File two separate flight plans.
h. If a pilot indicates the flight will penetrate
Class_A airspace, advise the pilot of the Class_A
requirements.
i. When a pilot files to an airport served by a
part-time FSS and the ETA is during the period the
facility is closed, ask the pilot to close with the
JO 7110.10T 2/14/08
6-1-2 General
associated AFSS/FSS, identified in FAAO
JO_7350.8, Location Identifiers and the Airport/Fa-
cility Directory.
j. Upon request, inform pilots filing IFR flight
plans of the appropriate and most effective means of
obtaining IFR departure clearances.
k. When a pilot files a DVFR flight plan, advise
the pilot to activate with Flight Service. Also advise
the pilot that a discrete beacon code will be assigned
upon activation.
NOTE1. A discrete beacon code may be assigned when the
flight plan is filed, as necessary. If the pilot wants to file
a DVFR flight plan that departs outside the facility's flight
plan area, provide the applicable toll-free number for the
departure FSS.
2. Discrete beacon codes are assigned to facilities in
accordance with FAAO 7110.66, National Beacon Code
Allocation Plan.
6-1-3. FLIGHT PLAN DATA
Handle flight plan data as follows:
a. AISR.
1. Record flight plan data received from an
operations office on FAA Form 7233-1 or a flight
progress strip. The operations office must obtain
complete information on the flight, but need forward
to the FAA only those items necessary for control or
VFR flight plan purposes.
2. Accept military flight plan proposals,
cancellations, and closures from any source
including collect telephone calls.
3. Pass the FAA Form 7233-1 to the appropriate
operating position for delivery of the flight
notification message.
b. M1FC/OASIS.
1. Record flight plan data on domestic or ICAO
flight plan mask or dialog box as appropriate. Flight
plan data received from an operations office may be
limited to only those items necessary for control or
VFR flight plan purposes, provided the operations
office obtains complete information on the flight.
2. Accept military flight plan proposals,
cancellations, and closures from any source,
including collect telephone calls.
3. Transmit flight notification messages as
follows:
(a) M1FC. From a flight plan mask in order
for M1FC to place the message in the aircraft data file
and provide automatic log and tally.
(b) OASIS. From a flight plan dialog box in
order for OASIS to place the message in the history
file and provide automatic log and tally.
NOTE-
Part-time operations offices must provide complete
information in the event it is needed for SAR purposes.
6-1-4. PART-TIME FSS CLOSURE ACTION
Part-time facilities shall forward the following
information to the designated guard AFSS/FSS.
a. Inbound flights - all information.
b. Outbound flights - VFR and IFR flight plan
data when proposed departure time and/or ETA is
within the period from 1 hour prior to closing until
1_hour after opening.
c. All other pertinent information; e.g., NOTAM,
pending outages.
JO 7110.10T 2/14/08
6-2-1 Flight Plan Proposals
Section 2. Flight Plan Proposals
6-2-1. FLIGHT PLAN RECORDING
Record flight plans on FAA Form 7233-1, M1FC
Domestic Flight Plan Mask, or in the OASIS
Domestic Flight Plan dialog box. Completion of all
blocks or fields is not required in every case, and all
items filed are not always transmitted. Use authorized
abbreviations where possible. Complete as follows:
NOTE-
OASIS. For detailed instructions on the Domestic
Flight Plan dialog box, refer to the WINGS online
help or the WINGS System Users Guide.
a. Item 1. Type of flight plan.
1. FAA Form 7233-1. Check the appropriate
box.
2. M1FC- FR: field.
(a) V - civilian VFR flight plans including
DVFR.
(b) MV - military VFR flight plans.
(c) PV - VFR flight plans departing from
outside the facility's flight plan area.
(d) DV - Do not use. See para 6-6-3a.
(e) I - civil IFR flight plans or military IFR
flight plans that do not require transmission of a flight
notification message.
(f) MI - military IFR flight plans that require
a flight notification message.
(g) PI - IFR flight plans departing from
outside the facility's flight plan area that require a
flight notification message.
NOTE1. M1FC. PI for transborder flights that require an
ADCUS (Mexico) or CANPASS/GATE (Canada/US)
flight notification message. PI messages are addressed to
the departure tie-in station. They are in addition to the
I_message transmitted to the departure ARTCC. Remarks
to be transmitted by the departure station as part of the
flight notification message must be included in the PI
message and preceded by a $ sign.
2. OASIS. IFR transborder flights that require an ADCUS
(Mexico) flight notification message will be automatically
addressed and transmitted to the departure ARTCC and
the departure tie-in station if ADCUS is entered in
remarks. To send an IFR Canadian flight plan departing
from outside the facility's flight plan area that requires a
flight notification message, enter the following in
remarks: $CANPASS %ADCUS. OASIS uses the ADCUS
to automatically address and transmit the flight plan to the
departure tie-in station but the only remark transmitted is
CANPASS. This is in addition to the message transmitted
to the departure ARTCC.
(h) SC - Stereo flight plans for civil aircraft.
(i) SM_-_Stereo flight plans for military
aircraft.
3. OASIS - Select type of flight plan from the
Flight Rules (FR) drop down list:
(a) VFR - civilian VFR flight plans,
including DVFR.
(b) IFR
(c) DVFR - Do not use. See para 6-6-3a.
(d) MIL VFR
(e) MIL IFR
(f) STEREO CVL
(g) STEREO MIL
(h) MIL IFR STOPOVER
(i) MIL VFR STOPOVER
(j) DVFR STOPOVER - Do not use.
b. Item 2. Aircraft Identification (M1FC- AI:
field. OASIS - Aircraft ID text box). Enter as
follows, but do not exceed seven alphanumeric
characters:
1. Civil Aircraft Including Air Carrier: Aircraft
letter/digit registration including the letter T prefix
for air taxi aircraft, the letter L for LIFEGUARD
aircraft, or the three-letter aircraft company
designator specified in FAAO JO 7340.2, Contrac-
tions followed by the trip or the flight number.
EXAMPLE-
N12345
TN5552Q
AAL192
LN751B
NOTE-
The letter L shall not be entered in Item 2 of the flight plan
for air carrier or air taxi LIFEGUARD aircraft. Include
7/31/08 JO 7110.10T CHG 1
JO 7110.10T 2/14/08
6-2-2 Flight Plan Proposals
the word LIFEGUARD in the remarks section of the flight
plan.
2. U.S. Military Aircraft. Use the military
abbreviation followed by the last five digits of the
aircraft's number. For certain tactical mission
aircraft, enter the assigned three-to-six letter code
word followed by a one-to-four digit number.
(See TBL 6-2-1.)
TBL 6-2-1
Military
Abbreviation Military Service
A USAF
C Coast Guard
E Air Evacuation
G Air/Army National Guard
L LOGAIR (USAF contract)
R Army
RCH REACH (USAF Air Mobility
Command)
S Special Air Mission
VM Marine Corps
VV Navy
3. Canadian Military Aircraft. The abbrevi-
ations shall be followed by a number group not to
exceed four digits. (See TBL 6-2-2.)
TBL 6-2-2
Canadian Military
Abbreviation Military Service
CFC Canadian Forces
CTG Canadian Coast Guard
c. Item 3. Aircraft Type (M1FC- AT: field.
OASIS_- Aircraft Type text box). Insert the name or
abbreviation (two-to-four alphanumeric characters)
of the manufacturer's or military designation. For
homebuilt/experimental aircraft, use HXA, HXB, or
HXC in accordance with the FAAO JO 7340.2,
Contractions. Spell out aircraft type in Remarks.
NOTE-
OASIS. OASIS validates all aircraft types in accordance
with FAAO JO 7340.2, Contractions. Nonstandard
contractions will be rejected.
1. Prefix to Aircraft Type (one-to-two alphanu-
meric characters). For IFR operations, if the aircraft's
weight class is heavy, indicate this with the prefix
“H”. If a formation flight is planned, enter the number
and type of aircraft; e.g., 2H/B52.
2. Suffix to Aircraft Type (one alpha character).
Indicate for IFR operations the aircraft's radar
transponder, DME, or RNAV (includes LORAN)
capability by adding the appropriate symbol
preceded by a slant (/). (See TBL 6-2-3.)
TBL 6-2-3
Suffix to Aircraft Type
Suffix Aircraft Equipment Suffixes
DME
/A Transponder with Mode C.
/B Transponder with no Mode C.
/D No transponder.
NO DME
/T Transponder with no Mode C.
/U Transponder with Mode C.
/X No transponder.
TACAN ONLY
/M No transponder.
/N Transponder with no Mode C.
/P Transponder with Mode C.
AREA NAVIGATION (RNAV)
/C LORAN, VOR/DME, or INS, transponder
with no Mode C.
/I LORAN, VOR/DME, or INS, transponder
with Mode C.
/Y LORAN, VOR/DME, or INS with no trans-
ponder.
ADVANCED RNAV With Transponder and
Mode C (If an aircraft is unable to operate
with a transponder and/or Mode C, it will re-
vert to the appropriate code listed above under
Area Navigation.)
/E Flight Management System (FMS) with
DME/DME and IRU position updating.
/F FMS with DME/DME position updating.
/G Global Navigation Satellite System (GNSS),
including GPS or WAAS, with en route and
terminal capability.
/R Required Navigational Performance. The
aircraft meets the RNP type prescribed for
the route segment(s), route(s) and/or area
concerned.
Reduced Vertical Separation Minimum
(RVSM). Prior to conducting RVSM opera-
tions within the U.S., the operator must ob-
tain authorization from the FAA or from the
responsible authority, as appropriate.
/J /E with RVSM
JO 7110.10T 2/14/08
6-2-3 Flight Plan Proposals
Suffix to Aircraft Type (continued)
/K /F with RVSM
/L /G with RVSM.
/Q /R with RVSM.
/W RVSM.
NOTE-
The /E and /F suffixes will only be used by aircraft
operating to and from airports within the U.S., unless
authorized by the controlling authority.
REFERENCE-
FAAO JO 7110.65, Para 2-3-7 and TBL 2-3-7, Aircraft Equipment
Suffix.
d. Item 4. True Airspeed (TAS Knots) (M1FC-
TS: field. OASIS_- Airspeed text box). Enter
two-to-four digits for TAS in knots; M followed by
three digits for Mach number; or SC for “speed
classified.”
e. Item 5. Departure Point.
1. M1FC- DD: field. Enter two-to-twelve
alphanumeric and slant characters for name or
identifier of the departure airport or point over which
the flight plan is activated.
NOTE-
Names may be used when there is no identifier available
and they do not exceed 12 characters with no spaces.
Unless a geographic point is converted to latitude/longi-
tude or fix-radial-distance (FRD), the M1FC computer
will not be able to provide weather/NOTAM information
and the route override function must be used to transmit
or modify the flight plan.
2. OASIS - Departure text box. Enter the
departure point as follows: 2-5 alphanumeric
character LOCID, 8-11 character fix-radial-distance
or 9-12_character latitude/longitude.
f. Item 6. Departure Time.
1. M1FC- TM: field. Enter departure time in
UTC. Prefix this time with a P in the TM: field for
proposals or a D for departures. If the departure time
is assumed, indicate this in the Remarks field.
2. OASIS - ETD text box. Enter the proposed
or actual time of departure as fol-
lows: {(DD)HHMM : DD = 01-31, HH = 00-23,
MM = 00-59}.
NOTE-
OASIS does not use prefixes (i.e., “P” or “D”) to determine
a proposed or actual time of departure. This determination
is made based on which button is used for filing.
g. Item 7. Cruising Altitude (M1FC- AE: field.
OASIS - Enroute Altitude text box). Proposed
altitude or flight level using two-to-seven charac-
ters; e.g., 80 or 080, OTP, OTP/125, VFR, ABV/060.
h. Item 8. Route of Flight (M1FC- RT: field.
OASIS_- Route text box.). Enter identifiers for
airways or jet routes to clearly indicate the proposed
flight path. For direct flight, use names or identifiers
of navigation aids, Navigation Reference System
(NRS) waypoints, and geographical points or
coordinates. If more than one airway or jet route is to
be flown, clearly indicate the transition points.
NOTE1. On some direct flights beyond the departure center's
airspace, it may be necessary to include a fix in the
adjacent center's airspace or latitude/longitude coordi-
nates, as appropriate, to facilitate computer acceptance.
Local procedures should be applied to these special
situations.
2. NRS waypoints consist of five alphanumeric charac-
ters, 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”
i. Item 9. Destination.
1. M1FC- AD: field. Enter two-to-twelve
alphanumeric and/or slant characters for name or
identifier of the destination airport or point over
which the flight plan is to be cancelled.
2. OASIS_- Destination text box. Enter the
destination airport or point over which the flight plan
is to be cancelled as follows: 2-5 alphanumeric
character LOCID, 8-11 character fix-radial-distance
or 9-12 character latitude/longitude.
j. Item 10. Estimated Time Enroute (M1FC- TE:
field. OASIS - Time Enroute text box). Enter in
hours and minutes the total elapsed time between
departure and destination; e.g., 0430 or 4+30. For
IFR proposals, ETE must be in four-digit format; i.e.,
0215.
NOTE-
OASIS facilities, enter the four digit enroute time in hours
and minutes; hhmm: hh=00-99, mm=00-59.
k. Item 11. Remarks (M1FC- RM: field. OASIS_-
Remarks text box). Information necessary for ATC or
to assist search and rescue operations, plus any other
JO 7110.10T 2/14/08
6-2-4 Flight Plan Proposals
data appropriate to the flight; e.g., the abbreviations
FAA or DOT. Enter names of experimental or
homebuilt aircraft (Veri-EZ, Long-EZ, Mustang,
Delta Dart). For RM: field only - Use 1-80 characters
beginning with *, #, $, or %. (See TBL 6-2-4.)
TBL 6-2-4
* transmit remarks to all centers.
# transmit remarks to departure centers only.
$ transmit remarks only to those addresses in
the CP field of the flight notification mes-
sage.
% for remarks not to be transmitted.
NOTE1. OASIS automatically inserts the appropriate symbol
according to the flight plan type (i.e., $-VFR, * -IFR)
2. Civil aircraft with authorized company identification
are required to file the full authorized radio call in
remarks.
l. Item 12. Fuel on Board (M1FC- FB: field.
OASIS - Fuel Capacity text box). Enter in hours and
minutes; e.g., 0330 or 3+30.
NOTE-
OASIS facilities, enter the fuel capacity; hhmm:
hh=00-99, mm=00-59.
m. Item 13. Alternate Airport/s.
1. (M1FC- AA: field). Enter the location
identifier if specified by the pilot. For AA: field only.
Use three-to-seven alphanumeric characters. For
two alternate airports, enter identifiers consecutively;
e.g., BJCFNL.
2. OASIS_- Alternate Airport text box. Enter
the location identifier of a single alternate airport in
3-4 alphanumeric characters. Additional alternate
airports may be entered in the Remarks text box as
nontransmitted information.
n. Item 14. Pilot's Name, Telephone Number,
Aircraft's Home Base (M1FC- PD: field. OASIS -
Pilot Data text box). Self-explanatory. For military
pilots, obtain the name and telephone of BASOPS.
NOTE-
Pilot's name not required if BASOPS' name is provided.
o. Item 15. Number Aboard (M1FC- NB: field.
OASIS_- Number On Board text box). Self-explana-
tory.
p. Item 16. Color of Aircraft. (M1FC- CR: field.
OASIS_- Aircraft Color text box). Use authorized
contractions when available. (See TBL 6-2-5.)
TBL 6-2-5
Code and Color
Code Color Code Color
A Amber B Blue
BE Beige BK Black
BR Brown G Green
GD Gold GY Gray
M Maroon O Orange
P Purple PK Pink
R Red S Silver
T Tan TQ Turquoise
V Violet W White
Y Yellow
NOTE1. For ICAO flight plans, see Appendix A.
2. Local procedures may be developed for use on the
reverse side of FAA Form 7233-1.
6-2-2. OUTBOUNDS DEPARTING FROM
OUTSIDE FLIGHT PLAN AREA
Accept flight plans regardless of departure point.
Forward VFR flight plan proposals for aircraft
proposing to depart from outside the facility's flight
plan area to the tie-in FSS/AFSS for the departure
point in the following format:
a. Type of Flight.
b. Aircraft Identification.
c. Aircraft Type.
d. Departure Point.
e. Destination.
f. Proposed Departure Time/ETE.
g. Remarks.
EXAMPLE-
AISR
FF KDAYYFYX
DTG KLOUYFYX
VFR N1234 BE9L DAY LOU P1330/0130
M1FC
FR:PV AI:N1234 AT:C150 TS:90 DD:DSM TM:P1800
AE:65 RT:DSM..OMA..LNK
AD:LNK TE:0300 RM:$FP KIKKYFYX
JO 7110.10T 2/14/08
6-2-5 Flight Plan Proposals
FB:0330 AA: PD:JOE PILOT
HB:DSM 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 DD:DBQ TM:P1700
AE:280
RT:DBQ..TNU..OFF/FOE 0+15 450 P1800 270
OFF..FOE
AD:OFF TE:0030 RM:*REMARKS $VT012115
FB:0230 AA: PD:ON FILE BASOPS
HB:DBQ 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 TM:P1800
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 DD:DBQ TM:P1700
AE:280
RT:DBQ..TNU..OFF/FOE 0+15
AD:OFF TE:0030 RM:*REMARKS $VTO12115
FB:0230 AA: PD:ON FILE BASOPS
HB:DBQ 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 TM:P1800
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 RM:$VT010600
FB:0400 AA: PD:ON FILE BASOPS
HB:DBQ 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 TM:P1800
AE:055
RT:FOD..DSM..OFF/MLC 3+10/SZL 2+10
AD:OFF TE:0200 RM:$VT010600
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.
6-3-2. NOTIFYING ARTCC
Transmit flight plans and flight plan amendments to
the ARTCC within whose control area IFR flight is
proposed to begin. AISR facilities use FAAO
JO_7350.8, Location Identifiers, or the appropriate
aeronautical charts to determine the ARTCC to which
each transmission shall be made. Transmit flight
plans (if necessary) and flight plan amendments via
interphone to the flight data position (error referral
position) or departure sector when the aircraft's
proposed departure time is less than 15 minutes from
transmittal time. Advise the ARTCC's departure
sector or error referral position, via interphone, when
a message is received indicating ineligibility or a
response is not received via data terminal within
10_minutes. Transmit flight plans as follows:
a. When multiple (two or more) flight plans are
received from the same aircraft, or for flight plans
which propose alternating VFR and IFR, stopover, or
terminal area delay, the station receiving the flight
plans transmits separate flight plans to the
appropriate ARTCCs for each IFR portion or
segment.
b. Transmit flight plans specifying special use
airspace delays (MOAs, Warning Areas, Restricted
Areas, ATC Assigned Airspace) as in subpara 6-3-2a
except when letters of agreement specify otherwise.
c. Aerial refueling delays, or any other en route
delays not covered in subparas 6-3-2a or b and not
involving a change of altitude stratum, do not require
separate messages. Delay information shall be filed
within the route of flight. If a change of altitude
stratum is indicated, transmit separate messages as in
subparas 6-3-2a or b.
d. When a composite, stopover, or terminal area
delay flight plan is revised:
1. Before departure, transmit the information to
the original addressees plus any new addressees.
JO 7110.10T 2/14/08
6-3-2 IFR Flight Plan Handling
2. After departure, transmit the information to
all new addresses who are affected by the change.
e. AISR. When a flight is to depart after 0500
hours local time on the day following the filing of the
flight plan, do not transmit the flight plan to the
ARTCC until after 0000 hours local time.
NOTE-
In the event of a time zone difference between the station
and the associated ARTCC, use the ARTCC's local time
in determining transmission time.
f. Address all IFR flight plan messages to the
ARTCC serving the point of departure and all
concerned oceanic and nonconterminous ATS units,
except FAA ATCTs.
NOTE-
The ARTCC within whose control area IFR flight is
proposed to begin will forward the proposed tower en
route flight plan data to the appropriate departure
terminal facility.
g. For flights inbound to the conterminous U.S.
from Alaska or Hawaii, address only the first
conterminous U.S. ARTCC; e.g., for a proposed
flight from Sitka to Houston, address PAZAZQZX,
CZVRZQZX, and KZSEZQZX.
REFERENCE-
FAAO JO 7110.65, Para 2-2-2, Forwarding Information.
6-3-3. IFR FLIGHT PLAN CONTROL
MESSAGES
(Pacific: Pacific Supplement.)
Transmit all proposed IFR flight plan messages to the
ARTCC within whose control area IFR flight is
proposed to begin.
a. Communications Functions. Flight plan data
messages shall be addressed to the computer only. All
other types of messages for ARTCC attention shall be
addressed to the Flight Data position only.
Acknowledgements for all numbered messages will
be received from the computer or the Flight Data
position indicating receipt by the ARTCC, but not
necessarily computer acceptance. (See TBL 6-3-1.)
b. Format.
1. Adhere to a fixed order of data. Do not exceed
the stated maximum number of characters or
elements allowed for each field in messages
addressed to an ARTCC computer. Flight plans filed
containing more than the stated character maximums
should be sent using the ARTCC flight data address.
2. AISR. One space character must be entered
at the end of each data field. The following
clarifications are presented:
(a) The first data field of a message need not
be preceded by a space.
TBL 6-3-1
ARTCC ID & Computer Flight Data
ARTCC ID Computer Flight Data
Albuquerque ZAB KZABZQZX KZABZRZX
Atlanta ZTL KZTLZQZX KZTLZRZX
Boston ZBW KZBWZQZX KZBWZRZX
Chicago ZAU KZAUZQZX KZAUZRZX
Cleveland ZOB KZOBZQZX KZOBZRZX
Denver ZDV KZDVZQZX KZDVZRZX
Fort Worth ZFW KZFWZQZX KZFWZRZX
Houston ZHU KZHUZQZX KZHUZRZX
Indianapolis ZID KZIDZQZX KZIDZRZX
Jacksonville ZJX KZJXZQZX KZJXZRZX
Kansas City ZKC KZKCZQZX KZKCZRZX
Los Angeles ZLA KZLAZQZX KZLAZRZX
Memphis ZME KZMEZQZX KZMEZRZX
Miami ZMA KZMAZQZX KZMAZRZX
Minneapolis ZMP KZMPZQZX KZMPZRZX
New York ZNY KZNYZQZX KZNYZRZX
Oakland ZOA KZ0AZQZX KZOAZRZX
Salt Lake ZLC KZLCZQZX KZLCZRZX
Seattle ZSE KZSEZQZX KZSEZRZX
Washington ZDC KZDCZQZX KZDCZRZX
(b) The last data field of a message need not
be followed by a space.
3. Each field of data is composed of one or more
elements. Discrete elements of information within a
field are separated by delimiters, generally slashes
(oblique strokes) or periods.
4. Messages addressed using an ARTCC flight
data address (KZRZX) are not processed by the
HOST computer. Response and/or interpretation of
these messages are dependent on flight data
personnel action. The prime consideration of these
types of messages, shall be the readability of the
transmitted data. The second, third, and fourth
character of the address shall be the same as the
ARTCC flight data address.
5. All domestic flight data processing comput-
ers have the capability to return acknowledgments to
the source and, depending on local adaption, return
error messages and accept amendments. Notify the
JO 7110.10T 2/14/08
6-3-3 IFR Flight Plan Handling
appropriate ARTCC Data Systems Specialist or
Primary A position when it is suspected that a flight
plan has been erroneously rejected by the computer.
6. IFR flight plans specifying stopovers or
terminal area delays require separate messages be
sent to the appropriate ARTCCs for each segment.
Unless otherwise covered by a letter of agreement,
treat flight plans proposing special use airspace
delays in the same manner. Separate messages are
also required for any other en route delays if a change
of altitude stratum is proposed at the delay point. See
subpara 6-3-3c14(h)(1) for delays not involving
a change of altitude stratum.
7. Some fields contain the necessary functions
to operate the computer data terminal adapters and are
designated by alpha characters. Do not separate these
fields with spaces.
c. For EAS FDP acceptance, the complete
message contents, the order of data, the number of
characters allowed within any data field or element,
and any associated operational procedures or
restrictions are as follows (as used here, field refers
to EAS FDP field and/xx refers to M1FC field):
NOTE-
OASIS. Detailed operating instructions for processing
IFR Flight Plans are contained in the WINGS online help
and the WINGS System Users Guide.
1. Start of Message Code (Field A). No entry
requirement for AISR equipment. (New Line Key)
2. Pream ble Line (Field B). Consists of
originator, priority, and addressee(s).
3. Originator Line (Field C). Consists of a
six-digit date-time group and the eight-character
originator identifier.
4. End of Line Function (Field E). Same as
subpara 6-3-3c1.
5. Source Identification (Field 00). Nine or ten
characters required followed by a space character in
the following order:
(a) The three-character address of the
originating AFSS/FSS or the three-character
identifier of the originating airline office.
(b) Four characters (digits) to indicate the
time (in UTC) the flight plan was composed by the
originator.
(c) Three characters (digits) representing the
number of the message; e.g., 021. It is recommended
that numbering systems be restarted with 001 at the
beginning of each day (0000Z).
NOTE-
There are no spaces between characters in subparas
6-3-3c5(a), (b), and (c).
6. Message Type (Field 01). The letters FP
followed by a space character.
7. Aircraft Identification (Field 02/AI:). 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:
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.
Published Radials. Published radials
(e.g., within a preferred route) are considered
airways. Do not file unpublished radials.
EXAMPLE.JFK053..DPK017
.RBV020
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:
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
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)
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)
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)
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
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.
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
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:
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.
d. When a pilot reports a departure time that is
more than 2 hours prior to the current clock time,
request an updated ETE based on the aircraft's
present position. M1FC/OASIS facilities amend the
ETE in the existing flight plan, and activate the flight
plan using the current time as the time of departure
(M1FC/OASIS will automatically calculate the
updated ETA) and inform the pilot of any changes.
6-4-2. DEPARTURE REPORT MESSAGE
When a pilot activates a flight plan with other than the
tie-in station for the departure point, transmit a
numbered message to the departure tie-in station.
EXAMPLE-
AISR
FF KRNOYFYX
DTG KHONYFYX
HON001 RNO
N98765 D1645 WMC ALW
M1FC
ORIGIN:MMV PRECEDENCE:FF TIME: ACK:Y
ADDR:RNO
TEXT:N98765 D1645 WMC ALW
NOTE1. M1FC. Origin may be left blank as M1FC will insert
the origin station's address.
2. OASIS. This function is performed using the General
Facility Message function and the origin may be left
blank, as OASIS will insert the originating station's
address.
6-4-3. ACKNOWLEDGING NUMBERED
MESSAGES
Acknowledge a numbered message as soon as
practicable after receipt. Prefix the acknowledgement
with the letter R followed by a space and then the
3-digit message number.
EXAMPLE-
AISR
FF KMMVYFYX
DTG KRNOYFYX
R 001
6-4-4. FLIGHT NOTIFICATION MESSAGE
a. When a departure report is received, or the pilot
requests an assumed departure, transmit a flight
notification message to the destination tie-in (FSS or
BASOPS) as specified in FAAO JO 7350.8, Location
Identifiers. Telephone or interphone, when available,
may be used for flights of 30 minutes or less. The
flight notification message shall contain the
following information:
1. Type of flight plan (VFR or IFR).
2. Aircraft identification.
JO 7110.10T 2/14/08
6-4-2 Flight Plan Handling
3. Aircraft type.
4. Departure point.
5. Destination.
6. ETA (If more than 24 hours, may use DTG).
7. Rem arks, preceded by a $ sign (as
appropriate).
EXAMPLE-
AISR
FF KBOIYFYX
DTG KCDCYFYX
VFR N2346F AC11/U PVU BOI 1348 $ASMD
DEP
M1FC
FR:V AI:N2346F AT:AC11/U TS:130 DD:PVU
TM:D1203 AE:85
RT:PVU..SLC..TWF..BOI
AD:BOI TE:0145 RM:$ASMD 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 DD:PVU
TM:D1813 AE:85
RT:PVU..BOI
AD:BOI TE:0145 RM:$FP KIADXCLX
FB: AA: PD:
NB: CR: OP:
CP: KBOIYFYX TA:1958
c. If the pilot elects to close the flight plan with a
station other than the AFSS/FSS designated as the
tie-in facility by FAAO JO 7350.8, Location
Identifiers, send the flight notification message with
remarks to both stations; e.g., FIRIV PNM. The
designated tie-in AFSS/FSS shall assume both
destination and search and rescue responsibility.
EXAMPLE-
AISR
FF KGFKYFYX KPNMYFYX
DTG KDCAYFYX
VFR N2346F AC11 FDK PMB 1303
$FIRIV PNM
M1FC
FR:V AI:N2346F AT:C172 TS:110 DD:FOD TM:P1800
AE:095
RT:FOD..OMA
AD:OMA TE:0050 RM:$FIRIV 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 DD:PVU
TM:P1813 AE:85
RT:PVU..SLC..TWF..BOI
AD:BOI TE:0145 RM:$LNDG TWF
FB: AA: PD:
NB: CR: OP:
CP:KBOIYFYX TA:1958
JO 7110.10T 2/14/08
6-4-3 Flight Plan Handling
f. On military flight plans, in remarks use coded
data pertinent to services, passengers, or cargo. In the
absence of remarks, enter the letter N (meaning none)
in the remarks field.
REFERENCE-
DOD Flight Information Publication, General Planning Document.
1. M1FC.
(a) Flight notification messages with remarks
activate a flag upon receipt in the M1FC computers
at selected terminals.
(b) When landing at a civil airport, if there are
no remarks with the flight notification message, it is
placed directly on the I list with no flag alert for
notification purposes.
(c) When landing at a military airport, all
flight notification messages generate an “N” flag.
2. OASIS.
(a) Flight notification messages with remarks
generate an Inbound alarm at designated worksta-
tions.
(b) When landing at a civil airport, if there are
no remarks with the flight notification message, it is
placed on the Inbound List with no alarms for
notification purposes.
(c) When landing at a military airport, all
flight notification messages generate an Inbound
alarm.
EXAMPLE-
AISR
FF KRCAYXYX
DTG KRIUYFYX
IFR DECAL01 T43/R SMF RCA 0135
$AP3NP3S
M1FC
FR:MI AI:DECAL1 AT:T43/R TS:400 DD:SMF
TM:D2205 AE:330
RT:SMF..FMG..SLC..DEN..RCA
AD:RCA TE:0330 RM:$AP3NP3 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
TM:D1813 AE:45
RT:SLC..TWF..BOI
AD:BOI TE:0130 RM:$N
FB: AA: PD:
NB: CR: OP:
CP:KBOIYFYX TA:1943
g. Address military stopover flight notification
messages to and obtain acknowledgements from the
destination tie-in AFSS/FSS or BASOPS serving all
destinations.
1. For the first leg, transmit the item s in
subparas 6-4-4a and 6-4-4f.
2. For each subsequent leg, transmit the
destination, ETE, and remarks applicable to that leg
only, prior to (/). AISR facilities: enter remarks,
applicable to the entire flight, after the final leg.
M1FC facilities: remarks pertaining to the entire
mission should be in the RM: field. OASIS
facilities: remarks pertaining to a particular leg of a
flight plan are entered in the Route text box of the
original flight plan and are transmitted with the
associated leg in the flight notification message.
Remarks pertaining to the entire flight are entered in
the Remarks text box of the original flight plan and
are transmitted to all addressees.
