TASHKENT LOCAL ACCEPTANCE CARD / UZBEKISTAN AIRWAYS VIRTUAL
Prepared 30 October 2026. Not a request to install patches or reset databases.

UTC date/time:
MSFS build / graphics preset / resolution / frame generation:
Fenix build / aircraft configuration / active AIRAC:
Scenery package / manifest version / locally modified files:
FSHud build / traffic source / AIG build and schedule time basis:
GSX build / airport and aircraft profiles:
UZB Ops version / booking pair / new OFP created at:
Weather / simulator time / runway / camera:

CHECK / OBSERVED RESULT / PASS-FAIL-NOT TESTED / EVIDENCE
1. Booking UZTT; identifiers shown by simulator, scenery, FSHud and navdata:
2. Airport integrity: doubled runways, lights, signs, stand numbering:
3. Recognition and published procedures in FSHud and aircraft:
4. Ground interaction, one pushback initiator, GSX placement and clearance:
5. Observed AI arrival AND departure; source, scheduled time basis and observation window:
6. First sector: booking, tracking, arrival and stand source:
7. Return: fresh booking/OFP; Pegasus and UZB Ops show the second sector:
8. If performance is compared: unchanged conditions, sample duration, repeated runs, FPS/frame time and frame-generation status:

Changes made during this test (prefer one variable at a time):
Original state / reversible baseline / supported rollback route:
Conclusion and limits:

Do not include pilot passwords, Hoppie credentials, personal IDs or unrelated desktop details.
Keep modified payware BGLs and licensed traffic archives on your PC; do not redistribute them.
An absence of AI in one observation window is not proof of an ICAO fault.