What UZB Ops adds

Your next arrival starts with the right sector, a believable estimate and a clear source for the information you read. UZB Ops brings those checks into a company companion and a Fenix document pack.

The public download currently identifies itself as 0.6.2, public beta, dated 27 October 2026. That is the distributed package, not confirmation of the version running on your PC. Its arrival desk sits alongside sector preparation, scenery checks, the Crew Deck and personal debrief notes.

UZB Ops on the website: Open the interactive flight desk →. Pair it with the separate 0.6.3 Windows website beta to use your local simulator tools. Bookings and PIREPs stay in vAMSYS/Pegasus.

Start with the official VA download and installation page →. This guide covers the documented workflow; Windows simulator integration and aircraft message reception are separate acceptance checks.

Set up the first sector

  1. Prepare between flights. Extract the complete current package, follow READ_ME_FIRST.txt and retain the existing data folder as directed. Check the version shown by the console.
  2. Match the booking. Generate the SimBrief OFP for the booked flight, load it in UZB Ops and connect MSFS. Compare the callsign, aircraft, departure and destination before enabling optional dispatch.
  3. Read the time source. The initial estimate comes from planned airborne time. It is different from block time and from the company-message trigger.
  4. Review before arming. Check the current estimate, sector and notices. Hoppie configuration is needed for optional TELEX; ordinary briefing preparation does not establish a message was delivered.

An arrival estimate needs a source

Strict dispatch uses a current crew-entered FMS estimate or verified simulator GPS timing. A crew estimate expires after 15 minutes and counts down in simulator time. Native GPS can differ from the Fenix FMGS, so read the source label rather than assuming both are identical.

The nominal trigger is about 30 minutes before estimated landing. It is not a promise that a message will arrive at exactly that minute: phase, workload, connection and dispatch conditions also apply. Planning estimates require an explicit opt-in for automatic use.

What STAND PENDING means

It means a numbered stand has not been established. UZB Ops has no live airport gate feed or stand-occupancy feed. The reviewed package ships no active numbered-stand profile; its Tashkent draft is a template.

A locally entered allocation must retain its ATC, apron or operations source. A planned VA preference needs valid scenery/build evidence, aircraft fit and a current restriction review. The scenery scanner can flag package changes; it cannot establish physical fit or current occupancy by itself.

A stand displayed by a companion, the stand selected in GSX and an actual ATC allocation describe different things. Compare them before taxiing. A request for arrival information cannot create evidence that is missing.

Bring the briefing into the Fenix

Enable EFB briefing in UZB Ops, then open Documents → My Documents → UZB_Ops in the aircraft. Six sector documents refresh while the companion runs; check their UTC timestamp and reopen a document if an old copy remains visible.

A manually downloaded Crew Kit is a static snapshot. Crew Deck is a separate external-browser/tablet view. Its supported links and separate-tab fallback are explained in the package; successful iPad framing and native cockpit rendering are not established by a desktop preview.

TELEX is read through the aircraft’s AOC interface. An EFB preview, a queued message and server acceptance are different delivery states.

Connection loss and the next rotation

Version 0.6.2 documents corrections to approach-state retention and reconnection. A terminated simulator connection or backward simulator-clock jump invalidates earlier phase/estimate history. Dispatch stays disarmed after connection loss; review the aircraft, sector and ETA before rearming.

For a turnaround, finish the previous monitoring session before loading the newly generated OFP. Check that the new sector and estimate actually replace the old ones. An active-sector lock is a guard against replacing the flight being monitored; generating a new SimBrief plan alone does not switch that session.

The release’s validation covers offline tests and mocked interfaces. It does not certify consecutive live rotations, all simulator-session changes, Hoppie reception or iPad/Safari acceptance.

Before relying on the arrival desk

  • The console shows the expected version and a current connection.
  • Booking, loaded OFP and aircraft agree on the sector.
  • The landing estimate has a current, understood source.
  • Any numbered stand has identifiable evidence for this scenery and aircraft.
  • The latest document timestamp belongs to this sector.
  • After reconnection or a turnaround, the flight is reviewed before dispatch is armed.

Release record and sources

Editorial review: 30 October 2026. The current distribution and its installation, release and validation records were inspected. The package checksum matched its manifest; the app was not installed or run for this article. Use the current distribution link when comparing an older 0.5.1 copy.

Use Pegasus and Phoenix for official VA flight records and activity credit. Personal companion progress is preparation and reflection, not an accepted PIREP.