UZB7414 / PILOT RESOURCES
Every flight. One company standard.
Booking, aircraft preparation, loading, VATSIM identification, Pegasus tracking and PIREP review across every operation.
Flight standards, aircraft categories and practical preparation for our virtual airline.
Flight standardsFleet validationChoose a serviceRoute labelsLoading & performanceTrack & reportActivities & sound
Flight standards and PIREP review
Operating rules for new and returning pilots · 26 October 2026
Fly at normal simulation speed (1×), track the actual flight with Pegasus and use the aircraft and registration shown in the booking.
Time-acceleration use and a gear-up landing are configured as rejection rules. The platform’s fixed-gear exception applies; report a suspected telemetry issue to staff.
An in-air fuel increase, negative score, diversion, excessive landing rate or G, multiple landings, or landing below final reserve triggers staff review under the active rules. Explain abnormal operations and recording problems in the PIREP; a review flag is not proof of misconduct.
If staff mark a PIREP as requiring your reply, respond in the PIREP comments within 7 days. The platform automatically invalidates an unanswered PIREP after that reply window. An ordinary support email does not replace the required PIREP reply.
Go-arounds and diversions are operational decisions to explain honestly. Use the current aircraft procedure and conditions; never continue an unsuitable approach or change configuration only to gain points.
Activity windows are in UTC. Follow each event’s registration, aircraft, airport, sequence and timing requirements.
Fleet scoring coverage — assignments checked 1 November 2026
All 12 fleets currently use eight assigned groups: seven fixed-wing Operational 100 R1 groups and Helicopters | Procedural checks for H125/H130. Fixed-wing regular points have a nominal maximum of 100; the helicopter group retains 50 for the flight record plus 5 for engine shutdown. Use the current native Scores page for the complete configured conditions.
Category standards and first-flight validation
R1 fixed-wing scoring starts at 0, with a nominal maximum of 100 regular points: Flight closure +5, Engine warm-up +5, Engine cool-down +5, Takeoff configuration +10, Landing configuration +10, Final reserve protected +25, Dispatch fuel compliance +10, Touchdown rate +5, Touchdown load +10, Taxi discipline +15. Flight duration and online network do not add regular points. Activity bonuses remain separate; promotion uses credited hours and accepted PIREPs, not points.
R1 validation — staff review of every PIREP. The current native Failure Rules table displays “R1 Validation - All PIREPs Require Staff Review”, applying to all PIREPs. Processing and scoring still occur, but every report is routed to staff review during this validation phase. This informational update does not change any operational configuration. A report marked Reply Needed blocks new flights until you reply; answer on that PIREP within seven days.
Aircraft-specific configurations. The observed minimum values are A320ceo 1+F / 3+F, A320neo and A321LR 1+F / 3, B767 and B787 5 / 25, ATR 72 15 / 30, L-410 18 / 42, and PC-24 8 / 15 (takeoff / landing). The current neo labels specify CONF 1+F, 2 or 3 for takeoff and CONF 3 or FULL for landing; Boeing labels specify takeoff 5–20 matched to the performance calculation and landing 25 or 30. A configured minimum or label does not prove that telemetry enforces every upper limit or certifies an aircraft procedure. Validate add-on mappings and follow the aircraft performance calculation and checklist.
Fuel, engine timing and taxi. Dispatch fuel below the SimBrief plan is tolerated by 100 kg for the A320 family, 200 kg for B767/B787, and 50 kg for ATR/L-410/PC-24. The displayed +1,000,000 kg upper scorer tolerance is not an aircraft fuel or mass allowance. Final reserve is compared with the matching OFP (+25 protected / −30 below reserve). Taxi reward/penalty is +15/−15 with 10 seconds of accumulated overspeed. Warm-up minima are A320ceo 3 minutes, neo/A321LR 5, B767/B787 3, ATR/L-410 2 and PC-24 2; cool-down minima are A320ceo/neo/A321LR/B767/B787 3, ATR/L-410 1 and PC-24 2 minutes. The native cool-down labels use the 30 kt reference. Use the actual aircraft procedure and explain telemetry mismatches.
Prepare here. Operate in Phoenix.
Open the public Pilot Centre →
Full fleet-specific scoring tables → · Current native Scores →
Booking, tracking, PIREPs and personal progress remain in the authenticated pilot portal.
ATR 72 and L-410: use the correct turboprop checklist, loading, fuel, performance and engine/propeller procedures. R1 awards +10 for each qualifying takeoff and landing configuration, with −20 / −25 penalties below the configured minima. ATR minima are 15 / 30; L-410 minima are 18 / 42. Validate telemetry mapping for the exact add-on/version and report any mismatch for staff review.
PC-24: use the business-jet checklist and actual charter load. The native R1 minimum flap values are 8 for takeoff and 15 for landing; labels refer to position 1 and positions 2/3 respectively. Rewards are +10 / +10 and configuration penalties −20 / −25. Validate add-on mapping and explain abnormal or approved alternative configurations in the PIREP.
Fixed-wing fuel and taxi: use the R1 requirements above and the full native tables. With manual planning, include planned reserve and actual landing fuel for staff review. A scorer result never substitutes for aircraft fuel, mass, performance or procedural limits.
H125 and H130: no flap, wheeled-taxi, two-engine sequence, jet pitch/roll or experimental stabilized-approach scoring is applied in this group. Use the helicopter flight manual for start, rotor checks, warm-up, cooling and shutdown. Plan the full sightseeing route, fuel/reserve, mass and balance, hover/power margins, weather, visual references and turn-back criteria. Record relevant planning figures and deviations in the PIREP; these are operational checks requiring pilot evidence and staff judgement, not telemetry that the scoring engine can certify.
Validation and review: fly one representative sector with Pegasus for each new add-on/version and check engine events, flap detents, fuel data and score against the log. Report a missing or inconsistent reward through Pilot Support with the PIREP reference. Follow the actual aircraft procedure; never change a safe configuration merely to gain points. Company AutoReject/review rules still apply, and an appropriate go-around or diversion should be explained for a contextual review.
Uzbekistan Airways Virtual
Choose a service
Passenger services cover the mainline network, regional flying and selected Express aircraft. Match the booked aircraft, registration and cabin to the simulator profile. Express is an aircraft option within our VA programme, rather than confirmation of the real-world equipment on a particular day.
Silk Avia services use the aircraft offered in the booking. Plan with the correct ATR or L-410 performance and loading information. When a suitable planning profile is unavailable, use the published manual procedure and ask Operations before substituting another aircraft.
Cargo services use the dedicated freighter configuration specified in the booking. The passenger B767 and freighter B767 are separate operational choices even where their ICAO type designator is the same.
Business Aviation services are on-demand VA charters. Set the actual passengers and baggage requested for that sector and verify fuel, performance and airport suitability for the selected PC-24.
Discovery Charters are fictional tourism programmes. Read the roadbook, passenger brief, aircraft requirements and sector order. A proposed group size is subject to the actual payload, fuel and performance limits on each flight.
Helicopter missions require the published VFR sightseeing route, actual mass and centre of gravity, suitable visual conditions and adequate power margins. The booked airport pair does not replace the sightseeing track. Use only the landing locations required by the mission.
Read the route labels
Passenger, Cargo, Business Aviation and Helicopter identify the primary operation. Express and Silk Avia identify the relevant aircraft option or regional programme. Freighter, On Demand, Charter, VFR and Grand Tour describe the service further.
Heritage identifies reconstructed services; Heritage VA network distinguishes reconstructed cargo-network services. Legacy Scenery identifies a sector that needs a period-appropriate airport/scenery plan. Use the source period and service notes to understand the reconstruction. VA-assigned flight numbers and open schedules are not a current commercial timetable. Legacy airports can require a dedicated simulator scenery and navigation plan.
Aircraft loading and performance
Applies to every dispatch. Use the aircraft and add-on documentation for the exact variant, engine and passenger, freighter or other configuration booked. The passenger B767-300ER and B767-300BCF require separate planning and loading configurations even though both use B763.
Match the planning profile
In SimBrief, select an airframe that matches the aircraft being simulated. Check units, operating empty mass, capacity, payload and fuel assumptions against that add-on. Where a suitable profile is unavailable, use the published manual-planning guidance and the aircraft’s own data. Obtain Operations guidance before substituting another type.
Load and check the aircraft
Load passengers, baggage, freight and fuel through the add-on’s supported controls or integration. Confirm the completed load in the aircraft or its EFB; importing an OFP alone does not establish that loading is complete. Compare actual mass, fuel and centre of gravity with the plan, allowing for the relevant phase of flight and documented model differences. Resolve unexplained discrepancies before departure.
Record freight in the correct mass units. Fuel, commercial freight, passenger baggage and container counts are different quantities. A total payload entry alone does not define a safe station distribution.
For cargo, use mass and station distribution, not container counts alone. Check station, compartment, floor and restraint limits where modelled. Verify the applicable mass and balance limits, including zero fuel, take-off and landing mass where published for the aircraft. Maximum fleet capacity is a limit, not a required load.
Calculate performance for the flight
Use a performance tool or manual appropriate to the loaded aircraft, actual mass, runway, weather, runway condition and selected configuration. Recalculate when a relevant input changes. Check fuel and reserves, alternates and suitable stand and handling arrangements. Regional, business and helicopter flights use their own loading and performance data; helicopter planning includes mass, balance and power margins for the intended conditions.
If the booked payload cannot be carried within the applicable limits, resolve the load or fuel plan and contact Operations when the booking needs correction. Apply the tolerances and methods documented for the actual add-on.
Operations Guide
Brief the actual route, weather, fuel and alternate options. A heritage route still requires a workable plan for the simulated conditions used on the day.
Track and report
Applies to all company flights. Read the booked service notes, route tags and any activity briefing before planning. Passenger, regional, cargo, business, heritage, Discovery Charter and helicopter operations retain their published scope and requirements.
Make the Phoenix booking before opening Pegasus. Select the VA and confirm the flight, aircraft and registration loaded by the client. Start tracking before departure and keep Pegasus running until the PIREP has been submitted successfully. Fly at normal simulation speed (1×), as required by the current company rules.
Prepare a new OFP for each sector using an aircraft profile that matches the booked variant and the add-on. Recheck the imported plan after regeneration. Review airport identifiers, route, weather, applicable publications, fuel, reserves, alternates and performance. Where no suitable SimBrief profile is available, follow the manual-planning guidance in Getting Started and the service briefing; ask Operations before substituting another aircraft.
Distinguish real-world aeronautical publications from VA notices and the conditions implemented in the simulator or online network.
VATSIM identification — required
Every company flight flown on VATSIM must identify Uzbekistan Airways Virtual in the filed flight-plan remarks. Dispatch through the VA and use Send to VATSIM on the booking page. Keep the automatically generated company identifier and website when filing or amending the plan. Check that UZBEKISTAN AIRWAYS VIRTUAL is present before submitting the flight plan.
Mainline example: CS=UZBEK=UZBEKISTAN AIRWAYS VIRTUAL
Silk Avia example: CS=SILK=UZBEKISTAN AIRWAYS VIRTUAL
Use the radio callsign of the booked operator and retain all applicable operational remarks. If filing manually or the company identifier is missing, restore the correct company remark before submission. VATSIM PIREP acceptance — mandatory. For company VATSIM flights dispatched after publication of this rule on 27 October 2026, the filed flight plan used for the flight must retain the complete VA identification: the matching CS marker, full VA name and supplied WEB link. A PIREP will not be accepted and will be rejected if that identification is missing, removed or altered so it no longer correctly identifies and links to Uzbekistan Airways Virtual. Keep a screenshot or copy of the filed VATSIM remarks until the PIREP is accepted; staff may request it. Staff verify the filed plan and record the evidence and reason for rejection. An automatically scored report is still subject to this acceptance requirement.
After landing, complete parking and shutdown, confirm PIREP submission and review the report in Phoenix. Explain significant deviations, go-arounds, diversions or recording issues in the PIREP. If a reply is required, answer in the PIREP comments within the published seven-day window. Activity credit follows the activity’s own airport, aircraft, sequence and timing requirements.
Pegasus and Phoenix hold the company flight record. UZB Ops and optional cockpit or ground-service tools support preparation and immersion; their progress or messages do not establish PIREP acceptance.
Getting Started
Pilot Support
Tashkent airport data guidance
Activities and sound
Register for activities that require it before the first qualifying flight. A route label alone does not establish badge eligibility. Follow the activity's fleet, leg and completion requirements.
Passenger cabin announcements belong to the appropriate passenger operation. Freighter operations use their own operational context. Regional and business aircraft should use announcements consistent with the aircraft and service actually flown.
This guide describes our independent flight simulation community and its VA programmes.
Continue your journey
Getting StartedHub BriefingsDestinations & SceneryPilot Support
UZBEKISTAN AIRWAYS VIRTUAL
From Tashkent to the world. · Independent flight simulation community.