Document from CIS Legislation database © 2003-2025 SojuzPravoInform LLC

RESOLUTION OF THE MINISTRY OF DEFENCE OF THE REPUBLIC OF BELARUS AND MINISTRY OF TRANSPORT AND COMMUNICATIONS OF THE REPUBLIC OF BELARUS

of March 3, 2014 No. 5/4

About approval of Aviation rules of creation of the formalized requests for use of airspace of the Republic of Belarus and messages on its use

(as amended on 20-12-2023)

Based on article 6 of the Air code of the Republic of Belarus and Item 50 of the Rules of use of airspace of the Republic of Belarus approved by the resolution of Council of Ministers of the Republic of Belarus of November 4, 2006 No. 1471, the Ministry of Defence of the Republic of Belarus and the Ministry of Transport and Communications of the Republic of Belarus is DECIDED:

1. Approve Aviation rules of creation of the formalized requests for use of airspace of the Republic of Belarus and messages on its use (are applied).

2. This resolution becomes effective since April 1, 2014.

Minister of Defence of the Republic of Belarus lieutenant general

Yu.V.Zhadobin

Minister of Transport and Communications of the Republic of Belarus

A. A. Sivak

 

Approved by the Resolution of the Ministry of Defence of the Republic of Belarus and the Ministry of Transport and Communications of the Republic of Belarus of March 3, 2014 No. 5/4

Aviation rules of creation of the formalized requests for use of airspace of the Republic of Belarus and messages on its use

Chapter 1. General provisions

1. In these Aviation rules the procedure for creation (registration), single and obligatory for all users of airspace of the Republic of Belarus, for the formalized requests for use of airspace of the Republic of Belarus (further - the request for IVP) and messages on use of airspace of the Republic of Belarus is established (further - the message on IVP).

2. For the purposes of these Aviation rules the following reducings are applied:

ADP – airdrome control office;

AMChS (AMHS) – service of processing of messages of air traffic services;

AFTN (AFTN) – network of the aviation fixed telecommunication;

AHR – aviation and chemical works;

BLA – the unmanned aerial vehicle;

Air Force and troops of air defense – Air Force and troops of air defense of Armed Forces of the Republic of Belarus;

VRL – secondary radar;

VCh – high frequency;

GPK – State boundary committee of the Republic of Belarus;

DMV – decimeter waves;

DOSAAF – Republican state public association "Volunteer Society for Cooperation with the Army, Aviation, and Fleet of the Republic of Belarus";

EU air traffic management – Single system of air traffic management of the Republic of Belarus;

IVP – use of airspace of the Republic of Belarus;

ICAO – International Civil Aviation Organization;

ILS (ILS) – tool system of landing;

INS (INS) – the inertial navigation system;

KV – short waves;

KTA – control point of airfield;

MV – meter waves;

MDP – local control office;

MO – Ministry of Defence of the Republic of Belarus;

MTK – Ministry of Transport and Communications of the Republic of Belarus;

Ministry of Emergency Situations – Ministry of Emergency Situations of the Republic of Belarus;

Department of Internal Affairs – servicing of air traffic;

OVCh – very high frequency;

PVP (VFR) – the visual flight rules;

PDZ – report Item on demand;

UNDER – Item of obligatory reports;

PPP (IFR) – the instrument flight rules;

ROOLAVVS – Republican public association of fans of aircraft, owners of aircrafts and pilots;

RPI – the region of flight information;

RSBN – radio engineering system of near navigation;

RSDN – radio engineering system of distant navigation;

The SPU – the aircraft intercom;

UVCh – ultrahigh frequency;

FSLA – public association "Belarusian federation of extralight aircraft";

TsES air traffic management – Center of the Single system of air traffic management of the Republic of Belarus;

ACARS – aviation system of addressing and transmission of messages;

ADF – the automatic radiopelengatorny equipment;

ADS-B – broadcasting automatic dependent observation;

ADS-C – contractual automatic dependent observation;

AFIL – the flight plan transferred from board;

APCH – landing approach;

APV – the scheme of landing approach with vertical targeting;

ATFM – the organization of flow of air traffic;

BARO-VNAV – barometric vertical navigation;

CPDLC – communication "the dispatcher – the pilot" on data line;

DAT – data and opportunities (the navigation, radio coherent or landing equipment);

D-FIS – FIS data line;

DME – the ranging equipment;

FANS – future systems of air navigation;

FIS – flight and information servicing;

FMC – COMPUTER (system) of flight control;

GBAS – land system of functional amendment;

GNSS – the global navigation satellite system;

INMARSAT – the international sea satellite organization;

Iridium – the global satellite communication system;

IRS – inertial basic system;

IRU – the inertial basic block (the inertial measuring instrument);

LAT/LONG – the geographical width and longitude;

LPV – landing approaches on course radio beacon with vertical targeting;

MLS – microwave system of landing;

MNPS – technical requirements to the minimum navigation characteristics;

PDC – preoutgoing dispatching permission;

QNH – the atmospheric pressure specified to the average level of the sea;

RCP – required characteristics of communication;

RNAV – zone navigation;

RNP – required navigation characteristics;

RTF – voice communication;

RVSM – the reduced minimum of vertical echeloning;

SATCOM – satellite communication;

SBAS – satellite system of functional amendment;

SELCAL – system of the selective challenge;

TACAN – short-range phase code azimuthal and ranging radio navigational system;

UAT – the transceiver of universal access;

VDL – VHF data transmission channel;

VNAV – vertical navigation;

VOR – omnidirectional OVCh-radio beacon.

3. In these Aviation rules the main terms and determinations in the values established in Rules of use of airspace of the Republic of Belarus are used.

Chapter 2. Requirements to creation of requests for IVP and messages on IVP

4. Requests for IVP are constituted in single forms which correspond to the forms recommended to ICAO for creation of plans of flights.

5. Requests for IVP are constituted according to appendix 1:

on accomplishment of regular flights along routes of Department of Internal Affairs of the Republic of Belarus - in form 1 "The request of the repeating plans of flights (RPL)" (further - the request for IVP in form 1);

on accomplishment of one-time flights along routes of Department of Internal Affairs of the Republic of Belarus - in form 2 "The request for accomplishment of one-time flight along routes of servicing of air traffic of the Republic of Belarus" (further - the request for IVP in form 2);

on implementation of activities for IVP out of routes of Department of Internal Affairs and accomplishment of one-time flights along routes of Department of Internal Affairs. If on accomplishment of the specified flights issue of permissions is not required or these permissions are already issued, the request for IVP is constituted according to appendix 1 in form 3 "The request for use of airspace of the Republic of Belarus" (further - the request for IVP in form 3).

6. The formalized requests for IVP and messages on IVP are constituted with use:

printing letters of the Russian or Latin alphabet - in case of creation of requests for IVP within the Republic of Belarus;

printing letters of the Latin alphabet - in case of creation of requests for IVP in case of accomplishment of the international flights.

In case of creation of requests for IVP and messages on IVP determination of compliance of letters of Latin and Russian alphabets is performed according to tables 1 and 2 according to appendix 2.

7. In case of creation of requests for IVP and messages on IVP transfer of the text on other line is allowed only by the whole groups (words) without gaps. The total quantity of signs in one line shall not exceed 69 signs.

8. Time in requests for IVP and messages on IVP is specified on the world coordinated time (UTC).

9. Requests for IVP and messages on IVP are represented to TsES air traffic management by means of AFTN, AMChS or Internet resources providing their documentation and the automated processing.

10. Requests for IVP are constituted by commanders of aircrafts (commanders of groups of aircrafts) or aviation specialists according to their job responsibilities.

11. Responsibility for timely submission to the relevant control office of the request for IVP and reliability of information specified in it is born by the commander of the aircraft or the specialist who is responsible for its creation. Responsibility for timely submission of the request for IVP in TsES air traffic management is born by the responsible specialist of control office of the user. Responsibility for timely issue of permission to IVP to the applicant of the request is born by the corresponding officials of TsES air traffic management.

12. Departures from rules of creation of requests for IVP are not allowed. Requests for IVP constituted with violations of the requirements provided in these Aviation rules to providing are not accepted.

Chapter 3. Procedure for creation of the request for IVP in case of accomplishment of route, route and route and route flights in airspace of the Republic of Belarus

13. Information part of the request for IVP in form 3 consists of ten information groups - data fields (further - the field). Fields have the following numbering and names:

field 3 "Message type";

field 7 "Identification index of the aircraft";

field 8 "Rules and type of flight";

field 9 "Quantity and type of aircrafts, category of turbulence of trace";

field 10 "Equipment and opportunities";

field 13 "Airfield and time of departure";

field 15 "Route";

the field 16 "Airfield of appointment and the general estimated expired time, reserve airfield(s) of destination";

field 18 "Other information";

field 19 "Additional information".

Sign of the beginning of each field (except the field 3 "Message type") is the hyphen. Data from the field 3 "Message type" to the field 18 "Other information" consist in fields in parentheses and are intended for the automated processing.

14. In the field 3 "Message type" after the opening parentheses without gap the sign designating type of the request for IVP is specified.

Например*:

(FPL;

(FPL.

______________________________

* The examples given in these Aviation rules cannot be reviewed as interlinear notes to Items, part or paragraphs of Items.

15. In the field 7 "Identification index of the aircraft" (at most 7 signs):

15.1. for civil aircrafts on accomplishment of all types of flights, and also for the state aircrafts number of flight is specified accomplishment of the international flights, except as specified, specified in subitems 15.2 and 15.3 of this Item.

For example:

- BRU1401;

- TTS1455;

- GOM1422;

15.2. for aircrafts which operators have no ICAO official registration code the registration sign is specified.

For example:

- EW85576;

- EW01SL;

15.3. for the state aircrafts in case of impossibility of specifying of number of flight or registration sign the radiotelephone call sign of the commander of the aircraft (conducting groups of aircrafts at flight in close flight procedure) is specified.

For example:

- 33615;

15.3-1. for the civil BLA which is subject to the state accounting figures of unique accounting number BLA without alphabetic index are specified.

For example:

- 0170606;

15.3-2. for BLA which is not subject to the state accounting or registration letters CH (SN) and five last signs of serial number of BLA are specified.

For example:

- CH10A72;

- SN10281;

15.4. the mode and the VRL code are specified in cases when the VRL code and this information is assigned for the aircraft is used in bodies of Department of Internal Affairs. Otherwise data on the mode and the VRL code in the request for IVP are not specified.

Data on the mode and the VRL code are specified after identification index of the aircraft through virgule: one letter designating VRL operating mode, and then four figures designating the VRL code assigned for the aircraft and transferred in the specified mode.

For example:

- BRU1401/A4100.

Examples of filling of the field 7 "Identification index of the aircraft":

- BRU1401;

- GOM1422;

- EW85576;

- 33615;

- BRU1401/A4100.

16. In the field 8 "Rules and type of flight" two letters designating rules of flight (the first letter) and flight type (the second letter) are specified:

16.1. for designation of rules of flight one of the following letters is specified:

And (I) * - if flight is carried out on PPP;

(V) - if flight is carried out on PVP;

Ы (Y) - if flight is originally carried out on PPP, and then during flight transition to PVP will be performed;

З (Z) - if flight is originally carried out on PVP, and then transition to PPP will be performed;

______________________________

* Hereinafter in the text of these Aviation rules when writing alphabetic references of information for different fields of requests for IVP the first letters of the Russian alphabet, and in brackets - the letters of the Latin alphabet corresponding to them are specified. When use of letters of the Russian alphabet for the specified designations is not provided in cases, in brackets letters of the Latin alphabet are specified.

16.2. for designation like flight further without gap one of the following letters is specified:

With (S) - for regular airborne transportations (flights of civil aircrafts according to the schedule);

N (N) - for irregular airborne transportations (flights of civil aircrafts out of the schedule);

(G) - for flights of aircrafts of aircraft of general purpose;

M (M) - for flights of the state aircrafts;

Ь (X) - for other flights.

Examples of filling of the field 8 "Rules and type of flight":

- IS;

- ZHN;

- IT;

- IS;

- VN;

- IM.

If during flight application of different rules of flight is planned, in the field 15 "Route" Items (points) where transition from one rules of flight to others will be performed, and through gap - rules of flight by which further flight will be carried out are specified: PPP (IFR - when filling the request for IVP with letters of the Latin alphabet) or PVP (VFR - when filling the request for IVP with letters of the Latin alphabet).

For example:

- K0550C0910... 5240C03020B PVP...;

- K0850S0910... 5240N03020E VFR ….

These records mean that over point with coordinates 52 °40" northern latitude and 30 °20" east longitude transition to PVP will be performed.

If in this point also flight parameters are changed, in the field 15 "Route" Items (points) where transition from one rules of flight to others will be performed, through virgule - new values of speed and flight altitude and through gap - rules of flight by which further flight will be carried out are specified further.

For example:

- K0220C0150 … 5240C03020B/K0220M0045 PVP …;

- K0220F050 … 5240N03020E/K0220M0045 VFR ….

These records mean that in point with coordinates 52 °40" northern latitude and 30 °20" east longitude new value of height will make 450 m and transition to PVP will be performed.

17. In the field 9 "Quantity and type of aircrafts, category of turbulence of trace" the number of aircrafts are specified by one or two figures if their more than one, and designation like the aircraft according to the document ICAO 8643 "Symbols of types of aircrafts" and the table of designations of types of aircrafts according to appendix 3.

For example:

- T154;

- 3TU16;

- 10IL76.

After type of the aircraft the virgule is put and the category of turbulence of trace of the aircraft of one of the following letters is specified:

X (N) - for heavy aircrafts (the take-off weight is 136 t or more);

M (M) - for average aircrafts (the take-off weight is less than 136 t, but more than 7 t);

L (L) - for light aircrafts (the take-off weight is 7 t or less).

For example:

- IL96/H;

- 2SU27/M;

- AH2/L;

- IL96/H;

- 2SU27/M;

- AN2/L.

Document in demo-mode!

Full text is available after subscription.

Disclaimer! This text was translated by AI translator and is not a valid juridical document. No warranty. No claim. More info

Effectively work with search system

Database include more 50000 documents. You can find needed documents using search system. For effective work you can mix any on documents parameters: country, documents type, date range, teams or tags.
More about search system

Get help

If you cannot find the required document, or you do not know where to begin, go to Help section.

In this section, we’ve tried to describe in detail the features and capabilities of the system, as well as the most effective techniques for working with the database.

You also may open the section Frequently asked questions. This section provides answers to questions set by users.