Section 3. Military Operations


Advise the ARTCC of flight notification messages, progress reports, changes en route, and related messages concerning Presidential or Vice‐Presidential flights.


Generally, all military foreign flights are required to clear through specified military bases. Pilots normally will not file flight plans directly with an FSS unless BASOPS is not available. BASOPS with no Service B access will forward an ICAO‐type flight plan message via their tie‐in FSS for relay through the Aeronautical Fixed Telecommunications Network (AFTN). BASOPS should specify all addressees, both ATC and operational, in accordance with ICAO standards and military regulations.


Aircraft piloted by solo U.S. Air Force/U.S. Navy undergraduate student pilots (who may occasionally request revised clearances), are normally restricted to flight in VFR conditions. The aircraft identification in the flight plan must include the letter “Z” as a suffix. Do not use this suffix in ground‐to‐air communication.


U.S. Air Force/U.S. Navy solo students who have passed an instrument certification check may penetrate cloud layers in climb or descent only. Requests for revised clearances to avoid clouds in level flight can still be expected. This does not change the requirement to use the letter “Z” as a suffix to the aircraft identification.


Accept and forward messages from any military authority that concern aircraft movement, national defense, safety of flight, or emergencies. This includes, but is not limited to, the following:

  1. Flight advisory messages.
  1. The FSS originating the advisory or receiving it from the originating BASOPS must determine the FSS nearest the aircraft's estimated position for VFR flights, or the appropriate ARTCC for IFR flights. Transmit a numbered message only to the facility identified. Include in the text “FLT ADVY,” aircraft identification and type, and route of flight, in that order. The last item must be the identifier of the originating BASOPS or FSS. Plain language may be used.
  2. Inform the originator if unable to deliver the flight advisory within 15 minutes. Store the message in the history files.
  3. For military flights to the U.S. that include “REQ ARR” (request arrival) in the remarks, suspend the flight plan until arrival information is received from BASOPS and forward to the departure location.
  4. For military flights from the U.S., include “REQ ARR” in remarks section of ICAO flight plan, if requested by BASOPS. Terminate suspense action only after receipt of an arrival message and delivery to BASOPS.
  1. Electronic counter measure (ECM) alerts. Transmit a numbered message via Service B to tie‐in stations serving the addressees. If acknowledgements are not received within one hour, deliver via telephone.
  2. REACH and SAM flight messages. Forward to the airlift command post specified by the pilot if message contains request “Pass to Air Mobility Command & Airlift Command Post,” specified by the pilot.

In addition to the normal handling of aircraft operating in accordance with IFR, specialists must forward ADIZ penetration information or position reports on IFR operations outside of controlled airspace immediately to the appropriate ARTCC.


For security control of air traffic, specialists must forward to NORAD specific information contained in flight plans filed by a pilot operating or proposing to operate in accordance with DVFR within an ADIZ.


Other offices, military and civilian, as well as pilots, may file DVFR flight plans for civilian aircraft with a FSS for forwarding to NORAD.

  1. Forward DVFR flight plan information to NORAD via the Service B NORAD address or by telephone.


  1. The following NORAD addresses are group addresses that include all appropriate NORAD sectors and law enforcement: KZAMZQZX - the CONUS and San Juan. PHIRAOCZ - Hawaii PAEDYYYX - Alaska
  2. NORAD will not send an acknowledgement and specialists must manually acknowledge the message in the suspense list. NORAD headquarters assumes responsibility for receipt.
  1. DVFR flight plans must be entered into the operational system for processing in accordance with system instructions and include the following information:
  1. Aircraft call sign.
  2. Number and type of aircraft.
  3. Altitude (within ADIZ).
  4. True airspeed.
  5. Time of departure.
  1. When the flight plan information is provided before the aircraft's departure, enter as a proposal. Depart the flight plan immediately upon receipt of the actual departure time.
  2. If arrangements cannot be made to obtain the actual departure time, forward the ETD.
  1. Point of departure.
  2. ETA.
  3. Destination.
  4. Remarks.
  1. DVFR discrete transponder code.
  2. True airspeed.
  3. Estimated point of penetration of the ADIZ (latitude/longitude or fix-radial-distance), except in Alaska.
  4. Estimated time of penetration of the ADIZ, except in Alaska.
  5. On a proposed flight plan, a single “X” may replace the DVFR discrete transponder code, true airspeed, estimated point of penetration of the ADIZ, or the estimated time of penetration of the ADIZ.
  6. If a no arrival report (NORIV) will be filed with an appropriate aeronautical facility, include the contraction “NORIV” as a non‐transmitted remark. Do not pass “NORIV” to NORAD.


Missing true airspeed: 1210 X 3442/09345 1446
Missing estimated point of ADIZ penetration and time: 1210 135 XX


The use of NORIV implies that NO SAR is desired.

  1. Forward DVFR flight plan information for aircraft operating into Canada using the same procedures in subparagraph 6-3-7b, except add “DVFR” in remarks and transmit the information to the appropriate Canadian transborder tie‐in facility.

Accept stopover DVFR flight plans filed on those aircraft planning one or more landings (within an ADIZ) en route to the destination, provided the information in paragraph 6-3-7 is furnished for each segment of flight. Remind the pilot that 14 CFR 99 requires departure times to be made good and that a written record should be retained of these times at each departure point.