Skip to content
Uzbekistan Airways Virtual Pilot Login
Menu

MAINLINE / A320-251N

Airbus A320neo.
Build your neo workflow.

A model-specific path through dispatch, MCDU, FCU, descent and arrival, keeping each developer’s procedure separate.

6 chapters · 20 topics · Simulator guides + official video

Match the aircraft before the procedure.

In our VA
Uzbekistan Airways A320-251N fleet, live Orwell check 30 October 2026.
This guide’s reference
iniBuilds A320neo V2 and FlyByWire A32NX; choose the source matching your loaded package.
Simulator and version context
MSFS 2024 references; the Microsoft Discovery film is a May 2024 MSFS (2020) recording.

FlyByWire explicitly models A320-251N / LEAP 1A-26. The iniBuilds manual is a separate A320neo V2 reference, not an A32NX or Fenix procedure.

WATCH THE PRODUCER

Watch with the aircraft context beside you.

Manufacturer and simulator-publisher material only. The context on each film identifies its aircraft, age and role.

YOUR AIRCRAFT / YOUR STUDY PATH

Find the subject. Take it to the cockpit.

20 topics shown

01

Prepare the right neo

Choose the package, then make the plan and loading agree.

Simulator guide

A320-251N: choose your implementation

Keep the shared aircraft identity and the separate simulator implementations in view.Open this topic

What to understand

  • Our VA type is A320-251N.
  • A32NX documentation explicitly identifies that variant and its LEAP engine.
  • iniBuilds V2 and FlyByWire use their own interfaces and procedures.

Bring it into your flight

Read the aircraft selection and use only the matching source buttons below.

Watch the manufacturer

Official reference

Read alongside: A32NX aircraft configuration; iniBuilds aircraft selection.

Simulator guide

Navigation data before route entry

Planning data and the loaded aircraft database must be understood before an import.Open this topic

What to understand

  • Check the cycle visible in the aircraft.
  • Compare route and procedure names with the planning source.
  • Treat an import error as a review prompt, not permission to remove all discontinuities.

Bring it into your flight

Compare the OFP runway and route with the aircraft’s current database.

Official reference

Read alongside: A32NX Preflight / Nav Data; iniBuilds MCDU and cockpit preparation.

Simulator guide

Make the OFP belong to this aircraft

A livery or family name is not an airframe performance profile.Open this topic

What to understand

  • Match variant, load and fuel units.
  • Generate the plan for the actual VA booking.
  • Use the package’s own import path.

Bring it into your flight

Read back origin, destination, aircraft profile, planned load and fuel before import.

Official reference

Read alongside: A32NX Flight Planning; iniBuilds EFB and cockpit preparation.

Simulator guide

EFB loading and performance inputs

The tablet, OFP and flight-management data must describe one loading state.Open this topic

What to understand

  • Know which interface sets payload and fuel.
  • Read the resulting mass and balance in the aircraft.
  • Recalculate when runway or conditions change.

Bring it into your flight

Cross-check the final load before completing performance entries.

Official reference

Read alongside: A32NX Payload Management; iniBuilds EFB, printed p22 onward.

02

Power and flight management

Build a coherent cockpit and a reviewed flight plan.

Simulator guide

Electrical, APU and cockpit preparation

Use the correct package flow to establish a known cockpit state.Open this topic

What to understand

  • Identify the active power source.
  • Observe initialization before entering flight data.
  • Locate the system indications used by the current checklist.

Bring it into your flight

Follow the current aircraft preparation flow with the developer guide beside it.

Official reference

Read alongside: A32NX Cockpit Preparation; iniBuilds walkthrough, printed p43 onward.

Simulator guide

ADIRS and position awareness

Position alignment is part of a usable navigation picture.Open this topic

What to understand

  • Know where alignment state is displayed.
  • Compare the entered or supplied position with the departure airport.
  • Keep the alignment check within the selected package procedure.

Bring it into your flight

Confirm the navigation displays and position reference before taxi.

Official reference

Read alongside: A32NX ADIRS alignment and MCDU; iniBuilds cockpit preparation.

Simulator guide

MCDU: INIT, F-PLN and route review

A successful import still needs a runway-to-arrival review.Open this topic

What to understand

  • Recognise INIT and flight-plan fields.
  • Review SID, airway connections and arrival geometry.
  • Understand each discontinuity before changing it.

Bring it into your flight

Step through the route on the ND and reconcile it with the OFP and clearance.

Official reference

Read alongside: A32NX MCDU programming; iniBuilds MCDU printed p29 and cockpit preparation.

Simulator guide

MCDU: fuel prediction and PERF

Use the numbers belonging to the current load, runway and aircraft.Open this topic

What to understand

  • Distinguish loading from entering a prediction.
  • Check units and the origin of each performance value.
  • Review changed conditions before accepting the data.

Bring it into your flight

Compare the aircraft’s final PERF and fuel entries with the matching performance calculation.

Official reference

Read alongside: A32NX INIT FUEL PRED and PERF; iniBuilds cockpit preparation.

03

Flight guidance and the FMA

Understand what is controlling the aircraft before changing a target.

Simulator guide

FCU: selected and managed targets

The control position and the active mode are related but different checks.Open this topic

What to understand

  • Recognise the package’s push, pull and rotary interactions.
  • Know whether a target comes from the FCU or flight management.
  • Verify the resulting FMA mode.

Bring it into your flight

State the lateral and vertical mode after each important FCU selection.

Official reference

Read alongside: A32NX Flight Guidance; iniBuilds FCU, printed p32 onward.

Simulator guide

Autothrust and flight-mode awareness

Thrust, pitch and speed control must be read together.Open this topic

What to understand

  • Distinguish armed from active guidance.
  • Monitor what the FMA says rather than assuming a knob change took effect.
  • Use the aircraft procedure when changing automation level.

Bring it into your flight

Explain what controls speed and vertical flight at the present phase.

Watch the manufacturer

Official reference

Read alongside: A32NX managed/selected guidance; iniBuilds FMA.

Simulator guide

Navigation source, radios and transponder

A route in the MCDU does not replace source and communication checks.Open this topic

What to understand

  • Locate radio and transponder controls in the actual cockpit.
  • Check the displayed navigation source for the planned approach.
  • Follow the current online-network identification instructions.

Bring it into your flight

Brief the actual frequencies and source using the aircraft and current charts.

Official reference

Read alongside: iniBuilds radio/transponder printed pp37–40; A32NX RAD NAV.

04

Start, taxi and departure

Connect preparation to takeoff without borrowing ceo numbers.

Simulator guide

Engine start and taxi

Use the neo package’s ground-operation flow.Open this topic

What to understand

  • Separate the selected start state from completed checks.
  • Observe engine and system indications.
  • Review flight controls and taxi clearance before moving.

Bring it into your flight

Use the current start and taxi checklist and identify the expected indication at each stage.

Official reference

Read alongside: A32NX Engine Start and Taxi; iniBuilds printed pp68–75.

Simulator guide

Takeoff configuration and first guidance

The actual runway and neo performance drive the departure.Open this topic

What to understand

  • Check runway, thrust and configuration against the calculation.
  • Understand the first guidance modes.
  • Keep the immediate departure and missed-takeoff plan in the briefing.

Bring it into your flight

Brief the current calculated takeoff data; do not copy the ceo’s speeds.

Official reference

Read alongside: A32NX Takeoff; iniBuilds printed p76 onward.

Simulator guide

Climb and cruise management

Track clearances, constraints and fuel as the workload changes.Open this topic

What to understand

  • Separate a clearance limit from a planned cruise level.
  • Monitor flight guidance after level changes.
  • Review fuel and the next flight phase.

Bring it into your flight

Compare the cleared altitude, FMA and flight-plan constraints.

Official reference

Read alongside: A32NX Climb and Cruise; iniBuilds printed pp80–85.

05

Descent, approach and landing

Prepare early and use the approach modes actually available.

Simulator guide

Descent path and energy

Know how the chosen vertical mode handles the planned path.Open this topic

What to understand

  • Review weather, arrival and constraints.
  • Understand managed versus selected descent behavior.
  • Monitor energy rather than assuming the aircraft will recover every error.

Bring it into your flight

Name the current vertical mode and next constraint before descent.

Official reference

Read alongside: A32NX Descent Planning; iniBuilds printed pp86–94.

Simulator guide

Approach briefing and navigation setup

Use the current chart and the selected aircraft’s supported approach procedure.Open this topic

What to understand

  • Check procedure, runway, minima and source.
  • Review the missed approach before final.
  • Confirm approach data after a runway change.

Bring it into your flight

Compare the MCDU arrival and navigation setup with the chart.

Official reference

Read alongside: A32NX Approach and ILS Landing; iniBuilds approach preparation and simplified approaches.

Simulator guide

ILS guidance and landing

Observe the capture and active modes before relying on them.Open this topic

What to understand

  • Distinguish a selected frequency from captured guidance.
  • Monitor stabilization and the intended automation level.
  • Use the aircraft’s own landing and deceleration reference.

Bring it into your flight

Explain the displayed approach modes and the plan for landing or going around.

Official reference

Read alongside: A32NX ILS landing; iniBuilds simplified ILS and landing procedures.

Simulator guide

Go-around preparation

Keep the next safe flight path in the same briefing as the landing.Open this topic

What to understand

  • Review the missed approach geometry.
  • Know the package-specific thrust and guidance procedure.
  • Reconfirm modes and clearance after initiation.

Bring it into your flight

Have the published missed approach and current aircraft procedure ready.

Watch the manufacturer

Official reference

Read alongside: iniBuilds Go-Around, printed p121.

06

Parking, systems and reference limits

Finish the sector and know where the next answer belongs.

Simulator guide

After landing and shutdown

Use the current package flow through stand arrival and securing.Open this topic

What to understand

  • Separate runway vacation from stand actions.
  • Coordinate ground services with the aircraft state.
  • Finish the tracker and aircraft shutdown as distinct tasks.

Bring it into your flight

Use the aircraft checklist and confirm the VA flight report separately.

Official reference

Read alongside: A32NX After Landing and Powering Down; iniBuilds printed pp122–124.

Simulator guide

System configuration and abnormal reference

Optional equipment and simulated failures vary between packages.Open this topic

What to understand

  • Read the configuration table for the installed aircraft.
  • Locate the applicable abnormal/checklist source.
  • Do not copy a Fenix V3 feature into another neo implementation.

Bring it into your flight

Identify your current reference before trying an unfamiliar system or abnormal scenario.

Official reference

Read alongside: A32NX simulated hardware; iniBuilds configuration summary and installed checklists.

Keep the scope beside the source.

The manufacturer introduction is not a complete current-build course. Use the separate developer manuals for full procedures.

The publisher-hosted iniBuilds manual carries an older internal revision. Current package documentation and release notes take precedence; this page supplies no unverified limits or speeds.

Source review and live VA fleet check: 30 October 2026. A reference implementation is not a declaration of your installed package or a local flight test. Current simulator-aircraft procedures and limits take precedence over older recordings and real-aircraft brochures.

Official source directory · 13

FLYBYWIRE SIMULATIONS

A32NX simulated aircraft configuration ↗

The developer explicitly identifies A320-251N with CFM LEAP 1A-26. Exact type match to our VA neo; this does not identify your installed add-on.

Checked 2026-10-30

INIBUILDS / MICROSOFT

A320neo V2 manual ↗

125-page PDF. Internal revision 1.0.4, 5 December 2023, retained by the publisher. Includes EFB, FMGS, FCU, normal-flight walkthrough and simplified procedures; compare the current installed package.

Checked 2026-10-30

FLYBYWIRE SIMULATIONS

A32NX MCDU preparation ↗

DATA, INIT, flight plan, secondary plan, radio navigation, fuel prediction and performance.

Checked 2026-10-30

Choose another fleet aircraft →Return to Fenix A320 →

WATCH OUR FLIGHTS

Take the briefing to the flight deck.

Our Fenix A320 night departure from Tashkent to Istanbul is waiting on YouTube.

Archive flight. Its aircraft build is unverified; this is not a V3 demonstration or an FSHud fix test.