NOTE: Generally, all military overseas flights are required to clear through a specified military base operations office (BASOPS). Pilots normally will not file flight plans directly with an FAA facility unless a BASOPS is not available. BASOPS will, in turn, forward the IFR flight notification message to the appropriate center.
NOTE: During EAS FDP operation, data is exchanged between interfaced automated facilities and both the data and time of transmission are recorded automatically.
Forward aircraft departure times to FSSs or military operations offices when they have requested them. Forward other VFR flight plan data only if requested by the pilot.
Forward departure times on all DVFR departures from joint-use airports to the military operations office.
Request a pilot to contact the appropriate FSS if the pilot informs you of a desire to change from an IFR to a VFR flight plan.
Forward control information from controller to controller within a facility, then to the receiving facility as the aircraft progresses along its route. Where appropriate, use computer equipment in lieu of manual coordination procedures. Do not use the remarks section of flight progress strips in lieu of voice coordination to pass control information. Ensure that flight plan and control information is correct and up-to-date. When covered by a letter of agreement/facility directive, the time requirements of subpara a may be reduced, and the time requirements of subpara b1 and para 2-2-11, Forwarding Amended and UTM Data, subpara a may be increased up to 15 minutes when facilitated by automated systems or mandatory radar handoffs; or if operationally necessary because of manual data processing or nonradar operations, the time requirements of subpara a may be increased.
NOTE: When an aircraft has crossed one facility’s area and assignment at a different altitude is still desired, the pilot will re-initiate the request with the next facility.
NOTE: When an IFR aircraft, or a VFR aircraft that has been assigned a beacon code by the EAS and whose flight plan will terminate in another facility’s area, cancels ATC service or does not activate the flight plan, send a remove strips (RS) message on that aircraft via the EAS keyboard, the FDIO keyboard or call via service F.
NOTE: EN ROUTE. This includes alerting the receiving controller that the flight is conducting celestial navigation training.
When a flight plan is manually entered into the computer and a computer-assigned beacon code has been forwarded with the flight plan data, insert the beacon code in the appropriate field as part of the input message.
When an aircraft is a part of an approved ALTRV, forward only those items necessary to properly identify the flight, update flight data contained in the ALTRV APVL, or revise previously given information.
Unless your facility is equipped to automatically obtain acknowledgment of receipt of transferred data, when you transfer control information by computer message, obtain, via Service F, acknowledgment that the receiving center has received the message and verification of the following:
NOTE: An element is defined as either a fix or route as specified in FAA Order JO 7110.10, Flight Services, para 6-3-3, IFR Flight Plan Control Messages.
NOTE: The term “receiving” facility means the ATC facility that is expected to transmit the amended clearance to the intended aircraft/pilot.
NOTE: FDIO only facilities are facilities with FDIO but without ARTS or STARS.
Forward to FSSs the following information received from airborne military aircraft:
NOTE: This makes current information available to FSSs for relay to military bases concerned and for use by centers in the event of two-way radio communications failure.
The exchange of flight plan data between Canadian ACCs and U.S. ARTCCs must be made as follows:
NOTE: Every effort should be made to ensure the aircraft is returned to the original filed flight plan/altitude as soon as conditions warrant.