ICAO Flight Plan

5−1−9. International Flight Plan (FAA Form
7233−4)− IFR Flights (For Domestic or
International Flights)
a. General
Use of FAA Form 7233−4 is:
1. Mandatory for assignment of RNAV SIDs
and STARs or other PBN routing,
2. Mandatory for all IFR flights that will depart
U.S. domestic airspace, and
3. Recommended for domestic IFR flights.
NOTE−
1. An abbreviated description of FAA Form 7233−4
(International Flight Plan) may be found in this section. A
detailed description of FAA Form 7233−4 may be found on
the FAA website at:
http://www.faa.gov/about/office_org/
headquarters_offices/ato/service_units/enroute/flight_pl
an_filing/
2. Filers utilizing FAA Form 7233−1 (Flight Plan) may not
be eligible for assignment of RNAV SIDs and STARs. Filers
desiring assignment of these procedures should file using
FAA Form 7233−4, as described in this section.

3. When filing an IFR flight plan using FAA Form 7233−4,
it is recommended that filers include all operable
navigation, communication, and surveillance equipment
capabilities by adding appropriate equipment qualifiers as
shown in Tables 5−1−3 and 5−1−4. These equipment
qualifiers should be filed in Item 10 of FAA Form 7233−4.
4. ATC issues clearances based on aircraft capabilities
filed in Items 10 and 18 of FAA Form 7233−4. Operators
should file all capabilities for which the aircraft and crew
is certified, capable, and authorized. PBN/ capability
should be filed as per paragraph 5-1-9 b 8 Items 18 (c) and
(d).
b. Explanation of Items Filed in FAA Form
7233−4
Procedures and other information provided in this
section are designed to assist operators using FAA
Form 7233−4 to file IFR flight plans for flights that
will be conducted entirely within U.S. domestic
airspace. Requirements and procedures for operating outside U.S. domestic airspace may vary significantly from country to country. It is, therefore,
recommended that operators planning flights outside U.S. domestic airspace become familiar with
applicable international documents, including
Aeronautical Information Publications (AIP); International Flight Information Manuals (IFIM); and
ICAO Document 4444, Procedures for Air Navigation Services/Air Traffic Management, Appendix 2.
NOTE−
FAA Form 7233−4 is shown in FIG 5−1−3. The filer is
normally responsible for providing the information
required in Items 3 through 19.
1. Item 7. Aircraft Identification. Insert the
full registration number of the aircraft, or the
approved FAA/ICAO company or organizational
designator, followed by the flight number.
EXAMPLE−
N235RA, AAL3342, BONGO33
NOTE−
Callsigns filed in this item must begin with a letter followed
by 1−6 additional alphanumeric characters.

2. Item 8. Flight Rules and Type of Flight.
(a) Flight Rules. Insert the character “I” to
indicate IFR
(b) Type of Flight. Insert one of the
following letters to denote the type of flight:
(1) S if scheduled air service
(2) N if non−scheduled air transport
operation
(3) G if general aviation
(4) M if military
(5) X if other than any of the defined
categories above.
NOTE−
Type of flight is optional for flights that will be conducted
entirely within U.S. domestic airspace.

3. Item 9. Number, Type of Aircraft, and
Wake Turbulence Category.
(a) Number. Insert the number of aircraft, if
more than 1 (maximum 99).
(b) Type of Aircraft.
(1) Insert the appropriate designator as
specified in ICAO Doc 8643, Aircraft Type
Designators;
(2) Or, if no such designator has been
assigned, or in the case of formation flights consisting
of more than one type;
(3) Insert ZZZZ, and specify in Item 18, the
(numbers and) type(s) of aircraft preceded by TYP/.

(c) Wake Turbulence Category. Insert an
oblique stroke followed by one of the following
letters to indicate the wake turbulence category of
the aircraft:
(1) H — HEAVY, to indicate an aircraft
type with a maximum certificated takeoff weight of
300,000 pounds (136 000 kg), or more;
(2) M — MEDIUM, to indicate an aircraft
type with a maximum certificated takeoff weight of
less than 300,000 pounds (136,000 kg), but more than
15,500 pounds (7,000 kg);
(3) L — LIGHT, to indicate an aircraft type
with a maximum certificated takeoff weight of
15,500 pounds (7,000 kg) or less.
4. Item 10. Equipment

5. Item 13. Departure Aerodrome/Time
(a) Insert the ICAO four−letter location
indicator of the departure aerodrome, or
NOTE−
ICAO location indicators must consist of 4 letters. Airport
identifiers such as 5IA7, 39LL and Z40 are not in ICAO
standard format.
(b) If no four−letter location indicator has
been assigned to the departure aerodrome, insert
ZZZZ and specify the non−ICAO location identifier,
or fix/radial/distance from a nearby navaid, followed
by the name of the aerodrome, in Item 18, following
characters DEP/,
(c) Then, without a space, insert the estimated
off−block time.
EXAMPLE−
1. KSMF2215
2. ZZZZ0330

6. Item 15. Cruise Speed, Level and Route
(a) Cruise Speed (maximum 5 characters).
Insert the true airspeed for the first or the whole
cruising portion of the flight, in terms of knots,
expressed as N followed by 4 digits (e.g. N0485), or
Mach number to the nearest hundredth of unit Mach,
expressed as M followed by 3 digits (for example,
M082).
(b) Cruising level (maximum 5 characters).
Insert the planned cruising level for the first or the
whole portion of the route to be flown, in terms of
flight level, expressed as F followed by 3 figures (for
example, F180; F330), or altitude in hundreds of feet,
expressed as A followed by 3 figures (for example,
A040; A170).
(c) Route. Insert the requested route of flight
in accordance with guidance below.
NOTE−
Speed and/or altitude changes en route will be accepted by
FAA computer systems, but will not be processed or
forwarded to controllers. Pilots are expected to maintain
the last assigned altitude and request revised altitude
clearances directly from ATC.
(d) Insert the desired route of flight using a
combination of published routes and/or fixes in the
following formats:

should be separated by the characters “DCT”,
meaning direct.
EXAMPLE−
FLACK DCT IRW DCT IRW125023
NOTE−
IRW125023 identifies the fix located on the Will Rogers
VORTAC 125 radial at 23 DME.
(2) Combinations of published routes, and
fixes, navaids or waypoints should be separated by a
single space.
EXAMPLE−
WORTH5 MQP V66 ABI V385
(3) Although it is recommended that filed
airway junctions be identified using a named junction
fix when possible, there may be cases where it is
necessary to file junctioning airways without a named
fix. In these cases, separate consecutive airways with
a space.
EXAMPLE−
V325 V49
NOTE−
This method of filing an airway junction may result in a
processing ambiguity. This might cause the flight plan to be
rejected in some cases.

7. Item 16. Destination Aerodrome, Total
EET, Alternate and 2nd Alternate Aerodrome
(a) Destination Aerodrome and Total Estimated Elapsed Time (EET).
(1) Insert the ICAO four−letter location
identifier for the destination aerodrome; or, if no
ICAO location identifier has been assigned,
(Location identifiers, such as WY66, A08, and 5B1,
are not an ICAO standard format),
(2) Insert ZZZZ and specify the non−ICAO
location identifier, or fix/radial/distance from a
nearby navaid, followed the name of the aerodrome,
in Item 18, following characters DEST/,
(3) Then, without a space, insert the total
estimated time en route to the destination.
EXAMPLE−
1. KOKC0200
2. ZZZZ0330
(b) Alternate and 2nd Alternate Aerodrome
(Optional).
(1) Following the intended destination,
insert the ICAO four−letter location identifier(s) of alternate aerodromes; or, if no location identifier(s)
have been assigned;
(2) Insert ZZZZ and specify the name of the
aerodrome in Item 18, following the characters
ALTN/.
EXAMPLE−
1. KDFW0234 KPWA
2. KBOS0304 ZZZZ
NOTE−
Although alternate airport information filed in an FPL 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.

8. Item 18. Other Information
(a) Insert 0 (zero) if no other information; or,
any other necessary information in the sequence
shown below, in the form of the appropriate indicator
followed by an oblique stroke and the information to
be recorded:
NOTE−
1. Operators are warned that the use of indicators not
included in the provisions may result in data being rejected,
processed incorrectly, or lost.
2. Hyphens “-” or oblique strokes “/” should only be used
as described.
3. Avoid use of any other special characters in Field 18
information- use only letters and numbers.
4. An indicator without any associated information will
result in flight plan rejection.
(b) STS/ Reason for special handling by ATS
as follows:
(1) ALTRV: For a flight operated in
accordance with an altitude reservation.
(2) ATFMX: For a flight approved for
exemption from ATFM measures by the appropriate
ATS authority.
(3) FFR: Fire-fighting.
(4) FLTCK: Flight check for calibration of
navaids.

(5) HAZMAT: For a flight carrying hazardous material.
(6) HEAD: A flight with Head of State
status.

(7) HOSP: For a medical flight declared by
medical authorities.

(8) HUM: For a flight operating on a
humanitarian mission.
(9) MARSA: For a flight for which a
military entity assumes responsibility for separation
of military aircraft.
(10) MEDEVAC: For a life critical medical
emergency evacuation.
(11) NONRVSM: For a non-RVSM
capable flight intending to operate in RVSM airspace.
(12) SAR: For a flight engaged in a search
and rescue mission.
(13) STATE: For a flight engaged in
military, customs, or police services.
NOTE−
Other reasons for special handling by ATS are denoted
under the designator RMK/.
(c) PBN/ Indication of RNAV and/or RNP
capabilities. Include as many of the descriptors below
as apply to the flight, up to a maximum of 8 entries;
that is a total of not more than 16 characters.

NOTE−
Combinations of alphanumeric characters not indicated
above are reserved.
(d) NAV/ Significant data related to navigation equipment, other than as specified in PBN/.
(1) When Performance Based Navigation
Capability has been filed in PBN/, if PBN routing is
desired for only some segment(s) of the flight then
that information can be conveyed by inserting the
character “Z” in Item 10 and “NAV/RNV” in field 18
followed by the appropriate RNAV accuracy value(s)
per the following:
[a] To be assigned an RNAV 1 SID,
insert the characters “D1”.
[b] To be assigned an RNAV 1 STAR,
insert the characters “A1”.
[c] To be assigned en route extensions
and/or RNAV PTP, insert the characters “E2”.
[d] To prevent assignment of an RNAV
route or procedure, insert a numeric value of “0” for
the segment of the flight. Alternatively, you may
simply remove the segment of the flight indicator and
numeric value from the character string.
EXAMPLE−
1. NAV/RNVD1 or NAV/RNVD1E0A0 (Same meaning)
2. NAV/RNVA1 or NAV/RNVD0E0A1 (Same meaning)
3. NAV/RNVE2 or NAV/RNVD0E2A0 (Same meaning)
4. NAV/RNVD1A1 or NAV/RNVD1E0A1 (Same meaning)

5. NAV/RNVD1E2A1
NOTE−
1. Route assignments are predicated on NAV/ data over
PBN/ data in ERAS.
2. Aircraft certification requirements for RNAV operations within U.S. airspace are defined in AC 90-45A,
Approval of Area Navigation Systems for Use in the U.S.
National Airspace System, and AC 90−100A, U.S.
Terminal and En Route Area Navigation (RNAV)
Operations, as amended.
(2) Operators should file their maximum
capabilities in order to qualify for the most advanced
procedures.
(e) COM/ Indicate communications capabilities not specified in Item 10a, when requested by an
air navigation service provider.
(f) DAT/ Indicate data applications or capabilities not specified in Item 10a, when requested by an
Air Navigation Service Provider.

No Comments - Share this on Facebook or Twitter.

Leave a Reply

By submitting a comment here you grant Flymall a perpetual license to reproduce your words and name/web site in attribution. Inappropriate or irrelevant comments will be removed at an admin's discretion.

Today in Aviation History