View source for DDFORM1801

{{DISPLAYTITLE:Filing a DoD International Flight Plan (DD Form 1801)}}

= Filing a DoD International Flight Plan (DD Form 1801) =

This article explains how to correctly fill out the DD Form 1801 / ICAO FPL message used for all cross-border and controlled airspace operations. Read this before filing your first plan — a malformed FPL will be rejected by ATC and may delay or ground your flight.

== Overview ==

The DD Form 1801 generates an ICAO-format '''FPL message''' — a structured string of fields separated by dashes that gets transmitted to ATC. Every field has strict formatting rules. The form handles the formatting for you, but you still need to know what goes where and why.

A complete FPL message looks like this:

<pre>
(FPL-[callsign]-[rules][type]
-[number]/[actype]/[WTC]
-[equipment]/[transponder]
-[departure][time]
-[speed][level] [route]
-[destination][EET] [alternate]
-[field 18])
</pre>

== Field-by-Field Guide ==

=== Field 7 — Aircraft Identification (Callsign) ===

Your '''mission callsign''', up to 7 alphanumeric characters, no spaces.

{| class="wikitable"
! Format !! Example !! Notes
|-
| Up to 7 alphanumeric chars || <code>SHADW11</code> || Formation lead uses flight callsign
|}

For a 4-ship, all aircraft file under the '''lead's callsign''' (<code>SHADW11</code>). Wingmen are not filed separately unless splitting.

=== Field 8 — Flight Rules / Type of Flight ===

Two characters, written together (e.g. <code>IM</code>, <code>VM</code>).

'''Flight Rules (first character):'''

{| class="wikitable"
! Code !! Meaning !! When to use
|-
| <code>I</code> || IFR || En-route in controlled airspace, IMC, or above transition altitude
|-
| <code>V</code> || VFR || Visual, low-level, uncontrolled airspace
|-
| <code>Y</code> || IFR → VFR || Departs IFR, transitions to VFR en route
|-
| <code>Z</code> || VFR → IFR || Departs VFR, picks up IFR clearance en route
|}

'''Type of Flight (second character):'''

{| class="wikitable"
! Code !! Meaning
|-
| <code>M</code> || Military
|-
| <code>S</code> || Scheduled Air Transport
|-
| <code>G</code> || General Aviation
|-
| <code>X</code> || Other
|}

All SHADW flights use <code>M</code>. Flight rules depend on the mission profile — see the examples below.

=== Field 9 — Number / Aircraft Type / Wake Turbulence Category ===

Format: <code>[number]/[type]/[WTC]</code>

{| class="wikitable"
! Sub-field !! Format !! Example !! Notes
|-
| Number of aircraft || Integer 1–99 || <code>4</code> || Formation size. Solo = <code>1</code>
|-
| Aircraft type || ICAO designator (2–4 chars) || <code>F16</code> || Per ICAO Doc 8643
|-
| Wake turbulence category || Single letter || <code>M</code> || L / M / H / J
|}

F-16 is always <code>F16/M</code> (Medium).

=== Field 10 — Equipment / Transponder ===

Format: <code>[equipment]/[transponder]</code>

Standard SHADW configuration is <code>ITUV/C</code>:

{| class="wikitable"
! Code !! Meaning
|-
| <code>I</code> || Inertial navigation
|-
| <code>T</code> || TACAN
|-
| <code>U</code> || UHF radio
|-
| <code>V</code> || VHF radio
|-
| <code>C</code> || Transponder Mode C (altitude reporting)
|}

Do not change this unless maintenance has confirmed a system is inoperative, in which case remove the relevant letter and add <code>STS/HOSP</code> or a RMK as appropriate.

=== Field 13 — Departure Aerodrome / Time ===

Format: <code>[ICAO][HHMM]</code> — no space, no separator.

{| class="wikitable"
! Sub-field !! Format !! Example !! Notes
|-
| Departure aerodrome || 4-letter ICAO code || <code>LTAG</code> || Incirlik AB
|-
| Departure time || HHMM UTC || <code>1530</code> || Block-out time, not wheels-up
|}

Always use '''UTC'''. Never local time.

=== Field 15 — Cruising Speed / Level / Route ===

This field has three parts written together: <code>[speed][level] [route]</code>

==== Speed ====

{| class="wikitable"
! Prefix !! Unit !! Example !! Meaning
|-
| <code>N</code> || Knots TAS || <code>N0420</code> || 420 kt TAS
|-
| <code>K</code> || km/h || <code>K0780</code> || 780 km/h TAS
|-
| <code>M</code> || Mach || <code>M082</code> || Mach 0.82
|}

==== Level ====

{| class="wikitable"
! Prefix !! Unit !! Example !! Meaning
|-
| <code>F</code> || Flight Level || <code>F120</code> || FL120 (12,000 ft, altimeter set to std)
|-
| <code>A</code> || Altitude (hundreds of ft) || <code>A025</code> || 2,500 ft MSL (QNH)
|-
| <code>S</code> || Standard metric level || <code>S1130</code> || (rare, used in some regions)
|}

'''F vs A:''' Use <code>F</code> when flying above the transition altitude (on standard pressure). Use <code>A</code> when flying below it on QNH. In Turkish airspace the transition altitude is typically 3,000 ft AMSL / FL050 — check current AIP.

==== Route ====

Space-separated routing elements after the speed/level. Common elements:

{| class="wikitable"
! Element !! Meaning !! Example
|-
| <code>DCT</code> || Direct to next fix || <code>DCT DAN</code>
|-
| Airway designator || Follow named airway || <code>AG105</code>
|-
| Waypoint name || 5-letter ICAO fix || <code>RUBIK</code>
|-
| <code>fix/speed level</code> || Speed/level change at fix || <code>RUBIK/N0420F120</code>
|-
| <code>STAYn/HHMM</code> || Holding/loiter at previous fix for duration || <code>STAY1/0100</code>
|}

'''<code>STAY</code> items''' are critical for training events. <code>STAY1/0100</code> means "hold/remain in the area of the preceding fix for 1 hour." The number after STAY is an index (1, 2, 3…) used to cross-reference <code>STAYINFO</code> in Field 18.

=== Field 16 — Destination / EET / Alternates ===

Format: <code>[destination][EET] [alternate] [2nd alternate]</code>

{| class="wikitable"
! Sub-field !! Format !! Example !! Notes
|-
| Destination || 4-letter ICAO || <code>LTAG</code> || Can be same as departure for closed patterns
|-
| Total EET || HHMM || <code>0120</code> || Estimated elapsed time departure→destination
|-
| Alternate || 4-letter ICAO || <code>LTAJ</code> || Diyarbakır. Required if weather/fuel rules apply
|-
| 2nd Alternate || 4-letter ICAO || (optional) ||
|}

=== Field 18 — Other Information ===

Free-text field with <code>INDICATOR/value</code> pairs, space-separated. Use <code>0</code> (zero) if nothing to declare.

'''Standard SHADW indicators:'''

{| class="wikitable"
! Indicator !! Format !! Example !! Meaning
|-
| <code>DOF/</code> || YYMMDD || <code>DOF/260428</code> || Date of flight — 28 April 2026
|-
| <code>OPR/</code> || Free text || <code>OPR/DOD</code> || Operating agency
|-
| <code>REG/</code> || Alphanumeric || <code>REG/TBN</code> || Aircraft registration. Use <code>TBN</code> (To Be Notified) for military
|-
| <code>STS/</code> || Code || <code>STS/STATE</code> || State aircraft — grants diplomatic overflight status
|-
| <code>RMK/</code> || Free text || see below || Remarks — used extensively for DoD-specific data
|}

'''<code>RMK/</code> sub-fields used in SHADW plans:'''

{| class="wikitable"
! Tag !! Example !! Meaning
|-
| <code>OAT</code> || <code>OAT</code> || Operational Air Traffic — identifies this as a military OAT flight
|-
| <code>FFLT ... FFLTEND</code> || <code>FFLT SHADW11 SHADW12 SHADW13 SHADW14 FFLTEND</code> || Formation flight membership list. List all callsigns between tags.
|-
| <code>MDCN</code> || <code>MDCN</code> || Medical clearance confirmed
|-
| <code>PERM</code> || <code>PERM 265501</code> || Diplomatic overflight permission number
|-
| <code>FUEL</code> || <code>FUEL0130</code> || Fuel endurance in HHMM
|-
| <code>POB</code> || <code>POB4</code> || Persons on board (integer, no space)
|-
| <code>STAYINFO</code> || <code>STAYINFO1/AREA LTR1 GND FL660 FOR ACM RUBIK0010 RUBIK0110</code> || Describes the STAY1 area/activity. Index matches STAYn in Field 15.
|}

<code>STAYINFO</code> format: <code>STAYINFOn/[free text description]</code>. The description should include the area name/block, vertical limits, activity type, and time window where applicable.

== Worked Examples ==

=== Example 1 — 4-Ship IFR ACM Sortie ===

<pre>
(FPL-SHADW11-IM
-4/F16/M
-ITUV/C
-LTAG1530
-N0420F120 AG105 DAN DCT RUBIK/N0420F120 STAY1/0100 RUBIK/N0420F110 DCT DAN DCT
-LTAG0120 LTAJ
-DOF/260428 OPR/DOD REG/TBN STS/STATE RMK/OAT FFLT SHADW11 SHADW12 SHADW13 SHADW14 FFLTEND MDCN PERM 265501 FUEL0130 POB4 STAYINFO1/AREA LTR1 GND FL660 FOR ACM RUBIK0010 RUBIK0110)
</pre>

'''Breakdown:'''

{| class="wikitable"
! Field !! Value !! Explanation
|-
| Callsign || <code>SHADW11</code> || Formation lead
|-
| Rules/Type || <code>IM</code> || IFR, Military
|-
| Aircraft || <code>4/F16/M</code> || 4-ship, F-16, Medium WTC
|-
| Equipment || <code>ITUV/C</code> || Standard fit
|-
| Departure || <code>LTAG1530</code> || Incirlik, departure-time 15:30Z
|-
| Speed/Level || <code>N0420F120</code> || 420 kt TAS, FL120
|-
| Route || <code>AG105 DAN DCT RUBIK/N0420F120 STAY1/0100 RUBIK/N0420F110 DCT DAN DCT</code> || Depart via airway AG105 to DAN, direct RUBIK; hold at RUBIK for 1 hr at FL120; exit RUBIK at FL110, direct DAN, then direct back
|-
| Destination || <code>LTAG0120</code> || Return Incirlik, EET 1h20
|-
| Alternate || <code>LTAJ</code> || Diyarbakır
|-
| DOF || <code>260428</code> || 28 Apr 2026
|-
| Formation || <code>FFLT SHADW11–14 FFLTEND</code> || 4 aircraft listed
|-
| Stay area || <code>STAYINFO1/AREA LTR1 GND FL660 FOR ACM RUBIK0010 RUBIK0110</code> || LTR1 area, surface to FL660, ACM, 00:10–01:10Z relative to block-out
|}

=== Example 2 — Solo VFR Approach Practice ===

<pre>
(FPL-SHADW11-VM
-1/F16/M
-ITUV/C
-LTAG1530
-N0420A025 DCT DAN/N0420A025 STAY1/0100 DAN/N0420A025 DCT
-LTAG0105 LTAJ
-DOF/260428 OPR/DOD REG/TBN STS/STATE RMK/OAT MDCN PERM 265501 FUEL0130 POB1 STAYINFO1/MULT APCH AT LTAG)
</pre>

'''Key differences from Example 1:'''

{| class="wikitable"
! Field !! Value !! Why it differs
|-
| Rules/Type || <code>VM</code> || '''VFR''' — this sortie is flown VMC below transition altitude
|-
| Aircraft count || <code>1</code> || Solo — no FFLT block needed in RMK
|-
| Level || <code>A025</code> || '''Altitude 2,500 ft''' on QNH, not a flight level — appropriate below transition
|-
| Route || <code>DCT DAN STAY1/0100 DAN DCT</code> || Direct to DAN, hold 1 hr, return direct
|-
| STAYINFO || <code>MULT APCH AT LTAG</code> || Multiple approaches at Incirlik during hold period
|}

=== Example 3 — Solo IFR Approach Practice ===

<pre>
(FPL-SHADW11-IM
-1/F16/M
-ITUV/C
-LTAG1530
-N0420A050 DCT DAN/N0420A050 STAY1/0100 DAN/N0420A050 DCT
-LTAG0105 LTAJ
-DOF/260428 OPR/DOD REG/TBN STS/STATE RMK/OAT MDCN PERM 265501 FUEL0130 POB1 STAYINFO1/MULT APCH AT LTAG)
</pre>

'''Key differences from Example 2:'''

{| class="wikitable"
! Field !! Value !! Why it differs
|-
| Rules/Type || <code>IM</code> || '''IFR''' — same profile but flown under instrument rules
|-
| Level || <code>A050</code> || '''Altitude 5,000 ft''' on QNH — higher block required for IFR separation
|}

'''IFR vs VFR approach practice:''' Both Examples 2 and 3 are the same mission (multiple approaches at LTAG), but the flight rules code and requested altitude differ. IFR requires a higher block for approach sequencing. Choose based on actual met conditions and whether you need an instrument clearance.

== Common Mistakes ==

{| class="wikitable"
! Mistake !! Correct practice
|-
| Using local time in Fields 13 / EET || Always UTC. <code>1530</code> means 15:30Z.
|-
| Filing <code>F</code> level below transition altitude || Use <code>A</code> (altitude on QNH) below transition. Use <code>F</code> (flight level) above.
|-
| Omitting <code>FFLT...FFLTEND</code> for a formation || Required for any multi-ship. ATC needs the full call list.
|-
| Leaving <code>STAYINFO</code> vague || Include area name, vertical limits, activity, and local time window.
|-
| Forgetting <code>DOF/</code> in Field 18 || Always include. Some ATSU systems reject plans without it.
|-
| <code>POB</code> not matching formation count || <code>POB4</code> for a 4-ship (one pilot per aircraft). Adjust for two-seat variants.
|-
| Using local registration for military jets || Use <code>REG/TBN</code> unless a specific tail number is required.
|}

== Quick Reference — SHADW Standard Template ==

Copy and adapt for each sortie. Replace values in <code>[brackets]</code>.

<pre>
(FPL-[CALLSIGN]-[RULES]M
-[N]/F16/M
-ITUV/C
-LTAG[HHMM]
-N0420[LEVEL] [ROUTE] STAY1/[HHMM] [FIX]/N0420[LEVEL] DCT
-LTAG[EET] LTAJ
-DOF/[YYMMDD] OPR/DOD REG/TBN STS/STATE RMK/OAT [FFLT ... FFLTEND] MDCN PERM [NUMBER] FUEL[HHMM] POB[N] STAYINFO1/[DESCRIPTION])
</pre>

== References ==

* ICAO Doc 4444 — PANS-ATM, Appendix 2 (FPL format)
* ICAO Doc 8643 — Aircraft Type Designators
* DoD FLIP General Planning
* DD Form 1801 Field Specification ([https://skybrary.aero/articles/flight-plan-completion DD Form 1801 Field Spec])