3.5 EQUIPMENT AND CAPABILITIES – ITEM 10
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.
The radio communication equipment, radio navigation equipment, approach aid equipment and capabilities and surveillance equipment shall be indicated.
3.5.1 The radio communication, radio navigation, approach aid equipment and capabilities - Item 10a
The radio communication, radio navigation, approach aid equipment and capabilities in message shall contain appropriate designator letter or letter/number combination with a maximum of 64 (sixty four) characters without repetition, followed by a “/”.
Radio communication, radio navigation, approach aid equipment and capabilities shall be indicated:
S if standard equipment (
VHF RTF,
VOR and
ILS) is carried and serviceable
N if no equipment is carried or the equipment is unserviceable
S and one or more of the following letters according to the equipment available and serviceable:
A -
GBAS landing system;
B -
LPVAPV with
SBAS;
C - LORAN C;
D -
DME;
E1 - FMC WPR
ACARS;
E2 -
D-FIS ACARS;
E3 - PDC
ACARS;
F -
ADF;
G -
GNSS.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;
H -
HF RTF;
I - Inertial Navigation;
J1 -
CPDLC ATN VDL Mode 2;
J2 -
CPDLC FANS 1/A
HFDL;
J3 -
CPDLC FANS1/A VDL Mode 4;
J4 -
CPDLC FANS 1/A VDL Mode 2;
J5 -
CPDLC FANS 1/A
SATCOM (INMARSAT);
J6 -
CPDLC FANS 1/A
SATCOM (MTSAT);
J7 -
CPDLC FANS 1/A
SATCOM (IRIDIUM);
K -
MLS;
L -
ILS;
M1 -
ATC SATVOICE (INMARSAT);
M2 -
ATC SATVOICE (MTSAT);
M3 -
ATC SATVOICE (IRIDIUM);
O -
VOR;
P1 - CPDLC RCP 400 (see Note 1)
P2 - CPDLC RCP 240 (see Note 1)
P3 - SATVOICE RCP 400 (see Note 1)
P4-P9 - Reserved for
RCP;
R -
PBN approved.
If the letter R is used, the performance based navigation levels that can be met shall be specified in Item 18 under “PBN/”;
T - TACAN;
U -
UHF RTF;
V -
VHF RTF;
W - RVSM approved;
X -
MNPS approved;
Y -
VHF with 8.33
KHZ channel spacing capability;
Z - Other equipment carried (whenever Z is being used in the equipment indicator of that flight plan, a specification shall be made by inserting the sub-field COM/ and/or NAV/ and/or DAT/of the flight plan to indicate the type of COM/ and/or NAV/ and/or DAT/ used for this flight).
Note 1: IP1, P2, P3: Guidance material 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 (ICAO Doc 9869).
3.5.1.1 Area Navigation (RNAV) Specifications
Operators of aircraft approved for basic area navigation (B-RNAV/
RNAV 5) operations shall insert the designator “
R” in Item 10a of the flight plan and “
PBN/” in Item 18 followed by the appropriate capability of that flight. The
PBN descriptors for B-RNAV are:
B1, B2, B3, B4, B5.
Operators of aircraft approved for precision area navigation (P-RNAV/RNAV 1) operations shall, in addition to the designator “
R” in Item 10a, also insert “
PBN/” in Item 18 followed by the appropriate capability of that flight. The descriptors for P-RNAV are:
O1, O2, O3, O4, D1, D2, D3, D4. It is also possible to indicate the P-RNAV capability by inserting “Z” in item 10a and “NAV/P-RNAV” in item 18.depending upon the sensors used, as appropriate unlike RNAV1 it is also possible to achieve P-RNAV capability using only VOR/DME in which case ‘Z’ should be inserted in item 10a and NAV/EURPRNAV in item 18.Operators of State aircraft not approved for B-RNAV or P-RNAV operations shall not insert any of the designators B1, B2, B3, B4, B5, D1, D2, D3, D4 within the PBN/ indicator of Item 18 of the flight plan. Instead, the letter ‘Z’ shall be inserted in Item 10a and NAV/RNAVX shall be inserted in Item 18 of the flight plan.
Where a failure or degradation results in the aircraft being unable to meet the B-RNAV functionality and accuracy requirements before departure, the operator of the aircraft shall not insert any of the designators B1, B2, B3, B4, B5 within the PBN/ indicator of Item 18 of the flight plan. Since such flights require special handling by ATC, the letter ‘Z’ shall be inserted in Item 10a and Item 18 shall contain NAV/RNAVINOP.
Note 1: 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.
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:
- insert EXM833 following “COM/“;
- insert RNAVX or RNAVINOP as appropriate following “NAV/“;
- insert CPDLCX following “DAT/”.
3.5.2 Surveillance Equipment and Capabilities – Item 10b
A minimum of 1 (one) and a maximum of 20 (twenty) characters shall be used to indicate the serviceable surveillance equipment in the equipment field of that flight plan.
To indicate the surveillance equipment and capabilities, insert:
N If no surveillance equipment for the route to be flown is carried, or the equipment is unserviceable or, one or more of the following descriptors:
A Transponder - Mode A (4 digits - 4 096 codes)
C Transponder - Mode A (4 digits - 4 096 codes) and Mode C
E Transponder - Mode S, including aircraft identification, pressure-altitude and extended squitter (ADS-B) capability
H Transponder - Mode S, including aircraft identification, pressure-altitude and enhanced surveillance capability
I Transponder - Mode S, including aircraft identification transmission, but no pressure-altitude capability
L Transponder - Mode S, including aircraft identification, pressure-altitude, extended squitter (ADS-B) and enhanced surveillance capability
P Transponder - Mode S, including pressure-altitude, but no aircraft identification capability
S Transponder - Mode S, including both pressure altitude and aircraft identification capability
X Transponder - Mode S with neither aircraft identification nor pressure- altitude capability
Note 1: I, P, X are mutually exclusive, i.e. only one of the 3 indicators may be present plus optionally one or more of the descriptors (ADS-B and ADS-C descriptors are optional and cannot be present without any transponder descriptor(s)):
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
D1 ADS-C with
FANS 1/A capabilities
G1 ADS-C with ATN capabilities
Additional surveillance application should be listed in Item 18 following the indicator “SUR/“
3.9 OTHER INFORMATION – ITEM 18
As far as supplementary information with regard to Items 7 to 16 or other additional information becomes necessary, it shall be indicated by using the following identification groups in Item 18.
If no other information, zero (“0“) shall be used.If no other information, zero (“0“) shall be used.
ALTN/ Name of destination alternate aerodrome(s). The IFPS shall accept approved ICAO aerodrome designators in Item 16: Alternate Aerodrome, of a flight plan or associated message. Where an aerodrome does not have such a designator, or the designator is not known, the message originator shall insert ‘ZZZZ’ in Item 16c and include the sub-field ALTN in Item 18. The sub-field ALTN shall indicate the name(s) and location(s) of the alternate aerodrome(s) of that flight.
CODE/ The sub-field CODE shall be used to indicate the unique 24-bit aircraft address of the airframe for this aircraft. Flights planning to use CPDLC over the aeronautical telecommunication network (ATN) shall include in Item 18 of the flight plan the indicator CODE/ followed by the 24-bit aircraft address (expressed in the form of alphanumerical code of six hexadecimal characters).
COM/ Indicate communications applications or capabilities not specified in Item 10a data.
If appropriate, insert “EXM833” as detailed in IFPS User Manual. Where the sub-field COM is used in a message submitted to the IFPS for processing, the associated Item 10a should include a ‘Z’ to indicate that other applications or capabilities are carried. Example:
Item 18: Other Information: COM/INOPERABLE
Item 10: Equipment: Z
Only those flights where an aircraft is not equipped with 8.33 kHz capable radios but that are EXEMPTED from the carriage requirements shall use the sub-field COM/EXM833 indicator.
The sub-field shall be denoted with the letters COM followed by a ‘/’, and free text to a maximum of 50 alphanumeric characters.
DAT/ Indicate data applications or capabilities not specified in 10a. Where the sub-field DAT is used in a message submitted to the IFPS for processing, the associated Item 10a should include a ‘Z’ to indicate that other applications or capabilities are carried.
One of the applications of that field is to indicate Controller Pilot Data Link Communications (CPDLC) exemption for flights conducted wholly or partly in the EUR CPDLC airspace and not equipped with CPDLC capabilities.
Example:
Item 18: Other Information: DAT/CPDLCX
Item 10: Equipment: Z
The sub-field shall be denoted with the letters DAT followed by a ‘/’, and free text to a maximum of 50 characters.
DEP/ Name and location of departure aerodrome. The IFPS shall accept approved ICAO aerodrome designators in Item 13: Departure Aerodrome of a flight plan or associated message. Where an aerodrome does not have such a designator, or the designator is not known, the message originator shall insert ‘ZZZZ’ in Item 13 and include the sub-field DEP in Item 18. The sub-field DEP shall indicate the name and location of the departure aerodrome. The location can be indicated either as bearing and distance from a significant point or as latitude and longitude.
The sub-field shall be denoted by the letters DEP followed by a ‘/’, then free text to a maximum of 50 alphanumeric characters detailing the name and location of the departure aerodrome.
DEST/ Name and location of destination aerodrome., The IFPS shall accept approved ICAO aerodrome designators in Item 16: Destination Aerodrome of a flight plan or associated message. Where an aerodrome does not have such a designator, or the designator is not known, the message originator shall insert ‘ZZZZ’ in Item 16 and include the sub-field DEST in Item 18. The sub-field DEST shall indicate the name and location of the destination aerodrome.
The location can be indicated either as bearing and distance from a significant point or as latitude and longitude.
DLE/ Enroute delay or holding. Whenever along the flight path a delay is planned to occur at significant point the indication of that delay shall be present. The sub-field shall be denoted by the letters DLE followed by a ‘/’, then a significant point or a significant point with bearing and distance or geographical coordinates, followed by an indication of a time period in hours and minutes. If the en-route delay or holding takes place at more than one location, each location shall be separated by a space.
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).
EET/ Estimated elapsed times. The EETs given in the sub-field EET, shall indicate the significant point, FIR boundary designators or geographical co-ordinates, immediately followed by the EET over those points.
Where the EET point is a geographical co-ordinate, the IFPS shall accept several formats.
The geographical co-ordinate shall be expressed in 2 digits latitude and 3 digits longitude, or 4 digits latitude and 5 digits longitude. The EET point however, may also be expressed as only 2 digits latitude, or only 3 digits longitude.
Example:
EET/NTM0120 LOVV0210 56N010E0306 011E0309 57N0321
EUR/ European designator. The European designator (EUR) has been introduced by EUROCONTROL to satisfy specific needs for flight planning into the IFPZ.
The sub-field EUR shall be used to indicate:
Those flights for which the details should only be available to a restricted audience (e.g. a security sensitive flight). In this case the value of the sub-field shall be PROTECTED. Those flights shall not automatically qualify for exemption from flow regulations.
PROTECTED: The sub-field shall be denoted with the letters EUR followed by a ‘/’, followed by PROTECTED i.e
EUR/PROTECTED
or
Those military flights wholly or partly under OAT conditions where the OAT portion(s) is/are as iOAT. In this case the value of the sub-field shall be OAT. A military flight is determined by the flight type with the value M. An iOAT flight is determined by the presence of ‘OAT’ in the sub-field EUR. The EUR sub-field shall not contain values other than PROTECTED and OAT.
OAT: The sub-field shall be denoted with the letters EUR followed by a ‘/’, followed by OAT i.e. EUR/OAT. When both values apply to a flight it may be indicated either as EUR/PROTECTED OAT or EUR/PROTECTED EUR/OAT.
NAV/ Significant data related to navigation equipment of that aircraft, 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,. It shall also be used to indicate the GNSS augmentation, with a space between two or more methods of augmentation, e.g. NAV/GBAS SBAS. Where the sub-field NAV is used in a message submitted to the IFPS for processing, the associated Item 10a should include a ‘Z’ to indicate that other equipment/capability is carried. e.g.
NAV/
GBAS SBAS.
ORGN/ Originator indicator. In case the sub-field is submitted in a message for processing by IFPS, it shall be the 8 letter AFTN address or other appropriate contact details in case the originator of the flight plan may not be readily identified.
The following message types shall have the sub-field ORGN indicator automatically inserted by the IFPS during processing of that message:
- Flight Plan;
- Flight Plan submitted by ATC for an aircraft in flight with source AFIL;
- APL (ATC Plan as a result of an AFP, FNM or MFS);
- ACH (ATC Flight Plan Change for an aircraft in flight).
OPR/ Aircraft Operator of the aircraft
to which that flight plan relatesoperating agency, if different from the aircraft identification in Item 7. A maximum of one OPR code for each flight plan shall be accepted by the IFPS. The sub-field shall be denoted with the letters OPR followed by a ‘/’, then by the AO’s ICAO code or the AO’s full name as stored in the NM CACD.
PBN/ Performance Based Navigation. Whenever a flight plan contains the equipment ‘R’ (PBN approved) in the Item 10a, the Performance Based Navigation (PBN) and/or the Required Navigation Performance (RNP) levels than can be met shall be specified in the Item 18 following the indicator PBN. The sub-field shall be denoted by the letters PBN followed by a ‘/’, then from one to eight of the following descriptors:
B1 RNAV 5 all permitted sensors
B2 RNAV 5
GNSS B3 RNAV 5
DME/
DME B4 RNAV 5
VOR/
DME B5 RNAV 5 INS or IRS
B6 RNAV 5 LORANC
C1 RNAV 2 all permitted sensors
C2 RNAV 2
GNSS C3 RNAV 2
DME/
DME C4 RNAV 2
DME/
DME/IRU
D1 RNAV 1 all permitted sensors
D2 RNAV 1
GNSS D3 RNAV 1
DME/
DME D4 RNAV 1
DME/
DME/IRU
O1 Basic
RNP 1 all permitted sensors
O2 Basic
RNP 1
GNSS O3 Basic
RNP 1
DME/
DME O4 Basic
RNP 1
DME/
DME/IRU
S1 RNP APCH
S2 RNP APCH with BARO-VNAV
T1 RNP AR APCH with RF
T2 RNP AR APCH without RF
PER/ Aircraft performance data. The sub-field PER shall be used to one aircraft performance data whenever that information is necessary (if required by an ATS authority). The specifications can be found in the Procedures for Air Navigation Services - Aircraft Operations (PANS-OPS, Doc 8168), Volume I - Flight Procedures. aircraft performance data. The sub-field shall be denoted with the letters PER followed by indicate a ‘/’, then one letter. The letter may be: A, B, C, D, E or H.
e.g. rate of climb, ceiling
RALT/ En-route Alternate Aerodrome. Where a flight is required to indicate en-route alternate(s), that information shall be indicated in the sub-field RALT. It can be indicated either by the ICAO four letter location indicator(s) of the aerodrome(s) when it exits, or by the name(s) if no indicator is allocated. For aerodromes not listed in the relevant Aeronautical Information Publication (AIP), the location shall also be indicated (whenever possible) in latitude and longitude or in bearing and distance from the nearest significant point.
The sub-field shall be denoted by the letters RALT followed by a ‘/’, then free text to a maximum of 100 alphanumeric characters detailing the en-route alternate aerodrome(s).
REG/ Aircraft Registration. The IFPS shall accept the sub-field REG to indicate the registration markings of the aircraft, whenever necessary and if different from the aircraft identification.
Where possible, the aircraft registration should be submitted to the IFPS, and where an aircraft change is made for that flight, the registration should be updated accordingly.
For operators of RVSM-approved aircraft, it is mandatory to insert the aircraft registration in Item 18 of the ICAO flight plan form.
The sub-field shall be denoted with the letters REG followed by a ‘/’, then the registration details of the aircraft(s), if different from the aircraft identification, with a maximum of 50 characters. Where the message concerns a formation flight, the registrations of the aircraft may be specified under one unique REG/ sub-field and separated by a space.
RFP/ Replacement Flight Plan. RFP/Qn followed by a digit (1-9) shall be used to indicate where a
n alternative routing is filed in a new flight plan during the pre-flight stage (within four hours of estimated off-blocks time).
RIF/ Re-Clearance in Flight. The route details to the revised destination aerodrome, following by the
ICAO four-letter location indicator
(code) of for that revised thedestination aerodrome.
The revised route is subject to re-clearance in flight.
Examples:
RIF/
DCT LQBK
RIF/
VEBAR L5 KEB LQSA
RMK/ Remarks. The sub-field RMK shall be used to indicate any plain language remarks required by the appropriate ATS authority or deemed necessary by the pilot-in-command for the provision of air traffic services. The character ‘/’ shall not be used in the RMK sub-field other than following the RMK. Also the character’-’ shall not be used in the free text of the sub-field RMK as it may happen that the IFPS disregards all information after the ‘/’ and/or ‘–‘and valid information for that flight might get lost or that the IFPS reads that information as Item 19 elements.
The sub-field shall be denoted with the three letters RMK followed by a ‘/’ and then free text. The RMK sub-field shall have no limit to the number of characters other than the maximum number of characters possible for the entire message (2100).
Example:
RMK/DIP CLEARANCE 410 23 5486
Special characters such as: ( ) ^ % $ # / - @ which are not allowed.
RVR/ Runway Visual Range. The minimum RVR requirement of the flight (in metres); All IFR/GAT flights or parts thereof intending to operate within the IFPZ are recommended to include in the flight plan the landing Runway Visual Range (RVR) capabilities of that flight. Landing RVR information may be used for flow management during low visibility conditions (full details are available in the ATFCM Users Manual).Note: This provision is detailed in the European Regional Supplementary Procedures (EUR SUPPs, Doc.7030), Chapter 2. SEL/ SELCAL code
; forof the aircraft
so equipped to which the flight plan relates. A maximum of one SELCAL code for each flight plan shall be accepted by the IFPS. STAYINFOn/ describes the type of the special planned flight listed in Item 15 with a STAY Indicator, “n” being the sequence number 1 to 9 of the STAY Indicators; The sub-field STAYINFO, followed by the appropriate sequence number (i.e. STAYINFOn) shall be inserted in the flight plan to provide information on those STAY indicators detailed in the route. The information provided is essential for ATC.
The sequence number of the sub-field STAYINFO shall correspond to the sequence number of the STAY indicator detailed in the route.
The sub-field shall be denoted with the letters STAYINFO followed by a sequence number ranging from 1 to 9 as appropriate, then ‘/’, followed by free text.
Example:
DOF/230513 PBN/B1D1 REG/FGFVO STAYINFO1/PHOTOGRAPHIC MISSION OVER LAKE
STS/ Reasons for special handling by
ATC. The following information only is permitted when making
STS/ entries:
for a flight operated in accordance with an altitude reservation;
for a flight approved for exemption from
ATFM measures by the appropriate
ATS authority;
FFR flights engaged in fire
-fighting;
flights performing flight check for calibration of navaids;
for a flight carrying hazardous material;
for a flight with Head of State status;
for a medical flight declared by medical authorities;
for a flight operating on a humanitarian mission;
for a flight for which a military entity assumes responsibility for separation of military aircraft;
MEDEVAC for a life critical medical emergency evacuation;
for a non-
RVSM capable flight intending to operate in
RVSM airspace;
SAR for a flight engaged in a search and rescue mission; and
STATE for a
military or civil registered aircraft used flight engaged in military, customs or police services.
By using this Item 18 sub-field STS/ATFMX, STS/FFR, STS/HEAD, STS/MEDEVAC and STS/SAR indicators the flight shall automatically be exempted from any relevant flow regulations.
Other reason for special handling by
ATS shall be denoted under the designator
RMK/.
Where multiple
STS indicators are necessary it shall be specified under 1(one)
STS/ header and separated by a space.
e.g.
STS/STATE
ATFMX SUR/ Include surveillance applications or capabilities not specified in Item 10b.
TALT/ Take-off Alternate. ICAO four letter indicator(s) for take-off alternate
aerodrome(s), 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 (
AIP), indicate location in
LAT/
LONG or bearing and distance from the nearest significant point
, as described in DEP/ above.
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. Where an aircraft does not have such a designator, or the aircraft type is not known, the message originator shall insert ‘ZZZZ’ in the flight plan or associated message. The message originator shall also then include the sub-field TYP that shall contain details of the aircraft type, preceded by the number of aircraft, as necessary. 3.10 SUPPLEMENTARY INFORMATION – ITEM 19
Supplementary information shall be given as follows:
E/ the total fuel endurance expressed by a 4 (four)-figure group indicating hours and minutes (HHMM);
P/ the total number of persons on board that flight. The sub-field shall be denoted with the letter P followed by a ‘/’ and then the number of persons on board that flight expressed in digits to a maximum of three (3).
R/ the available emergency radio capabilities, whereby:
-
U shall be crossed out if
UHF frequency 243.0
MHZ is not available;
-
V shall be crossed out if
VHF frequency 121.5
MHZ is not available;
-
E shall be crossed out if the emergency location beacon-aircraft (
ELTELBA) is not carried in the aircraft.
S/ the type of survival equipment carried, whereby:
- P shall be crossed out if polar survival equipment is not carried;
- D shall be crossed out if desert survival equipment is not carried;
- M shall be crossed out if maritime survival equipment is not carried;
- J shall be crossed out if jungle survival equipment is not carried.
J/ the type of life jackets carried, whereby:
- L shall be crossed out if life jackets are not equipped with lights;
- F shall be crossed out if life jackets are not equipped with fluorescent;
- U shall be crossed out if life jackets are not equipped with UHF on frequency 243.0 MHZ.according to the criteria under “R/ “;
- V shall be crossed out if life jackets are not equipped with VHF on frequency 121.500 MHZ.
D/ the number, capacity, type and colour of the dinghies carried, whereby:
- D and C shall be crossed out if no dinghies are carried;
- insert number of dinghies (2 numerics) carried;
- insert total capacity (3 numerics), in persons of all dinghies carried;
- C shall be crossed out if the dinghies are not covered;
- insert colour of dinghies if carried.
A/ the colour of the aircraft and significant markingsof the aircraft making that flight;
N/ N shall be cross out no remarks, or INDICATE any other survival equipment carried and any other useful remarks regarding survival equipment for that flight.
C/ name of pilot-in-command.
Name of the Flight Plan Originator - The name of the flight plan originator shall be given.
Space reserved for additional requirements - The flight plan originator should ensure that he can be reached in case of further enquiries and additional information until shortly prior to taking off, preferably by indicating a Phone number.