DDFORM175 - Revision history

Niknam3: /* DD Form 175 — Military Flight Plan */

2026-04-25T11:01:21Z

DD Form 175 — Military Flight Plan

← Older revision		Revision as of 11:01, 25 April 2026
Line 2:		Line 2:

	''How to file a military flight plan''		''How to file a military flight plan''

			[https://sourcedcs.page/flightplan.html File a Flight Plan]

	== 1. Overview ==		== 1. Overview ==

Niknam3 at 10:30, 25 April 2026

2026-04-25T10:30:31Z

← Older revision		Revision as of 10:30, 25 April 2026
Line 188:		Line 188:
	; Filling base ops fields		; Filling base ops fields
	: Fields 21 (signature) and 23 (actual departure time) are base ops only. Do not fill these during initial plan submission.		: Fields 21 (signature) and 23 (actual departure time) are base ops only. Do not fill these during initial plan submission.

	~~[[Category:Flight Operations]]~~
	~~[[Category:Squadron Procedures]]~~

Niknam3 at 10:29, 25 April 2026

2026-04-25T10:29:56Z

← Older revision		Revision as of 10:29, 25 April 2026
Line 1:		Line 1:
	= DD Form 175 — Military Flight Plan =		= DD Form 175 — Military Flight Plan =

	''How to file a military flight plan ~~for your virtual squadron~~''		''How to file a military flight plan''

	~~{{toc}}~~

	== 1. Overview ==		== 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; ~~one copy stays with base ops, one flies with the crew.~~		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'''.		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'''.

	{\| style="border-left: 4px solid #36c; background: #eef; padding: 8px; width: 100%;"		{\| style="border-left: 4px solid #36c; background: #eef; padding: 8px; width: 100%;"
	\| '''Note:''' In the virtual squadron digital form, required fields are marked with a red asterisk (*)~~. Fields labeled "Base ops" are filled after submission — do not fill these yourself~~.		\| '''Note:''' In the virtual squadron digital form, required fields are marked with a red asterisk (*).
	\|}		\|}

Niknam3: /* DD Form 175 — Military Flight Plan */

2026-04-25T10:27:06Z

DD Form 175 — Military Flight Plan

← Older revision		Revision as of 10:27, 25 April 2026
Line 11:		Line 11:
	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'''.		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'''.

	{~~{Callout~~\|In the virtual squadron digital form, required fields are marked with a red asterisk (*). Fields labeled "Base ops" are filled after submission — do not fill these yourself.}}		{\| style="border-left: 4px solid #36c; background: #eef; padding: 8px; width: 100%;"
			\| '''Note:''' In the virtual squadron digital form, required fields are marked with a red asterisk (*). Fields labeled "Base ops" are filled after submission — do not fill these yourself.
			\|}

	== 2. Before you start ==		== 2. Before you start ==
Line 41:		Line 43:
	\|}		\|}

	{{Note\|The Authority field is pre-filled (<code>10 USC 8012 AND EO 9397</code>) and does not need to be changed for standard missions.}}		{\| style="border-left: 4px solid #36c; background: #eef; padding: 8px; width: 100%;"
			\| '''Note:''' The Authority field is pre-filled (<code>10 USC 8012 AND EO 9397</code>) and does not need to be changed for standard missions.
			\|}

	== 4. Route of flight (fields 4–11) ==		== 4. Route of flight (fields 4–11) ==
Line 98:		Line 102:
	\|}		\|}

	{{Warning\|For stopover legs: add <code>(R)[ICAO]</code> 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.}}		{\| style="border-left: 4px solid #e8a000; background: #fef6e0; padding: 8px; width: 100%;"
			\| '''Warning:''' For stopover legs: add <code>(R)[ICAO]</code> 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) ==		== 5. Administrative data (fields 12–20) ==
Line 124:		Line 130:
	\|}		\|}

	{{Note\|Fields 21 (approval signature) and 23 (actual departure time) are filled by base operations after submission. Leave these blank.}}		{\| style="border-left: 4px solid #36c; background: #eef; padding: 8px; width: 100%;"
			\| '''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) ==		== 6. Crew manifest (fields 24–28) ==

Niknam3: Created page with "= DD Form 175 — Military Flight Plan = ''How to file a military flight plan for your virtual squadron'' {{toc}} == 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; one copy stays with base ops, one flies with the crew. The form has four logical parts: a '''document header''' that identifies the..."

2026-04-25T10:23:54Z

Created page with "= DD Form 175 — Military Flight Plan = ''How to file a military flight plan for your virtual squadron'' {{toc}} == 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; one copy stays with base ops, one flies with the crew. The form has four logical parts: a '''document header''' that identifies the..."

New page

= DD Form 175 — Military Flight Plan =

''How to file a military flight plan for your virtual squadron''

{{toc}}

== 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; one copy stays with base ops, one flies with the crew.

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'''.

{{Callout|In the virtual squadron digital form, required fields are marked with a red asterisk (*). Fields labeled "Base ops" are filled after submission — do not fill these yourself.}}

== 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: <code>LS 18</code> (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. <code>KLSF</code>).

; Step 3 — Compute fuel and ETE
: Calculate estimated time en-route and total fuel endurance in <code>H+MM</code> format (e.g. <code>2+30</code> = 2 hours 30 minutes). This is DoD standard — do not use <code>HH:MM</code>.

; 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.

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

{{Note|The Authority field is pre-filled (<code>10 USC 8012 AND EO 9397</code>) 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.

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

=== 4b. Special annotations in field 9 ===

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

{{Warning|For stopover legs: add <code>(R)[ICAO]</code> 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) ==

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

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

== 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 <code>[ICAO]-S</code>. 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 <code>(R)[ICAO] D0+MM</code> notation on the second line of field 9.

=== Aerial refueling ===

Include the <code>AR[###]</code> track identifier in field 9, followed by the anchor fix sequence. Add any PPR reference to Remarks (e.g. <code>KFWH-PPR 0723</code>). 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 <code>[NAME]/D[H+MM] [exit fix]</code> format. Add the joining statement to Remarks: <code>ALTRV: (ALB) JOINED AT ALB/MARSA</code>. ALTRV coordination itself happens outside the form.

=== Heavy aircraft ===

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

== 8. Common mistakes ==

; Wrong time format
: All times are Zulu and in <code>HHMM</code> format. All durations are in <code>H+MM</code>. Never use <code>HH:MM</code> or local time.

; Altitude in feet instead of hundreds
: Field 8 takes altitude in hundreds of feet. Enter <code>200</code> for 20,000 ft — not <code>20000</code>.

; 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.

[[Category:Flight Operations]]
[[Category:Squadron Procedures]]