* It is known that there are obvious MISALIGNMENT between the ILS localizer track and the runway in case you are using navdata from 3rd vendors like Navigraph or payware aircraft like Fenix A32X. However the runway for this airport is placed in alignment with satellite imagery, which is most accurate so I decided not to make the runway to align with the ILS for the case stated above. DO NOT USE AUTOLAND and fly manually on short final*

When I was making the Afghanistan Airstrip Pack, I found this airport on Google Map at the border between Tajikistan and Afghanistan, and it is missing in the game. I search on this website, no one made this, so it's my turn again.

The runway of this airport is obviously inclined, which the elevation difference between runway thresholds is more than 40M. Takeoff and landing could only be conducted at the south of the airport, although I don't think it is technically challenging at the opposite side. The only precaution is that don't fly at the east of the airport if you are not flying to/from Afghanistan, as it is very close to the border.

The size of the terminal is very small comparing with the size of the apron. All the parking spaces are taxi-in taxi-out, which means no pushback is needed although there will be one in the sim. Although the runway is longer than 3KM, you are recommended to land not faster than 140KIAS if you can, otherwise you maybe unable to stop the plane before the last exit (TWY C), then you need to keep taxi forward to the end of the runway and then turn back to enter TWY C.

Now the navdata and the scenery have been separated. Just delete the file "navdata-utdk.bgl" if you have subscribed 3rd party global navdata from vendors like Navigraph to prevent conflicts. Also check here if you experience the very common "double runway" issue:
https://www.youtube.com/watch?v=JzOTMAh7wIw

--
Welcome to subscribe my channels for MSFS live game-play:
https://www.youtube.com/channel/UC21efZOlIujoYpzzCGoiYfQ
https://www.twitch.tv/kychungdotcom