Section 4. Flight Plan Handling
6-4-1. FLIGHT PLAN ACTIVATION
a. If a departure report has not been received
within a predetermined time, but not less than 1 hour
of the proposed departure time, and specific
arrangements have not been made to activate the
flight plan, cancel and store in the history file.
b. The FSS history file is used for statistical and
historical purposes. Movement messages, pilot
briefings, and aircraft contacts are stored in the
history files automatically and retained for 15 days.
c. When a pilot reports an actual departure time of
more than 2 hours prior to the current clock time,
request an updated ETE based on the aircraft's
present position. Amend the ETE in the existing
flight plan and activate the flight plan using the
current time as the time of departure and inform the
pilot of the new ETA.
6-4-2. DEPARTURE REPORT MESSAGE
When a pilot activates a flight plan with other than the
facility holding the flight
plan, transmit a numbered
message to the departure tiein facility.
EXAMPLE-
FF KRCAYXYX
DTG KHONYFYX
HON001 RCA
N98765 D1645 RCA ALW
6-4-3. ACKNOWLEDGING NUMBERED
MESSAGES
Acknowledge a numbered message as soon as
practical after receipt. Prefix the acknowledgement
with the letter “R” followed by a space and then the
3digit message number.
EXAMPLE-
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 tiein facility
as specified in FAA Order JO 7350.8, Location
Identifiers. Telephone or interphone, when available,
may be used for flights of 30 minutes or less. The
flight notification message must contain the
following information:
1. Type of flight plan (VFR or IFR).
2. Aircraft identification.
3. Aircraft type.
4. Departure point.
5. Destination.
6. ETA (If more than 24 hours, may use DTG).
7. Remarks, preceded by a $ sign (as
appropriate).
EXAMPLE-
FF KBOIYFYX
DTG KCDCYFYX
VFR N2346F AC11/U PVU BOI 1348 $ASMD DEP
NOTE-
The operational system will automatically format the
required items and transmit the flight notification
message when activated.
b. When the proposed flight plan is received from
another FSS, base operations (BASOPS), or direct
user access terminal (DUAT) vendor and the
departure facility has only partial flight plan data, add
a remark indicating the Service B address of the
facility holding the complete flight plan. Operational
systems will automatically add this to the “Remarks”
section of the flight plan.
EXAMPLE-
FF KBOIYFYX
DTG KCDCYFYX
VFR N12345 C182/U PVU BOI 1958 $FPKIADXCLX
c. If the pilot elects to close the flight plan with a
facility other than the designated tiein facility, send
the flight notification message with remarks to both
tiein facilities; for example, FIRIV FAI. The
designated tiein facility must assume both
destination and search and rescue responsibility
EXAMPLE-
FF PAENYFYX PAFAYFYX
DTG KJNUYFYX
VFR N2346F AC11 JNU FAI 1303
$FIRIV ENA
NOTE-
The operational system will auto address to the tiein
facility. Because the pilot elected to FIRIV with ENA (a
facility other than the tiein facility), the message must
also be manually addressed to ENA.
d. The facility with which the pilot elects to close
the flight plan must forward a numbered closure
message to the designated tiein facility.
e. On civil flight plans, if the pilot advises of
stopover points, show these in remarks.
EXAMPLE-
FF KBOIYFYX
DTG KCDCYFYX
VFR N12345 C182/U PVU BOI 1958 $LNDG
TWF
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. Flight notification messages with remarks
generate an alert at designated workstations.
2. 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 alerts for
notification purposes.
3. When landing at a military airport, all flight
notification messages generate an alert.
EXAMPLE-
FF KRCAYXYX
DTG KRIUYFYX
IFR DECAL01 T18/R SMF RCA 0135
$AP3NP3S
FF KBOIYFYX
DTG KCDCYFYX
VFR R54321 2/UH1/U SLC BOI 1943 $N
g. Address military stopover flight notification
messages to and obtain acknowledgements from the
destination tiein facility serving all destinations.
1. For the first leg, transmit the items in
subparas 644a and 644f.
2. For each subsequent leg, transmit the
destination, ETE, and remarks applicable to that leg
only, prior to (/). Remarks pertaining to the entire
flight are entered in the “Remarks” section of the
original flight plan and are transmitted to all
addressees.
3. Separate stopover legs by inserting a slant (/)
at the end of each leg except the last. Begin each leg
on a new line.
EXAMPLE-
FF KANDYFYX KGNVYFYX KMIAYFYX
DTG KDCAYFYX
IFR VV12345 P3 ADW CHS 1300/
NIP 01+30 A5 BALL DP10 AP5 S/
MIA 02+30 NO DEICING EQUIPMENT
4. For composite flights, specify type flight plan
as the first item of each leg.
5. When en route delays are involved, include
delay time in ETE.
h. Apply military flight plan procedures to all civil
aircraft landing at military bases.
NOTE-
It is the civil pilot's responsibility to obtain permission
(from military authorities) to land at a military base.
i. Apply civil flight plan procedure to civil aircraft
departing military bases and en route to civil airports.
6-4-5. SUSPENDING FLIGHT
NOTIFICATION MESSAGES
a. Suspend the flight notification message or
proposal message until acknowledgment is received
from the addressee, then store in the history file.
b. If an acknowledgment is not received within the
following time period, use the telephone or
interphone to assure delivery.
1. Thirty minutes after departure if ETE is
between 30 minutes and 2 hours.
2. One hour before ETA if ETE is 2 hours or
more.
3. Thirty minutes after departure if remaining
overnight (RON)/VIP information is contained in
remarks of a military flight notification.
c. When an acknowledgment for a message is
required and has not been received in accordance with
the procedure described above, retransmit the
complete message to the addressee.
d. Messages awaiting acknowledgment are suspended on the Suspense List. It contains a list of all
numbered Service B messages and those messages
transmitted from the flight plan mask not acknowledged by all the addressees.
1. The message identification is the aircraft
identification for flight notifications and/or the
message number for all other message types.
2. Acknowledgments received via NADIN will
be automatically processed if they are in the proper
format.
3. Improperly formatted acknowledgments will
be directed to a list for manual processing and will
generate an alert at designated workstations for
editing.
4. The Suspense List will display the aircraft
identification and message numbers in chronological
order of transmission times and the addressees for
each message with an indication of those that have
not acknowledged.
5. If a transmission has not been acknowledged
by all addressees within 30 minutes, an alert will be
generated by the operational system.
6. Upon receipt of a Suspense alert, retransmit
the message to addressees who have not acknowledged the message.
7. When an acknowledgment message is
received from any other source, such as interphone/telephone or facility guarding for the addressee, the
specialist must manually acknowledge the message.
6-4-6. ACKNOWLEDGING FLIGHT
NOTIFICATION MESSAGES
Acknowledge a flight notification message or
proposal as soon as practical after receipt. Prefix the
acknowledgment with the letter “R” followed by a
space and then the full aircraft identification.
EXAMPLE-
FF KRCAYXYX
DTG KRIUYFYX
R DECAL01
NOTE-
The operational system will automatically acknowledge
flight notification messages which are received in or have
been edited into the correct format.
6-4-7. ACTION BY ADDRESSEES
In addition to acknowledging receipt of flight
notification, addressees must take the following
actions:
a. Military IFR flights.
1. Notify BASOPS, if applicable, of the
inbound flight.
2. Upon request, deliver flight plan amendments to the ARTCC.
3. File the flight notification message in the
operational system history files or with the daily
traffic.
4. Forward the actual departure time to the
destination tiein facility for the next destination.
b. Military VFR flights.
1. Notify BASOPS, if applicable, of the
inbound flight.
2. Suspense the message, await
closure/cancellation/departure and assume
destination station responsibility.
3. Forward the departure time to the destination
tiein facility and assume departure station responsibility.
4. All flight notification messages are suspended on the Inbound List. An entry on the list will
remain there until the flight plan is closed. Thirty
minutes after the ETA, if the flight plan has not been
closed, it is considered overdue and will generate an
alert at designated workstations.
c. If no information is received (for example,
departure time, revised ETA) indicating that the flight
is still active prior to the void time, close the flight
plan and note this on the flight notification message
and file.
6-4-8. MAJOR FLIGHT PLAN CHANGES
FROM EN ROUTE AIRCRAFT
a. Change of Destination.
1. When a civil aircraft on a VFR flight plan or
a military aircraft on any flight plan changes
destination, obtain, as a minimum, the following
information if not already known:
(a) Type of flight plan.
(b) Aircraft identification.
(c) Aircraft type.
(d) Departure point.
(e) Old destination.
(f) Present position.
(g) Altitude and route.
(h) New destination.
(i) Estimated time en route.
2. Transmit a revised flight notification
message to the departure, original, and new
destination tiein facilities containing the type of
flight, aircraft identification, aircraft type, departure
point, new destination, new ETA, and in Remarks,
aircraft position and time, the words “ORIG DESTN”
followed by the identifier of the original destination.
EXAMPLE-
VFR Change of Destination:
FF KBOIYFYX KSEAYFYX
DTG KCDCYFYX
VFR N98789 C182/U PVU GEG 2230 $0VR SLC 1900
ORIG DESTN BOI
IFR Change of Destination:
FF KRCAYXYX KTIKYXYX KRIUYFYX
DTG KCDCYFYX
IFR DECAL01 T43/R SMF TIK 0230 $AP3NP3S OVR
SLC 2330 ORIG DESTN RCA
b. Change from IFR to VFR. When a civil aircraft
changes from an IFR to a VFR flight plan, obtain all
flight plan information and send a flight notification
message to the destination tiein facility. Include the
type of flight plan, aircraft identification and type,
departure point, destination, ETA, and pertinent
remarks.
EXAMPLE-
FF KABQYFYX
DTG KOAKYFYX
VFR N87690 C182/U SFO ELP 2100 $CNLD
IFR OVER BFL
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-
FF KTIKYXYX
DTG KDENYFYX
DECAL01 CHGD TO VFR RON
6-4-9. CHANGE IN ETA
When an aircraft wants to change its ETE, obtain a
new ETA, and forward the information to the
destination tiein facility as a numbered message. The
destination tiein facility must acknowledge and,
thereafter, use the new ETA as the standard for any
necessary followup action; for example, QALQ
message.
EXAMPLE-
FF KENAYFYX
DTG KSEAYFYX
SEA001 ENA
N34567 E2140
REFERENCE-
FAA0 7210.3, Para. 1313.c. Flight Plan Area.
6-4-10. FLIGHT PLAN CLOSURE
Do not transmit arrival reports except under unusual
circumstances or in the following cases:
a. Transmit arrival or other information involving
FAA or Canadian MOT aircraft by a numbered
message to any facility requested by the pilot.
EXAMPLE-
FF KDCAYFYX
DTG KHHRYFYX
HHR002 DCA
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 tiein
station for the planned destination, transmit a
numbered arrival message to the departure station
with the remark “FPNO” and the departure point and
destination identifiers. The departure station must
relay the arrival information to the station holding the
flight plan notification message in the active file.
EXAMPLE-
FF KDCAYFYX
DTG KMIVYFYX
MIV001 DCA
N8567 A1745 FPNO PHF NMK
2. If the station receiving the closure message is
not the destination tiein station, transmit a numbered
closure message to the destination tiein station,
including the aircraft identification, the closure time,
the departure point, and destination. Remarks are
optional.
EXAMPLE-
FF KHUFYFYX
DTG KDAYYFYX
DAY003
N11ND C1217 LOU IND LNDD CMH
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.
|
