1.2.1   In Belgium

An abbreviated flight plan transmitted in the air contains as a minimum:

• call sign;
• type of aircraft;
• point of entry;
• point of exit;
• level.

1.2.2   In Luxembourg

An abbreviated flight plan transmitted in the air by radiotelephony for the crossing of controlled airspace contains, as a minimum:

• call sign;
• type of aircraft;
• point of entry;
• point of exit;
• level.

For domestic VFR flights (no border crossing), an abbreviated flight plan may be submitted at least 30 MIN prior departure. It comprises the following information:

• aircraft identification;
• departure aerodrome and estimated off-block time;
• destination aerodrome or operating site and total estimated flight time;
• mandatory reporting point for CTR exit;
• fuel endurance;
• total number of persons on board;
• name of the pilot in command.

1.3.1   IFR Flight Plan

A full flight plan shall be submitted for IFR flights prior to departure either to the IFPS or to an ARO, or during flight to an appropriate ATS unit.

The IFPS is the responsible unit for accepting IFR/GAT flight plans, for flights conducted within the IFPS Zone. Unless a flight plan has been received and accepted by the IFPS (i.e. an ACK message has been received), the requirement to submit a flight plan for an IFR/GAT flight intending to operate into the IFPS-Zone will not have been satisfied and no ATC clearance will be issued for such a flight.

Aircraft operators shall file their flight plans and associated messages for IFR/GAT flights directly with the IFPS, whenever possible, or they can use the intermediate of a local ARO. The IFPS will send back “Operational Reply Messages” to the message originator (aircraft operator or ARO), indicating the status of processing of his flight plan or associated message:

• an acknowledge message (ACK) will indicate the successful processing of the message;
• a reject message (REJ) indicates that the submitted message could not be processed and that the message originator should file a new corrected message;
• a manual message (MAN) means that the message contains errors and that it will be presented to an IFPS operator for manual processing. A MAN message will be followed either by an ACK message, if the message has been corrected successfully by the IFPS operator, or by a REJ message, if the error(s) could not be solved.

Detailed information on flight plan filing procedures with IFPS is published in the IFPS Users Manual (see ENR 1.9, § 3).

1.3.2   VFR Flight Plan

Flight plans shall be submitted for VFR flights as required in § 1.1 above. A full flight plan can be submitted for VFR flights prior to departure to an ARO or during flight to an appropriate ATS unit. Alternatively, an abbreviated flight plan may be submitted to the ATS unit concerned. A full flight plan must be filed if the pilot requires other ATS units affected by his flight to be notified.

1.3.3   Adherence to Airspace Utilisation Rules and Availability

No flight plans shall be filed via the Brussels FIR/UIR deviating from the State restrictions defined within the Route Availability Document (RAD). This common European reference document contains all airspace utilisation rules and availability for the Brussels FIR/UIR and any reference to them shall be made via:

1.3.4   Procedures for Submitting Flight Plans Prior to Departure

1.3.5   Procedures for Submitting Flight Plans during Flight (AFIL)

A flight plan submitted during flight should normally be transmitted to the ATS unit in charge of the FIR or control area in which the aircraft is flying in, or through which the aircraft wishes to fly.

In case of an AFIL, the ATS unit receiving the flight plan will be responsible for addressing the flight plan message in accordance with the procedures described above.

An AFIL for a flight to be provided with ATC service shall be submitted at a time that will ensure its receipt by the appropriate ATS unit at least 10 MIN before the aircraft is estimated to reach:

• the intended point of entry into a control area;
• the point of crossing an airway.

Note: If the flight plan is submitted for the purpose of obtaining ATC service, the aircraft is required to wait for an ATC clearance prior to proceed under the conditions requiring compliance with ATC procedures.

1.4.1   General

A form based of the model shown in § 3 below shall be used for the purpose of completing flight plans. If the flight plan is transmitted by FAX, a special model shall be used. This model can be obtained from EBBR or ELLX ARO.

Whatever the purpose for which it is submitted, a flight plan shall contain information, as applicable, on the items listed up to § 1.4.9 below, regarding the whole route or the portion thereof for which the flight plan is submitted. It shall contain in addition, as applicable, information as listed in § 1.4.10 below, when submitted to facilitate the provision of alerting and SAR services or prior to departure for an IFR flight.

When filling in a flight plan, pilots shall:

• Adhere closely to the prescribed formats and manner of specifying data;
• Commence inserting data in the first space provided. Where excess space is available, leave unused spaces blank;
• Insert all clock times in 4 figures UTC;
• Insert all estimated elapsed times in 4 figures (HR and MIN);
• Complete items 7 to 18 as indicated hereunder;
• Complete also item 19 as indicated hereunder, when so required by the appropriate ATS authority or when otherwise deemed necessary.

Note 1: Item numbers on the form are not consecutive, as they respond to Field Type numbers in ATS messages.

Note 2: The fields preceding item 3 are to be completed by ATS and COM services, unless the responsibility for originating flight plan messages has been delegated

1.4.2   Item 7: Aircraft Identification (MAX 7 characters)

Insert one of the following aircraft identifications, not exceeding 7 alphanumeric characters and without hyphens or symbols:

1. the ICAO designator for the aircraft operating agency followed by the flight identification (e.g. “BEL511”, “NGA213”), when in RTF the call sign of the aircraft will consist of the ICAO telephony designator for the operating agency followed by the flight identification (e.g. “BEELINE 511”, “NIGERIA 213”,...). In this case, the registration marking of the aircraft shall be specified in Item 18, preceded by “REG/”;
2. the nationality or common mark and the registration mark of the aircraft (e.g. “EIAKO”, “4XBCD”, “OOSDE”, “N2567GA”), when:
   • in RTF the call sign to be used by the aircraft will consist of this identification alone (e.g. “OOSDE”), or preceded by the ICAO telephony designator for the aircraft operating agency (e.g. “BEELINE OOSDE”). in this case the name of the operator shall be specified in item 18, preceded by “OPR/”;
   • the aircraft is not equipped with radio.

Note: Provisions for the use of RTF call signs are contained in chapter 5 of ICAO Annex 10, Volume II. ICAO designators for aircraft operating agencies are contained in ICAO Doc 8585.

1.4.3   Item 8: Flight Rules and Type of Flight (1 or 2 characters)

1.4.4   Item 9: Number and Type of Aircraft and Wake Turbulence Category

Insert the number of aircraft, if more than one.

Insert the appropriate designator as specified in ICAO Doc 8643. If no such designator has been assigned, or in case of formation flights comprising more than one type, insert “ZZZZ” and specify the (numbers and) type(s) of aircraft in item 18, preceded by “TYP/”.

Insert an oblique stroke followed by one of the following letters to indicate the wake turbulence category of the aircraft:

1.4.5   Item 10: Equipment and Capabilities

Capabilities comprise the following elements:

• presence of relevant serviceable equipment on board the aircraft;
• equipment and capabilities commensurate with flight crew qualifications; and
• where applicable, authorization from the appropriate authority.

Otherwise, any or more of the following letters shall be inserted:

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. 8.33 KHZ channel spacing capability of VHF equipment shall be indicated separately by adding the letter Y.

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

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

Note 4: If the letter R is used, the performance based navigation levels that can be met shall be specified 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 Manual (ICAO Doc 9613).

Note 5: If the letter Z is used, the other equipment carried or other capabilities shall be specified in item 18, preceded by “COM/”, “NAV/” and/or “DAT/”, as appropriate. Exemptions for RNAV, CPDLC and 8.33 KHZ are to be indicated by inserting the letter Z in item 10a and then inserting the appropriate descriptors in the following indicators in item 18 (“NAV/RNAVX”, “NAV/RNAVINOP”,“DAT/CPDLCX” or “COM/EXM833”).

Note 6: Operators of aircraft approved for P-RNAV, relying solely on VOR/DME for determination of position, shall insert the letter Z in item 10a and the descriptor “NAV/EURPRNAV” in item 18.

Note 7: Information on navigation capability is provided to ATC for clearance and routing purposes.

Insert N if no surveillance equipment for the route to be flown is carried or the equipment is unserviceable, or insert one or more of the following descriptors, to a maximum of 20 characters, to describe the serviceable surveillance equipment and/or capabilities on board:

(*) Enhanced surveillance capability is the ability of the aircraft to down-link aircraft derived data via Mode S transponder.

Note: Additional surveillance applications and capabilities should be listed in Item 18 following the indicator “SUR/”.

1.4.6   Item 13: Departure Aerodrome and Time (8 characters)

Insert the ICAO location indicator of the departure aerodrome. If no location indicator has been assigned, insert “ZZZZ” and specify the name and location of the aerodrome in item 18, preceded by “DEP/”.

If the aircraft has not taken off from an aerodrome, insert “ZZZZ” and specify the first point of the route or the marker beacon in item 18, preceded by “DEP/”.

If the flight plan is received from an aircraft in flight, insert “AFIL” and specify the ICAO location indicator of the ATS unit from which supplementary flight plan data can be obtained in item 18, preceded by “DEP/”.

Then, without a space, insert for a flight plan submitted before departure, the EOBT, or, for a flight plan received from an aircraft in flight, the actual or estimated time over the first point of the route to which the flight plan applies.

1.4.7   Item 15: Route

Insert the first cruising speed as in § 1.4.7.1 and the first cruising level as in § 1.4.7.2, without a space between them. Then, following the arrow, insert the route description as in § 1.4.7.3.

1.4.8   Item 16: Destination Aerodrome, Total Estimated Elapsed Time and Alternate Destination Aerodrome(s)

Insert the ICAO location indicator of the destination aerodrome followed, without a space, by the total estimated elapsed time, or, if no location indicator has been assigned, insert “ZZZZ” followed, without a space, by the total estimated elapsed time, and specify the name and location of the aerodrome in item 18, as indicated below (§ 1.4.9).

Note: For a flight plan received from an aircraft in flight, the total estimated elapsed time is the estimated time from the first point of the route to which the flight plan applies to the termination point of the flight plan.

Insert the ICAO location indicator(s) of not more than two alternate destination aerodromes, separated by a space, or, if no location indicator has been assigned to the alternate aerodrome, insert “ZZZZ” and specify the name and location of the alternate aerodrome in item 18, as indicated below (§ 1.4.9).

1.4.9   Item 18: Other Information

Operators are warned that the use of indicators not included in the provisions may result in data being rejected, processed incorrectly or lost.

Only indicators described in the provisions may be used, and they must be inserted in the order shown. The indicators defined are as follows, and are listed in the order in which they are to be inserted, if used:

Note 4: According to ICAO Annex 11, an ATS unit will, when practicable, inform the aircraft operator when an alerting service is provided to an aircraft. In order to facilitate quick and effective coordination, it is advisable to provide in the flight plan (item 18 ‘Other information’) information sufficient to enable the ATS unit to contact the on-duty staff of the aircraft operator if such information has not been provided to the ATS unit by other means.

STS/
Reason for special handling by ATS, e.g. a search and rescue mission, as follows:

Note: Other reasons for special handling by ATS shall be denoted under the designator “RMK/”

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, i.e. a total of not more than 16 characters.

Note 1: Operators of aircraft approved for B-RNAV shall indicate the availability of capabilities relevant to RNAV 5. It is not necessary to insert additional information to indicate the aircraft is approved for B-RNAV.

Note 2: Operators of aircraft approved for P-RNAV, not relying solely on VOR/DME for determination of position, shall indicate the availability of capabilities relevant to RNAV 1. It is not necessary to insert additional information to indicate the aircraft is approved for P-RNAV.

NAV/
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”. If appropriate, insert “RNAVX” or “RNAVINOP” as described in the IFPS Users Manual, or “EURPRNAV” as described in chapter 2 of EUR SUPPS, ICAO Doc 7030.

COM/
Indicate communications applications or capabilities not specified in item 10a. If appropriate, insert “EXM833” as described in chapter 2 of EUR SUPPS, ICAO Doc 7030.

DAT/
Indicate data applications or capabilities not specified in item 10a. If appropriate, insert “CPDLCX” as described in chapter 2 of EUR SUPPS, ICAO Doc 7030.

SUR/
Include surveillance applications or capabilities not specified by item 10b.

DEP/
Name and location of departure aerodrome, if “ZZZZ” is inserted in item 13, or the ICAO location indicator of the location of the ATS unit from which supplementary flight plan data can be obtained, if “AFIL” is inserted in item 13. For aerodromes not listed in the relevant AIP, indicate location in any of the following ways:

• With four figures describing latitude in degrees and tens and units of minutes, followed by “N” (north) or “S” (south), followed by five figures describing longitude in degrees and tens and units of minutes, followed by “E” (east) or “W” (west). Make up the correct number of figures, where necessary, by insertion of zeros, e.g. “4620N07805W” (11characters);
• Bearing and distance from the nearest significant point, as follows: the identification of the significant point followed by the bearing from the point in the form three figures giving degrees (MAG), then the distance from the point in the form of three figures expressing nautical miles. In areas of high latitude where it is determined by the appropriate authority that reference to degrees magnetic is impractical, degrees true may be used. Make up the correct number of figures, where necessary, by insertion of zeros (e.g. a point 180° MAG at a distance of 40 NM from VOR “DUB” should be expressed as “DUB180040”;
• The first point of the route (name or LAT/LONG) or the marker radio beacon, if the aircraft has not taken off from an aerodrome.

DEST/
Name and location of destination aerodrome, if “ZZZZ” is inserted in item 16. For aerodromes not listed in the relevant AIP, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described under “DEP/” above.

DOF/
Date of flight departure in a six figure format (YYMMDD where: YY = year; MM = month; DD = day).

REG/
The nationality or common mark and registration mark of the aircraft, if different from the aircraft identification in item 7.

EET/
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 (e.g. “EET/CAP0745 XYZ0830”, “EET/EINN0204”).

SEL/
SELCAL code, for aircraft so equipped.

TYP/
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 (e.g. “TYP/2F15 5F5 3B2”).

CODE/
Aircraft address (expressed in the form of an alphanumerical code of six hexadecimal characters) when required by the appropriate ATS authority (e.g. “F00001” is the lowest aircraft address contained in the specific block administered by ICAO).

RVR/
The minimum RVR requirement of the flight, as detailed in the EUR SUPPS, ICAO Doc 7030.

DLE/
In case of en route 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) (e.g. “DLE/MDG0030”).

OPR/
ICAO designator or name of the aircraft operating agency, if different from the aircraft identification in item 7.

ORGN/
The originator’s eight 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.

Note: In some areas, flight plan reception centres may insert the “ORGN/” identifier and originator’s AFTN address automatically.

PER/
Aircraft performance data, indicated by a single letter as specified in ICAO Doc 8168, Volume I, if so prescribed by the appropriate ATS authority.

ALTN/
Name of destination alternate aerodrome(s), if “ZZZZ” is inserted in item 16. For aerodromes not listed in the relevant AIP, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in “DEP/” above.

RALT/
ICAO four letter indicator(s) for en-route alternate(s), as specified in ICAO Doc 7910, or name(s) of en-route alternate aerodrome(s), if no indicator is allocated. For aerodromes not listed in the relevant AIP, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in “DEP/” above.

TALT/
ICAO four letter indicator(s) for take-off alternate, as specified in ICAO Doc 7910, Location Indicators, or name of take-off alternate aerodrome, if no indicator is allocated. For aerodromes not listed in the relevant AIP, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in “DEP/” above.

RIF/
The route details to the revised destination aerodrome, followed by the ICAO four-letter location indicator of the aerodrome. The revised route is subject to re-clearance in flight (e.g. “RIF/DTA HEC KLAX”, “RIF/ESP G94 CLA YPPH”).

RMK/
Any other plain language remarks when required by the appropriate ATS authority or deemed necessary.

RFP/
Q followed by a digit to indicate the sequence of the replacement flight plan being submitted, see ENR 1.9, § 5.3.

STAYINFOn/
Indication of the reason for the insertion of a STAY indicator in item 15 (see § 1.4.7 above). Insert “STAYINFO” followed by the sequence number of the STAY indicator, an oblique stroke and an explanation in free text (e.g. “STAYINFO1/CALIBRATION OF SOG”).

1.4.10   Item 19: Supplementary Information

Note: In the paper flight plan form, an indicator is crossed out to denote that it is not available, in the digital flight plan form however, a mark is placed at the emergency and survival equipment that is available.

After “E/” insert a 4-figure group giving the fuel endurance in HR and MIN.

After “P/” insert the total number of persons (passengers and crew) on board.

insert “TBN” (to be notified) if the total number of persons is not known at the time of filing.

“R/” (RADIO)

• cross out “U” if UHF on FREQ 243.000 MHZ is not available;
• cross out “V” if VHF on FREQ 121.500 MHZ is not available;
• cross out “E” if emergency location beacon-aircraft (ELBA) is not available.

“S/” (SURVIVAL EQUIPMENT)

• cross out “P” if polar survival equipment is not carried;
• cross out “D” if desert survival equipment is not carried;
• cross out “M” if maritime survival equipment is not carried;
• cross out “J” if jungle survival equipment is not carried.

“J/” (JACKETS)

• cross out “J” if life jackets are not carried;
• cross out “L” if life jackets are not equipped with lights;
• cross out “F” if life jackets are not equipped with fluorescein;
• cross out “U” or “V” or both as in “R/” above to indicate radio capability of jackets, if any.

“D/” (DINGHIES)

• (Number): cross out “D” and “C” if no dinghies are carried, or insert number of dinghies carried;
• (Capacity): insert total capacity, in persons, of all dinghies carried;
• (Cover): cross out “C” if dinghies are not covered;
• (Colour): insert colour of dinghies if carried.

“A/” (AIRCRAFT COLOUR AND MARKINGS)

• insert colour of aircraft and significant markings.

“N/” (REMARKS)

• cross out “N” if no remarks, or indicate any other survival equipment carried and any other remarks regarding survival equipment.

“C/” (PILOT)

• insert name of pilot-in-command.

“Filed by”: insert the name of the unit, agency or person filing the flight plan.

2.2.1   Delay of Flight Plan Submission

• GAT or mixed OAT/GAT (subject to ATFM measures): at least 3 HR before EOBT/ETD;
• Other flights (except night flights): at least 60 MIN prior ETD;
• OAT night flights conducted entirely or partially in class G airspace: before 1100 of the same day;
• OAT night flights conducted entirely in controlled airspace (class C and D): at least 60 MIN prior ETD;
• Flights to foreign FIR/UIR: according to foreign national regulations.

Note: Reservation of airspace by foreign Mil aircraft: see ENR 5.2, § 1.3

In the event of a delay of 30 MIN in excess of the EOBT for a flight for which a flight plan has been submitted, the flight plan shall be amended or a new flight plan should be submitted and the old one should be cancelled. See ENR 1.9, § 5.2 for the specifications in reference to FPL which are subject to ATFM measures.

2.3.1   Insertion of ATS Data

Complete items 7 to 19 as indicated hereunder. Item numbers on the form are not consecutive, as they respond to Field Type numbers in ATS messages.

If a flight plan for a flight conducted wholly in the EUR Region is filed more than 24 HR in advance of the EOBT, it is mandatory to provide the date of the flight. This information will be indicated in the item 18 of the flight plan in the form of a 3-letter indicator (DOF) followed by an oblique stroke and the date of the flight in a 6-figure group format: DOF/YYMMDD (YY = year; MM = month; DD = day). These flight plans shall be processed and transmitted without being held in abeyance.

Note: Air traffic services data systems may impose communications or processing constraints on information in filed flight plans. Possible constraints may, for example, be limits with regard to item length, number of elements in the route item or total flight plan length. Significant constraints are documented in the relevant Aeronautical Information Publication.

Note: Enhanced surveillance capability is the ability of the aircraft to down-link aircraft derived data via a Mode S transponder.

ADS-B:

• B1 - ADS-B with dedicated 1090 MHz ADS-B “out” capability
• B2 - ADS-B with dedicated 1090 MHz ADS-B “out” and “in” capability
• U1 - ADS-B “out” capability using UAT
• U2 - ADS-B “out” and “in” capability using UAT
• V1 - ADS-B “out” capability using VDL Mode 4
• V2 - ADS-B “out” and “in” capability using VDL Mode 4

ADS-C:

• D1 - ADS-Cwith FANS 1/A capabilities
• G1 - ADS-C with ATN capabilities

Alphanumeric characters not indicated above are reserved.

Example: ADE3RV/HB2U2V2G1

Note: Additional surveillance application should be listed in Item 18 following the indicator SUR/.

Remarks:

What is entered at Item 7 before the slash ‘/’ (aircraft identifications) match exactly what is entered in the Mode S aircraft Identification (also known as Flight ID) input device in the cockpit. If it does not, then the aircraft will not be correlated with its stored FPL and delays will ensue.

There must be no spaces between the designator letters and flight number, nor any zeros preceding the flight number.

• ALTRV - a flight operated in accordance with an altitude reservation;
• ATFMX - For a flight approved for exemption from ATFM measures by the appropriate ATS authority;
• FFR - Fire fighting;
• FLTCK - Flight check for calibration of navaids;
• HAZMAT - For a flight carrying hazardous material;
• HEAD - A flight with Head of State status;
• HOSP - For a medical flight declared by medical authorities;
• HUM - For a flight operating on a humanitarian mission;
• MARSA - For a flight for which a military entity assumes responsibility for separation of MIL aircraft;
• MEDEVAC - For a life critical medical emergency evacuation;
• NONRVSM - For a non-RVSM capable flight intending to operate in RVSM airspace;
• SAR - For a flight engaged in a search and rescue mission;
• STATE - For a flight engaged in military, customs or police services.

Other reasons for special handling by ATS shall be denoted under the designator RMK/.

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, i.e. a total of not more than 16 characters.

Combinations of alphanumeric characters not indicated above are reserved.If any of the indicators B1, B2, C1, C2, D1, D2, O1 or O2 are filed, then a ‘G’ must be present in Field 10a.If any of the indicators B1, B3, C1, C3, D1, D3, O1 or O3 are filed, then a ‘D’ must be present in Field 10a.If either of the indicators B1 or B4 is filed, then either an ‘O’ or ‘S’ must be present and a ‘D’ must also be present in Field 10a.If any of the indicators B1, B5, C1, C4, D1, D4, O1 or O4 are filed, then an ‘I’ must be present in Field 10a.If any of the indicators C1, C4, D1, D4, O1 or O4 are filed, then a ‘D’ must be present in Field 10a.

NAV/
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.

COM/
Indicate communications applications or capabilities not specified in Field 10a.

Example:
“COM/EXM833”

DAT/
Indicate data applications or capabilities not specified in Field 10a.

Example:
“DAT/CPDLCX”

SUR/
Include surveillance applications or capabilities not specified in Field 10b.

DEP/
Name and location of departure aerodrome, if ZZZZ is inserted in Item 13, or the ATS unit from which supplementary flight plan data can be obtained, if AFIL is inserted in Item 13. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location as follows: With 4 figures describing latitude in degrees and tens and units of minutes followed by “N” (North) or “S” (South), followed by 5 figures describing longitude in degrees and tens and units of minutes, followed by “E” (East) or “W” (West). Make up the correct number of figures, where necessary, by insertion of zeros, e.g.4620N07805W (11 characters).

Or,
Bearing and distance from the nearest significant point, as follows:The identification of the significant point followed by the bearing from the point in the form of 3 figures giving degrees magnetic, followed by the distance from the point in the form of 3 figures expressing nautical miles. In areas of high latitude where it is determined by the appropriate authority that reference to degrees magnetic is impractical, degrees true may be used. Make up the correct number of figures, where necessary, by insertion of zeros, e.g. a point of 180° magnetic at a distance of 40 nautical miles from VOR “DUB” should be expressed as DUB180040.

Or,
The first point of the route (name or LAT/LONG) or the marker radio beacon, if the aircraft has not taken off from an aerodrome.

DEST/
Name and location of destination aerodrome, if ZZZZ is inserted in Item 16. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described under DEP/ above.

DOF/
The date of flight departure in a six-figure format (YYMMDD, where YY equals the year, MM equals the month and DD equals the day).

REG/
The nationality or common mark and registration mark of the aircraft, if different from the aircraft identification in Item 7 (50 characters maximum).

EET/
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”
“EET/EINN0204”

SEL/
SELCAL Code, for aircraft so equipped.

TYP/
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”

CODE/
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.”

DLE/
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).

Example:
“DLE/MDG0030”

OPR/
ICAO designator or name of the aircraft operating agency, if different from the aircraft identification in item 7.

ORGN/
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.

Note 1: In some areas, flight plan reception centres may insert the ORGN/ identifier and originator’s AFTN address automatically.

Note 2: Check the EUROCONTROL Basic CFMU Handbook – IFPS Manual for further instructions.

PER/
Aircraft performance data, indicated by a single letter (A, B, C, D, E or H) as specified in the Procedures for Air Navigation Services — Aircraft Operations (PANS-OPS, Doc 8168), Volume I — Flight Procedures, if so prescribed by the appropriate ATS authority.

ALTN/
Name of destination alternate aerodrome(s), if ZZZZ is inserted in Item 16. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in DEP/ above.

RALT/
ICAO four letter indicator(s) for en-route alternate(s), as specified in Doc 7910, Location Indicators, or name(s) of en-route alternate aerodrome(s), if no indicator is allocated. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in DEP/ above.

TALT/
ICAO four letter indicator(s) for take-off alternate, as specified in Doc 7910, Location Indicators, or name of take-off alternate aerodrome, if no indicator is allocated. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in DEP/ above.

RIF/
The route details to the revised destination aerodrome, followed by the ICAO four-letter location indicator of the aerodrome. The revised route is subject to re-clearance in flight.

Examples:
“RIF/DTA HEC KLAX”
“RIF/ESP G94 CLA YPPH”

RMK/
Any other plain-language remarks when required by the appropriate ATS authority or deemed necessary.

Note: RMK/IFPSRA (IFPS reroute accepted) is used where route definition help is sought. Check the EUROCONTROL Basic CFMU Handbook – IFPS Manual for further instructions.

STAYINFOn/
It shall be possible to indicate the reason for the STAY in the item 15 of the flight plan; for this purpose the sub-field heading ‘STAYINFOn’ shall be used, immediately followed by a ‘/’, then free alphanumeric text.

Example:
“Item 15: Route ….WAL STAY1/0100 WAL…. ”
“Item 18: Other Information STAYINFO1/CALIBRATION OF WAL”

2.3.2   Acceptance of the Flight Plan

Indicate acceptance of the flight plan in the manner prescribed by the appropriate ATS authority.

2.3.3   Insertion of Data

Complete the FPL form.

Complete Item 19 (Supplementary information (not to be transmitted in FPL messages)) only when necessary; in accordance with the provisions in PANS-ATM, chapter 11, 11.2.1.2, unless ATS prescribes otherwise.

2.4.1   Correction

Unless otherwise prescribed, correct obvious format errors and/or omissions (i.e. oblique strokes) to ensure adherence as specified in § 2.3.

2.4.2   Items to be transmitted

Transmit items as indicated hereunder, unless otherwise prescribed:

1. The items in the shaded lines, above item 3

2. Starting with “<<= (FPL” in item 3:

   • all symbols and data in the unshaded boxes down to “) <<=” at the end of item 18
   • additional alignment functions as necessary to prevent the inclusion of more than 69 characters in any line of items 15 or 18. The alignment function is to be inserted only in lieu of a space so as not to break up a group of data
   • letter shifts and figure shifts (not pre-printed on the form) as necessary

3. The AFTN ending, as described below:

4. • End-of-text signal:

     1. one letter shift
     2. two carriage returns, one line feed
   • Page-feed sequence: seven line feeds
   • End-of-message signal: four of the letter N