A guide to installing and fine-tuning the Microsoft Flight Simulator X (FSX) flight simulator. Guide to installing and fine-tuning the flight simulator Microsoft Flight Simulator X (FSX) Installing addons that will significantly improve graphics and realistic

Signs of pregnancy after embryo implantation

Because in January of this year, the entire team involved in the FS line was disbanded. So we are unlikely to see version 11, although there are rumors that the development team has founded its own studio. Aerosoft is also not asleep, and in October announced Aerosoft Flight Simulator 2012! The project is developing in its infancy. In the meantime, we can only wait, I decided to document all the experience I have gained in installing and using FSX, choosing the necessary addons to increase realism, tweaking FSX to increase FPS, and in general, try to get the most out of what is left of this wonderful aircraft -simulator. For everyone who is interested in this topic, please see the cut (be careful, 10MB of images!).

Before starting the article, I want to immediately note that FSX and almost all add-ons that will be discussed below are paid. Therefore, you need to buy everything you like, because the simulation industry already has a hard time. However, if for some good reason you cannot afford to purchase this or that product, or simply want to evaluate its capabilities first, everything described here (and also the carriage and trolley) can be found. And further. Almost all the tips for optimizing FSX have already been described here and there in pieces on the net. I just sorted everything out. If you disagree with anything or want to add something, please, comments are welcome! So:

FSX is quite demanding on computer resources. And no matter what kind of computer you have, in the end, everything will come down to the “realism or FPS” compromise. The math here is simple: the more addons you install and the better aircraft model you use, the less FPS you get. Therefore, I want to immediately announce the minimum (in my opinion) system requirements that can provide a high-quality and pleasant picture with reasonable FPS:

  • OS: Windows XP, Windows Vista or Windows 7 (I recommend the latter)
  • CPU: Intel Core Duo/Quad (or better), 2GHz or higher. The higher the GHz the better, the number of cores has virtually no effect on FPS in FSX. AMD, of course, will also be able to handle it, but I’m not very familiar with their processors.
  • Memory: 2GB and above. Memory speed affects FPS, so it's better to take care of the frequency and timings.
  • HDD: any modern hard drive with free space at least 100 GB.
  • Video card: preferably from nVidia, because Radeon users sometimes have problems. GeForce 8800 GT or better. Also, it is preferable to have a higher GPU frequency and more memory (256MB - minimum, 512MB - good, 1024MB - excellent) rather than doing SLI or buying cool multi-core video cards.
  • Joystick: A joystick is required to play the game.! Which one is up to you, I personally use Logitech Extreme 3D Pro and am very pleased with it. Ideally, you can even purchase a steering wheel :)
For example, I can give you my configuration, which is quite modest these days: Core Duo E6750 (2.6 GHz), 2GB RAM (OCZ), GeForce 8800GT, Hitachi 500GB. With this configuration, FSX produces: on the ground from 10 to 40 FPS depending on the airport, aircraft and weather conditions; in flight from 15 to 60 FPS. For those who are afraid of 10-15 FPS, I can add that this happens quite rarely, and I see below 20 FPS only 2-5% of the entire flight time. Plus, 15 FPS in a flight simulator is far from the same as 15 FPS in some NFS or GTA :) And the quality of the graphics can be assessed by the screenshots presented at the end of the article. If your computer meets the system requirements described above, then you can start installing the game.

Installing FSX

Installing the simulator consists of two stages:

  1. Installation of the basic version of Flight Simulator X (comes on two DVDs). After installation, it is advisable to launch the simulator, enter the game and exit to initiate the creation of configuration files.
  2. Installing the “Overclocking” add-on (another DVD). This is a very IMPORTANT stage, because... The add-on includes the necessary service pack with a bunch of solved problems. After installation, it is recommended to restart your computer, and then run the simulator once to be sure.

Setting options inside FSX

The game has quite a lot of different settings. I will only touch on those that can affect the quality of graphics and FPS. I'm not saying that the above settings are the MOST optimal. There are no such things. For one computer they are the same, for another they are different. It is recommended to use this option as a starting point, so that later you can tweak it if you have a reserve of FPS, or vice versa, a shortage.

Below I provide screenshots of all tabs with settings. Basic settings:

It is better to turn off DirectX 10; this mode, unfortunately, was never fully developed, which is why it promises nothing but problems. Aircraft settings:

Scenery:

Weather:

Air traffic. Everything here is individual and depends on what kind of traffic you have, default or a separate addon. But in any case, the rule is standard: the more objects in the game, the lower the FPS. You assess the level of realism yourself.

After applying all the settings, the overall settings window in FSX should look like this:

For greater realism, I highly recommend going to the “Realism” section and adjusting a few sliders there, because... The default ones are no good:

The main thing is that the “General” slider is at maximum, as required by many aircraft model manufacturers. Now exit the simulator so that the settings are saved to a file. Then run it again to make sure the settings are loaded successfully. Now close the simulator again, because... Now you will need to correct a few lines manually in the main FSX config: fsx.cfg. This file is located in the Windows user settings folder, i.e. in the directory “C:\Documents and Settings\YOURNAME\Application Data\Microsoft\FSX” or “C:\Users\YOURNAME\AppData\Roaming\Microsoft\FSX” depending on the version of Windows. In order not to bother with paths, you can simply select the “Run” command in Start and enter the line there:

notepad %APPDATA%/Microsoft/FSX/fsx.cfg

The config will automatically open in Notepad in any version of Windows. Don’t forget to save a copy of the file just in case you make a mistake. We need to change (if the parameter is already present in the file) or add the following parameters:


TEXTURE_BANDWIDTH_MULT=70

TEXTURE_MAX_LOAD=4096

DisablePreload=1
FIBER_FRAME_TIME_FRACTION=0.33

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1200
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=1000

PoolSize=12000000

Let me explain what each means:

TEXTURE_BANDWIDTH_MULT Controls the “speed” of loading textures into memory. Recommended value is 70-80 (default 30). If the simulator slows down when turning the camera, try setting a higher value (maximum 400).
TEXTURE_MAX_LOAD Maximum size of supported textures. The parameter is required for the REX addon and (possibly) other addons. 4096 is the maximum.
DisablePreload The simulator will not load the flight by default every time it starts, which allows you to slightly increase the loading speed of the game.
FIBER_FRAME_TIME_FRACTION The parameter determines the ratio of processor time required for loading the scene and rendering. For example, 0.33 in this case means that about 30% of the processor time will be spent loading the scene, and the remaining 70% will be spent on rendering. Recommended values ​​for the sample are in the region of 0.05 - 0.66
TERRAIN_MAX_AUTOGEN_TREES_PER_CELL Number of trees for landscape autogeneration. Large And These values ​​significantly reduce FPS. You can experiment, the range of optimal values ​​varies from 800 to 3000.
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL The same thing, only it determines the number of 3D buildings during auto-generation of the landscape.
PoolSize This parameter determines the size of the buffer for texture memory in order to “pull” the necessary texture from there in time. Some write that it significantly affects the quality of rendering, objects and textures appear more smoothly, without jerking, if you set the value to 12000000 or even more (in bytes). If you have a video card with 512+ megabytes of memory, you can try playing around to find the optimal value.
After saving the changes, run the simulator to evaluate the impact of the tweaked settings. To measure graphics quality and FPS, I always used Brisbane Airport - Australia (ICAO code: YBBN). Select one aircraft and load at this airport (Free flight -> Location -> Edit -> By airport code -> YBBN).
To get the most CPU time out of FSX, you can run it at higher priority. To do this, create a .bat file and insert the following line there, substituting the full path to the fsx.exe file:

start /HIGH J:\GAMES\FSX\fsx.exe

Installing nHancer for fine-tuning nVidia video cards

If you own any GeForce, the nHancer utility will give you much more options for fine-tuning graphics than their standard panel in the Windows Control Panel. The utility is completely free and can be used to adjust graphics in any other game. You can download it (I used version 2.5.7). Also, I advise you to download the latest drivers from the nVidia website. After starting the program, find the “MS Flight Simulator X” profile in the list, select it, make sure that the “Profile” item is active and configure the graphics according to the following recommended values ​​(make changes on the right side of the window ):

In the “Global” section, you also need to correct several values:

After all the manipulations, you can close the program, it is no longer needed, not in the tray, anywhere. The settings are already saved globally. Although, of course, no one forbids you to play with the parameters yourself, especially with the anti-aliasing level, maybe there are more optimal parameters for your video card. Restart your computer and try out the new settings in action.

Setting the shader version

To configure the shaders version, we need to edit another FSX configuration file - display.cfg, which is located in the ROOT directory of the simulator. For me it is “J:\GAMES\FSX”. But first we need the dxdiag utility that comes with Windows. To run it, simply type “dxdiag” in “Start->Run”. In the window that appears, click on the “Save all information...” button and save the resulting dxdiag.txt file to any folder.
Now open both files (dxdiag.txt and display.cfg) in Notepad for editing and create (if there is no similar one) a section in the following format:
The example is given for a GF 8800 GT card, but should work for ATI cards as well. After these manipulations, you may notice a slight increase in FPS and water rendering quality.

Installing addons that will NOTICELY improve the graphics and realism of the simulator

FSX is a very good simulator, but it is still far from reality :) Therefore, on the Internet you can find hundreds of addons that can add new photorealistic landscapes to the game (in fact, ground textures in the form of satellite photographs), real clouds, real weather conditions, models of almost all real aircraft, most of which are 100% complete, i.e. any lever or switch will work as on a real car, air traffic and many other interesting things. Below I provide a list of the most necessary addons (in my opinion), which significantly transform the simulator. I recommend installing in order, starting the simulator after completing the installation of each add-on:

  1. FS Global 2010- replaces the default mesh of the earth's surface with a more detailed one with a resolution of up to 9 meters!.. Here are screenshots for comparison:

    FSX default:


    FS Global 2010:


    Photo:


    Addon size: about 24GB! I would like to add that FS Global 2010 is noticeably better than the previous version - FS Global 2008, so look for the latest version.

  2. Ultimate Terrain X Europe- makes the European part more detailed. Adds textures, road markings, etc. Addon size: 1.5GB. There are also versions for the USA and Canada.
  3. Ground Environment X Europe/USA/Canada- The best addon to replace standard ground textures for Europe, USA and Canada. Can be used in conjunction with Ultimate Terrain X, because it contains only land classes (roads, lakes, bridges, residential areas, etc.). Addon size: ~3.0GB.
  4. ORBX Australia- an excellent addon that will make the entire Australian continent photorealistic. The addon consists of four parts (northern, southern, central and western parts). Addon size: 3.5GB.
  5. Other scenes- There are still a LOT of different scenarios for different parts of the world and countries. For example, the Hawaii scenario from Megascenery. You can also find a ton of detailed airports, you can continue the list yourself, just go to the simmarket and look for what you personally like.
  6. Real Environment Extreme (REX)- perhaps the best addon for adding photorealistic clouds and weather conditions, as well as stunning water! At the same time, FPS does not drop much. Addon size: version 1.0 - 4GB, plus update to 2.0 - 100MB. Has a built-in weather engine that can load real weather in and around your chosen airport.
  7. MyTraffic 5.2- creates more realistic traffic at airports and in the sky (looks something like this). FPS doesn't drop much. Includes a bunch of different aircraft models with real airline liveries. I would like to note that there are other traffic options for FSX, for example, “World of AI Traffic”, “Morten's AI Traffic v2.2”, etc. For me personally, traffic does not play such an important role, so I did not compare All these products, I just chose MyTraffic. Size is about 1GB.
  8. FsPassengers- the addon allows you to create a virtual airline, buy virtual planes, transport virtual passengers and earn virtual money from it :) It is made of quite high quality, you can hire a crew on board the plane, feed passengers in flight and much more interesting things. With this addon, flying offline will become much more interesting.
  9. FSUIPC- a small addition to the FSX SDK, which is required for some addons so that they can connect to the simulator to exchange data (even over a network on a separate computer).
  10. FlightSim Commander 8.5- a program for planning a flight route. Of course, you can plan a route using the built-in planner in the simulator itself, but in FSC, in my opinion, this is done much more conveniently. Here you can easily plot a route using VOR beacons, view a map of the airport (taxiing, gates), etc.:

    You plan a route, save it to a .pln file, open it in FSX and fly. If you want even more realism, you can use real Jeppesen maps (Jeppview program), which are used by real pilots. The maps contain all the necessary information: SID/STAR schemes, approach schemes using ILS, VOR, DME, GPS, taxiway markings, and so on. The program looks like this:


  11. Additional aircraft- A lot of airplane and helicopter models have been created for FSX. There are even space shuttles :) Of the light aircraft, I especially want to note the following:

    RealAir Beechcraft Duke B60- My favorite:)

    Carenado C172n

    IRIS Pro Christen Eagle


    (39) AERODROME GROUND TRAFFIC CHART - ICAO
    (41) AERODROME GROUND TRAFFIC AND AIRCRAFT PARKING CHART - ICAO
    (42) AERODROME GROUND TRAFFIC AND AIRCRAFT PARKING CHART - ICAO
    (43) AERODROME GROUND TRAFFIC AND AIRCRAFT PARKING CHART - ICAO
    (44) AERODROME GROUND TRAFFIC AND AIRCRAFT PARKING CHART - ICAO
    (55) AREA MAP - ICAO (DEPARTURE ROUTES)
    (56) AREA MAP - ICAO (ARRIVAL ROUTES)
    (57) OVERVIEW MAP OF MINIMUM RELATIVE HEIGHTS OF ATS
    (59) STANDARD INSTRUMENT DEPARTURE ROUTES - (SID). Runway 32P/32, 14L/14, 32L, 14P
    (69) STANDARD INSTRUMENT DEPARTURE (SID) CHART - ICAO. Runway 14L, 14
    (70) STANDARD INSTRUMENT DEPARTURE (SID) CHART - ICAO. Runway 32P, 32
    (71) STANDARD INSTRUMENT DEPARTURE CHART (SID) - ICAO.RWY 14P
    (72) STANDARD INSTRUMENT DEPARTURE (SID) CHART - ICAO. Runway 32L
    (77) STANDARD INSTRUMENT ARRIVAL ROUTES - (STAR). Runway 14P/14, 32L/32
    (87) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. Runway 14P, 14
    (88) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. Runway 14P, 14
    (89) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. Runway 14P, 14
    (90) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. Runway 14P, 14
    (91) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. Runway 32L, 32
    (92) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. Runway 32L, 32
    (93) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. Runway 32L, 32
    (94) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. Runway 14P, 32L
    (97) INSTRUMENT APPROACH CHART - ICAO. ILS. Runway 14P KAT I/II/IIIA
    (98) INSTRUMENT APPROACH CHART - ICAO. ILS. Runway 32L KAT I
    (99) INSTRUMENT APPROACH CHART - ICAO. ILS. Runway 14 KAT I
    (100) INSTRUMENT APPROACH CHART - ICAO. ILS. Runway 32 KAT I
    (101) INSTRUMENT APPROACH CHART - ICAO. VOR. Runway 14P
    (102) INSTRUMENT APPROACH CHART - ICAO. VOR. Runway 32L
    (135) WAYPOINT COORDINATES BY RNAV (GNSS) (PZ-90.02)
    (145) STANDARD INSTRUMENT ARRIVAL ROUTES - (STAR). Runways 14, 14L, 14P, 32, 32P, 32L
    (147) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. RNAV (GNSS). Runway 32L, 32P
    (148) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. RNAV (GNSS). Runways 14P, 14L, 14
    (149) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. RNAV (GNSS). Runway 32L, 32P
    (150) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. RNAV (GNSS). Runway 14P, 14L
    (151) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. RNAV (GNSS). Runway 32
    (152) STANDARD INSTRUMENT ARRIVAL (STAR) CHART - ICAO. RNAV (GNSS). Runway 14
    (157) INSTRUMENT APPROACH CHART - ICAO. GLS. Runway 14P
    (158) INSTRUMENT APPROACH CHART - ICAO. GLS. Runway 32L
    (159) INSTRUMENT APPROACH CHART - ICAO. GLS. Runway 14
    (160) INSTRUMENT APPROACH CHART - ICAO. GLS. Runway 32
    (161) INSTRUMENT APPROACH CHART - ICAO. RNAV (GNSS). Runway 14P
    (162) INSTRUMENT APPROACH CHART - ICAO. RNAV (GNSS). Runway 32L
    (163) INSTRUMENT APPROACH CHART - ICAO. RNAV (GNSS). Runway 14
    (164) INSTRUMENT APPROACH CHART - ICAO. RNAV (GNSS). Runway 32
    (165) INSTRUMENT APPROACH CHART - ICAO. RNAV (GNSS). Runway 14L
    (166) INSTRUMENT APPROACH CHART - ICAO. RNAV (GNSS). Runway 32P
    Scenario name Scenario type Flight Simulator 9 Flight Simulator X Prepar3D v2 Prepar3D v3 Prepar3D v4 xPlane
    Domodedovo (x-flight.su) free
    MDesign - Moscow Domodedovo FSX/P3D paid
    UUDD Moscow Domodedovo (RVV1973) free
    UUDD Moscow Domodedovo (RVV1973) Conversion free

    Domodedovo(IATA: DME, ICAO: UUDD) is an international airport of federal significance, one of the three main airports in Moscow and the Moscow region, the second in terms of passenger traffic in the Russian Federation. Located on the border of the Domodedovo urban district and the Ramensky district of the Moscow region, 45 kilometers southeast of the center of Moscow, 22 kilometers from the Moscow Ring Road.

    Based on the results of 2015, it is the second largest Russian airport by passenger turnover, and is also among the twenty busiest airports in Europe. Flights from Domodedovo Airport are operated by 52 airlines to 185 destinations around the world. Among the airport's partners are 48 foreign airlines and 28 Russian ones.

    The airport complex includes an airfield formed by two independent parallel runways (Runway-1 and Runway-2). They are located two kilometers from each other, which makes Domodedovo the only airport in the Moscow aviation hub capable of simultaneously carrying out independent takeoff and landing operations on its runways. The reconstruction of IVPP-1 in 2009 made Domodedovo the first Russian airport capable of receiving a passenger airliner Airbus A380.

    In 2014, the Federal Air Transport Agency decided to build a new runway with a length of 3,800 m at Domodedovo Airport. It will be located at a distance of 287.5 m northeast of the current Runway 2 (parallel to it). During construction, the existing Runway 2 will continue to operate, which will maintain the airport's capacity. After construction is completed, the designation will be Runway-2, and the former Runway-2 will be converted into a main taxiway.

    runway Dimensions, m Hpore, m Take-off/landing control panel Runway category DPRM BPRM ILS
    14L 2370×53 167,8 135° RNAV only - - -
    32R 2370×53 158,3 315° RNAV only - - -
    14R 3500×60 180,6 135° CAT IIIA 320 (DM) - 110.100 (IDM)
    32L 3500×60 161,8 315° CAT I 659 (DO) - 109.300 (IDO)
    14* 3800×60 168,2 135° - - - -
    32* 3800×60 159,4 315° - - - -

    * - under construction (runway is not working)

    A VOR beacon with an operating frequency of 113.300, call sign DMD, is installed at runway 32L.

    ATS communication means:

    UUDD_R_APP- Domodedovo-Krug - 127.700

    UUDD_1_TWR- Domodedovo-Tower (14R-32L) - 118.600

    UUDD_2_TWR- Domodedovo-Tower (14L-32R) - 119.700

    UUDD_GND- Domodedovo-Perron - 119.000

    UUDD_DEL- Domodedovo-Delivery - 129.150

    UUDD_ATIS- Domodedovo-ATIS - 128.300

    Responder code range: 1540-1577

    :: Current]

    Learning to read Jeppesen diagrams


    For example, Pulkovo. Approach to lane 28 on the right (the diagram is given as an example and is not current at the moment).

    Let's go. Map title:

    1. Airport code according to ICAO. His name.

    2. Date of last revision.

    4. City and country of the airport.

    5. The procedure for which this card is intended.

    Band number. Communication (frequencies):

    1. Frequency ATIS (Automatic Terminal Information Service) - an iron woman, a voice recorded on tape and broadcasting information about the airport such as weather, operating lanes and other useful information in a circle. 127.4 MHz in this case. In Russia it is also called the Meteo service. Here's what it sounds like:

    2 - 4. Approach control center frequencies. We work with “Approach” when approaching the airfield area, when crossing the transition altitude. They report the conditions for entering the zone, the conditions for completing the approach (STAR). When departing, coordinate the exit point from the airfield area.

    2. Frequency used during the time period from 4 am to 8 pm for aircraft with a true sector heading of 360 to 180 degrees (easterly direction).

    3. Frequency used during the time period from 4 am to 8 pm for aircraft with a true sector heading of 180 to 360 degrees (westerly direction).

    4. Frequency used during the time period from 8 pm to 4 am (Greenwich Time, also known as GMT, also known as Zulu Time).

    5. Frequency for communication with the near-field dispatcher. There is no “Circle” zone in the Western radio exchange system. The “Circle” service protects us at an altitude of 200 meters (the “Start” service operates below), assigns a safe altitude (usually 1800 meters) and gives instructions on leaving the airfield area. This is during takeoff. When landing, "Krug" allows the approach and adjusts its pattern.

    6. Frequency for communication with the Start service. During takeoff, she is asked for permission to take control and for takeoff, and she conveys to us the conditions for leaving the airport area. When landing, we must declare readiness for it or go around. Area of ​​responsibility up to a height of 200 meters. Above is the area of ​​responsibility of the "Circle" service. After landing and clearing the runway, we contact this service, thank and say goodbye, switching to the “Taxiing” service.

    7. Frequency for communication with the dispatcher “Taxiing” (Ground). At this frequency they ask for permission to start engines and taxi. In this situation (landing), we must be informed of the taxi route and parking location.

    Navigation letters and numbers:

    1. Localizer frequency. IPL - identifier - these three letters in Morse code are constantly transmitted on this frequency.

    2. NDB frequency. An asterisk (*) means that this beacon operates intermittently. At Pulkovo they change the direction of takeoff and landing twice a day - I see this almost every day from my kitchen window.

    6. During an ILS landing, the decision altitude is 266 feet. "H" in brackets - height - height above the airfield.

    7. 440 feet - MDA (Minimum Descent Altitude) - the minimum altitude to which descent is allowed during an approach using non-precision systems, in the absence of visual contact with landmarks.

    8. Apt Elev - elevation of the airfield, in other words: the highest point of the runway. RWY is the height of the runway at the point of contact in feet above sea level.

    9. Instructions for second approach.

    10. MSA - minimum safe altitude in the specified sectors. "Aiport" - an indication that there is an airport in the center of the circle. Circle radius is 25 miles by default.

    11. Additional information regarding the procedure is written here. Alt set - setting the altimeter. Here, millimeters (MM) are used by default, and hectopascals are used on request. QNH on req (QFE) - the barometric pressure at sea level is given by the ATS on demand. Transition altitude - transition height. Below this altitude, the altimeter is adjusted to the pressure above sea level. Above - 29.92 inches of mercury or 1013.25 hectopascals (millibars) or 760 mm of mercury. Transition level - transition echelon, where the altimeter is reset from 760 mm to the real pressure at sea level. FL 49 - 4900 feet. The unit in the black circle is a note that we will remember a little later.

    The actual map

    And here are its details:

    The VOR is pictured here. From the footnote we understand that it refers to St. Petersburg. That its frequency is 113.4. That on this frequency three characters "SPB" are transmitted in Morse code. Below is what it sounds like: three dots, dot-dash-dash-dot, etc.

    The letter "D" means that the VOR is equipped with a DME system.

    Marker combined with NDB. NDB is a circle consisting of three rows of dots. The marker is a gray cigar-shaped thing.

    The shadow of the footnote (around the rectangle) indicates that this beacon is crucial for navigation.

    In the footnote: the frequency of the beacon and the code it broadcasts.

    		ILS parameters: landing course, and ILS frequency.

    This was discussed above - in the section “Navigation letters and numbers”. Note refer to the instructions for the transition level.

    Level 5900 feet if the pressure is between 706 and 733 mmHg. Level 6900 feet if pressure is below 706 mm.

    30-40 is part of the coordinate grid. 30 degrees, 40 minutes east longitude.

    A drawn tower shows any tall man-made structure. In our case, its height is 1022 feet. The thick arrow shows that this is the tallest structure in the airfield area.

    		The triangle represents a path point (intersection). Its parameters are also described here, which read as follows: At a distance of 11 nautical miles from the VOR SPB, with a radial of 091 degrees, the altitude should be 3020 feet (or 2954 above the end of the runway).

    069 degrees is the course from NDB to the next waypoint (intersection). 7.6 - the distance between these two points in miles.

    The dashed line shows the boundaries of the no-fly or restricted-fly zone. The letter "R" means it is forbidden. If there was an "R" then it would be a restricted area. UL(P)-22 - name (index) of the zone.

    		Conversion table. The column on the left is the altitude above sea level in feet, on the right is the altitude above the airfield in feet and meters.

    The dotted line shows the missed approach.

    Solid black does NOT mean that you MUST follow it when planting. See the STAR map (more on this later). Here it is a recommendation for landing after a missed approach.

    Landing profile

    1. Follow the middle marker at an altitude of at least 262 feet.

    2. OCA - Obstacle Clearance Altitude - safe height for clearing obstacles - minimum height above the runway threshold is 28 P. Each height for its own category.

    3. TSN 50" - the height of crossing the threshold of the strip. 50 feet, therefore.

    4. LMM - middle marker. The shaded figure represents the marker. Gray - NDB.

    5. LOM - long-range marker. When crossing this point on the glide path, the altitude should be 722 feet (656).

    6. From LOM to missed approach point 1 mile. MAP - missed approach point. The departure point is shown by an arrow with the letter "M". The second arrow - the one below - is the decision height.

    7. Glide path entry point (marked with a cross). "D 7.5 SPB" - distance to VOR SPB - 7.5 miles. 2040 - altitude for entering the glide path.

    8. The arrow indicates that for those landing on the NDB, the altitude at LOM should be 730 feet.

    9. The numbers above the line (1.7 and 4.5) show the distance between adjacent points. The numbers BELOW the line (0.5 and 2.2) show the distance to the strip threshold.

    Conversion table, light markings and missed approach

    1. The table shows the relationship between crafting speed and vertical speed when landing. For example, at 120 knots the vertical speed should be 570 feet per minute. And after crossing the LOM point, there are 30 seconds to the missed approach point.

    2. HIALS - High Intensity Approach Light System. The picture shows what kind of light awaits us in front of the end of the strip.

    3. Just some kind of comic (story in pictures) about a missed approach. The comic reads like this: if Missed approach, then we gain an altitude of 2040 feet, while moving on course 279. Then we make a left turn to NDB PL (frequency 525), for those who cannot determine by the arrow which is right and which is left, it is written: "LT" - Left Turn. Upon reaching PL, we climb to 3020 feet.

    Landing minimums

    The current visibility state in the airfield area is reported by the ATIS service. If visibility is below the specified parameters, then, most likely, you will have to leave for an alternate airfield.

    1. Minimums for ILS: decision altitude 266.
    FULL - fully switched on light lane markings.
    ALS OUT - with approach lights turned off.

    2. RVR - stripe visibility range. That is, the range at which a pilot located on the axis of the strip can distinguish its markings.
    VIS - visibility on the strip surface.

    3. When the approach lights are turned off, the minimum visibility range of the runway is 1200 meters.

    4. Landing by localizer (without GS activation) is prohibited.

    5. NDB landing minimums. Here in the left column there is a gradation by category.

    [:: Current]

Publications on the topic