CHAPTER 1 - FLIGHT PLANNING

1. Applicable Regulations.

    a. General: Army personnel engaged in the operation of Army aircraft shall comply with applicable:

        (1) Military regulations.

        (2) DOD flight information publications (FLIP).

        (3) Federal aviation regulations, laws, and rules.

        (4) Host country regulations, laws, and rules.

        (5) International Civil Aviation Organization (ICAO) regulations.

        (6) Aircraft operator's manuals and checklists.

        (7) Non aviation federal and state laws applicable to Army aviation operations.

    c. Smoking is prohibited in, or within 50 feet of, Army aircraft.

    d. Procedures for packaging, handling, and air transportation of dangerous materials are described in AR 95-27, TM 38-250, and AR 55-203. Aircrews assigned to move dangerous materials in Army aircraft will comply with the requirements listed in these publications.

    e. Aircraft must be grounded during refueling, arming, oxygen servicing, and loading or unloading of flammable or explosive cargo. Aircraft will be grounded for maintenance per the appropriate maintenance publication.

    f. Army aviators will comply with the provisions of AR 95-1, and applicable portion of the Federal Aviation Regulations (FAR) Part 91 and Part 105, specifically addressed in AR 95-1. In the event of a conflict between the wording found in AR-95-1 and that found in the FARs, Army aviators are expected to comply with AR 95-1. The U.S. Army Aeronautical Services Agency (USAASA) has negotiated with the Federal Aviation Administration (FAA) and has obtained written authorization to deviate, in certain instances, from the requirements stipulated in the FARs. Lighting requirements for night vision training, and alternate airport weather requirements, are examples of the Army’s authorization to deviate from Federal Aviation Regulations.

1-2. DD FORM 175 MILITARY FLIGHT PLAN. The following are instructions for filling out the DD Form 175 (Figures 1 & 2) Military Flight Plan with notes provided for additional clarification. The sample flight plans are only examples of some of the ways to fill out a flight plan. There are many varied combinations that may serve the purpose for the flight. The use of checkmarks X's, specific verbiage, etc. is insignificant. Remember: It is important to convey the precise intent of the aviator through his flight plan to ATC.

ITEM (1) DATE -- Enter date of flight in local time.

ITEM (2) AIRCRAFT CALL SIGN -- This entry is limited to 7 characters. Enter the following:

    a. Use the applicable code followed by the last five digits of the aircraft tail/bureau number.

R - ARMY

E - EVAC

G - Army National Guard

NOTE: Formation flights will use only the radio call sign of the leader's aircraft.

    b. Special US Army non-tactical call signs must be approved by the Director, USAASA, and will be entered as spoken with an assigned number to complete 5 or fewer alphanumeric characters (e.g. Pat 62, Saf 11, etc.).

ITEM (3) AIRCRAFT DESIGNATION AND TD CODES

    a. AIRCRAFT DESIGNATION - Enter the military designation of the aircraft. In formation flights of the same type aircraft, enter the number of aircraft in the flight and the designation (e.g., 6/H-1). For formation flights of mixed type aircraft, enter the lead aircraft and identify the other type aircraft in the REMARKS section (e.g., for an H-58 and a H-1 in formation, the DESIGNATION block entry is "2/B06/U" ("U" is the TD code) and the REMARKS would contain the entry #2 aircraft is a H-1/U.

    b. TD CODE -- Select the code from the following graph which denotes the transponder/NAVAID capability of the aircraft and add this suffix to the aircraft designation.

        (1) The TD suffix "X" indicates no transponder.

        (2) Use the suffix which denotes the maximum transponder or navigation capability of the aircraft. Aircraft with Area Navigation (RNAV) equipment should use the W, C, or R suffix even if RNAV routing has not been requested.

        (3) Area Nav Equipment (transponder codes W, C, or R) may be a single computer or a combination of computer and TACAN/VOR.

ITEM (4) TYPE FLIGHT PLAN -- Enter "I" (IFR) or "V" (VFR) as appropriate for that segment. Do not combine IFR and VFR route segments on the same line. Enter "D" (DVFR) for VFR flights conducted in accordance with ADIZ procedures in the appropriate Enroute Supplement.

ITEM (5) TRUE AIRSPEED -- Enter TAS to be maintained at initial cruising altitude/flight level. This entry is not required for VFR local flights.

ITEM (6) POINT OF DEPARTURE -- Enter the location identifier of the departure aerodrome or the point (NAVAID or fix) where IFR will begin. If there is no location identifier, enter the installation name.

NOTE: Aerodrome location identifiers entered on the DD 175 shall consist of three or four alphanumeric characters. If the identifier in the US IFR Supplement has four letters, do not use the first letter, "K". If the identifier in the Alaska Enroute Supplement has four letters, do not use the first letter, "P." Four-letter identifiers are used on international flight plans.

ITEM (7) PROPOSED DEPARTURE TIME (Z) -- Enter the proposed departure time in Coordinated Universal Time (UTC); allow sufficient time for Base Operations to process the flight plan. For activation of an airborne segment (e.g., after enroute delay), enter the proposed time for beginning that segment.

NOTE: Pilots must advise Base Operations or the tie-in FSS serving the departure, stopover, or enroute delay aerodrome when actual departure time will be delayed one hour or more beyond the filed proposed departure time, and provide an updated proposed departure time. When departing non-military fields, the pilot must ensure that the actual departure time is passed to the tie-in FSS servicing the departure field. This can be done by pilot request through the tower or by the pilot direct to the tie-in FSS. If the take-off time is not passed to the tie-in FSS, the aircraft will arrive unannounced at the next destination.

ITEM (8) ALTITUDE

    a. For IFR flights, enter the initial cruising altitude /flight level in hundreds of feet (e.g., enter 6000 feet as "60", 15,000 feet as "150", FL 240 as "240", etc.). For VFR flights, enter the initial cruising altitude in hundreds of feet (e.g., enter 4500 feet as "45"). For IFR/VFR-on-top, enter "OTP" and an altitude if so desired (e.g., "OTP" or "OTP 125").

    b. If a subsequent enroute altitude change(s) is planned, enter the requested altitude/flight level and location of the change in the REMARKS section.

    c. If an altitude block is desired, enter the lower altitude of the requested block, the letter "B", and the top of the block (e.g., 60B80).

ITEM (9) ROUTE OF FLIGHT

    a. For composite flight plans, do not combine IFR and VFR route segments on the same line.

    b. If a radar departure or VFR climb is desired, enter this request in the REMARKS section. The first point in the route of flight should be the planned NAVAID or fix for entering enroute structure (i.e. VOR, TACAN, TACAN/DME fix, named intersection, etc.).

    c. If a DP is used, enter the DP coded identifier (if none is available, enter the DP name and number), followed by either the DP termination point, or the transition fix (e.g., CLIOS 1 Departure, enter "CLIOS 1·CLIOS;" CLIOS 1 Departure with Banbi transition, enter "CLIOS 1. Banbi).

    d. Clearly define the route of flight by using NAVAID identifiers, fix radial distance, airway/jet route designations, named intersections, or RNAV waypoints. The absence of airway identifiers between fixes/NAVAIDs indicates direct flight. To transition from one airway to another at an unnamed intersection, enter the designations of the two airways, separated by a space (e.g., YKM V4 V187 TCM).

    e. Enter "Local" if the flight is to be conducted VFR within the designated local flying area and expected to terminate at the base of departure or an installation under the operational control of the base of departure.

    f. For VFR flight plans, the last fix entered is the point from which the final leg is begun to the destination.

    g. For IFR flight plans, the last fix entered is:

        (1) The identifier of the nearest appropriate IAF, transition fix, or NAVAID which most clearly establishes the route of flight to the destination to include identifying the intended approach when possible. A single five-letter combination serves as the fix name, assigned identifier, and computer code and should be used when published. If a fix is co-located with a NAVAID, LOM, ILS marker, waypoint, or other type fix, the five-letter name/name-code applies to both. Fixes may also be filed using fix radial distance which consists of NAVAID identifier, three characters for azimuth, and three characters for distance in nautical miles (e.g., MCC 220017), or by listing the latitude and longitude.

        (2) If a Standard Terminal Arrival (STAR) is planned, enter the coded identifier of the STAR or the coded transition identifier if a transition is used (e.g., BOIDS EIGHT ARRIVAL enter as "BOIDS8", or with the Wichita Falls transition, enter "SPS.BOIDS8").

    h. For a composite flight plan the last entry in the ROUTE OF FLIGHT is the fix/facility at which the transition is made. Comply with paragraph f. above if the final leg to destination is VFR, and comply with paragraph g. above if the final leg to destination is IFR.

    i. STOPOVER FLIGHT PLANS

        (1) Each leg after the initial leg of a stopover flight plan is entered as described in ITEMS (4) through (11).

        (2) In parenthesis following the last entry of successive legs, enter the hours of fuel on board (e.g., (3+30)).

            (a) If in flight refueling is planned, enter an additional time group in brackets following the fuel on board to show the additional flight time attainable after the refueling (e.g. 3+30 (2+30)).

            (b) If an alternate is required, enter the airfield identifier and the ETE to the alternate in parenthesis with the fuel on board entry. (i.e., 3+30 SKF 0+30).

        (3) Enter VOID time in the REMARKS section as described in ITEM (12).

    j. ENROUTE DELAYS

        (1) HOLDING DELAY - Flight plans will normally be presented as one continuous flight. A holding delay will be shown immediately after the holding fix (e.g., BANBI/D 0+10 V7). No remarks are necessary.

        (2) TERMINAL AREA DELAY - Enter the delay location identifier as the last item in the route of flight. Do not make an entry in the TO block; enter the time required to fly the segment in the ETE block. Explain the delay as a remark on the next line in the ROUTE OF FLIGHT block; do not make entries in any other blocks on this line. Precede the delay remark with a circled "R" to indicate that the information to follow should be transmitted as a remark. Enter a "D" and the length of the delay, the delay location identifier, and the identifier of the final destination (e.g., R D 0+15 BSM RND). Complete ITEMS (4) through (11) for the subsequent leg of flight. Enter VOID time in the REMARKS as described in ITEM (12).

NOTE: Use this delay for practice multiple approaches.

    k. AREA NAVIGATION (RNAV) PROCEDURES

        (1) Pilots filing flight plans which include random RNAV routes shall:

            (a) Indicate the appropriate RNAV capability suffix on the flight plan.

            (b) Identify each waypoint defining the route of flight with a NAVAID identifier, fix name, fix radial distance, or airfield identifier.

            (c) When practical, use established departure/arrival routing to and from the random RNAV portion for the flight plan route (i.e., a DP, published instrument departure procedure, local area procedure, STAR, etc.). Begin and end the random route over published fixes. The last fix entered in the route of flight is according to ITEM (9)g above.

            (d) Avoid prohibited and restricted airspace by three (3) nautical miles unless permission has been obtained to operate in that airspace. Advise appropriate ATC facilities when permission has been obtained.

            (e) File a minimum of one waypoint in each ARTCC's area over which the random portion of flight will be conducted. Such waypoints must be located within 200 NM of the preceding ARTCC's boundary.

            (f) File an additional route description waypoint for each turnpoint in the route.

        (2) RNAV routes may be filed with latitude/longitude coordinate navigation capability, independent of VOR/TACAN references when at or above FL 390 using the following procedures:

            (a) Define the route of flight after the departure fix, including each intermediate fix (turnpoint) and the arrival fix for the destination airfield in terms of latitude/longitude coordinates plotted to the nearest minute. The arrival fix must be identified by both latitude/longitude coordinates and fix identifier (i.e., 2933/09839 SKF).

            (b) Comply with ITEM (9)(K)(1)(a), (c), and (d) above.

        (3) Limitations to the use of random RNAV routes:

            (a) Fly all routes/route segments in Great Circle tracks.

            (b) Contact Air Traffic Control for inflight requests for RNAV clearances or amendments.

ITEM (10) TO -- Enter location identifier of full stop or final destination (as appropriate) opposite the last line entry in the ROUTE OF FLIGHT. If there is no location identifier, enter the aerodrome name.

ITEM (11) ESTIMATED TIME ENROUTE

    a. VFR Flight Plan - The time from takeoff to a position over the destination airfield, including known or preplanned enroute delays (practice airwork, approaches, landings, etc.)

    b. IFR Flight Plan - The time planned to fly from the takeoff to the destination airfield via flight plan route, exclusive of the time required for planned enroute delays. See NOTES below.

NOTE 1: FAR 91.169(a) states ETE will be to a point over the destination airfield. This does not mean to the IAF serving the airfield.

NOTE 2: Include the procedure turn (PT) time only when planning to execute an approach that requires a PT.

NOTE 3: Remember, ETE is only an estimate.

NOTE 4: Time for enroute delays should be figured in fuel management procedures.

    c. Composite Flight Plan - For each IFR segment, use time planned to fly the segment exclusive of enroute delays; for each VFR segment, use time planned to fly the segment including known delays (practice airwork, landings, etc.)

ITEM (12) REMARKS -- Enter information essential to safe and efficient control of air traffic. Service codes and other pertinent information should also be included in this section.

    a. Aircraft on an IFR flight plan equipped with ADF as the only enroute NAVAID will be identified as 'ADF only".

    b. Enter "Hazardous cargo", "Inert devices", or both (as appropriate).

    c. SERVICE CODES

PPR (number) - PPR number, if applicable. (e.g. PPR 0723)

S - Service required (e.g., FSI-5)

R - Aircraft will remain over night (e.g., DAA-R)

    d. Enter in plain English any other pertinent information deemed necessary to be transmitted to the destination.

NOTE: For stopover flight plans, identify the destination to which the information applies (e.g., MGM-S LSF-PPR 0723 S R Mission Code 6R44).

    e. VOID Time - Required for all stopover and/or terminal area delay flight plans. Calculate VOID time by taking the total time from takeoff to final destination, rounded to the next whole hour. (e.g., for total time 4+20, enter "VOID 5+00").

NOTE: This entry is required by the FAA.

ITEM (13) RANK/HONOR CODE -- See the FLIP GP for FLIGHT PLAN VIP CODES. For stopover flight plans, enter pick-up and drop-off points of VIP (e.g., R50 OZR to MGM).

ITEM (14) FUEL ON BOARD -- Enter total time that an aircraft can stay aloft while flying the planned profile with the fuel available at initial takeoff using procedures recommended in the appropriate flight manual.

NOTE: Do not include fuel required for run-up and taxi.

ITEM (15) ALTERNATE AIRFIELD -- Alternate airfields will be selected on the basis of criteria contained in AR 95-1. If IFR on a stopover flight plan, the alternate listed is for the first point of intended landing. Alternates required for subsequent stops will be included in the ROUTE OF FLIGHT section of the flight plan. Use the location identifier to identify alternate airports. If there is no location identifier, enter the installation name.

ITEM (16) ETE TO ALTERNATE -- Enter the time required to fly from original destination to the alternate aerodrome, based on flight at the last cruising altitude.

NOTE: The time figured is to a point over the alternate airfield.

ITEMS (17) and (18) NOTAMS/WEATHER -- Included as a pre-flight reminder and may be used as directed locally.

ITEM (19) WEIGHT AND BALANCE -- File a DD Form 365-4 with the flight plan or certify on the flight plan that the loading for the proposed flight does not exceed the loading limits. When making this certification cite a previously filed DD Form 365-4 for the particular aircraft and enter one of the following:

    a. Enter individual organization/location identifier. If there is no identifier, enter installation name.

    b. For formation flights enter the aircraft serial number applicable to that particular crew member or passenger.

    c. If the crew is composed of members from different military services, identify the branch in parenthesis.

NOTE: Ditto marks may be used when appropriate.

Figure 1 Sample DD Form 175

    b. The DOD Internet NOTAM Service (DINS) is the current method for aircrews to obtain safe, reliable and up to date aeronautical information for flight planning. The web-based service provides NOTAM data and access at locations not serviced by current weather distribution systems (AWDS). Aircrews will consider DINS as the preferred means of obtaining NOTAMs. The operational web address is http://www.notams.jcs.mil/.

CFR Title 14, Part 152, Appendix D, Para. 26 states, in part, "All facilities of the Airport developed with Federal aid and all those usable for the landing and taking off of aircraft, will be available to the United States at all times, without charge, for use by government aircraft in common with other aircraft, except that if use by government aircraft is substantial, a reasonable share, proportional to such use, of the cost of operating and maintaining facilities so used, may be charged."

If you do have to pay a landing fee, obtain a receipt. If possible relay the name of the person, the organization, airport name, and their telephone numbers to the United States Army Aeronautical Services Agency, Airspace Support Division. (Note: If you use an FBO’s services or facilities you may have to pay. Example: Marshaling, use of rest rooms and lounge, etc.; these are not landing fees.)

Return to Special Flight Information Bulletin