DDFORM1801

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:

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

Field-by-Field Guide

Field 7 — Aircraft Identification (Callsign)

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

Format	Example	Notes
Up to 7 alphanumeric chars	SHADW11	Formation lead uses flight callsign

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

Field 8 — Flight Rules / Type of Flight

Two characters, written together (e.g. IM, VM).

Flight Rules (first character):

Code	Meaning	When to use
I	IFR	En-route in controlled airspace, IMC, or above transition altitude
V	VFR	Visual, low-level, uncontrolled airspace
Y	IFR → VFR	Departs IFR, transitions to VFR en route
Z	VFR → IFR	Departs VFR, picks up IFR clearance en route

Type of Flight (second character):

Code	Meaning
M	Military
S	Scheduled Air Transport
G	General Aviation
X	Other

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

Field 9 — Number / Aircraft Type / Wake Turbulence Category

Format: [number]/[type]/[WTC]

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

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

Field 10 — Equipment / Transponder

Format: [equipment]/[transponder]

Standard SHADW configuration is ITUV/C:

Code	Meaning
I	Inertial navigation
T	TACAN
U	UHF radio
V	VHF radio
C	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 STS/HOSP or a RMK as appropriate.

Field 13 — Departure Aerodrome / Time

Format: [ICAO][HHMM] — no space, no separator.

Sub-field	Format	Example	Notes
Departure aerodrome	4-letter ICAO code	LTAG	Incirlik AB
Departure time	HHMM UTC	1530	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: [speed][level] [route]

Speed

Prefix	Unit	Example	Meaning
N	Knots TAS	N0420	420 kt TAS
K	km/h	K0780	780 km/h TAS
M	Mach	M082	Mach 0.82

Level

Prefix	Unit	Example	Meaning
F	Flight Level	F120	FL120 (12,000 ft, altimeter set to std)
A	Altitude (hundreds of ft)	A025	2,500 ft MSL (QNH)
S	Standard metric level	S1130	(rare, used in some regions)

F vs A: Use F when flying above the transition altitude (on standard pressure). Use A 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:

Element	Meaning	Example
DCT	Direct to next fix	DCT DAN
Airway designator	Follow named airway	AG105
Waypoint name	5-letter ICAO fix	RUBIK
fix/speed level	Speed/level change at fix	RUBIK/N0420F120
STAYn/HHMM	Holding/loiter at previous fix for duration	STAY1/0100

STAY items are critical for training events. STAY1/0100 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 STAYINFO in Field 18.

Field 16 — Destination / EET / Alternates

Format: [destination][EET] [alternate] [2nd alternate]

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

Field 18 — Other Information

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

Standard SHADW indicators:

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

RMK/ sub-fields used in SHADW plans:

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

STAYINFO format: STAYINFOn/[free text description]. 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

(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)

Breakdown:

Field	Value	Explanation
Callsign	SHADW11	Formation lead
Rules/Type	IM	IFR, Military
Aircraft	4/F16/M	4-ship, F-16, Medium WTC
Equipment	ITUV/C	Standard fit
Departure	LTAG1530	Incirlik, block-out 15:30Z
Speed/Level	N0420F120	420 kt TAS, FL120
Route	AG105 DAN DCT RUBIK/N0420F120 STAY1/0100 RUBIK/N0420F110 DCT DAN DCT	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	LTAG0120	Return Incirlik, EET 1h20
Alternate	LTAJ	Diyarbakır
DOF	260428	28 Apr 2026
Formation	FFLT SHADW11–14 FFLTEND	4 aircraft listed
Stay area	STAYINFO1/AREA LTR1 GND FL660 FOR ACM RUBIK0010 RUBIK0110	LTR1 area, surface to FL660, ACM, 0010–0110 relative to departure-time

Example 2 — Solo VFR Approach Practice

(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)

Key differences from Example 1:

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

Example 3 — Solo IFR Approach Practice

(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)

Key differences from Example 2:

Field	Value	Why it differs
Rules/Type	IM	IFR — same profile but flown under instrument rules
Level	A050	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

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

Quick Reference — SHADW Standard Template

Copy and adapt for each sortie. Replace values in [brackets].

(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])

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 (DD Form 1801 Field Spec)