Note: To navigate through this part click on the items in the left hand side when using a desktop browser.
In order to submit your flight plan by e-mail, please fill out the interactive 1801 Flight Plan Form (.pdf) and and send it to: firstname.lastname@example.org Please enter the call sign first thing in the subject line!
Completing the DD1801 form is quite simple. The white boxes on the form are to be completed by the pilot. Please adhere closely to the prescribed formats.
DD1801 with Continuation
General rules applying:
Use capital letters.
Insert data only in the fields and spaces provided. Do not write on the grey areas.
Leave unused space blank.
All times have to be UTC (Zulu time).
Complete items 7 to 19.
After sending the flight plan to AFOD please verify receipt if you don’t get a response in a reasonable time frame.
Report any updates like cancellation, delays or changes.
If you want or need your flight plan to be send to any AFTN address you can add it here. If you file your flight plan at a non US Army airfield, enter AD ETEEYWYX in the third line of the addressee portion to ensure the flight plan will be addressed to the AFOD.
Maximum 7 alphanumerical characters.
Enter your approved call sign. This can be beyond others:
R (for US Army) followed by the last five digits of your aircraft registration visible on the tail of your aircraft e.g. R12345!
A call sign assigned to you/your unit or your mission.
Note: If your call sign is longer than 7 characters you need to abbreviate it. Enter the full call sign in item 18 using the entry RMK/VOICE CALLSIGN …!
Indicate the flight rules, under which your flight will be conducted:
Y (IFR to VFR)
Z (VFR to IFR)
Enter M for military flight (state aircraft).
Item 9a Number
Leave blank for a single aircraft.
Item 9b Type of Aircraft
Enter the type designator as published in ICAO Doc 8643 Aircraft Type Designators:
EC45 for all Lakota models e.g. UH-72A=EC45
H47 for all Chinook models e.g. CH-47F=H47
H60 for all Blackhawk models e.g. UH-60=H60, HH-60=H60 etc.
H64 for all Apache models e.g. AH-64D=H64
Do not enter the DOD designator e.g. UH60.
Formations flights with different aircraft types:
In the case of a formation flight performed with different aircraft types, "ZZZZ" shall be inserted. The types and number of aircraft of each type shall be inserted in Item 18, preceded by "TYP/".
Item 9c Wake Turbulence Category
Enter the category of your aircraft as published in ICAO Doc 8643.
If you want to search the ICAO Doc 8643 just follow this link: https://www.icao.int/publications/doc8643/pages/search.aspx
List the equipment and capabilities of your aircraft starting with S if standard equipment (VHF RTF, VOR and ILS) is carried and serviceable. The designator S must not be inserted if en-route equipment (RNP) for area navigation is not available.
Then enter the designators for the rest of your equipment in alphabetical order.
If the letter R is used, the performance based navigation levels that can be met are to be specified in Item 18 following the indicator PBN/. For guidance see ICAO Doc 9613.
If the letter G is used, the types of external GNSS augmentation, if any, are to be specified in Item 18 following the indicator NAV/.
For IFR flights, if not equipped with RNP (R or G), enter NAV/RNAVX in Item 18 and ‘Z’ in Item 10a.
For IFR flights, if unable to meet minimum RNAV requirements due to equipment failure or degradation, enter NAV/RNAVINOP in Item 18 and ‘Z’ in Item 10a. ‘S’ or ‘R’ shall not be entered in Item 10a.
State aircraft not equipped with 8.33 kHz radio (Y) can be exempt from this requirement if equipped with UHF RTF. Enter the ‘U’ and the ‘Z’ in item 10a and the entry COM/EXM833 in Item 18.
For flights inside RVSM airspace (F290 and above), if not RVSM equipped, enter STS/NONRVSM in Item 18.
Surveillance equipment and capabilities
This item includes transponder, ADS-B and ADS-C capabilities.
Note: If your aircraft is only equipped with e Mode-C transponder special permissions may be required to operate it.
Departure Aerodrome (maximum 4 characters)
As specified in ICAO Doc 7910 Location Indicators e.g. ETOU.
ZZZZ if not specified and then:
Specify the name and the lat/longs in item 18 using the entry DEP/. Example: DEP/4711N00815E FARP
Or Radial/DME e.g. DEP/RMS180017 which means bearing 180 degrees and a distance of 17NM from RMS nav aid).
Note: Do not use self-made indicators like ET43 or ED40 or NSTA. These indicators are no official ICAO location indicators and can't be used in a flight plan! Specify the name and the lat/longs in item 18 using the entry DEP/.
Maximum 4 characters. Enter your EOBT (Estimated Off Block Time) in UTC (Z).
Note: EOBT = desired takeoff time – standard taxi time for your aerodrome of departure.
Cruising speed in:
Knots, indicated by ‘N’ followed by four digits e.g. N0120.
Kilometers per hour expressed as K followed by 4 figures.
Mach number e.g. M080.
Initial flight level:
‘A’ followed by three digits indicating your altitude in hundreds of feet or, if above transition altitude,
‘F’ followed by three digits indicating your flight level.
Note 1: When you fly in airspace where the metric system is used, please consult the GP or the appropriate AIP.
Note 2: Make sure you chose the appropriate flight level (odd or even) for your direction of flight.
For VFR flights (except VFR Night flights into other than US Army controlled airspace), “VFR” can be entered instead of the requested cruising level.
For VFR Night flights, enter an appropriate VFR cruising altitude or flight level for your direction of flight.
Start with the designator for the published standard instrument departure (SID) you plan to use e.g. DKB if you plan to use the DKB SID at Nürnberg (EDDN).
Note: If no SID is published start your route description with ‘DCT’ followed by the first point of your route.
Route: The route of flight shall be indicated by points connected by published ATS routes or ‘DCT’ for flights outside published ATS routes. Route points can be specified by published waypoints, navaids, lat/long coordinates and DME points. Please don’t insert VFR points, city names or airfield identifiers, but provide the corresponding lat/long coordinates if you want to use them.
The end of route will be the designator for the published standard arrival route (STAR) of the destination aerodrome. If no STAR is published, enter a ‘DCT’ after the last point of your route.
The stay indicator enables you to indicate special en-route activities such as airwork or holdings at a certain point or in a certain area.
The stay indicator consists of the letter group STAY followed by a sequence number from 1 to 9, a slash and the time spent in the area indicated in hours and minutes: STAY1/0120
The stay indicator is inserted between the point of entry in the STAY AREA and the point of exit from the STAY AREA. The entry and the exit point can be the same.
To indicate the reason for the stay a pertinent STAYINFO indicator with the same sequence number shall be entered in item 18 of the FPL.
The stay indicator shall only be used for en-route special activities and not for approaches at an airport along your route of flight or at your destination aerodrome.
Don’t forget to add the duration of your stay to your total EET.
The STAY indicator can only be used for flights entirely inside Eurocontrols Integrated Flight Planning Zone (IPFZ). For flights partially or entirely outside IFPZ airspace the delay shall only be indicated in item 18 of your flight plan as’ DLE/’ followed by the point and duration (HHMM) of the delay. (Example: DLE/GESAD0100).
GAT is inserted after the reporting point at which the change from OAT to GAT is completed.
OAT is inserted after the reporting point at which the change from GAT to OAT is completed.
VFR routes shall be indicated by points connected by ‘DCT’. Route points can be specified by published waypoints, navaids, lat/long coordinates and DME points. Please don’t insert VFR checkpoint names, city names or airfield identifiers, but provide the corresponding lat/long coordinates if you want to use them. Please don’t be lazy and file just DCT. The major purpose of a VFR flight plan is for search and rescue. Don’t go overboard with the waypoints. Be realistic, but provide at least major turning points.
For VFR flights at night, the route shall be indicated as far as possible in accordance with an IFR routing.
The route of flight shall be defined by points connected by published ATS routes or ‘DCT’ for flights outside published ATS routes. Route points can be specified by published waypoints, navaids and DME points.
Destination Aerodrome (maximum 4 characters) as specified in ICAO Doc 7910 Location Indicators. Do not use self-made indicators like ET43 or ED40 or NSTA. These indicators are no official ICAO location indicators and can't be used in a flight plan! This also applies for LBNS and LYBS! Use ZZZZ as described above instead. Specify the name and the lat/longs in item 18 using the entry DEP/.
Example: DEST/4711N00815E FARP
Another option is to use radial DME e.g. DEST/RMS180017 which means bearing 180 degrees and a distance of 17NM from RMS nav aid).
For IFR flights, the estimated time required from departure until arrival over the established point defined by reference to navigation aids, from which an instrument approach procedure is intended, or, if no navigation aid is associated with the destination aerodrome, until arrival over the destination aerodrome.
For flights arriving VFR, the estimated time required from departure until arrival over the destination aerodrome.
Insert ICAO location identifier(s) for your destination alternate aerodrome(s). If no ICAO location identifier is published for one or both your destination alternate aerodromes, enter ZZZZ and specify the name AND lat/long coordinates or bearing and distance from the nearest significant point after ALTN/ in item 18.
Take-off alternate aerodromes and en-route alternate aerodromes shall be entered in item 18 after TALT/ for take-off alternates or RALT/ for en-route alternates.
Indicate relevant RNAV or RNP capabilities. Only 8 codes (16 characters) are allowed after PBN/. If you have more than 8 codes, enter the 8 most relevant for your flight after PBN/ and the least relevant after NAV/ and include ‘Z’ in Item 10a.
Significant NAV equipment other than specified in PBN. ‘Z’ required in item 10a.
SBAS - If the letter G is used, the types of external GNSS augmentation, if any, are specified in Item 18 following the indicator NAV/ and separated by a space.
RNAVX or RNAVINOP - If RNAV equipment is missing or the minimum RNAV requirements cannot be met.
DEP/ or DEST/
If you plan to land on a field site or there is no ICAO code published for your ADES, enter ZZZZ in item 16 and list the name AND lat/long coordinates or bearing and distance from the nearest significant point of your landing site.
Date of Flight in the format YYMMDD
Registration mark of the aircraft if it is different from the aircraft identification entered in item 7 In a formation, the registration marks of ALL aircraft of the formation shall be inserted.
(ZM) Estimated elapsed time until crossing the switch over point to IFR (Format: PointHHMM)
(International VFR) Point of crossing the international border and estimated elapsed time to this point. Not required by all countries. Consult the respective national AIP.
(FIR Boundary Crossing (IFR)) Estimated elapsed time to FIR boundary crossing for international flights. This is not required for border crossings within the IFPZ with exception of Turkey. Format: FIR entered followed by time HHMM.
In a formation with different types of aircraft, state the number and types of aircraft along with the identification group TYP/. If an ICAO type designator is published in ICAO DOC 8643, do not use the military designator.
Designator of aircraft operator as published in ICAO DOC 8585 or name of aircraft operator, if no designator has been assigned. (e.g. USR for US Army)
Indicate one aircraft performance data (single letter) if required by an ATS authority.
This entry indicates that a flight is conducted as OAT. It shall be entered directly after the identification group “RMK/”
OAT OVER GERMANY
Is to be entered for all flights into, out of or flying over Germany, does not indicate OAT versus GAT operations which would be indicated in the route of flight as required.
The entry “VFR NIGHT” is required after “RMK/” for all VFR flights at night into controlled airspace (except US Army controlled).
If a PPR is required for your destination aerodrome, state the PPR number or status of your PPR request as “pending” or “approved”. This will prevent unnecessary inquiries by the AFOD personnel and the recipients of your flight plan.
Indicate your intentions at your destination aerodrome (e.g. LOW APPROACH ONLY), unless a full stop landing is planned. Please consult the DOD FLIP Enroute Supplement for PPR requirements and, if a PPR is required, state the PPR number or status of your PPR request as “pending” or “approved”.
(REQ) Other Requests
Indicate any requests you have at your destination aerodrome, e.g. FUEL or RON.
REQ DEP ARR TO ETEEYWYX
This entry ensures that your actual time of departure and/or arrival is passed to the AFOD
List your Military Diplomatic Clearance Numbers, preceded by the first two letters of the ICAO location identifiers of the FIR/UIRs entered. Please consult the Foreign Clearance Guide for respective aircraft entry requirements.
Diplomatic Clearances shall be listed after MDCN in the identification group RMK/. Example: MDCN ED XXXX LS XXXX LI XXXX
If a Diplomatic Clearance is still on request at the time you submit your flight plan, indicate that by the word “pending” in place of the Diplomatic Clearance Number and submit it to us when available. This will prevent unnecessary inquiries by the AFOD personnel and the recipients of your flight plan.
A STAYINFO indicator with the same sequence number as the corresponding STAY in item 15 shall be entered in item 18, explaining the reason for your stay and your intentions during that stay.
For a printable summary of all explanations, see AFOD Flight Planning Hints.
VFR Flight Plans:
IFR Flight Plans:
IFR RNAV INOP
IFR Mixed GAT/OAT
IFR Outside IFPS
IFR with Approaches
IFR with a STAY
Composite Flight Plans
AFOD Flight Planning Hints