ENR 1.10  Flight planning

1  Procedures for the submission of a flight plan

1.1 Because of the great difficulties of Search and Rescue operations within Somalia, the pilot is strongly advised, regardless of his formal obligations, to file a Flight Plan for every flight. At aerodromes which are not manned by the Somalia Civil Aviation Authority (SCAA). The Flight Plan should be filed with ATS Reporting Officer, if established or the nearest ATS Unit by telephone or over the Radio (VHF or HF). In this way, the general intentions regarding the flight will be known, or will ultimately become available to Air traffic Services, and could be used as a basis for any Search operations that might become necessary.
1.2 A pilot MUST file a Flight Plan:
  1. If intending to fly in controlled airspace.
  2. If intending to fly an aircraft operating as a public transport aircraft under VFR or IFR.
  3. If wanting to fly across an international border.
  4. If departing from aerodromes manned by ANSP Somalia.
  5. If intending to fly in IFR.

Note:The Air Traffic Services Unit may, at their discretion, exempt the Commander of an aircraft in respect of an intended flight which is to be made in a local flying area within a radius of 30NM and in which the aircraft will return to the aerodrome of a departure without making an intermediate landing

2  How to File a Flight Plan
2.1 Flights from Aerodromes on the Aeronautical Fixed Telecommunication Network (AFTN)
2.1.1  Except when other arrangement have been made for submission of repetitive flight plans, the pilot should complete and sign the Flight Plan form (ICAO format) and submit it to the ATS Unit at the aerodrome. (By local arrangement at large aerodromes, the operator’s competent representative may file the Flight Plan on behalf of the pilot.).
2.1.2 Flight Plan should be filed at least 60 minutes before departure or at most 120 HRs before EOBT unless arrangement have been made for submission of a repetitive Flight Plan which shall be activated by providing supplementary information before departure.
2.2 Airborne Flight Plans
2.2.1 Where it has not been possible to file a flight plan on the ground, or where conditions make such an action necessary, a Flight Plan may be filed in the air with any ATS unit. Any desired operator’s address should be given by beginning with the words “I wish to file an airborne flight plan."
2.3 Acceptance of a Flight Plan
2.3.1 The first ARO receiving a Flight Plan, or change thereto, shall:
  1. Check it for compliance with the format and data conventions.
  2. Check it for completeness and, to the extent possible, for accuracy.
  3. Take action if necessary to make it acceptable to the Air Traffic Services, and change thereto, to the originator.
  4. Check it for compliance with the national requirement as entry flight clearance as required by the Civil Aviation Authority for the region where the airport is located.
2.4 Cancellation of IFR Flight Plan in Controlled Airspace
2.4.1 If a pilot has begun a flight in controlled airspace under IFR Flight Plan, he may decide that on entering VMC he will cancel, it must be emphasized, however, that a pilot cannot exercise this choice in a controlled airspace, if ICAO SARPs prohibit.
2.4.2 In a controlled airspace where the exercise of the pilot’s choice is still possible, pilots may cancel IFR Flight Plans by notifying the ATS Unit concerned, provided that they are then operating in VMC. An IFR Flight Plan may be cancelled by transmitting the following message: “............ identification) - cancel IFR Flight Plan”.
2.4.3 ATC cannot approve or disapprove cancellation of an IFR Flight Plan, but when in possession of information along the route of the flight, will advise the pilot accordingly in the following manner “IMC reported (or forecast) in relation to other IFR traffic.
2.4.4 The fact that a pilot reports that he is flying in VMC does not itself constitute cancellation of IFR Flight Plan and unless a definite cancellation of the IFR Flight Plan, the flight will continue to be regulated in relation to other IFR traffic.
3  Through Flight Plans
3.1 Through Flight Plans may only be filed where;
  1. In the course of the proposed flight, it is not intended that the aircraft will cross the boundary of Mogadishu Flight Information Region, and;
  2. Where the aerodromes of intended intermediate landing is/are not on the AFTN, and,
  3. Where the time spent on the ground at any intermediate place of landing is not expected to be in excess of 60 minutes.
3.2 When a through Flight Plan has been filed, the portion of the plan for each segment of the flight will be active for ATS purposes only when the appropriate ATS Unit has received a message announcing departure from the previous point of landing indicated in the Flight Plan.
3.3 If an ATS unit is established at the aerodrome of departure, the following information shall be passed to that unit before departure on each segment of the flight, except the first segment.
  1. Either: Confirmation of the relevant part of item 15 of the Flight Plan using the phrase “THRU PLAN VALID”; or amendment of the relevant part of item 15;
  2. Number of persons on board.
  3. Endurance.
3.4 If no ATS unit is established at the aerodrome of departure, a departure message including items (ii) and (iii) above shall be sent by radio to the ACC as soon as possible after departure.
4  Booking-out and Booking-in
4.1 Before making a flight, in a local flying area within a radius of 30 nm from an aerodrome manned by the SCAA, a pilot must notify the Air Traffic Service Unit of the intended flight and obtain exemption from the requirement of submitting a Flight Plan. The information thus given to the ATS Unit will not be sent to any other unit.
4.2 Where a “SARTIME” has been entered in Item ‘18' of a Flight Plan, the pilot is responsible for notifying his whereabouts at, or before, the time of expiry of the “SARTIME”, unless the flight to which the Flight Plan refers has already been completed and the Flight Plan closed with an Air Traffic Control Service Unit. Notification of arrival shall be made to the Reporting Officer where such exists or by any other means possible. If a radio-telephony report landing or imminent landing is acknowledged by an Air Traffic Service Unit, then no confirmatory message is required. A pilot must ensure before departure that communication links exist, and can be used, to notify arrivals before entering a “SARTIME” on the Flight Plan.
4.3 A pilot who has given notice of his intended arrival at any aerodrome is responsible whether or not a “SARTIME” has been included in the Flight Plan, for notifying the air Traffic Control Service Unit, or the appropriate authority at that aerodrome of any change in destination or estimated delay in ETA of 45 minutes or more.
4.4 If a SARTIME is not included in a Flight Plan terminating at an aerodrome which is not manned by SCAA search and Rescue action will not be taken unless information is received which casts doubt upon the safety of the aircraft.
4.5 An operator shall, prior to departure
  1. Ensure that, where the flight is intended to operate on a route or in an area where an RNP type is prescribed, the aircraft has an appropriate RNP approval, and that all conditions applying to that approval will be satisfied;
  2. Ensure that, where operation in reduced vertical separation minimum (RVSM) airspace is planned, the aircraft has the required RVSM approval; and
  3. Ensure that, where the flight is intended to operate where an RCP type is prescribed, the aircraft has an appropriate RCP approval, and that all conditions applying to that approval will be satisfied.
5   The Flight Plan Form
5.1 Each Flight Plan form is filled in triplicate. The top sheet will be retained by the ATS. The top sheet will be retained by the ATS unit concerned. The second sheet is used for immediate transmission over the AFTN. The third is for retention by the pilot.
5.2 The Flight Plan form is illustrated on page ENR 1.10-16.

The term “aerodrome” when used in the Flight Plan is intended to cover also sites other than aerodromes which may be used by certain types of aircraft e.g. helicopters or balloons.

5.3 Instruction for completing the flight plan form:-
5.3.1 It is essential that care should be exercised in completing the flight plan form. Block letters should be used wherever possible to ensure clear reproduction of the information. Detailed instruction for using the component parts of the flight plan are detailed hereunder.
  1. use block capitals
  2. All times UTC
  3. Pilot/Representative to complete Item 7 to 18 indicated hereunder unless ATS prescribes otherwise.
  4. Item 19 should be completed unless arrangements have been made for this information to be available to ATS if needed for SAR purposes.

Note :Item numbers on the form are not consecutive, as they correspond to field type numbers in ATS messages.

ITEM 7: AIRCRAFT IDENTIFICATION (MAXIMUM 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. 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 (e.g. KLM511, NIGERIA 213, JESTER 25);
  2. the nationality or common mark and registration mark of the aircraft (e.g. EIAKO, 4XBCD, N2567GA), when:
    1. In radiotelephony the call sign to be used by the aircraft will consist of this identification alone (e.g. CGAJS), or preceded by the ICAO telephony designator for the aircraft operating agency (e.g. BLIZZARD CGAJS)
    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.

Note 2: Provisions for the use of 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.

ITEM 8: FLIGHT RULES AND TYPES OF FLIGHT (ONE OR TWO CHARACTERS)

Flight Rules

INSERT one of the following letters to denote the category of flight rules with which the pilot intends to comply:

I if it is intended that the entire flight will be operated under the IFR

V if it is intended that the entire flight will be operated under the VFR

Y if the flight initially will be operated under the IFR, followed by one or more subsequent changes of flight rules or

Z if the flight initially will be operated under the VFR, followed by one or more subsequent changes of flight rules

Specify in Item 15 the point or points at which a change of flight rules is planned.

Type of flight

INSERT one of the following letters to denote the type of flight when so required by the appropriate ATS authority:

S if scheduled air service

N if non-scheduled air transport operation

G if general aviation

M if military

X if other than any of the defined categories above.

Specify status of a flight following the indicator STS in Item 18, or when necessary to denote other reasons for special handling by ATS, indicate the reason following the indicator RMK in Item 18.

ITEM 9: NUMBER AND TYPE OF AIRCRAFT AND WAKE TURBULENCE CATEGORY

Number of aircraft (1 or 2 characters)

INSERT the number of aircraft, if more than one.

Type of aircraft (2 to 4 characters)

INSERT the appropriate designator as specified in ICAO Doc 8643, Aircraft Type Designators,

OR, if no such designator has been assigned, or in case of formation flights comprising more than one type,

INSERT ZZZZ, and SPECIFY in Item 18, the (numbers and) type(s) of aircraft preceded by TYP/ .

Wake turbulence category (1 character)

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

H HEAVY, to indicate an aircraft type with a maximum certificated take-off mass of 136 000 kg or more;

M MEDIUM, to indicate an aircraft type with a maximum certificated take-off mass of less than 136 000 kg but more than 7 000 kg;

L LIGHT, to indicate an aircraft type with a maximum certificated take-off mass of 7 000 kg or less.

J SUPER HEAVY

ITEM 10: EQUIPMENT

Item 10a  (Radio communication, navigation and approach aid equipment and capabilities):

INSERT  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

INSERT  one or more of the following letters to indicate the serviceable COM/NAV/approach aid equipment and capabilities available:

A GBAS landing system

B LPV (APV with SBAS)

C LORAN C

D DME

E1 FMC WPR ACARS

E2 D-FIS ACARS

E3 PDC ACARS

F ADF

G GNSS (See Note 2)

H HF RTF

I Inertial Navigation

J1 CPDLC ATN VDL Mode 2 (See Note 3)

J2 CPDLC FANS 1/A HFDL

J3 CPDLC FANS 1/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 RTF SATCOM (INMARSAT)

M2 ATC RTF (MTSAT)

M3 ATC RTF (Iridium)

O VOR

P1–P9 Reserved for RCP

R PBN approved (see Note 4)

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 or other capabilities (see Note 5)

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.

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 are 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 (Doc 9613).

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

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

Item 10b (Surveillance equipment and capabilities):

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:

SSR Modes A and C

A   Transponder — Mode A (4 digits — 4 096 codes)

C    Transponder — Mode A (4 digits — 4 096 codes) and Mode C

SSR Mode S

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, 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: - 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-C with 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/.

ITEM 13: DEPARTURE AERODROME AND TIME – (8 CHARACTERS)

INSERT the ICAO four-letter location indicator of the departure aerodrome as specified in Doc 7910, Location Indicators,

OR, if no location indicator has been assigned,

INSERT ZZZZ and SPECIFY, in Item 18, the name and location of the aerodrome preceded by DEP/,

OR, the first point of the route or the marker radio beacon preceded by DEP/…, if the aircraft has not taken off from the aerodrome,

OR, if the flight plan is received from an aircraft in flight,

INSERT AFIL, and SPECIFY, in Item 18, the ICAO four-letter location indicator of the location of the ATS unit from which supplementary flight plan data can be obtained, preceded by DEP/.

THEN, WITHOUT A SPACE,

INSERT for a flight plan submitted before departure, the estimated off-block time (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.

ITEM 15:  ROUTE

INSERT the first cruising speed as in (a) and the first cruising level as in (b), without a space between them.

THEN, following the arrow, INSERT the route description as in

  1. Cruising speed (maximum 5 characters)

    INSERT the True airspeed for the first or the whole cruising portion of the flight, in terms of: Kilometres per hour, expressed as K followed by 4 figures (e.g. K0830), or Knots, expressed as N followed by 4 figures (e.g. N0485), or True Mach number, when so prescribed by the appropriate ATS authority, to the nearest hundredth of unit Mach, expressed as M followed by 3 figures (e.g. M082).

  2. 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 (e.g. F085; F330), or * Standard metric level in tens of metres, expressed as S followed by 4 figures (e.g. S1130), or Altitude in tens of metres, expressed as M followed by 4 figures (e.g. M0840), or for uncontrolled VFR flights, the letters VFR. Altitude in hundreds of feet, expressed as A followed by 3 figures (e.g. A045; A100), or * When so prescribed by the appropriate ATS authorities.

  3. Route (including changes of speed, level and/or flight rules)

    Flights along designated ATS routes INSERT, if the departure aerodrome is located on or connected to the ATS route, the designator of the first ATS route, OR,if the departure aerodrome is not on or connected to the ATS route, the letters DCT followed by the point of joining the first ATS route, followed by the designator of the ATS route. THEN, INSERT each point at which either a change of speed and/or level is planned to commence, or a change of ATS route, and/or a change of flight rules is planned, Note:- When a transition is planned between a lower and upper ATS route and the routes are oriented in the same direction, the point of transition need not be inserted. FOLLOWED IN EACH CASE by the designator of the next ATS route segment, even if the same as the previous one, OR by DCT, if the flight to the next point will be outside a designated route, unless both points are defined by geographical coordinates.

Flights outside designated ATS routes

INSERT   points normally not more than 30 minutes flying time or 370 km (200 NM) apart, including each point at which a change of speed or level, a change of track, or a change of flight rules is planned.

OR,  when required by appropriate ATS authority(ies),

DEFINE the track of flights operating predominantly in an east-west direction between 70°N and 70°S by reference to significant points formed by the intersections of half or whole degrees of latitude with meridians spaced at intervals of 10 degrees of longitude. For flights operating in areas outside those latitudes the tracks shall be defined by significant points formed by the intersection of parallels of latitude with meridians normally spaced at 20 degrees of longitude. The distance between significant points shall, as far as possible, not exceed one hour’s flight time. Additional significant points shall be established as deemed necessary. For flights operating predominantly in a north-south direction, define tracks by reference to significant points formed by the intersection of whole degrees of longitude with specified parallels of latitude which are spaced at 5 degrees.

INSERT  DCT between successive points unless both points are defined by geographical coordinates or by bearing and distance.

USE ONLY the conventions in (1) to (5) below and SEPARATE each sub-item by a space
  1. ATS route (2 to 7 characters)

    The coded designator assigned to the route or route segment including, where appropriate, the coded designator assigned to the standard departure or arrival route (e.g. BCN1, Bl, R14, UB10, KODAP2A).

    Note: - Provisions for the application of route designators are contained in Annex 11, Appendix 1.

  2. Significant point (2 to 11 characters)

    The coded designator (2 to 5 characters) assigned to the point (e.g. LN, MAY, HADDY), or, if no coded designator has been assigned, one of the following ways:

    — Degrees only (7 characters):

    2 figures describing latitude in degrees, followed by “N” (North) or “S” (South), followed by 3 figures describing longitude in degrees, followed by “E” (East) or “W” (West). Make up the correct number of figures, where necessary, by insertion of zeros, e.g. 46N078W.

    — Degrees and minutes (11 characters):

    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.

    — Bearing and distance from a reference point:

    The identification of the reference 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 180° magnetic at a distance of 40 nautical miles from VOR “DUB” should be expressed as DUB180040.

  3. Change of speed or level (maximum 21 characters)

    The point at which a change of speed (5% TAS or 0.01 Mach or more) or a change of level is planned to commence, expressed exactly as in (2) above, followed by an oblique stroke and both the cruising speed and the cruising level, expressed exactly as in (a) and (b) above, without a space between them, even when only one of these quantities will be changed.

    Examples: LN/N0284A045

    MAY/N0305Fl80

    HADDY/N0420F330

    4602N07805W/N0500F350

    46N078W/M082F330

    DUB180040/N0350M0840

  4. Change of flight rules (maximum 3 characters)

     Change of flight rules (maximum 3 characters)

    The point at which the change of flight rules is planned, expressed exactly as in (2) or (3) above as appropriate, followed by a space and one of the following:

    VFR if from IFR to VFR

    IFR if from VFR to IFR

    Examples: LN VFR

    LN/N0284A050 IFR

  5. Cruise climb (maximum 28 characters)

    The letter C followed by an oblique stroke; THEN the point at which cruise climb is planned to start, expressed exactly as in (2) above, followed by an oblique stroke; THEN the speed to be maintained during cruise climb, expressed exactly as in (a) above, followed by the two levels defining the layer to be occupied during cruise climb, each level expressed exactly as in (b) above, or the level above which cruise climb is planned followed by the letters PLUS, without a space between them.

Examples:C/48N050W/M082F290F350

C/48N050W/M082F290PLUS

C/52N050W/M220F580F620.

ITEM 16: DESTINATION AERODROME AND TOTAL ESTIMATED ELAPSE TIME, ALTERNATE AERODROME(S)

Destination aerodrome and total estimated elapsed time (8 characters)

INSERT  the ICAO four-letter location indicator of the destination aerodrome as specified in Doc 7910, Location Indicators,

OR,      if no location indicator has been assigned,

INSERT  ZZZZ and SPECIFY in Item 18 the name and location of the aerodrome, preceded by DEST/ .

THEN  WITHOUT A SPACE

INSERT the total estimated elapsed time.

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

Destination alternate aerodrome(s)

INSERT      the ICAO four-letter location indicator(s) of not more than two destination alternate aerodromes, as specified in Doc 7910, Location Indicators, separated by a space,

OR,     if no location indicator has been assigned to the destination alternate aerodrome(s),

INSERT   ZZZZ and SPECIFY in Item 18 the name and location of the destination alternate aerodrome(s), preceded by ALTN/.

ITEM 18:  OTHER INFORMATION

Note: Use of indicators not included under this item may result in data being rejected, processed incorrectly or lost.

Hyphens or oblique strokes should only be used as prescribed below.

INSERT  0 (zero) if no other information,

OR,    any other necessary information in the sequence shown hereunder, in the form of the appropriate indicator selected from those defined hereunder followed by an oblique stroke and the information to be recorded:

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

ALTRV  :      for 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 military 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; and

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.

RNAV SPECIFICATIONS

A1 RNAV 10 (RNP 10)

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 LORAN C

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

RNP SPECIFICATIONS

L1 RNP 4

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 (special authorization required)

T2 RNP AR APCH without RF (special authorization required)

Combinations of alphanumeric characters not indicated above are reserved.

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 Item 10a. 

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

SUR/   Include surveillance applications or capabilities not specified in Item 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 “LV” should be expressed as LV180040.

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

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.

RVR/   The minimum RVR requirement of the flight.

Note.— This provision is detailed in the Africa-Indian Ocean Regional Supplementary Procedures (AFI SUPPs, Doc 7030), Chapter 2.

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.: 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 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 reclearance 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.

RFP/    Q followed by a digit to indicate the sequence of the replacement flight plan being submitted.

Note: — This provision is detailed in the Africa-Indian Ocean Regional Supplementary Procedures (AFI SUPPs, Doc 7030), Chapter 2.

ITEM 19: SUPPLEMENTARY INFORMATION

Endurance

After E/ INSERT a 4-figure group giving the fuel endurance in hours and minutes.

Persons on board

After P/  INSERT the total number of persons (passengers and crew) on board, when required by the appropriate ATS authority. INSERT TBN (to be notified) if the total number of persons is not known at the time of filing.

Emergency and survival equipment

R/ (RADIO)      CROSS OUT U if UHF on frequency 243.0 MHz is not available. CROSS OUT V if VHF on frequency 121.5 MHz is not available. CROSS OUT E if emergency locator transmitter (ELT) is not available.

S/ (SURVIVAL EQUIPMENT)      CROSS OUT all indicators if survival equipment is not carried. 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 all indicators 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)      CROSS OUT indicators D and C if no dinghies are carried, or

(NUMBER)            INSERT number of dinghies carried; and

(CAPACITY)          INSERT total capacity, in persons, of all dinghies carried; and

(COVER)              CROSS OUT indicator C if dinghies are not covered; and

(COLOUR)            INSERT colour of dinghies if carried.

A/ (AIRCRAFT COLOUR AND MARKINGS)      INSERT colour of aircraft and significant markings.

N/ (REMARKS)      CROSS OUT indicator 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.

Indicate acceptance of the flight plan by giving the name and signature of the AIM personnel.

6  REPETITIVE FLIGHT PLAN
6.1 A Repetitive Flight Plan is a Flight Plan related to frequently recurring regularly operated IFR flights with identical basic features. It is submitted by an operator for storage and repetitive use by ATS Units. Whilst the repetitive Flight Plans do not fulfil the functions of a normal Flight Plan, they do offer operators and ATS Units considerable advantages in handling of Flight Plan information.
6.2 Instructions for the Completion of the Repetitive Flight Plan (RPL) Listing Form

6.2.1. List only Flight Plans which will operate in accordance with IFR.  (Flight rules I in FPL format).

It is assumed that all aircraft are operating as scheduled flights (Type of flights S in FPL format) otherwise notify in Q (Remarks).

It is assumed that all aircraft operating on RPLs are equipped with 4 096-code transponders with modes A and C. Otherwise notify in Q (Remarks)

List flight plans in alphabetical order of the location indicator of the departure aerodrome.

List Flight Plans for each departure aerodrome in chronological order of estimated off-block times.

Adhere closely to the data conventions as indicated for the Flight Plan Form unless otherwise specifically indicated in 6.5.

Insert all clock times in 4 figures UTC.

Insert all estimated elapsed times in 4 figures (hours and minutes).

Insert data on a separate line for each segment of operations with one or more stops; i.e. from any departure aerodrome to the next destination aerodrome even though call sign or flight number is the same for multiple segments.

Clearly identify additions and deletions in accordance with Item H at 6.5.  Subsequent listings shall list the corrected and added data, and deleted flight plans shall be omitted.

Number of pages by indicating number of page and total number of pages in submission.

Utilize more than one line for any RPL where the space provided for items O and Q on one line is not sufficient.

6.3. A flight shall be cancelled as follows:

  1. Indicate a minus sign in item H  followed by all other items of the cancelled flight.
  2. Insert a subsequent entry denoted by a  plus sign in Item H and the date of the last flight in item J, with all other items of the cancelled flight unchanged.

Modification to a flight shall be made as follows:

  1. Carry out the cancellation as indicated in  6.3; and
  2. Insert a third entry giving the new flight  plan(s) with the appropriate items modified as necessary, including the new validity dates in items I and J.

Note: All entries related to the same flight will be inserted in succession in the order specified above.

6.4 Instructions for insertion of RPL data.
Complete Items A to Q as indicated hereunder:
  1. TEM A: OPERATOR 

    Insert name of operator

  2. ITEM B: ADDRESSEE(S)  

    Insert name of agency (ies) designated by States to administer RPLs for FIRs or areas of responsibility concerned with the route of flight.

  3. ITEM C:  DEPARTURE  AERODROME(S)  

    Insert  Location  indicator of departure aerodrome.

  4. ITEM D:  DATE 

    Insert on each page of submission, the date (year, month, day) in a 6-figure group that the listing was submitted.

  5. ITEM E:  SERIAL NO. 

    Insert serial number of submission (2 numerics) indicting last two digits of year, a dash, and the sequential number of the submission for the year indicated (start with numeral 1 each new year).

     
  6. ITEM F: PAGE  OF

    Insert page number and total number of pages submitted.

  7. ITEM G: SUPPLEMENTARY DATA

    Insert name of contact where information normally provided under Item 19 of the FPL is kept readily available and can be supplied without delay.

  8. ITEM H: ENTRY TYPE  

    Insert a minus sign (-) for each flight plan that is to be deleted from the listing.

    Insert a plus sign (+) for each initial listing and, in the case of subsequent submissions, for each flight plan not listed in the previous submission.

    Note: No information is required under this items for any flight plan which is unchanged from the previous submission.

  9. ITEM I:  VALID FROM 

    Insert first date (year, month, day) upon which the flight is scheduled to operate.

  10. ITEM J: VALID UNTIL

    Insert last date (year, month day) upon which the flight is scheduled to operate as listed, or UFN if the duration is unknown.

     
  11. ITEM K:   DAYS OF OPERATION

    Insert number corresponding to the day of the week in the appropriate column: 

    Monday=1 through Sunday =7 

    Insert 0 for each day of non-operation in the appropriate column.

     
  12. ITEM L: AIRCRAFT  IDENTIFICAT-ION

    Insert aircraft identification to be used for the flight.

     
  13. ITEM M: TYPE OF AIRCRAFT AND WAKE TURBULANCE CATEG-ORY ( item 9 of the ICAO flight plan)

    Insert appropriate ICAO designator as specified in ICAO Doc 8643 - Aircraft

     

Type Designators.

Insert H, M, or L indicators as appropriate.

H HEAVY to indicate an aircraft type with a maximum certificated take-off mass of 136,000 kg or more.

M MEDIUM to indicate an aircraft type with a maximum certificated take-off mass of less than 136,00kg but more than 7,000 kg.

L LIGHT to indicate an aircraft type with a maximum certificated take-off mass of 7,000 kg or less.

J SUPERHEAVY

  1. ITEM N: DEPARTURE AERODROME AND TIME

    Insert location indicator of the departure aerodrome.
    Insert the off-block time, i.e. the estimated time that the aircraft will commence movement associated with departure

  2. ITEM O: ROUTE (item 15 of the ICAO flight plan )
    1. Cruising speed
    2. Insert the true airspeed for the first or whole cruising portion of the flight in accordance with item 15 (a) of the ICAO flight plan.
    3. Cruising level
    4. Insert the planned cruising level for the first or whole portion of the route in accordance with Item 15 (b) of the ICAO flight plan.
    5. Route
      Insert the entire route in accordance with Item 15 (c) of the ICAO flight plan.
  3. ITEM P: DESTINATION AERODROME AND TOTAL ESTIMATED ELAPSED TIME ( Item 16 of the ICAO flight plan )
    1. Insert location indicator of the destination aerodrome
  4. ITEM Q: REMARKS

    Insert items normally notified in Item 8 of the ICAO Flight Plan. For RVSM approved aircraft insert letter W to indicate approved status and any other pertinent to the flight of concern to ATS.

7  Deviation from Flight Plan
7.1 If a pilot decides or is compelled by circumstances to land elsewhere than at the destination aerodrome specified in the flight plan or departure message, he must immediately inform the Area control Centre. When the landing is made at an aerodrome not on the AFTN, or at which a Reporting Officer is not established, or at a place other than an aerodrome, a “free category” message should be sent as soon as possible to the nearest station on the AFTN via a Post Office Channel, or by any other means that can be devised. The term “free category” should be used when asking for the required telephone number. If the telegraph service is used, the prefix ”NAV”. No charge will then be made to the pilot.
7.2 When a deviation from route has been made which will substantially delay arrival at the first point of intended landing shown in the flight plan or departure message, the pilot should, if possible notify the ACC by radio of the deviation, and give a revised estimated time of arrival.
8  ATS Messages
8.1 Origination of Messages

8.1.1. The pilot is always responsible for the origination of ATS messages in the categories shown below, but at aerodromes on the AFTN, the ATS Unit concerned will carry out this duty on behalf of the pilot during its hours of service. The ATS Unit must, however, be provided by the pilot or his representative with information forming the basis of delay or cancellation messages.

8.1.2. At aerodromes not on the AFTN, it is the pilot’s responsibility to originate the appropriate message and communicate to the nearest ATS/AIS unit who shall in turn disseminate it accordingly. This shall be via radio or as stipulated in GEN 3.4.3 para 6.

8.2 Flight plan Messages

8.2.1. Filed flight plan messages shall be transmitted for all flights for which a flight plan has been submitted with the object of being provided with air traffic control service, flight information service or alerting service along part or the whole of the route of flight.

8.2.2. A filed flight plan message shall be originated and addressed as follows by the ATS/AIS unit serving the departure aerodrome or, when applicable, by the ATS/AIS unit receiving a flight plan from an aircraft in flight:

  1. A FPL message shall be sent to the ACC or flight information centre serving the control area or FIR within which the departure aerodrome is situated;
  2. Unless basic flight plan data are already available as a result of arrangements made for repetitive flight plans, an FPL message shall be sent to all centres in charge of each FIR or upper FIR along the route which are unable to process current data. In addition, an FPL message shall be sent to the aerodrome control tower at the destination aerodrome. If so required, an FPL message shall also be sent to flow management centres responsible for ATS units along the route;
  3. When a potential reclearance in flight (RIF) request is indicated in the flight plan, the FPL message shall be sent to the additional centres concerned and to the aerodrome control tower of the revised destination aerodrome;
  4. Where it has been agreed to use CPL messages but where information is required for early planning of traffic flow, an FPL message shall be transmitted to the ACCs concerned;
  5. For a flight along routes where flight information service and alerting service only are provided, an FPL message shall be addressed to the centre in charge of each FIR or upper FIR along the route and to the aerodrome control tower at the destination aerodrome.

8.2.3. In the case of a flight through intermediate stops, where flight plans for each stage of the flight are filed at the first departure aerodrome, the following procedure shall be applied:

  1. The ATS/AIS unit at the first departure aerodrome shall:
    1. Transmit an FPL message for the first stage of flight in accordance with 8.2.2;
    2. Transmit a separate FPL message for each subsequent stage of flight, addressed to the air traffic services reporting office at the appropriate subsequent departure aerodrome;
  2. the air traffic services reporting office at each subsequent departure aerodrome shall take action on receipt of the FPL message as if the flight plan has been filed locally.

8.2.4. FPL messages shall be transmitted immediately after the filing of the flight plan. However, if a flight plan is filed more than 24 hours in advance of the estimated off-block time of the flight to which it refers, the date of light departure shall be inserted in Item 18 of the flight plan.

8.2.5. Flight plans shall not be submitted more than 120 hours before the estimated off-block time of a flight.

8.3 Departure Messages

8.3.1. If a flight plan message has been sent, whether voluntarily or by regulation, a departure message must be sent as soon as the aircraft has taken off. It should be sent to the same addressees as the flight plan message

8.3.2. Departure messages contain the following information in the order shown:

  1. Type of message (DEP)
  2. Radio call sign or aircraft identification as shown in the flight plan.
  3. Departure aerodrome and time
  4. Destination aerodrome
  5. DOF where included in the filed Flight plan and "0" where DOF/or no other information is not included.

Example with DOF: (DEP-KQA172-HKJK1115-EGLL-DOF/120120)
Example without DOF: (DEP-KQA172-HKJK1115-EGLL-0)

8.3.3. When a departure message is sent instead of a flight plan message, it will also contain the aerodrome of departure and the aerodrome of first intended landing.

8.3.4. A departure message associated with a flight plan filed through intermediate stops should include the number of persons and the fuel on board under Item 19.

8.4 Delay Messages (DLA)

8.4.1. A DLA message shall be transmitted when the departure of an aircraft, for which basic flight plan data (FPL or RPL) has been sent, is delayed by more than 30 minutes after the estimated off-block time contained in the basic flight plan data.

8.4.2. However it should be noted that a flight plan in respect to an IFR flight is valid for one hour and two hours for a VFR flight. On expiry of this times a new flight plan should be submitted.

8.4.3. Delay messages should contain the following information as shown in the flight plan:

  1. Type of Message (DLA)
  2. Radio call sign or aircraft identification as shown in the flight plan.
  3. Revised estimated time of departure, expressed as a four-figure group in UTC
  4. Destination aerodrome and time.
  5. DOF where included in the filed Flight plan and "0" where DOF/or no other information is not included.

Example with DOF:(DLA-KQA172-HKJK1115-EGLL-DOF/120120)
Example without DOF: (DLA-KQA172-HKJK1115-EGLL-0)

Note: For a Delay that spills over to the next day, i.e delay over midnight, the modification message type (CHG) is used instead of DLA.(Ref 8.7 below)

8.5 Cancellation Message (CNL)

A flight plan cancellation (CNL) message shall be transmitted when a flight, for which basic flight plan data has been previously distributed, has been cancelled. The ATS/AIS unit serving the departure aerodrome shall transmit the CNL message to ATS units which have received basic flight plan data. A cancellation message contains the following information in the order shown:

  1. Type of message (CNL).
  2. Radio call sign or aircraft identification as shown in the flight plan.
  3. Departure aerodrome and time.
  4. Destination aerodrome.
  5. DOF where included in the filed Flight plan and "0" where DOF/or no other information is not included.

Example with DOF: (CNL-KQA172-HKJK1115-EGLL-DOF/120120)
Example without DOF: (CNL-KQA172-HKJK1115-EGLL-0)

8.6 Arrival Message (ARR)

8.6.1. When an arrival report is received by the ATS unit serving the arrival aerodrome, this unit shall transmit an ARR message:

  1. for a landing at the destination aerodrome:
    1. To the ACC or flight information centre in whose area the arrival aerodrome is located, if required by that unit; and
    2. To the air traffic services unit, at the departure aerodrome, which originated the flight plan message, if that message included a request for an ARR message;
  2. for a landing at an alternate or other aerodrome:
    1. To the ACC or flight information centre in whose area the arrival aerodrome is located; and
    2. To the aerodrome control tower at the destination aerodrome; and
    3. To the air traffic services reporting office at the departure aerodrome; and
    4. To the ACC or flight information centre in charge of each FIR or upper FIR through which the aircraft would have passed according to the flight plan, had it not diverted.

8.6.2. At unmanned aerodromes, it is the pilot’s responsibility to report his arrival to the nearest KCAA-manned aerodrome if a SARTIME has been filed in the flight plan.

8.6.3. When a controlled flight which has experienced failure of a two- way communication has landed, the aerodrome control tower at the arrival aerodrome shall transmit an ARR message:

  1. For a landing at the destination aerodrome:
    1. To all air traffic service units concerned with the flight during the period of communication failure; and
    2. To all other air traffic service units which may have been alerted:
    3. For a landing at an aerodrome other than the destination aerodrome:
    4. To the ATS units serving the destination aerodrome; this unit shall then transmit an ARR message to other ATS units concerned or alerted as in a) above.

8.6.4. An arrival message will contain the following information in the order shown:

  1. Type of message (ARR)
  2. Radio call sign or aircraft identification as shown in the flight plan or departure message.
  3. Departure aerodrome and time
  4. The four letter code or the name of the aerodrome where the aircraft has landed followed, without a space by the time of arrival expressed as a four-figure group in UTC.

Example: (ARR-KQA509-DIAP0005-HKJK0430)

8.7 Modification Message (CHG)

8.7.1. A CHG message shall be transmitted when any change is to be made to basic flight plan data contained in previously transmitted FPL or RPL data. The CHG message shall be sent to those recipients of basic flight plan data which are affected by the change.

8.7.2. Modification messages contain the following information in the order shown:

  1. Message type (CHG)
  2. Aircraft Identification
  3. Departure aerodrome and time
  4. Destination aerodrome and total estimated elapsed time, destination alternate aerodrome(s) other informationThe amendment to the flight plan

Example with CHG in 8 with DOF: (CHG-KQA172-HKJK1015-EGLL-DOF/120120-8/I)

Example with CHG in 8 without DOF: (CHG-KQA172-HKJK1015-EGLL-8/I-0)

Meaning: Modification message-aircraft identification KQA172, en route from Jomo Kenyatta to London Heathrow- Field Type 8 of the related filed flight plan is corrected to IFR..

Note: When modifying a field 18 element, the complete field 18 must be provided and not just the modified elements. Elements not repeated will be deleted

8.7.3 Request flight plan message (RQP)

A request flight plan (RQP) message shall be transmitted when an A TS unit wishes to obtain flight plan data. This might occur upon receipt of a message concerning an aircraft for which no corresponding basic flight plan data had been previously received. The RQP message shall be transmitted to the transferring ATS unit which originated an EST message, or to the centre which originated an update message for which no corresponding basic flight plan data are available. If no message has been received at all, but an aircraft establishes radiotelephony (RTF) communications and requires air traffic services, the RQP message shall be transmitted to the previous ATS unit along the route of flight.

Request flight plan messages must contain the following information in the order shown:

  1. Message type (RQP)
  2. Aircraft identification
  3. Departure aerodrome
  4. Destination aerodrome

Example:( RQP-GBREN-EGLL-HTKJ)

8.8 Request Supplementary flight plan message (RQS)

8.8.1. A request supplementary flight plan (RQS) message shall be transmitted when an air traffic services unit wishes to obtain supplementary flight plan data. The message shall be transmitted to the air traffic services reporting office at the departure aerodrome or in the case of a flight plan submitted during flight, to the air traffic services unit specified in the flight plan message.

8.8.2. Request flight plan messages must contain the following information in the order shown:

  1. Message type (RQS)
  2. Aircraft identification
  3. Departure aerodrome and time
  4. Destination aerodrome
  5. DOF where included in the filed Flight plan and "0" where DOF not included.

Example:

(RQS-KQA172-HKJK1015-EGLL-DOF/ 120120) or

(RQS-KQA172-HKJK1015-EGLL-0) for filed FPL without DOF:

8.9 Supplementary flight plan message (SPL).

8.9.1. An SPL message shall be transmitted by the air traffic services reporting office at the departure aerodrome to air traffic services units requesting information additional to that already transmitted in a CPL or FPL message. When transmitted by the AFTN, the message shall be assigned the same priority indicator as that in the request message.

Composition of a Supplementary flight plan message:-

  1. Message type, number and reference data
  2. Aircraft identification and SSR Mode and Code.
  3. Departure Aerodrome and time
  4. Destination aerodrome and total estimated elapsed time, alternate aerodrome(s)
  5. Other information
  6. Supplementary information

Example:

(SPL-LTU660-EDDL0920-HKMO0800 HTKJ-REG/DABUA RMK/CHARTER -E/1040P/150 R/V J/L A/BLUE C/DENKE)

Meaning: Supplementary flight plan message – aircraft identification LTU660-departed Düsseldorf 0920 UTC- destination Mombasa, total estimated elapsed time 8 hours- alternate Kilimanjaro- aircraft registration DABUA-charter flight- endurance 10 hours and 40 minutes after departure-150 persons on board-portable radio working on International Distress Frequency 121.5MHZ – life jackets fitted with lights are carried- the aircraft colour is blue- the pilot’s name is Denke.

8.9.2. Request supplementary flight plan messages must contain the following information in the order shown:

  1. Message type (RQS)
  2. Aircraft identification
  3. Departure aerodrome and time
  4. Destination aerodrome
  5. DOF where included in the filed Flight plan and "0" where DOF not included.

Example with a RQS from FSIA:

(RQS-KQA172-HKJK1015-FSIA-DOF/ 120120), or

RQS-KQA172-HKJK1015-FSIA-0) for filed FPL without DOF: