1.1.1 A flight plan shall be submitted to the unit for receiving flight plan at least 1 hour before departure for international, at least 30 minutes prior to the beginning of the flight for domestic.

1.1.2 Departing flight plan from Chinggis Khaan International Airport and Buyant-Ukhaa International Airport is received by the AIS division and distributed in the following ways:

On personally:

Internet self-briefing

Internet self-briefing

1.1.3 In case of aerodromes with no ATS Reporting Office (ARO), flight plans and ATS messages shall be submitted to the address of aerodrome ATS unit. The addresses of aerodrome ATS units can be found in ENR 1.11.

1.2.1 The flight plan form and completion of the flight plan form shall comply with Appendix 2 to the PANS-ATM (ICAO Doc 4444).

1.2.2 The following additional requirements are also applicable within Ulaanbaatar FIR:

Item 8: Flight rules and type of flight

The point or points at which a change of flight rules is planned must be specified in Item 15.

Item 9: Number and type of aircraft and wake turbulence category

Number of aircraft

One flight plan shall be submitted for group flight consisting of several aircraft.

Item 10: Equipment and Capabilities

Radio COM/NAV/approach aid equipment and capabilities

Item 13: Departure aerodrome and time

Estimated off-block time (EOBT)

The EOBT shall be given in Coordinated Universal Time (UTC). If the departure is planned at 0000 UTC, the EOBT shall be 0001 UTC in the flight plan.

Item 15: Route

Cruising speed

Cruising speed in terms of kilometers per hour shall be inserted only (e.g. K0830).

Cruising level

For IFR flights, insert the planned cruising level in terms of:

Standard metric level in tens of metres, expressed as S followed by 4 figures (e.g. S1130) using ENR 1.7.5 “Table of cruising levels”, or

Altitude in tens of metres, expressed as M followed by 4 figures (e.g. M0840).

For VFR flights, the letters VFR shall be inserted.

Item 18: Other information

1. STS/ Reason for special handling by air traffic services, 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;

   Note: Aircraft that are not RVSM compliant may not flight between 8900m (29100ft) and 12500m (41100ft), except for the following situations:

   1. The aircraft is being initially delivered to the State of Registry or Operator; or

   2. The aircraft was RVSM approved but has experienced an equipment failure and is being flown to a maintenance facility for repairing in order to meet RVSM requirements and/or obtain approval; or

   3. The aircraft is being utilized for mercy or humanitarian purposes; or

   4. State aircraft (those aircraft used in military, custom and police services shall be deemed state aircraft).

   SAR for a flight engaged in a search and rescue mission;

   STATE for a flight engaged in military, customs or police services.

   For example: STS/HEAD shall be used for a flight with Head of State status.

2. DOF/ The date of flight departure in a six figure format (YYMMDD). DOF/ must be specified in flight plans.

3. OPR/ ICAO designator or name of the aircraft operating agency, if different from the aircraft identification in Item 7 must be specified.

4. ORGN/ The originator’s 8 letter AFTN address or other appropriate contact details must be specified. For example: ORGN/PHONE 97671281010, Fax 97671282022.

Iridium or satellite phone number shall be specified after RMK/ in case of general aviation flights (flights operated in G class airspace). For example: RMK/IRIDIUM 886141451210 or SAT PHONE 886141451210 etc.

3.1.1 In case of delay in the departure of aircraft for more than 30 minutes than indicated in the flight plan, a delay message shall be submitted otherwise the flight plan shall be considered invalid. When delay is for short period (up to 2 hours) but moves the departure of aircraft to the next day, a modification (CHG) message shall be submitted instead of DLA message. For example: A modification (CHG) message shall be submitted for a flight planned for 2300 UTC of 10 February but delayed until 0100 UTC of 11 February.

3.1.2 In case of delay in the departure of aircraft for up to 72 hours from the time indicated in the flight plan, a delay message shall be transmitted to the following addresses of Air Traffic Flow Management DivisionTUNIT;TXT_NAME;142:

3.2.1 When it deemed necessary to make changes to the flight identification, type of aircraft, EOBT or route specified in the flight plan, information related to the change shall be submitted to the Air Traffic Flow Management DivisionTUNIT;TXT_NAME;142 during working hours and to the Tactical Planning Section of Air Traffic Flow Management DivisionTUNIT;TXT_NAME;142 during non-working hours to the addresses mentioned in GEN 1.2.3.

3.2.2 In case of change in the nationality and registration marking of aircraft, information related to the aircraft shall be included in the modification (CHG) message. For example: SEL/, CODE/, equipment and capability etc.

3.3.1 The date of flight departure (DOF/) must be specified. For example: (DEP-MGL223-ZMUB0015-ZBAA-DOF/140224).

3.4.1 Cancellation message of a flight plan should be transmitted to the Air Traffic Flow Management DivisionTUNIT;TXT_NAME;142 during working hours and to the Tactical Planning Section of Air Traffic Flow Management DivisionTUNIT;TXT_NAME;142 during non-working hours to the addresses mentioned in GEN 1.2.3.