ENR 1.10  FLIGHT PLANNING

1.10.1  Procedures For The Submission Of A Flight Plan

1.10.1.1 A flight plan shall be submitted prior to operating:
  1. any flight or portion thereof to be provided with air traffic control service;

  2. any IFR flight within advisory airspace;

  3. any flight within or into designated areas, or along designated routes, when so required by the appropriate ATS authority to facilitate the provision of flight information, alerting and search and rescue services;

  4. any flight within or into designated areas, or along designated routes, when so required by the appropriate ATS authority to facilitate co-ordination with appropriate military units or with air traffic services units in adjacent States in order to avoid the possible need for interception for the purpose of identification;

  5. any flight across international borders.

Note: The term "flight plan" is used to mean variously, full information on all items comprised in the flight plan description, covering the whole route of a flight, or limited information required when the purpose is to obtain a clearance for a minor portion of a flight such as to cross an airway, to take off from, or to land at a controlled aerodrome.

1.10.1.2 The pilot-in-command or the operator shall use the ICAO Flight Plan format.
1.10.1.2.1 Flight plans and ATS messages must be filed in accordance with amendment 1 of 16th edition of PANS-ATM, DOC 4444. FPL and ATS messages filled in incorrect format will be rejected, potentially causing delay to such flights.
1.10.1.3 Prior to departure, a flight plan shall be submitted via the web-based e-Flight Plan portal, e-FPL, at https://myefpl.caam.gov.my
or any other AFTN/AMHS based system to the Air Traffic Services Reporting Office (ARO) at the departure aerodrome. If no such unit exists at the departure aerodrome, the flight plan shall be submitted to the unit serving or designated to serve the departure aerodrome (refer to ENR 1.11), or to the nearest Air Traffic Services Unit (ATSU).
1.10.1.4 In the event of e-FPL is unserviceable, the flight plan shall be submitted to the ARO through AFTN/AMHS or by email using the flight plan form, which is available at https://www.caam.gov.my/wp-content/uploads/2024/07/Flight-Plan-Form.pdf.
1.10.1.5 The flight plan shall not be submitted more than 120 hours before the estimated off-block time of a flight (see CAD 1101 – ATM Management, Chapter 4 Para 4.4.2)
1.10.1.6 The flight plan shall be submitted by the operator or pilot-in-command at least 180 minutes prior to the estimated off-block time for the following:
  1. Flights departing Malaysia airports whose destinations are outside Malaysia.

  2. Flights departing Peninsular Malaysia airports for Sabah/Sarawak and vice versa.

  3. Flights operating within Peninsular Malaysia.

  4. Flights operating within Sabah and/or Sarawak.

1.10.1.7 Procedures for the submission of a flight plan shall be in accordance with CAD 2 – Rules of the Air, Chapter 3 Para 3.3.1 and CAD 1101 – ATM Management, Chapter 4 Para 4.4.2 and Appendix 2.
1.10.1.8 Flights with the status of Search and Rescue (SAR), Firefighting, Medical (including MEDEVAC), Humanitarian, Head of State, MARSA, and State flights are exempted from the requirements outlined in paragraph 1.10.1.6. Instead, the timing for the flight plan submission is based on real-time coordination with the unit serving or designated to serve the departure aerodrome.

1.10.2  DELAY

1.10.2.1 In the event of a delay of 30 minutes or more to the estimated off-block time for a controlled flight or a delay of one hour or more for an uncontrolled flight, the flight plan shall be amended, or a new one shall be submitted. Additionally, the previous flight plan shall be cancelled, as appropriate.
1.10.2.2 Failure to comply with the requirements in paragraph 1.10.2.1 will result in automatic cancellation of the flight plan.

1.10.3  LANDING OF AIRCRAFT AT OTHER THAN DESIGNATED AERODROME

1.10.3.1 The procedures for landing of aircraft at other designated aerodrome is outlined in Civil Aviation Directive 2001 – Protection of Persons and Property (CAD 2001).
1.10.3.2 A Safety Risk Assessment (SRA) shall be submitted via email to the Air Traffic Services Unit (ATSU) at the departure aerodrome, before departure.
1.10.3.3 The flight plan for such aircraft will not be approved until a complete SRA is received from the pilot-in-command.

1.10.4  ADHERENCE TO ATS ROUTE STRUCTURE

1.10.4.1 No flight plan shall be filed for routes deviating from the published ATS route structure provided in eAIP Malaysia on flight planning requirement for aircraft operating in Kuala Lumpur FIR and Kota Kinabalu FIR (listed in ENR 1.8), unless prior permission has been obtained from CAAM.
1.10.4.2 Flights of a specific character, such as survey flights, scientific research flights, etc., may be exempted from the restriction specified above. A request for exemption should be mailed to CAAM.

1.10.5  ADHERENCE TO FLIGHT PLAN

1.10.5.1 Whenever a flight, for which a flight plan has been submitted, is cancelled, the appropriate ATS unit shall be informed immediately.
1.10.5.2 Changes to a current flight plan for a controlled flight during flight shall be reported or requested, subject to the provisions in CAD 2 – Rules of the Air, Chapter 3 Para 3.6.2 (Adherence to flight plan).

1.10.6  ARRIVAL REPORT (CLOSING A FLIGHT PLAN)

1.10.6.1 A report of arrival shall be made at the earliest possible moment after landing to the airport office of the arrival aerodrome by any flight for which a flight plan has been submitted except when the arrival has been acknowledged by the local ATS unit.
1.10.6.2 Procedures of closing a flight plan shall be in accordance with CAD 2 - Rules of the Air, Chapter 3 Para 3.3.5.

1.10.7  DATA LINK COMMUNICATION AND SURVEILLANCE

1.10.7.1 Aircraft using data link communications (see ENR 1.1) must insert one or more of the following letters in Item 10a of their flight plan to indicate serviceable communication aid equipment and capabilities available:
DescriptorCPDLC Equipment and Capabilities
J1CPDLC ATN VDL Mode 2
J2CPDLC FANS 1/A HFDL
J3CPDLC FANS 1/A VDL Mode A
J4CPDLC FANS 1/A VDL Mode 2
J5CPDLC FANS 1/A SATCOM (INMARSAT)
J6CPDLC FANS 1/A SATCOM (MTSAT)
J7CPDLC FANS 1/A SATCOM (Iridium)
P1CPDLC RCP 400
P2CPDLC RCP 240
P3SATVOICE RCP 400
1.10.7.2 Aircraft using data link surveillance (see ENR 1.1) must insert one or more of the following letters in Item 10a of their flight plan to indicate serviceable surveillance (SUR) equipment and capabilities available:
DescriptorSUR equipment and capabilities
D1ADS-C with FANS 1/A capabilities
G1ADS-C with ATN capabilities
1.10.7.3 Additional surveillance equipment or capabilities are to be listed in Item 18 following the indicator SUR/:
DescriptorSUR equipment and capabilities
RNP10PBN/A1
RNP 4PBN/L1
RNP 2NAV/RNP 2
RSP180SUR/RSP180

1.10.8  RNAV APPROVED AIRCRAFT

1.10.8.1 Aircraft flying on RNAV routes (see ENR 3.3) must be RNAV equipped and should annotate their flight plan as follows:
Item 10 (Descriptor)RNAV equipment
on-board
Item 15Item 18

I

Inertial Navigation

True Mach number and FL at entry and exit points

The types of external GNSS augmentation, if any, are specified following the indicator NAV/ and separated by a space.

R

PBN
approved

The performance-based navigation levels that can be met shall be specified following the indicator PBN/.

PBN/A1 where A1 = RNAV 10 (RNP 10); or

PBN/L1 where L1 = RNP 4; or

PBN/O1 where O1 = Basic RNP1 all permitted sensors; or

PBN/O2 where O2 = Basic RNP1 GNSS; or

PBN/O3 where O3 = Basic RNP1 DME/DME; or

PBN/O4 where O4 = Basic RNP1 DME/DME/IRU

1.10.9  RVSM AND NON-RVSM APPROVED AIRCRAFT

1.10.9.1 Operator of RVSM or non-RVSM approved aircraft operating in RVSM airspace (see ENR 1.8) shall annotate their flight plan as follows:
Item 10 (Descriptor) Item 18Description
W RVSM approved aircraft
 STS/NONRVSMNon-RVSM approved aircraft

1.10.10  NON-SCHEDULED AND GENERAL AVIATION (GA) AIRCRAFT

1.10.10.1 Pilots-In-Command and operators of non-scheduled and GA flight must indicate CAAM Flight Approval reference number under Item 18 of their flight plan as follows:
AuthorityCAAM Flight Approval reference number format
CAAM HQ (IP)RMK/CAAM ATM XXXX XX XX (sequence number, month, year)
RMK/CAAM NS XX XX XX (sequence number, month, year)
MAVCOM (Aerofile)RMK/CAAM AT XXXX XX XX (sequence number, month, year)
1.10.10.2 Failure to indicate valid CAAM Flight Permit Approval reference number in the flight plan may result in delay for air traffic controller to grant clearance to enter Kuala Lumpur FIR and Kota Kinabalu FIR.