DDFORM175

DD Form 175 — Military Flight Plan

How to file a military flight plan

File a Flight Plan

1. Overview

The DD Form 175 is the standard US military domestic flight plan. Every mission—regardless of aircraft type or complexity—is filed on this form before departure. Base Operations reviews and approves it;

The form has four logical parts: a document header that identifies the aircraft and date, one or more route leg rows covering the actual routing, an administrative section for fuel, weather, and remarks, and a crew manifest.

Note: In the virtual squadron digital form, required fields are marked with a red asterisk (*).

2. Before you start

Step 1 — Get your weather brief

Obtain a weather briefing and note the source and time (Zulu). You will enter this in field 18. Example: LS 18 (local brief at 1800Z).

Step 2 — Plan your route

Determine departure fix, airways, intermediate fixes, and destination. Note any refueling anchors, SUA transits, or holding requirements. All ICAO identifiers are 4-letter codes (e.g. KLSF).

Step 3 — Compute fuel and ETE

Calculate estimated time en-route and total fuel endurance in H+MM format (e.g. 2+30 = 2 hours 30 minutes). This is DoD standard — do not use HH:MM.

Step 4 — Check NOTAMs and alternate

Review NOTAMs for your route and select an alternate airfield (required for IFR). You will check a box confirming NOTAM review.

3. Document header (fields 1–3)

These three fields identify the mission and appear once at the top of the form. They apply to every leg.

Field	What to enter	Status
Field 1 — Date	Date of flight in DD MON YY format. Example: 24 APR 26.	Required
Field 2 — Call sign	Radio call sign for this mission. Example: HAWK 11, VIPER 07. Uppercase, 4–12 characters.	Required
Field 3 — A/C designation	Aircraft MDS and performance code in [Type]/[Code] format. Example: F-16C/B, H/C-17/R. The H/ prefix denotes a heavy aircraft.	Required

Note: The Authority field is pre-filled (10 USC 8012 AND EO 9397) and does not need to be changed for standard missions.

4. Route of flight (fields 4–11)

Each leg of the flight occupies one row. A direct flight has one leg; a mission with a stopover or multiple segments has multiple rows. Click + Add leg in the form to add more rows.

Field	What to enter	Status
Field 4 — Type	Flight rules for this leg: I (IFR), V (VFR), Y (IFR then VFR), Z (VFR then IFR).	Required
Field 5 — TAS	True airspeed in knots, integer, no unit suffix. Examples: 330, 450, 98.	Required
Field 6 — Departure	ICAO 4-letter identifier of the departure airfield. Example: KLSF, KVAD. For legs originating from a fix, enter the fix and radial/distance: PSX 242038.	Required
Field 7 — Dep time (Z)	Planned departure in Zulu time, 4-digit HHMM format. Example: 1430. All times on DD 175 are Zulu.	Required
Field 8 — Altitude	Cruising altitude in hundreds of feet MSL. Example: 200 = 20,000 ft, 260 = FL260. For low-level legs: 50 = 5,000 ft.	Required
Field 9 — Route	Free-text route string. See section 4a below.	Required
Field 10 — Destination	ICAO 4-letter identifier of the destination for this leg. Example: KSKF.	Required
Field 11 — ETE	Estimated time en-route in H+MM format. Example: 1+30, 0+45.	Required

4a. Writing the route string (field 9)

Field 9 is a free-text field. Enter your routing exactly as you would on the paper form — space-separated airways and fixes on a single line. Do not add punctuation between tokens unless it is a defined annotation (see section 4b).

Simple point-to-point:

EUF V159 PZD V578 IFM

High-altitude jet route:

MQP J23 BATIK J58 SPS 282078

Fix defined by radial and distance:

AUS 291061 BSM344017

Radial/distance fixes are written as [NAVAID][3-digit radial][6-digit distance], all run together with no spaces within the token.

4b. Special annotations in field 9

Situation	Notation	Example
Airborne holding delay at a fix	[FIX]/D0+MM	DUMPS/D0+10 J17
Ground stop at intermediate airport	(R)[ICAO] D0+MM on a second route line	(R)KVAD D0+30 KLSF
Aerial refueling track	AR[###] followed by anchor points	AR611 AUS 302044 AUS J21 SAT
SUA transit with delay	[SUA name] D0+MM [exit fix]	REESE 1 D0+15 KREE
ALTRV block entry	[ALTRV name]/D[H+MM] [exit fix]	ALB/D4+39 PGS

Warning: For stopover legs: add (R)[ICAO] as a second line in the route field — do not create a separate leg row for the ground stop. The ETE for the leg should cover the total time including the ground delay.

5. Administrative data (fields 12–20)

Field	What to enter	Status
Field 12 — Remarks	Free text. Common entries: stopover notation KMGM-S; PPR reference KFWH-PPR 0723; ATC requests REQUEST RADAR DEPARTURE; ALTRV joining statement.	Recommended
Field 13 — Rank / honor code	Priority code and mission description. Example: R50 REAL KOZR TO KMGM. Required only for VIP or priority missions.	Conditional
Field 14 — Fuel on board	Total fuel endurance at departure in H+MM. Example: 7+30.	Required
Field 15 — Alternate	ICAO identifier of the alternate airfield. Required for all IFR flights. Example: KLSF.	IFR only
Field 16 — ETE to alternate	Time from destination to alternate in H+MM. Example: 0+50.	IFR only
Field 17 — NOTAMs	Check the box after reviewing NOTAMs for your route.	Required
Field 18 — Weather	Brief source and time code. Example: LS 18 (local, 1800Z).	Required
Field 19 — Weight and balance	Reference to your W&B document: home station and date. Example: KOZR, 24 APR 26.	Required
Field 20 — Serial / unit / station	Aircraft serial, unit name, and home station ICAO separated by /. Example: 96-0001 / VIPER SQDN / UGKO.	Required

Note: Fields 21 (approval signature) and 23 (actual departure time) are filled by base operations after submission. Leave these blank.

6. Crew manifest (fields 24–28)

Add one row per crew member or passenger. Click + Add row to add more. The pilot-in-command row is pre-populated.

Field	What to enter
Field 24 — Duty	Position: PILOT IN COMMAND, CP (copilot), CE (crew chief), N (navigator), TO, or free text for non-standard roles.
Field 25 — Name	Last name, first initial, middle initial. Format: SMITH, J.R. Uppercase.
Field 26 — Rank	Pay grade abbreviation. Examples: CPT, CW4, MAJ, 1LT, CDR.
Field 27 — Member ID	Virtual squadron member ID (replaces SSN in sim context). Format: ###-##-####.
Field 28 — Unit / station	Unit name and home station ICAO. Example: VIPER SQDN / UGKO.

7. Plan types

Simple point-to-point

One leg row. Fill fields 4–11 for the single segment. Remarks are brief or absent.

Multi-leg / stopover

Use multiple leg rows. Each row is a complete segment with its own departure, routing, destination, and ETE. Note each stopover in Remarks as [ICAO]-S. If the aircraft makes a ground stop but the planner treats it as one continuous leg (composite plan), use a single leg row with the (R)[ICAO] D0+MM notation on the second line of field 9.

Aerial refueling

Include the AR[###] track identifier in field 9, followed by the anchor fix sequence. Add any PPR reference to Remarks (e.g. KFWH-PPR 0723). If the refueling point is also the alternate, note that in field 15.

ALTRV (altitude reservation)

The ALTRV block name and timing go in field 9 using the [NAME]/D[H+MM] [exit fix] format. Add the joining statement to Remarks: ALTRV: (ALB) JOINED AT ALB/MARSA. ALTRV coordination itself happens outside the form.

Heavy aircraft

Prefix the aircraft designation in field 3 with H/ (e.g. H/C-17/R). No other fields change; the prefix affects ATC wake turbulence separation only.

8. Common mistakes

Wrong time format

All times are Zulu and in HHMM format. All durations are in H+MM. Never use HH:MM or local time.

Altitude in feet instead of hundreds

Field 8 takes altitude in hundreds of feet. Enter 200 for 20,000 ft — not 20000.

Blank NOTAMs checkbox

Field 17 must be checked before submission. Base ops will reject plans with an unchecked NOTAM box.

No alternate for IFR flight

Any IFR leg requires field 15 (alternate airfield) and field 16 (ETE to alternate) to be filled.

Filling base ops fields

Fields 21 (signature) and 23 (actual departure time) are base ops only. Do not fill these during initial plan submission.