Destination briefing
DISCONNECTEDAirport context awaits your OFP
- Terminal
- Pending
- Apron
- Pending
- Stand
- Pending
- Basis
- No local assignment
- Availability
- No live airport or simulator occupancy feed
UZBEKISTAN AIRWAYS VIRTUAL / FLIGHT OPERATIONS
Arrival desk
UZB OPS 0.6.3— UTC
COMPANY WEBSITE / UZB OPS
Your flight desk. Now on the website.
Use your existing UZB Ops tools here. The Windows companion connects this tab to MSFS, local scenery and Fenix on your simulator PC.
- Start the updated companion. Extract the complete 0.6.3 website beta, run SETUP_WINDOWS.cmd, then START_UZB_OPS.cmd. Close the previous companion console first.
- Generate a connection code. In its local browser window, select “Generate connection code”. Enter that code below on the same PC.
- Connect, then prepare your flight. Allow local network / loopback access if Edge or Chrome asks. Load your OFP and connect MSFS using the tools below.
Not paired. No simulator data is being requested from this PC.
UZB Ops 0.6.3 · Windows · Separate beta downloadSetup & limitations
Flight data stays between this tab and your PC; this page does not upload it to the website. The connection key stays in memory and is cleared on reload. Use the local Crew Deck setup for a separate tablet. vAMSYS and Pegasus continue to manage bookings, PIREPs and VA progression.
Waiting for UZB OpsConnecting to the local companion…
No successful contact yetThis tab belongs to a different UZB Ops version. Reopen START_UZB_OPS.cmd from the new folder and use the tab it opens.
COMPANY ARRIVAL SERVICES
Every arrival. A little closer to home.
CONNECTING
NO ACTIVE FLIGHT
Your next arrival
Load the OFP generated for your booked flight.
ESTIMATED TO LANDING—Landing estimate unavailable
YOUR NEXT DESTINATION
Destination photography
Destination photograph. Displayed with a crop and a dark gradient; the original retains its listed licence.
01
Flight planLoad your SimBrief OFP
02
Aircraft linkConnect MSFS
03
Company dispatchDisarmed
SECTOR WORKSPACE
Provenance, notice review and your personal debrief.
Arrival estimate
Strict mode uses a crew-entered current FMS estimate, or a simulator GPS estimate whose aircraft integration you have verified. SimBrief supplies the initial planned airborne time; planning estimates remain labelled until updated.
Load an OFP to fill the planned airborne minutes.
Confirm the displayed minutes against the current aircraft FMS before applying a crew update.
Crew-entered estimates count down with simulator time and expire after 15 minutes. Refresh if your route or holding changes.
Local allocation
Applies to this flight and destination only; expires after one hour. Scenery compatibility is not automatically established.
Company message
AOC / TELEXUZBEKISTAN AIRWAYS VIRTUALOPERATIONS / ARRIVALMESSAGE PREVIEW
LOAD YOUR FLIGHT FIRST
UZB DISPATCH / COMPANY COMMUNICATIONS
Waiting for flight data.
Preview sends nothing. Once live dispatch is armed, a crew request can transmit immediately when workload permits.
Connection status
- Simulator
- Not connected
- Hoppie
- Not configured
- vAMSYS
- Booked-flight OFP via SimBrief. Direct account API is not connected.
- Aircraft
- TELEX: MCDU AOC received messages. EFB: optional saved briefing in Documents.
This checks Python and the SimConnect DLL separately from the aircraft connection. It does not send messages.
YOUR COMPANY, IN THE COCKPIT
Bring the briefing to your EFB.
A UZB document pack for the Fenix Documents app, with optional briefing updates from this PC.
Diversion
Clears the previous stand and ETA, then disarms dispatch for the new destination.
YOUR SECTOR / START TO FINISH
NO ACTIVE SECTORBrief. Fly. Look back.
Keep the source in view, review company notices and build your own record of the flight.
Waiting for the operations workspace…
Know the source.
DATA PROVENANCE & CURRENCYCurrent means a source was checked against its stated clock and review threshold. An OFP weather snapshot stays a planning snapshot; a manual confirmation stays a pilot entry.
Airport & scenery review
SOURCE CHECK REQUIREDLoad a sector to inspect the destination’s published sources and installed scenery.
A numbered VA planning stand needs a current source, scenery mapping, physical fit and restriction review. A stand supplied by ATC or apron control is a separate local assignment; record it on the Arrival desk.
CREW DECK / READ-ONLY BRIEFING
Your briefing, beside the instruments.
Sharing is off until you enable it on this PC. Only a minimal sector briefing is shared; notes, accounts, settings and message history stay private.
Company notice review
—Acknowledgements belong to this sector and notice revision. Read the current source before confirming; the offline digest does not synchronise with Phoenix.
Your sector debrief
PERSONAL RECORDLoad your booked flight’s OFP to start a sector record.
Closing a local record does not file or approve a PIREP. Pegasus and your VA remain responsible for tracking, reports and awards.
Previous debriefs
Exports retain data provenance and distinguish previews, network acceptance and pilot-confirmed reception.
CENTRAL ASIA / PILOT PASSPORT
PERSONAL PROGRESSMake every sector count.
Prepare with a purpose, record your own progress and carry a lesson into the next flight. This is your local learning record; course eligibility and VA approval remain separate.
Build your personal route board
Pick routes from the VA catalogue for your own planning. Selection and local completion do not book a flight or certify tour eligibility.
NEW / UZB CREW DECK
One home for your iPad flight deck.
A navy UZB launcher for the external EFB, MCDU and cabin FAP, with Home, Back and EFB controls outside the original Fenix panels.
On the simulator PC, run START_IPAD_DECK.cmd, then open the address it prints on your iPad over the same Wi-Fi. Paste your actual MCDU and FAP tab URLs once. See IPAD_CREW_DECK.txt. Embedded panels require compatibility testing with your Fenix version; a separate-tab option is included.
The cockpit tablet continues to use Documents → My Documents → UZB_Ops. Crew Deck is an external launcher.
UZBEKISTAN AIRWAYS VIRTUAL / FENIXYour company.
Your company.
Your flight deck.
Bring UZB arrival briefings and crew documents to the Fenix EFB using its supported Documents feature.
FENIX WITH DOCUMENTS SUPPORT · WINDOWS PCIN YOUR FENIX EFBDocuments↓My Documents↓UZB_Ops15 crew documents · Current-sector briefings
Connect the EFB briefing
NOT ENABLEDChecking this PC…
- Updates
- Every 15 seconds while UZB Ops stays open
- Last saved
- Not yet saved
- Folder
C:\ProgramData\Fenix\EFB\Documents\UZB_Ops
Enable this on the Windows PC running Fenix. The button writes only UZB Ops files into its own Documents folder. If the folder is unavailable, open Fenix Documents first and check your installed Fenix version.
Prefer a manual install?
- Download the document pack below and extract it.
- Copy its
UZB_Opsfolder intoC:\ProgramData\Fenix\EFB\Documents. - In the aircraft, open Documents → My Documents → UZB_Ops.
Downloads are static copies. Automatic updates need the companion running with EFB briefing enabled. Reopen the document if your EFB does not refresh it.
BRIEFING CONTENT
Your company flight bag.
- SimBrief flight release: route, fuel, loading and planned UTC dates
- Initial airborne minutes from your OFP, with crew updates
- OFP METAR / TAF and planned alternates
- Departure, destination and alternate airport cards
- Arrival stand source and company message preview
- Interactive crew checks and briefing prompts
- VA operations, dated notices and irregular operations
- Crew resources, PDF planning card and revision register
The EFB shows a saved briefing. The live controls stay in this console, and received TELEX stays in the aircraft's MCDU AOC inbox. No custom EFB home-screen icon is installed.
THE UZB CREW COLLECTION
A flight deck of our own.
Our new signature wallpaper joins the original crew collection. Four full-size PNGs, available offline without SimBrief, Hoppie or a simulator connection.
NEW / SIGNATURE WALLPAPER
Registan Afterglow
Silk Road architecture, midnight blue and warm gold. Created for your Uzbekistan flight deck.
2028 × 1536 PNG · Space reserved for the native Fenix icons.
Download Registan Afterglow →
Fenix format · 2028 × 1536 pixels · VA emblem and wordmark
Download the complete wallpaper collection (ZIP)Apply your wallpaper in Fenix / Come impostare lo sfondo
- Save one PNG above to your simulator PC.
- Load the Fenix aircraft into a flight.
- On that same PC open the Fenix web EFB settings, find Wallpaper and use Upload to select your downloaded PNG.
The Fenix web EFB is a separate local service. Check its availability here before opening it. Downloads above remain available even if Fenix is closed.
On a phone or tablet, use your configured external Fenix EFB address: localhost refers to the device you are using. Wallpaper selection is manual.
Official Fenix references
Documents, checklists and supported links ↗
How do I see it on the Fenix tablet?
Run this companion on your simulator PC, open Fenix EFB and select Enable EFB briefing. In the aircraft tablet, open Documents → My Documents → UZB_Ops for the company briefing and checklists. A Fenix version supporting Documents is required.
The interactive desk stays in your browser. The Documents reader displays saved documents. The companion refreshes the saved briefing every 15 seconds; always check its UTC timestamp.
FIRST FLIGHT / CONNECTION WALKTHROUGH
Two accounts. One connected flight deck.
Find both identifiers below, then save them in the form. Your SimBrief account supplies the OFP; Hoppie carries company TELEX to your aircraft.
01 / FLIGHT PLAN
Find your SimBrief Pilot ID
- Open SimBrief Account Settings ↗ and sign in with your Navigraph account.
- Find Your SimBrief Data → Pilot ID and copy the numeric value.
- Paste it into SimBrief Pilot ID or username below. The account alias also works.
Use the same account that vAMSYS uses to generate your OFP. Example ID: 123456. Keep your Navigraph password on the SimBrief website.
02 / COMPANY MESSAGES
Get your Hoppie logon code
- Open Hoppie · Get Logon Code ↗ and complete the personal registration yourself.
- Check your email, including spam, for the ACARS logon code.
- Paste that code here and into your aircraft's Hoppie settings. Both must use the same code and Hoppie network.
Keep this code private. Use My ACARS Account to check your network. Re-requesting with the same name and email resends a valid code; an unused code expires after 120 days.
03 / FENIX A320
Enter the Hoppie code in the Fenix desktop application before opening MSFS. In the aircraft, enter the flight number on MCDU INIT. Match the UZB Ops recipient to the identifier actually used by the aircraft, for example UZB282.
I cannot find my code
SimBrief: open Account Settings, find Your SimBrief Data and copy the numeric Pilot ID. Your VA pilot number, VATSIM CID and email are different identifiers.
Hoppie: request your code on the official website and check your spam folder. Use the same code in the companion and Fenix. To recover it, request it again using the same name and email address.
No OFP found? Generate the booked flight in the correct SimBrief account, then use Load SimBrief OFP. Saved connection settings alone do not create a flight plan.
No message in the cockpit? Check the recipient callsign, Hoppie code and network, then the MCDU AOC received messages and printer. Network acceptance alone is not proof of cockpit delivery.
Your flight deck connection
On Windows the Hoppie code is protected for your Windows user with DPAPI. The password field clears after saving; “Code configured” means it is stored, not yet delivery-tested. Enter it on your own PC. Keep credentials out of support screenshots.
YOUR SIMULATOR / SCENERY
NEEDS REVIEWKeep track of your installed scenery.
Check scenery on your PC and compare its version and build with your saved inventory. Changed files flag a build for review; this does not certify gate compatibility.
No scenery check loaded in this session.
| Airport | Scenery / local build | Inventory comparison | Stand suitability |
|---|
Select Check scenery to create or refresh the local inventory.
Two separate checks. An unchanged or recognised build does not establish stand mapping, aircraft fit, restrictions or availability. ATC/apron assignments remain separate from VA planning.
THE UZB DESTINATION COLLECTIONA world worth arriving in.EXPLORE THE NETWORK
Real destination photography across our network. The arrival banner follows your flight automatically; this collection lets you explore the places behind the ICAO codes.
No matching destination.
Airport-specific stand validation
Planning contexts loaded from the VA's existing network.
Numbered VA planning requires a current source, the exact installed scenery and version, a stand present in that scenery, an aircraft-specific physical fit check, the correct operation type and a current restriction review. Live occupancy remains unknown.
The supplied template is deliberately inactive. Its physical-fit and scenery checks are false; fill it from the actual current charts and installed scenery. Tashkent B4/B5 and D14–D17 are conditional VA preferences, not airline-reserved allocations.
Recent company messages
PERSISTENT FLIGHT LEDGER“Accepted by Hoppie” confirms network acceptance only. After an uncertain send, check the aircraft inbox and resolve it here before rearming.
Updating from an older version
Extract the new ZIP completely into a new folder and run SETUP_WINDOWS.cmd there. Use the browser tab it opens and check UZB OPS 0.6.3 at the top. If an older copy still occupies the usual address, this release opens a different local address and shows a notice. Close the old black console with Ctrl+C; closing its browser tabs does not stop the old app. Live dispatch and automatic EFB writes wait for that older copy to close. Starting this same folder again reopens the existing current instance.
Before your first flight
- Open Connections and follow the numbered setup cards. They link to your SimBrief account settings and the official Hoppie registration page.
- Configure the same Hoppie code in the Fenix app before launching MSFS, and enter the flight identifier on the MCDU INIT page.
- Generate your booked flight's SimBrief OFP. Load it in UZB Ops, then connect MSFS.
- Check the displayed flight, destination and operation. In strict mode, enter the current FMS landing estimate shortly before the arrival window.
- Record a local stand assignment if you receive one, or use a fully validated scenery profile. Otherwise the message correctly says STAND PENDING.
- Confirm the callsign and aircraft, then arm live dispatch. Keep this app running for the flight.
Need help with your identifiers?
Connections includes official links, field examples, code recovery advice and an Italian troubleshooting section. SimBrief uses your numeric Pilot ID or account alias. Hoppie uses the personal ACARS logon code emailed to you. The latter is separate from your VATSIM CID and the four-letter CPDLC ATC facility identifier.
What happens during arrival
The default window is 30 minutes before estimated landing. This is a configurable VA policy. Routine messages wait during pause, slew, speed-up, takeoff, approach and go-around. In taxi-in, a crew request retrieves operational arrival information when needed.
Inspect messages under MCDU → ATSU → AOC → received messages. Fenix's COMPANY MSG notification may be absent when automatic printing is enabled.
What this release verifies
The app reads simulator data, fetches the current OFP and sends compact TELEX through Hoppie. It does not control MSFS, FSHud, GSX or the aircraft. The optional Fenix Documents bridge saves a read-only briefing in the EFB; live dispatch controls remain in this console. It does not reserve stands, determine taxi clearances, or claim access to real-airport gate allocations. Airport templates and the Windows/Fenix integration require acceptance testing on your PC.