THE AIRPORT WE FLY FROM
UZTTUTTT

One Tashkent. Different references across the simulator setup.

A flight can begin with a mismatch long before the aircraft moves. At Tashkent, our local FSHud investigation led through the scenery definition and the airport references inside AI traffic plans. The owner now reports that the combined work resolved the local problem.

Why the identifier mattered

The useful starting point was to compare what each layer called the airport: the VA booking, the installed scenery, the navigation source and the traffic-plan files. Seeing Tashkent in one application did not establish that every other layer used the same reference.

Our booking identifier remains UZTT. We treated the simulator compatibility work as a local setup investigation, preserving the company network and keeping reversible copies of the files involved.

The work behind the result

  • 01 / THE AIRPORT

    Align the scenery.

    The installed 27 October intervention replaced the airport scene BGL in dstf-uttt-middleasia with an ICAO-aligned build, updated layout.json and added zzzz-tashkent-icao-retirement for the old UTTT definition. The audit records backups, hashes and installed ICAO alignment.

  • 02 / THE TRAFFIC PLANS

    Match the airport references.

    The separate 29 October AIG preparation converted UTTT → UZTT in copies of 68 AIGFP archives: 788 departures and 788 arrivals, with 431 route definitions aligned. Flight numbers, schedules, aircraft and intermediate waypoints were preserved. These are AI traffic plans, distinct from your own OFP.

  • 03 / THE RESULT

    A local solution, with dated evidence.

    On 30 October the owner confirms that the local problem was resolved, including flight-plan changes. The available 29 October traffic report still records an offline preparation, not an installation or a post-import FSHud traffic test. That report does not establish the final import sequence.

What another pilot can take from this

  1. Map the layers first. Record the identifier shown by the scenery, FSHud, navigation database and the relevant flight-plan source. A successful airport lookup alone does not establish SID/STAR, ground or traffic behaviour.
  2. Keep the VA booking at UZTT. The local compatibility work is not a change to the VA network or imported route identifiers.
  3. Preserve a reversible baseline. The documented scenery work retained original files; the AIG work used separate prepared copies and exact structural comparisons.
  4. Verify the application result. Check airport recognition, procedures, ground interaction and actual AI arrivals/departures separately on the relevant software/scenery versions. Use a supported import/refresh method; no database reset or blanket code replacement is established here.

Evidence and reproducibility
The scenery installation is documented; the working outcome is owner-confirmed. The final traffic-plan installation/import sequence is not established by the available offline report. This case is not a universal downloadable patch or a copy-and-paste recipe for every FSHud installation.

Developer hotfix · 2.1.209

On 29 October, the FSHud developer account announced version 2.1.209 as a hotfix for two items directly relevant to this setup: AIRAC 2611 importing and a compatibility issue with Fenix A320 V3. Pilots using both products should check their installed FSHud build before the next Fenix sector.

Keep the evidence separate.
The developer hotfix is a new general compatibility record. It does not establish that 2.1.209 is installed on the owner’s PC, and it is not evidence that the separate Tashkent UZTT/UTTT scenery and AIG-plan case has been retested with this build.

Sources: local modification audit (27 October work, reported 28 October); AIG offline preparation report (29 October); owner confirmation (30 October); FSHud 2.1.209 developer announcement (29 October). The company notice keeps the operational context and identifiers together.

Read UZB-NAV-002/26 in Phoenix →FSHud 2.1.209 announcement ↗FSHud official resources ↗

The evidence, in order

27 OCTOBER / INSTALLED SCENERY WORK

The airport definition

The modification audit records the BGL change, layout update and retirement package, with backups and hashes. It establishes installed ICAO alignment.

29 OCTOBER / OFFLINE TRAFFIC PREPARATION

The AI plan references

The separate report records 68 prepared archives and 1,576 Tashkent legs: 788 departures and 788 arrivals. Its explicit status is NOT INSTALLED. It does not establish the final import sequence or a post-import traffic test.

29 OCTOBER / DEVELOPER HOTFIX

FSHud 2.1.209

The FSHud developer account announces fixes for AIRAC 2611 importing and Fenix A320 V3 compatibility. This general hotfix record remains separate from our local Tashkent evidence and does not prove the build is installed here.

30 OCTOBER / OWNER-CONFIRMED RESULT

The setup now works locally

Riccardo reports that the scenery and flight-plan changes resolved his local problem. This is the latest operating report; it is separate from the narrower file evidence available in the earlier audits.

Sources and scope

Our source record consists of the local modification audit covering the 27 October work, the 29 October AIG offline preparation report, the FSHud 2.1.209 developer announcement and the owner’s 30 October confirmation. The company notice links the operational context together. Internal audit files and modified scenery binaries are not distributed here.

This is a company case report. AI traffic plans are separate from the pilot’s SimBrief OFP. Use the current developer documentation for supported installation and refresh methods; do not treat a public hotfix announcement as proof of the locally installed build.