Section 4. Flight Plan Handling
- 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.
- The 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.
- When a pilot reports an actual departure time of more than 2 hours prior to the current clock time, request an updated 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 .
When a pilot activates a flight plan with other than the facility holding the flight plan, transmit a departure message to the departure tie-in facility.
- When a pilot activates a flight plan or requests an assumed departure, transmit a departure message to the destination tie-in facility as specified in FAA Order JO 7350.9, Location Identifiers.
- When the proposed flight plan is received from another FSS or base operations (BASOPS), the departure facility will have 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.
VFR N12345 C182/U PVU BOI 1958 $FPKIADXCLX
- If the pilot elects to close the flight plan with a facility other than the designated tie-in facility, send the departure message with remarks to both tie-in facilities; for example, FIRIV FAI. The designated tie-in facility must assume both destination and search and rescue responsibility.
FF PAENYFYX PAFAYFYX
(DEP (MN) (RD)-N12345-KANC1500-KFAI-FIRIV ENA)
- On civil flight plans, if the pilot advises of stopover points, show these in Item 18.
- When using the format of FAA Form 7233-4 or DD Form 1801, in remarks use coded data pertinent to services, passengers, or cargo. In the absence of Item 18 entries, enter the number “0” (meaning none) in the remarks field.
DOD Flight Information Publication, General Planning Document.
- Flight notification messages with remarks generate an alert at designated workstations.
- 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.
- When landing at a military airport, all flight notification messages generate an alert.
IFR DECAL01 T18/R SMF RCA 0135
VFR R54321 2/UH1/U SLC BOI 1943 $N
- Address military stopover flight notification messages to and obtain acknowledgements from the destination tie-in facility serving all destinations.
- For the first leg, transmit the items in subparagraphs and .
- 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.
- Separate stopover legs by inserting a slant (/) at the end of each leg except the last. Begin each leg on a new line.
- For composite flights, specify type flight plan as the first item of each leg.
- When en route delays are involved, include delay time in ETE.
- Apply military flight plan procedures to all civil aircraft landing at military bases.
It is the civil pilot's responsibility to obtain permission (from military authorities) to land at a military base.
- Apply civil flight plan procedure to civil aircraft departing military bases and en route to civil airports.
- Following transmission, suspend the following message types until acknowledgment is received from the addressee, then store in the history file:
- FPL Flight Plan
- SPL Supplemental
- DEP Departure
- CNL Cancellation
- MOD Modification
- If an acknowledgment is not received within the following time priod, use the telephone or interphone to assure delivery.
- Thirty minutes after departure if ETE is between 30 minutes and 2 hours.
- One hour before ETA if ETE is 2 hours or more.
- Thirty minutes after departure if remaining overnight (RON)/VIP information is contained in remarks of a military flight notification.
- 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.
- 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.
- The message identification is the aircraft identification for flight notifications and/or the message number for all other message types.
- Acknowledgments received via NADIN will be automatically processed if they are in the proper format.
- Improperly formatted acknowledgments will be directed to a list for manual processing and will generate an alert at designated workstations for editing.
- 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.
- If a transmission has not been acknowledged by all addressees within 30 minutes, an alert will be generated by the operational system.
- Upon receipt of a Suspense alert, retransmit the message to addressees who have not acknowledged the message.
- 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.
Acknowledge a flight notification message as soon as practical after receipt. Message acknowledgement formats are contained in Appendix D, Service B Message Formats.
The operational system will automatically acknowledge flight notification messages which are received in or have been edited into the correct format.
In addition to acknowledging receipt of flight notification, addressees must take the following actions:
- Notify BASOPS, if applicable, of the inbound flight.
- Upon request, deliver flight plan amendments to the .
- File the flight notification message in the operational system history files or with the daily traffic.
- Forward the actual departure time to the destination tie-in facility for the next destination.
- Notify BASOPS, if applicable, of the inbound flight.
- Suspense the message, await closure/cancellation/departure and assume destination station responsibility.
- Forward the departure time to the destination tie-in facility and assume departure station responsibility.
- 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.
- 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.
- Change of Destination.
- When an aircraft on a VFR flight plan changes destination, obtain and record, as a minimum, the following information if not already known:
- Type of flight plan.
- Aircraft identification.
- Aircraft type.
- Departure point.
- New destination.
- New ETA.
- Present position.
- Old destination.
- Estimated time en route.
- Transmit a revised flight notification message to the departure, original, and new destination tie-in 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.
- 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 appropriate flight plan messages, including a SPL message.
- 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.
When an aircraft wants to change its ETE, obtain a new ETA, and using appropriate messaging procedures, notify the destination tie-in facility of the new ETA. The destination tie-in facility must acknowledge and, thereafter, use the new ETA as the standard for any necessary follow-up action; for example, QALQ message.
Do not transmit arrival reports except under unusual circumstances or in the following cases:
- Transmit arrival or other information involving FAA or Canadian MOT aircraft by a numbered message to any facility requested by the pilot.
N2 A0839 (Remarks, as appropriate)
- For U.S. military aircraft, transmit arrival reports to the departure station only when:
- Requested by BASOPS.
- Special military flights arrive.
- 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.
- If the station receiving the closure is the tie-in station for the planned destination, transmit the appropriate 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.
- If the station receiving the closure message is not the destination tie-in station, transmit the appropriate closure message to the destination tie-in station.
- 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.
- From U.S. If requested by BASOPS, include “REQ ARR” in remarks section of flight plan. Terminate suspense action only after receipt of an arrival message and delivery to BASOPS.