Appendix 1. FAA Form 7233-4 - International Flight Plan

a. The FAA will accept a flight plan in international format for IFR, VFR, SFRA, and DVFR flights. File the flight plan electronically via a Flight Service Station (FSS), FAA contracted flight plan filing service, or other commercial flight plan filing service. Depending on the filing service chosen, the method of entering data may be different but the information required is generally the same.

b. The international flight plan format is mandatory for:

1. Any flight plan filed through a FSS or FAA contracted flight plan filing service; with the exception of Department of Defense flight plans and civilian stereo route flight plans, which can still be filed using the format prescribed in FAA Form 7233-1.

NOTE-
DOD Form DD-175 and FAA Form 7233-1 are considered to follow the same format.

2. Any flight that will depart U.S. domestic airspace. For DOD flight plan purposes, offshore Warning Areas may use FAA Form 7233-1 or military equivalent.

3. Any flight requesting routing that requires Performance Based Navigation.

4. Any flight requesting services that require filing of capabilities only supported in the international flight plan format.

c. Flight Plan Contents

1. A flight plan will include information shown below:

(a) Flight Specific Information (TBL 1-1)

(b) Aircraft Specific Information (TBL 1-19)

(c) Flight Routing Information (TBL 1-20)

(d) Flight Specific Supplementary Information (Item 19)

2. The tables indicate where the information is located in the international flight plan format, the information required for U.S. domestic flights, and the location of equivalent information in the domestic flight plan format.

3. International flights, including those that temporarily leave domestic U.S. airspace and return, require all applicable information in the international flight plan. Additional information can be found in ICAO Doc. 4444 (Procedures for Air Navigation Services, Air Traffic Management), and ICAO Doc. 7030 (Regional Supplemental Procedures) as well as the Aeronautical Information Publications (AIPs), Aeronautical Information Circulars (AICs), and NOTAMs of applicable other countries.

TBL 1-1
Flight Specific Information

d. Instructions for Flight-Specific Information Items

1. Aircraft Identification (Item 7) Aircraft Identification is always required. Aircraft identification must not exceed seven alphanumeric characters and be either:

(a) The ICAO designator for the aircraft operating agency, followed by the flight identification (for example, KLM511, NGA213, JTR25). When in radiotelephony the call sign to be used by the aircraft will consist of the ICAO telephony designator for the operating agency followed by the flight identification (for example, KLM511, NIGERIA213, JESTER25);

(b) The nationality or common mark and registration of the aircraft (for example, EIAKO, 4XBCD, N2567GA), when:

(1) In radiotelephony, the call sign to be used by the aircraft will consist of this identification alone (for example, CGAJS) or preceded by the ICAO telephony designator for the aircraft operating agency (for example, BLIZZARD CGAJS); or

(2) The aircraft is not equipped with radio.

NOTE-
1. Standards for nationality, common and registration marks to be used are contained in Annex 7, Chapter 2.

2. Provisions for using radiotelephony call signs are contained in Annex 10, Volume II, Chapter 5. ICAO designators and telephony designators for aircraft operating agencies are contained in Doc 8585—Designators for Aircraft Operating Agencies, Aeronautical Authorities and Services.

NOTE-
Some countries' aircraft identifications begin with a number, which cannot be processed by U.S. ATC automation. The FAA will add a leading letter temporarily to gain automation acceptance for aircraft identifications that begin with a numeral. For flight-processing systems (e.g., ERAM or STARS) which will not accept a call sign that begins with a number, if the call sign is 6 characters or less, add a Q at the beginning of the call sign. If the call sign is 7 characters, delete the first character and replace it with a Q. Put the original call sign in the remarks section of the flight plan.

EXAMPLE-
9HRA becomes Q9HRA
5744233 becomes Q744233

2. Flight Rules (Item 8a)

(a) Flight rules are always required.

(b) Flight rules must indicate IFR (I) or VFR (V).

(c) For composite flight plans, submit separate flight plans for the IFR and VFR portions of the flight. Specify in Item 15 the point or points where change of flight rules is planned. The IFR plan will be routed to ATC, and the VFR plan will be routed to a Flight Service for Search and Rescue services.

NOTE-
The pilot is responsible for opening and closing the VFR flight plan. ATC does not have knowledge of a VFR flight plan's status.

3. Type of Flight (Item 8b)

(a) The type of flight is optional for flights remaining wholly within U.S. domestic airspace.

(b) Indicate the type of flight as follows:

• G - General Aviation

• S - Scheduled Air Service

• N - Non-Scheduled Air Transport Operation

• M - Military

• X - other than any of the defined categories above

4. Equipment and Capabilities (Item 10, Item 18 NAV/, COM/, DAT/, SUR/)

(a) Equipment and capabilities that can be filed in a flight plan include:

• Navigation capabilities in Item 10a, Item 18 PBN/, and Item 18 NAV/

• Voice communication capabilities in Item 10a and Item 18 COM/

• Data communication capabilities in Item 10a and Item 18 DAT/

• Approach capabilities in Item 10a and Item 18 NAV/

• Surveillance capabilities in Item 10b and Item 18 SUR/

(b) Codes allowed in Item 10a are shown in Table 1-2. Codes allowed in Item 10b are shown in TBL 1-3. Codes recognized in Item 18 NAV/, COM/, DAT/, and SUR/ are shown in TBL 1-4. Note that other service providers may define additional allowable (and required) codes for use in Item 18 NAV/, COM/, DAT/, or SUR/. Codes to designate PBN capability are described in TBL 1-5.

Radio communication, navigation and approach aid equipment and capabilities

ENTER one letter as follows:

N if no COM/NAV/approach aid equipment for the route to be flown is carried, or the equipment is unserviceable,

OR

S if standard COM/NAV/approach aid equipment for the route to be flown is carried and serviceable (see Note 1),

AND/OR

ENTER one or more of the following letters from TBL 1-2 to indicate the serviceable COM/NAV/ approach aid equipment and capabilities available.

TBL 1-2
Item 10a Navigation, Communication, and Approach Aid Capabilities

Any alphanumeric characters not indicated above are reserved.

NOTE-
1. If the letter “S” is used, standard equipment is considered to be VHF RTF, VOR, and ILS, unless another combination is prescribed by the appropriate ATS authority.

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

EXAMPLE-
NAV/SBAS

3. See RTCA/EUROCAE Interoperability Requirements Standard for ATN Baseline 1 (ATN B1 INTEROP Standard - DO -280B/ED-110B) for data link services air traffic control clearance and information/air traffic control communications management/air traffic control microphone check.

4. If the letter “R” is used, the performance-based navigation levels that can be met are specific in Item 18 following the indicator PBN/. Guidance material on the application of performance-based navigation to a specific route segment, route, or area is contained in the Performance-based Navigation (PBN) Manual (Doc 9613)

5. If the letter “Z” is used, specify in Item 18 the other equipment carried or other capabilities, preceded by COM/, NAV/, and/or DAT, as appropriate.

6. Information on navigation capability is provided to ATC for clearance and routing purposes.

7. Guidance on the application of performance-based communication, which prescribes RCP to an air traffic service in a specific area, is contained in the Performance-based Communication and Surveillance (PBCS) Manual (Doc 9869).

TBL 1-3
Item 10b Surveillance Capabilities

TBL 1-4
Item 18 NAV/, COM/, DAT/, and SUR/ capabilities used by FAA

NOTE-
1. Other entries in NAV/, COM/, DAT/, and SUR/ are permitted for international flights when instructed by other service providers. Direction on use of these capabilities by the FAA is detailed in the following sections.

2. In NAV/, descriptors for advanced capabilities (Z1, P1, R1, M1, and M2) should be entered as a single character string with no intervening spaces, and separated from any other entries in NAV/ by a space.

EXAMPLE-
NAV/Z1P1M2 SBAS

TBL 1-5
Item 18. PBN/ Specifications
(Include as many of the applicable descriptors, up to a maximum of 8 entries (not more than 16 characters).

NOTE-
1. PBN Codes B1-B6 indicates RNAV 5 capability. The FAA considers these B codes to be synonymous and qualifying for point-to-point routing but not for assignment to the PBN routes shown in the table.

2. Combinations of alphanumeric characters not included above are reserved.

3. The PBN/ specifications are allowed per ICAO Doc. 4444. The FAA makes use of a subset of these codes as described in the section on filing navigation capability.

(c) The following sections detail what capabilities need to be provided to obtain services from the FAA for:

• IFR flights (general).

• Assignment of Performance-Based Navigation (PBN) routes.

• Automated Departure clearance (via Datacom DCL or PDC).

• Reduced Vertical Separation Minima (if requesting FL 290 or above).

• Reduced Separation in Oceanic Airspace.

(d) Capabilities such as voice communications, required communications performance, approach aids, and ADS-C, are not required in a flight plan that remains entirely within domestic airspace.

(e) Flights that leave domestic United States airspace may be required to include additional capabilities, per requirements for the FIRs being overflown. Consult the appropriate State Aeronautical Information Publications for requirements.

(f) Include the capability only if:

• The requisite equipment is installed and operational;

• The crew is trained as required; and

• Any required Operations Specification, Letter of Authorization, or other approvals are in hand.

NOTE-
Do not include a capability solely based on the installed equipment if an operational approval is required. For example, all U.S. civil operators require either Operations Specification, Management Specification, or Letter of Authorization B036, as applicable, in order to include NAV/M2 (RNP 2 (oceanic/remote)), PBN/A1 (RNAV 10 (RNP 10)), or PBN/L1 (RNP 4) in Item 18.

5. Filing equipment and capability in an IFR Flight Plan. This section details the minimum requirements to identify capabilities in an IFR flight plan for flights in the domestic United States. Other requirements to file a capability are associated with obtaining specific services as described in subsequent sections. The basic capabilities that must be addressed include Navigation, Transponder, Voice, and ADS-B Out as described below. A designator for “Standard” capability is also allowed to cover a suite of commonly carried voice, navigation, and approach equipment with one code.

(a) Standard Capability and No Capability (Item 10a)

• Use “S” if VHF radio, VOR, and ILS equipment for the route to be flown are carried and serviceable. Use of the 'S' removes the need to list these three capabilities separately.

• Use “N” if no communications, navigation, or approach aid equipment for the route to be flown are carried or the equipment is unserviceable.

• When there is no transponder, ADS-B, or ADS-C capability then file only the letter 'N' in Item 10b.

(b) Navigation Capabilities (Item 10a, Item 18 NAV/)

• Indicate radio navigation capability by filing one or more of the codes in TBL 1-6.

• Indicate Area Navigation (RNAV) capability by filing one or more of the codes in TBL 1-7.

TBL 1-6
Radio Navigation Capabilities

TBL 1-7
Area Navigation Capabilities

NOTE-
1. SBAS - Space-Based Augmentation System
GBAS - Ground-Based Augmentation System

2. No PBN/ code needs to be filed to indicate the ability to fly point-to-point routes using GNSS or INS.

3. Filing one of these four area navigation capabilities as shown does not indicate performance based navigation sufficient for flying Q-Routes, T-Routes, or RNAV SIDs or STARs. To qualify for these routes, see the section on Performance Based Navigation Routes.

(c) Transponder Capabilities (Item 10b)

• For domestic flights, it is not necessary to indicate Mode S capability. It is acceptable to simply file one of the following codes in TBL 1-8.

TBL 1-8
Mode C

• International flights must file in accordance with relevant AIPs and regional supplements. Include one of the Mode S codes in TBL 1-9, if appropriate.

NOTE-
File only one transponder code.

TBL 1-9
Mode S

(d) ADS-B Capabilities (Item 10b, Item 18 SUR/ and Item 18 CODE/)

• Indicate ADS-B capability as shown in TBL 1-10. The accompanying entry in Item 18 indicates that the equipment is compliant with 14 CFR §91.227. Some ADS-B equipment used in other countries is based on an earlier standard and does not meet U.S. requirements.

• Do not file an ADS-B code for “in” capability only. There is currently no way to indicate that an aircraft has “in” capability but no “out” capability.

• For aircraft with ADS-B “out” on one frequency and “in” on another, include only the ADS-B “out” code. For example, B1 or U1, (See TBL 1-10).

TBL 1-10
ADS-B Capabilities

(e) Voice Communication Capabilities (Item 10a)

The FAA does not require indication of voice communication capabilities in a flight plan for domestic flights, but it is permissible. For flights outside the domestic United States, all relevant capabilities must be indicated as follows (See TBL 1-11):

TBL 1-11
Voice Communication Capabilities

(f) Approach Aid Capabilities (Item 10a).

The FAA does not require filing of approach aid capability in order to request a specific type of approach, however any of the codes indicated in TBL 1-12 in 10a are permissible.

• International flights may be required to indicate approach capability, based on instructions from relevant service providers.

TBL 1-12
Approach Aid Capabilities

6. Performance-Based Navigation Routes (Item 10a, Item 18 PBN/, Item 18 NAV/)- When planning to fly routes that require PBN capability, file the appropriate capability as shown in TBL 1-13.

TBL 1-13
Filing for Performance Based Navigation (PBN) Routes

NOTE-
1. If the flight is requesting an RNAV SID only (no RNAV STAR) or RNAV STAR only (no RNAV SID) then consult guidance on the FAA website at
https://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/air_traffic_services/flight_plan_filing.

2. PBN descriptor D1 includes the capabilities of D2, D3, and D4. PBN descriptor B1 includes the capabilities of B2, B3, B4, and B5. PBN descriptor C1 includes the capabilities of C2, C3, and C4.

3. In NAV/, descriptors for advanced capabilities (Z1, P1, R1, M1, and M2) should be entered as a single character string with no intervening spaces, and separated from any other entries in NAV/ by a space.

EXAMPLE-
NAV/Z1P1M2 SBAS

7. Automated Departure Clearance Delivery (DCL or PDC). When planning to use automated pre-departure clearance delivery capability, file as indicated below.

(a) PDC provides pre-departure clearances from the FAA to the operator's designated flight operations center, which then delivers the clearance to the pilot by various means. Use of PDC does not require any special flight plan entry.

(b) DCL provides pre-departure clearances from the FAA directly to the cockpit/FMS via Controller Pilot Datalink Communications (CPDLC). Use of DCL requires flight plan entries as follows:

• Include CPDLC codes in Item 10a only if the flight is capable of en route/oceanic CPDLC, the codes are not required for DCL.

• Include Z in Item 10a to indicate there is information provided in Item 18 DAT/.

• Include the clearance delivery methods of which the flight is capable, and order of preference in Item 18 DAT/. (See AIM 5-2-2)

○ VOICE - deliver clearance via Voice

○ PDC - deliver clearance via PDC

○ FANS - deliver clearance via FANS 1/A

○ FANSP - deliver clearance via FANS 1/A+

EXAMPLE-
DAT/1FANS2PDC
DAT/1FANSP2VOICE

8. Operating in Reduced Vertical Separation Minima (RVSM) Airspace (Item 10a). When planning to fly in RVSM airspace (FL 290 up to and including FL 410) then file as indicated below.

(a) If capable and approved for RVSM operations, per AIM 4-6-1, Applicability and RVSM Mandate (Date/Time and Area), file a W in Item 10a. Include the aircraft registration mark in Item 18 REG/, which is used to post-operationally monitor the safety of RVSM operations.

• Do not file a “W” in Item 10a if the aircraft is capable of RVSM operations, but is not approved to operate in RVSM airspace.

• If RVSM capability is lost after the flight plan is filed, request that ATC remove the 'W' from Item 10a.

(b) When requesting to operate non-RVSM in RVSM airspace, using one of the exceptions identified in AIM 4-6-10, do not include a “W” in Item 10a. Include STS/NONRVSM in Item 18. STS/NONRVSM is used only as part of a request to operate non-RVSM in RVSM airspace.

9. Eligibility for Reduced Oceanic Separation. Indicate eligibility for the listed reduced separation minima as indicated in the tables below. Full Operational Requirements for these services are found in the U.S. Aeronautical Information Publication (AIP) ENR 7, Oceanic Operations, available at http://www.faa.gov/air_traffic/publications/atpubs/aip_html/index.html.

TBL 1-14
Filing for Gulf of America CTA

NOTE-
If not RNAV10/RNP10 capable and planning to operate in the Gulf of America CTA, then put the notation NONRNP10 in Item 18 RMK/, preferably first.

TBL 1-15
Filing for 50 NM Lateral Separation in Anchorage Arctic FIR

TBL 1-16
Filing for 30 NM Lateral, 30 NM Longitudinal, and 50 NM Longitudinal Oceanic Separation
in Anchorage, Oakland, and New York Oceanic CTAs

TBL 1-17
Filing for Reduced Oceanic Separation when RSP/RCP Required on March 29, 2018

NOTE-
1. Filing of RNP 2 alone is not supported in FAA controlled airspace; PBN/L1 (for RNP 4) or PBN/A1 (for RNP 10) must be filed to obtain the indicated separation.

2. Use of “RNP 2” in NAV/ signifies continental RNP 2 (and means the same as M1). Continental RNP 2 is not adequate for reduced oceanic separation. Descriptor M2 indicates RNP 2 global/oceanic RNP 2 capability.

10. Date of Flight (Item 18 DOF/)

Flights planned more than 23 hours after the time the flight plan is filed, must include the date of flight in DOF/ expressed in a six-digit format YYMMDD, where YY equals the year (Y), MM equals the month, and DD equals the day.

NOTE-
FAA ATC systems will not accept flight plans more than 23 hours prior to their proposed departure time. FAA Flight Service and commercial flight planning services generally accept flight plans earlier and forward to ATC at an appropriate time, typically 2 to 4 hours before the flight.

EXAMPLE-
DOF/171130

11. Reasons for Special Handling (Item 18 STS/)

(a) Indicate the applicable Special Handling in Item 18 STS/ as shown in TBL 1-18.

NOTE-
Priority for a flight is not automatically granted based on filing one of these codes but is based on documented procedures. In some cases, additional information may also be required in remarks; follow all such instructions as well.

TBL 1-18
Special Handling

(b) Any other requests for special handling must be made in Item 18 RMK/.

(c) Include plain-language remarks when required by ATC or deemed necessary. Do not use special characters, for example; / * - = +.

EXAMPLE-
RMK/NRP
RMK/DVRSN

12. Remarks

Include when necessary.

13. Operator (Item 18 OPR/)

When the operator is not obvious from the aircraft identification, the operator may be indicated.

EXAMPLE-
OPR/NETJETS

14. Flight Plan Originator (Item 18 ORGN/)

(a) VFR flight plans originating outside of FAA FSS or FAA contracted flight plan filing services must enter the 8-letter AFTN address of the service where the flight plan was originally filed. Alternately, enter the name of the service where the FPL was originally filed. This information is critical to locating the FPL originator in the event additional information is needed.

(b) For IFR flight plans, the original filers AFTN address may be indicated, which is helpful in cases where a flight plan has been forwarded.

EXAMPLE-
ORGN/Acme Flight Plans
ORGN/KDENXLDS

TBL 1-19
Aircraft Specific Information

e. Instructions for Aircraft-Specific Information.

1. Number of Aircraft (Item 9) when there is more than one aircraft in the flight; indicate the number of aircraft up to 99.

2. Type of Aircraft (Item 9)

(a) Provide the appropriate 2-4 character aircraft type designator listed in FAA Order JO 7360.1, Aircraft Type Designators. FAA Order JO 7360.1 may be located at: Orders & Notices (faa.gov), then enter 7360.1 in the Search box.

(b) When there is no designator for the aircraft type use 'ZZZZ', and provide a description in Item 18 TYP/.

3. Wake Turbulence Category (Item 9)

A Wake Turbulence Category is required for all aircraft types. Provide the appropriate wake turbulence category for the aircraft type as listed in FAA Order 7360.1. The categories include:

(a)  J - SUPER, aircraft types specified as such in FAA Order JO 7360.1, Aircraft Type Designators.

(b) H - HEAVY, to indicate an aircraft type with a maximum certificated take-off mass of 300,000 lbs. or more, with the exception of aircraft types listed in FAA Order JO 7360.1 in the SUPER (J) category.

(c) M - MEDIUM, to indicate an aircraft type with a maximum certificated take-off mass of less than 300,000 lbs. but more than 15,500 lbs.

(d) L - LIGHT, to indicate an aircraft type with a maximum certificated take-off mass of 15,500 lbs. or less.

4. Aircraft Registration (Item 18 REG/)

The aircraft registration must be provided here if different from the Item 7 entry. The registration mark must not include any spaces or hyphens. Additionally, the actual aircraft registration must also be included if Item 7 would have contained a leading numeric and was modified to be prefixed with the appropriate alphabetic character for U.S. ATC acceptance.

EXAMPLE-
U.S. aircraft with registration N789AK
REG/N789AK
Belgian aircraft with registration OO-FAH
REG/OOFAH

5. Mode S Address (Item 18 CODE/)

There is no U.S. requirement to file the aircraft Mode S Code in Item 18.

6. SELCAL code (Item 18 SEL/)

(a) Flights with HF radio and Selective Calling capability should include their 4-letter SELCAL code. Per the U.S. AIP, GEN 3.4, Paragraph 9, Selective Calling System (SELCAL) Facilities Available.

(b) The SELCAL is a communication system that permits the selective calling of individual aircraft over radio-telephone channels from the ground station to properly equipped aircraft, to eliminate the need for the flight crew to constantly monitor the frequency in use.

EXAMPLE-
SEL/CLEF

7. Performance Category (Item 18 PER/)

Include the appropriate single-letter Aircraft Approach Category as defined in the Pilot/Controller Glossary.

EXAMPLE-
PER/A

TBL 1-20
Flight Routing Information

f. Instructions for Flight Routing Items

1. Departure Airport (Item 13, Item 18 DEP/)

(a) Enter the departure airport. The airport should be identified using the four-letter location identifier from FAA Order JO 7350.9, Location Identifiers, or from ICAO Document 7910. FSS and FAA contracted flight plan filing services will allow up to 11 characters in the departure field. This will permit entry of non-ICAO identifier airports, and other fixes such as an intersection, fix/radial/distance, and latitude/longitude coordinates. Other electronic filing services may require a different format.

NOTE-
While user interfaces for flight plan filing are not specified, all flight plan filing services must adhere to the appropriate Interface Control Document upon transmission of the flight plan to the control facility.

(b) When the intended departure airport (Item 13) is outside of domestic U.S. airspace, or if using the paper version of FAA Form 7233-4, or DOD equivalent, if the chosen flight plan filing service does not allow non-ICAO airport identifiers in Item 13 or Item 16, use the following ICAO procedure. Enter four Z's (ZZZZ) in Item 13 and include the non-ICAO airport location identifier, fix, or waypoint location in Item 18 DEP/. A text description following the location identifier is permissible in Item 18 DEP/.

NOTE-
Use of non-ICAO identifiers in Item 13 and Item 16 is only permissible when flight destination is within U.S. airspace. If the destination is outside of the U.S., then both Item 13 and Item 16 must contain either a valid ICAO airport identifier or ZZZZ. Use of non-ICAO departure point is not permitted in Item 13 if destination in Item 16 is outside of U.S.

EXAMPLE-
DEP/MD21
DEP/W29 BAY BRIDGE AIRPORT
DEP/EMI211017
DEP/3925N07722W

2. Departure Time (Item 13)

Indicate the expected departure time using 4 digits, 2 digits for hours and 2 digits for minutes. Time is to be entered as Coordinated Universal Time (UTC).

3. Requested Cruising Speed (Item 15)

(a) Include the requested cruising speed as True Airspeed in knots using an N followed by four digits.

EXAMPLE-
N0450

(b) Indicate the requested cruising speed in Mach using an M followed by three digits.

EXAMPLE-
M081

4. Requested Cruising Altitude or Flight Level (Item 15)

(a) Indicate a Requested Flight Level using the letter F followed by 3 digits.

EXAMPLE-
F350

(b) Indicate a Requested Altitude in hundreds of feet using the letter A followed by 3 digits.

EXAMPLE-
A080

5. Route (Item 15)

Provide the requested route of flight using a combination of published routes, latitude/longitude, and/or fixes in the following formats.

(a) Consecutive fixes, lat/long points, NAVAIDs, and waypoints should be separated by the characters “DCT”, meaning direct.

EXAMPLE-
FLACK DCT IRW DCT IRW12503
4020N07205W DCT MONEY

(b) A published route should be preceded by a fix that is published on the route, indicating where the route will be joined. The published route should be followed by a fix that is published as part of the route, indicating where the route will be exited.

EXAMPLE-
DALL3 EIC V18 MEI LGC4

(c) It is acceptable to specify intended speed and altitude changes along the route by appending an oblique stroke followed by the next speed and altitude. However, note that FAA ATC systems will neither process this information nor display it to ATC personnel. Pilots are expected to maintain the last assigned altitude and request revised altitude clearances from ATC.

EXAMPLE-
DCT APN J177 LEXOR/N0467F380 J177 TAM/N0464F390 J177

6. Delay En Route (Item 15, Item 18 DLE/)

(a) ICAO defines Item 18 DLE/ to provide information about a delay en route. International flights with a delay outside U.S. domestic airspace should indicate the place and duration of the delay in Item 18 DLE/. The delay is expressed by a fix identifier followed by the duration in hours (H) and minutes (M), HHMM.

EXAMPLE-
DLE/EMI0140

(b) U.S. ATC systems will accept but not process information in DLE/. Therefore, for flights in the lower 48 states, it is preferable to include the delay as part of the route (Item 15). Delay in this format is specified by an oblique stroke (/) followed by the letter D, followed by 2 digits for hours (H) of delay, followed by a plus sign (+), followed by 2 digits for minutes (M) of delay: /DHH+MM.

EXAMPLE-
DCT EMI/D01+40 DCT MAPEL/D00+30 V143 DELRO DCT

7. Destination Airport (Item 16, Item 18 DEST/)

(a) Enter the destination airport. The airport should be identified using the four-letter location identifier from FAA Order JO 7350.9, Location Identifiers, or from ICAO Document 7910. FSS and FAA contracted flight plan filing services will allow up to 11 characters in the destination field. This will permit entry of non-ICAO identifier airports, and other fixes such as an intersection, fix/radial/distance, and latitude/longitude coordinates. Other electronic filing services may require a different format.

NOTE-
While user interfaces for flight plan filing are not specified, all flight plan filing services must adhere to the appropriate Interface Control Document upon transmission of the flight plan to the control facility.

(b) When the intended destination (Item 16) is outside of domestic U.S. airspace, or if using the paper version of FAA Form 7233-4, or if the chosen flight plan filing service does not allow non-ICAO airport identifiers in Item 13 or Item 16, use the following ICAO procedure. Enter four Z's (ZZZZ) in Item 13 and include the non-ICAO airport location identifier, fix, or waypoint location in Item 18 DEP/. A text description following the location identifier is permissible in Item 18 DEP/.

EXAMPLE-
DEST/06A MOTON FIELD
DEST/4AK6
DEST/MONTK
DEST /3925N07722W

8. Total Estimated Elapsed Time (Item 16)

All flight plans must include the total estimated elapsed time from departure to destination in hours (H) and minutes (M), format HHMM.

9. Alternate Airport (Item 16, Item 18 ALTN/)

(a) When necessary, specify an alternate airport in Item 16 using the four-letter location identifier from FAA Order 7350.9 or ICAO Document 7910. When the airport does not have a four-letter location identifier, include ZZZZ in Item 16c and file the non-standard identifier in Item 18 ALTN/. 

(b) While the FAA does not require filing of alternate airports in the flight plan provided to ATC, rules for establishing alternate airports must be followed.

(c) Adding an alternate may assist during Search and Rescue by identifying additional areas to search.

(d) Although alternate airport information filed in a flight plan will be accepted by air traffic computer systems, it will not be presented to controllers. If diversion to an alternate airport becomes necessary, pilots are expected to notify ATC and request an amended clearance.

EXAMPLE-
ALTN/W50 2W2

10. Estimated Elapsed Times (EET) at boundaries or reporting points (Item 18 EET/)

EETs are required for international or oceanic flights when crossing a Flight Information Region (FIR) boundary. The EET will include the ICAO four-letter location identifier for the FIR followed by the elapsed time to the FIR boundary (e.g., KZNY0245 indicates 2 hours, 45 minutes from departure until the New York FIR boundary).

EXAMPLE-
EET/MMFR0011 MMTY0039 KZAB0105

11. Remarks (Item 18 RMK/)

Enter only those remarks pertinent to ATC or to the clarification of other flight plan information. Items of a personal nature are not accepted.

NOTE-
1. “DVRSN” should be placed in Item 11 only if the pilot/company is requesting priority handling to their original destination from ATC as a result of a diversion as defined in the Pilot/Controller Glossary.

2. Do not assume that remarks will be automatically transmitted to every controller. Specific ATC or en route requests should be made directly to the appropriate controller.

g. Flight Specific Supplemental Information (Item 19)

1. Item 19 data must be included when completing FAA Form 7233-4. This information will be retained by the facility/organization that transmits the flight plan to Air Traffic Control (ATC), for Search and Rescue purposes, but it will not be transmitted to ATC as part of the flight plan.

2. Do not include Supplemental Information as part of Item 18. The information in Item 19 is retained with the flight plan filing service for retrieval only if necessary.

NOTE-
Supplemental Information within Item 19 will be transmitted as a separate message to the destination FSS for VFR flight plans filed with a FSS or FAA contracted flight plan filing service. This will reduce the time necessary to conduct SAR actions should the flight become overdue, as this information will be readily available to the destination Flight Service Station.

3. Minimum required Item 19 entries for a domestic flight are Endurance, Persons on Board, Pilot Name and Contact Information, and Color of Aircraft. Additional entries may be required by foreign air traffic services, or at pilot discretion.

(a) After E/ Enter fuel endurance time in hours and minutes.

(b) After P/ Enter total number of persons on board using up to 30 alphanumeric characters. Enter TBN (to be notified) if the total number of persons is not known at the time of filing.

EXAMPLE-
P/005
P/TBN
P/ON FILE CAPEAIR OPERATIONS

(c) R/ (Radio) Cross out items not carried

(d) S/ (Survival Equipment) Cross out items not carried.

(e) J/ (Jackets) Cross out items not carried.

(f) D/ (Life Raft/Dinghies) Enter number carried and total capacity. Indicate if covered and color.

(g) A/ (Aircraft Color and Markings) Enter aircraft color(s).

EXAMPLE-
White Yellow Blue

4. N/ (Remarks. Not for ATC) select N if no remarks. Enter comments concerning survival equipment and information concerning personal GPS locating service, if utilized. Enter name and contact information for responsible party to verify VFR arrival/closure, if desired. Ensure party will be available for contact at ETA. (for example; FBO is open at ETA)

5. C/ (Pilot) Enter name and contact information, including telephone number, of pilot-in-command. Ensure contact information will be valid at ETA in case SAR is necessary.

FIG 1-1
FAA Form 7233-4, Pre-Flight Pilot Checklist and International Flight Plan

NOTE-
Current FAA Form 7233-4 available at https://www.faa.gov/forms/.