These images show data input restrictions for each field.
Step 1: Select the field buttons to filter the topics related to each field.
Step 2: Select topic buttons to filter the items related to that topic.
Step 3: Select an item to see more detail.
You can also use the keyword search to filter items.
This field lists the radio communication, navigation, approach aid equipment and capabilities of the flight.
This field lists the surveillance equipment and capabilities of the flight.
"0" (zero) or One or more of these elements in this order: STS/ , PBN/, NAV/ , COM/ , DAT/ , SUR/ , DEP/ , DEST/ , DOF/ , REG/ , EET/ , SEL/ , TYP/ , CODE/ , RVR/ , DLE/ , OPR/ , ORGN/ , PER/ , ALTN/ , RALT/ , TALT/ , RIF/ , RMK/ , RFP
No equipment, standard equipment and other equipment carried or other capabilities.
Radio Communication equipment carried and serviceable.
Navigation and Approach aid equipment carried and serviceable.
No Surveillance Equipment.
SSR Modes A,C and S.
ADS B and C
0 (zero) if no other information.
STS/Reason for special handling by ATS, e.g. a search and rescue mission, as follows:
ATFMX, FFR, FLTCK, HAZMAT, HEAD, HOSP, HUM, MARSA, MEDEVAC, NONRVSM, SAR and STATE.
Other reasons for special handling by ATS shall be denoted under the designator RMK/.
When more than one reason apply to a flight, it shall be noted under one STS/ entry and separated by a space.
Example: STS/HOSP ATFMX
No longer accepted: ATFMEXEMPTAPPROVED, EXM833, NONRNAV, EMER, free text.
New reasons: ATFMX, FFR, FLTCK, HAZMAT, MARSA, MEDEVAC.
Any of the following STS descriptors when found in a message shall automatically exempt that flight from flow regulations: HEAD, ATFMX, FFR, SAR, MEDEVAC.
The PBN sub-field contains the RNAV and/or RNP certifications and operational approvals applicable for the flight. Include as many of the descriptors below, as apply to the flight, up to a maximum of 8 entries, i.e. a total of not more than 16 characters, inside an single occurrence of PBN/. Duplicate entries for the sub-field PBN/ is not permitted.
Significant data related to navigation equipment, other than specified in PBN/, as required by the appropriate ATS authority. Indicate GNSS augmentation under this indicator, with a space between two or more methods of augmentation, e.g. NAV/GBAS SBAS.
Indicate communications applications or capabilities no specified in Item 10a.
Indicate data applications or capabilities not specified in Item 10a.
Include surveillance applications or capabilities not specified in Item 10b.
Name and location of departure aerodrome, if ZZZZ is inserted in Item 13, or the ATS unit for which supplementary flight plan data can be obtained if AFIL is inserted in Item 13.
Name and location of destination aerodrome, if ZZZZ is inserted in Item 16.
Date Of Flight departure in a six figure format: YYMMDD.
The nationality or common mark and registration mark of the aircraft, if different from the aircraft identification in Item 7.
Significant points or FIR boundary designators and accumulated estimated elapsed times from take-off to such points or FIR boundaries, when so prescribed on the basis of regional air navigation agreements, or by the appropriate ATS authority.
Examples: EET/CAP0745 XYZ0830 and EET/EINN0204
SELCAL Code, for aircraft equipped.
Type(s) of aircraft preceded if necessary without a space by number(s) of aircraft and separated by one space if ZZZZ is inserted in Item 9.
Example: –TYP/2F15 5F5 3B2
Aircraft address (expressed in the form of an alphanumerical code of six hexadecimal characters) when required by the appropriate ATS authority. Example: “F00001” is the lowest aircraft address contained in the specific block administered by ICAO.
Enroute delay or holding: insert the significant point(s) on the route where a delay is planned to occur, followed by the length of delay using four figure time in hours and minutes (hhmm).
ICAO designator or name of the aircraft operating agency, if different from the aircraft identification in item 7.
The originator’s 8 letter AFTN address or other appropriate contact details, in cases where the originator of the flight plan may not be readily identified, as required by the appropriate ATS authority
Aircraft performance data, indicated by a single letter.
Name of destination aerodrome alternate aerodrome(s), if ZZZZ in inserted in Item 16.
ICAO four letter indicator(s) for en-route alternate(s), as specified in Doc 7910, Location Indicators, or name(s) of en-route alternate(s), if no indicator is allocated.
ICAO four letter indicator(s) for take-off alternate(s), as specified in Doc 7910, Location Indicators, or name(s) of take-off alternate(s), if no indicator is allocated.
The route details to the revised destination aerodrome, following by the ICAO four-letter location indicator of the aerodrome. The revised route is subject to reclearance in flight.Examples: RIF/DTA HEC KLAX and RIF/ESP G94 CLA YPPH
Any other plain language remarks when required by the appropriate ATS authority or deemed necessary.
Replacement Flight Plan. ICAO Doc 7030 Regional Supplementary Procedures, EUR region.
Runway Visual Range. It indicates the minimum RVR requirement of the flight. ICAO Doc 7030 Regional Supplementary Procedures, EUR region.