This guide walks you through a complete flight in the LVFR Airbus A330 NEO, from the moment you spawn at a dark, powered-off gate to the moment you park and shut down at your destination. Each chapter covers one phase of flight. If you are familiar with flying smaller aircraft in MSFS but have never flown a modern airliner with a full glass cockpit, start here.

This guide also includes a Quick Reference section for fast lookups once you know the basics, and a full FAQ for the questions that come up most often.

Note: this guide is written for simulation purposes only. Procedures are simplified for the simulator context and may differ from real-world airline operations.

ADVAdvanced: FMS / CDU Deep Dive ADVAdvanced: Autoflight / FMA Deep Dive

Before your first flight, it helps to know what you are looking at. The A330 NEO cockpit uses a “glass cockpit” — almost everything is shown on large screens rather than traditional round gauges. It keeps the real A330-900's classic MCDU layout rather than a touchscreen-style flight computer, so the center pedestal will feel familiar if you have flown other classic-generation Airbus aircraft. Here is a quick map of every major display and panel.

The Screens

PFD — Primary Flight Display

The main instrument in front of each pilot.

  • Airspeed (left side, vertical tape)
  • Altitude (right side, vertical tape)
  • Attitude — the artificial horizon showing pitch and bank in the center
  • The flight path vector (“bird”) and, in TRK-FPA mode, a flight path director
  • Autopilot and auto-thrust mode information across the top strip (the FMA)

ND — Navigation Display

The moving map next to each PFD.

  • Your programmed flight plan as a magenta line, including manually-drawn legs
  • Nearby airports, waypoints, and navigation beacons
  • Terrain (color-coded by height relative to the aircraft), traffic, and the FLS/RNAV approach beam when one is loaded
  • Computed flight path markers: T/C (top of climb), T/D (top of descent), DECEL

E/WD — Engine/Warning Display

The upper center screen.

  • Engine thrust (N1%) for both Trent 7000 engines
  • Fuel flow and quantity
  • Any active warnings, cautions, or memos (e.g. TAKEOFF MEMO, LANDING MEMO)

SD — System Display

The lower center screen. It automatically cycles through aircraft system pages depending on what the aircraft is doing.

  • ENGINE, BLEED, ELEC (AC and DC), HYD, FUEL, APU, COND, DOOR, WHEEL, F/CTL, CB, and STATUS
  • For example, the WHEEL page shows automatically on landing, and the DOOR page at the gate
  • You can also select any page manually from the ECAM control panel

FCU — Flight Control Unit

The long horizontal panel at the top of the glareshield. This is where you dial in:

  • Speed or Mach number
  • Heading or track
  • Target altitude
  • Vertical speed or flight path angle
  • You also engage the autopilot (AP1/AP2) and auto-thrust (A/THR) here

MCDU — Multipurpose Control & Display Unit

The keypad/screen on the center pedestal. Two full crew MCDUs, each fully independent (the First Officer's is not a mirror of the Captain's), plus a third, independent center MCDU for display/navigation reference only.

  • Program your route and flight plan (F-PLN), including a secondary flight plan
  • Enter fuel, weight, and cost index
  • Set up the departure and arrival procedures
  • Calculate and confirm takeoff and landing speeds

EFB — Electronic Flight Bag

A tablet visible on the side panel.

  • Load fuel and set passenger/cargo weight (weight & balance)
  • Import your flight plan and load sheet from SimBrief
  • Control ground services — doors, pushback, catering, baggage, boarding
  • Run interactive checklists and check the weather
  • Switch between KG/LB and M/FT display units

By default the A330 NEO spawns cold and dark at the gate — no electrical power, no hydraulics, engines off — just like the real aircraft between flights. This is the most realistic (and most involved) way to start a flight.

Step 1 — Get electrical power

Turn on the batteries on the overhead panel. If you are parked at a gate, connect external/ground power so you are not draining the batteries. You will see the screens do a brief self-test flash — this is normal, it mimics the real aircraft's built-in test sequence and clears on its own.

Step 2 — Start the IRS alignment

Turn the three IRS (Inertial Reference System) knobs on the overhead panel to NAV. The IRS needs time to work out its exact position before it can feed the PFD and ND — until it finishes, the ND stays blank and PFD attitude flags stay red. This takes a few minutes; use the time to work through the rest of this checklist.

If you spawn already on a runway or in the air, the IRS pre-loads aligned so you can fly immediately.

Step 3 — Load your flight plan and fuel (EFB)

Open the EFB. If you use SimBrief, log in once from EFB Settings, then use the SimBrief page to pull your OFP — this sets your route, fuel, and payload together. Otherwise use the Performance and Mass & Balance pages to set fuel and payload by hand. Ground crew will start boarding/loading based on what you set here.

Step 4 — Set up the MCDU

On the INIT page, confirm the city pair and cost index, and either accept the SimBrief-imported route or build it manually. Move to F-PLN to review the lateral route, and PERF to review the TAKEOFF and CLB pages — this is where you confirm your V-speeds (V1/VR/V2) and thrust setting (CLB, FLEX, or TOGA).

Step 5 — Start the APU

Turn the APU master switch on, then start it, so you have a bleed-air and electrical source independent of ground power — you will need its bleed air to start the engines.

With the APU running and the flight plan loaded, it is time to get the engines running and get off the gate.

Step 1 — Pushback (if required)

Use the EFB's pushback controls to call for a tug, choose a direction, and pull back off the gate. Ground services (catering, baggage, boarding) run automatically off the same EFB flow when you select a realistic (ramped) load.

Step 2 — Start the engines

With APU bleed air available, run the engine start sequence per your checklist — engine 2 first is the common flow. Watch N2 rise, then introduce fuel, and watch N1, EGT, and oil pressure settle on the E/WD as the engine stabilizes.

Step 3 — After start

Once both engines are running and stable, you can switch bleed air/electrics off the APU and shut it down (unless you need it for packs at the gate). Set flaps for takeoff per your PERF TAKEOFF page, and run your flight control check.

Getting to the runway and off the ground.

Taxi

Use the tiller/rudder to steer and light taxi power to get moving. Arm autobrake as briefed — RTO (rejected takeoff) is normally armed by the time you reach the runway. Autobrake has five positions: RTO, OFF, LO, MED, MAX.

Before Takeoff

Confirm the TAKEOFF MEMO on the E/WD shows no outstanding items (it will list anything not yet configured — flaps, spoilers, trim, etc.). Set your FCU targets: runway heading/track, a safe altitude, and your climb speed or managed NAV.

Takeoff

Advance the thrust levers to FLEX or TOGA. SRS (speed reference system) guidance engages automatically once airborne and manages your pitch target through the initial climb; if you reject the takeoff, SRS/runway guidance correctly drops out. Retract the gear once a positive rate is confirmed, then follow the flap retraction schedule.

Engaging the autopilot and managing the climb.

  • Engage AP1 or AP2 and A/THR once comfortable after takeoff.
  • NAV mode will follow your MCDU flight plan laterally; CLB manages the climb speed and respects any SID speed/altitude restrictions until they are sequenced past.
  • The ND shows a T/C (top of climb) marker computed from your current performance — this updates as conditions change.
  • Use the WIND pages (climb/cruise/descent) to enter forecast winds for more accurate predictions, and CMS/RTA if you are managing a required arrival time.

The cruise phase is where the FMS does the most work quietly in the background — this is a good time to get familiar with the tools available if your routing changes.

  • DIR TO — jump directly to any waypoint in your flight plan or a new one.
  • HOLD — insert a holding pattern at any waypoint, with entry computed automatically.
  • LATERAL/VERTICAL REVISION — change your route or step-climb plan at any waypoint, including STEP ALTS for a planned step climb.
  • FIX INFO — mark a radial/distance off any navaid or waypoint, useful for planning a diversion or just situational awareness; four independent slots are available, each with two radials and its own intercept prediction.
  • SEC F-PLN — build and hold a second, alternate flight plan without disturbing your active one, then activate it if you need it.
  • Traffic — TCAS shows nearby traffic on the ND; ATSAW additionally correlates online traffic (VATSIM) if you fly online, with dedicated TRAFFIC LIST/INFO MCDU pages.
  • ATC datalink — if you use Hoppie ACARS, PDC and Oceanic Clearance requests can be auto-filled from your active flight plan, and messages arrive on the DCDU.

Setting up for arrival well ahead of time makes the descent and approach much easier.

  • Insert your arrival (STAR) and approach from the MCDU's F-PLN or arrival pages ahead of top of descent — this also lets the FMS compute a T/D that respects your constraints.
  • Choose managed descent (DES) to follow the FMS-computed profile, or select speed/V-S manually if ATC gives you a specific instruction.
  • For an ILS approach, tune and identify the localizer/glideslope; for an RNAV or FLS approach, the ND will draw the approach course as a beam once selected.
  • ACTIVATE APPR PHASE (from the PERF page) arms the approach-phase logic once you are established on the arrival.

Bringing it down safely.

  • Configure flaps and gear per your normal approach checklist; monitor the LANDING MEMO on the E/WD for anything outstanding.
  • Couple the autopilot to the localizer/glideslope (LOC/APPR) or the RNAV/FLS course, and disconnect at your planned point to hand-fly the landing (or when ready to take manual control at any point along the approach).
  • Select your landing autobrake setting (LO/MED/MAX) before touchdown.
  • ROW/ROP will alert you if you are not going to be able to stop within the remaining runway — treat it as a safety net, not a replacement for planning your approach and braking correctly.
  • Go-around: advancing the thrust levers to TOGA and selecting the go-around mode arms a proper go-around phase, including ENABLE ALTN if you need to divert.

Getting the aircraft safely parked and put to bed.

  • Taxi clear of the runway, retract flaps per your checklist, and disarm spoilers.
  • Watch the brake temperature model on the WHEEL SD page after a heavy landing — a hot brake arc and BRAKES HOT/BRK FAN warnings will appear if temperatures run high; the EFB also shows a live brake cooling readout while you taxi in and park.
  • At the gate: set the parking brake, shut down both engines, and start the APU first if you need bleed air or power before ground power is connected.
  • Use the EFB to open doors and start disembarking/ground services as needed — GPU, wheel chocks, ground air, and jetway are grouped together under one EQUIPMENT row.
  • Setting wheel chocks from the EFB physically holds the aircraft in place and satisfies the sim's parked-on-stand check — a good habit once you're on stand.

Cockpit Screens

ScreenWhat it shows
PFDSpeed, altitude, attitude, flight director, FMA
NDMoving map: route, terrain, traffic, approach beam
E/WDEngine data, memos, warnings/cautions (upper ECAM)
SDSystem pages — ENGINE/BLEED/ELEC/HYD/FUEL/APU/COND/DOOR/WHEEL/F-CTL/CB/STATUS (lower ECAM)
FCUSpeed, heading, altitude, V/S, AP/A-THR engagement
MCDUFlight plan, performance, and route programming
EFBFuel, weight & balance, ground services, checklists, weather, settings

Autobrake Settings

SettingTypical use
RTOArmed for takeoff — activates automatically on a rejected takeoff
OFFNo autobrake; manual braking only
LOLong runway, light braking preferred
MEDStandard landing runway length
MAXShort runway or wet/contaminated conditions

Key MCDU Pages

PagePurpose
INITCity pair, cost index, SimBrief import
F-PLNActive lateral flight plan
SEC F-PLNAlternate/secondary flight plan
PERFTakeoff/climb/cruise/descent/approach/go-around performance
DIR TODirect routing to any waypoint
HOLDInsert a holding pattern
LAT REV / VERT REVLateral or vertical revision at a waypoint, incl. STEP ALTS
FIX INFORadial/distance marking off any fix (4 slots)
DATAClosest airports, pilot waypoints/routes, position monitor
RTA / CMSRequired time of arrival / cruise management
WINDClimb/cruise/descent forecast wind entry
MCDU MENUATSU/AOC menu and ATC COMM suite (datalink)

Cold-and-Dark Checklist (Condensed)

  • Batteries ON, external/ground power connected
  • IRS knobs to NAV (allow a few minutes to align)
  • EFB: load fuel & weight (SimBrief or manual)
  • MCDU: INIT page — city pair, cost index, route
  • MCDU: PERF TAKEOFF — V-speeds, thrust setting, flaps
  • APU master ON, then start APU
  • Pushback (EFB) if required, then engine start
  • After start: flaps set, flight controls checked
  • Before takeoff: TAKEOFF MEMO clear, FCU set, autobrake RTO armed

After-Landing Checklist (Condensed)

  • Autobrake disarms automatically — confirm speed under control
  • Flaps retracted per checklist, spoilers disarmed
  • Check WHEEL page brake temperature after a heavy landing
  • Parking brake set at the gate
  • Both engines shut down; APU started first if power is needed
  • EFB: doors opened, ground services requested as needed
  • EFB: wheel chocks set (EQUIPMENT row) once parked on stand

First Steps

Why are all the screens dark or blank when I first load in?

This is intentional. When you spawn cold and dark (at a gate with engines off), the plane has no electrical power, so all displays are off — just like the real aircraft. Turn on the batteries and external/ground power on the overhead panel to bring everything to life.

If you spawn on a runway or in the air, the plane pre-loads into a powered state and screens come on automatically.
The screens did a quick flash / self-test when I powered up. Is something wrong?

Completely normal. It simulates the real aircraft's built-in test sequence that checks all displays are working when avionics power comes on, and clears on its own after a few seconds.

The Navigation Display is blank and the PFD shows red flags. What do I do?

The IRS (Inertial Reference System) needs time to work out exactly where it is before it can feed the displays. Turn the three IRS knobs on the overhead panel to NAV. It takes a few minutes to align from cold and dark. Until it finishes, the map stays blank and some PFD indicators show red flags — this is correct behavior.

If you load in at a runway or in the air, the IRS starts pre-aligned so you can fly immediately.
What are all these screens? I don't know what any of them are called.

Quick tour of the glass cockpit: PFD (Primary Flight Display) — speed, altitude, attitude, and autopilot modes; ND (Navigation Display) — the moving map; E/WD (Engine/Warning Display) — the upper ECAM screen; SD (System Display) — the lower ECAM screen; FCU (Flight Control Unit) — the autopilot/speed/heading/altitude panel; MCDU — the flight plan keypad/screen; EFB (Electronic Flight Bag) — the tablet for fuel, weight & balance, and ground services.

The MCDU and Flight Planning

Is the MCDU a touchscreen glass-style FMS, like some other Airbus add-ons?

No — the A330 NEO deliberately keeps the classic, physical-key MCDU presentation used by the real A330-900 (rather than a newer glass-cockpit style FMS). If you have flown other classic-generation Airbus MCDUs before, the layout and LSK (line-select key) navigation will be familiar.

How do I load my SimBrief flight plan?

Log in to SimBrief once from the EFB's Settings page, generate your OFP as normal on simbrief.com, then use the EFB's SimBrief page to import it. This sets your route, fuel, and payload together. You can also uplink it directly from the MCDU MENU using INIT REQUEST.

I pressed SYNC on the SimBrief page and nothing happened — do I need to press it twice?

No — this used to be a real bug (an earlier version needed two presses) but it has been fixed. If SYNC still seems unresponsive, check you are actually logged in on the Settings page first.

What is the difference between F-PLN and SEC F-PLN?

F-PLN is your active flight plan — what the aircraft is actually flying. SEC F-PLN lets you build and hold a completely separate, alternate plan (for example a diversion) without touching the active one, then activate it later if you need it.

What is FIX INFO for?

It lets you mark a radial and distance off any waypoint or navaid, independent of your flight plan — useful for situational awareness, diversion planning, or coordinating with ATC. There are four independent slots, each with two radials and its own intercept prediction, plus a TMPY INSERT step before it commits.

There's a third MCDU in the center — what does it do?

That is an independent, reference-only unit. It displays route and navigation information but is not a third fully-functional flight computer — think of it as a convenient extra display rather than a spare MCDU.

ENABLE ALTN isn't showing where I expect it.

ENABLE ALTN appears at enroute revision points once you have an alternate set on the INIT page (or imported via SimBrief) — it lets you activate a direct routing to your alternate for a diversion. If you do not see it, confirm an alternate airport is set.

Autoflight and Handling

The autopilot won't stay engaged after landing, or a mode looks “stuck.”

This was a real issue in earlier builds where a lateral or vertical mode could get stranded after landing. It has been fixed — the autopilot directors now clear properly. If you still see something similar, note the FMA indications and the flight phase when it happens.

What is TRK-FPA mode, and what is “the mustache” on my PFD?

TRK-FPA (Track / Flight Path Angle) is an alternative to HDG/V-S for hand-flying with the flight director. “The mustache” is the flight path director symbol that appears on the PFD in that mode, guiding you to a target flight path angle rather than a pitch attitude.

What is SRS, and why did it drop out when I rejected takeoff?

SRS (Speed Reference System) is the takeoff guidance director — it manages your pitch target during the initial climb after a normal takeoff. If you reject the takeoff, SRS and runway guidance correctly disengage rather than staying armed.

What is ROW/ROP?

Runway Overrun Warning and Protection. It monitors your landing performance against the remaining runway and alerts you if you are unlikely to stop in time. It is a safety net, not a substitute for briefing and flying a stabilized approach with the correct autobrake setting.

Autobrake, Ground Handling and Systems

What do the autobrake settings mean?

There are five: RTO (rejected takeoff — the default armed setting for takeoff), OFF, LO, MED, and MAX. RTO is normally armed for takeoff and disarms automatically once you are safely airborne; select LO, MED, or MAX before landing depending on the runway available.

Where is the “PACKS” indication? I don't see a PACKS memo like I've seen on other Airbus add-ons.

The A330 family does not have a “PACKS” memo the way some other Airbus types do — per the FCOM, the only air-conditioning memos are RAM AIR, PACK FLOW LO, and PACK FLOW HI. There is a separate PACKS/NAI/WAI indication in the thrust-rating block at the top right of the E/WD, which shows on the ground before takeoff to confirm the bleed configuration your takeoff thrust was computed against — that is a different thing from a memo, and it is present.

Does the A330 NEO have a PTU (Power Transfer Unit) like some other Airbus add-ons?

No — matching the real A330, there is no PTU. The aircraft has three independent hydraulic systems.

My brakes are showing hot after landing — is that a bug?

No — it's a real-time brake temperature model (now a two-node model calibrated against real performance data). A hard or long landing, or heavy braking, will raise brake temperatures, shown with a hot-brake arc and BRAKES HOT/BRK FAN warnings on the WHEEL system page and a live cooling readout in the EFB. Let them cool (BRK FAN can help) before your next departure if they're running hot.

Do the EFB's wheel chocks actually do anything?

Yes — once set from the EFB, wheel chocks physically hold the aircraft in place and satisfy the sim's “parked on stand” check. They no longer block you from requesting other ground services (GPU, air, jetway) at the same time.

Multi-Crew

Does the First Officer's side just mirror the Captain's ND and MCDU?

No — the F/O's Navigation Display and MCDU run as fully independent instances. Each pilot can display a different range/mode on their ND or work a different MCDU page without affecting the other side.

Navigation and Systems Realism

My navigation accuracy (RNP/ANP) indication looks different than I expected.

Navigation accuracy is computed for real per FCOM 34.4.4.10/34.6.8.1 rather than shown as a fixed placeholder, so it will vary with your actual navigation sensors and satellite/station geometry.

I saw a GNSS jamming or spoofing effect, or my position accuracy degraded unexpectedly — is that a bug?

No — GNSS jamming and spoofing is a simulated realism feature that can affect specific regions/scenarios. If your navigation accuracy or position degrades without an obvious cause, this may be why.

What is the PWS switch on the overhead panel?

PWS is Predictive Windshear. The switch is functional — turning it off shows a PRED W/S OFF memo on the E/WD, matching real behavior.

What are the AUTOLAND lights on the glareshield?

They flash to indicate an autoland status/warning condition, matching the real aircraft's glareshield AUTOLAND annunciation.

Why does the rudder sit at an odd angle after a total hydraulic failure?

That's realistic — with all three hydraulic systems dead, the rudder is mechanically free and weathervanes with the relative wind, matching the real A330. Rudder pedal input still carries some aerodynamic authority in that state.

Traffic, ATC and Datalink

What's the difference between TCAS and ATSAW?

TCAS is the standard traffic-collision-avoidance display, working off simulated traffic. ATSAW (Airborne Traffic Situational Awareness) additionally correlates real online traffic if you fly on a network like VATSIM, and adds dedicated TRAFFIC LIST/INFO pages on the MCDU.

My Hoppie ACARS messages aren't arriving.

Confirm your Hoppie logon code is entered on the EFB's Hoppie/ACARS login section and that you are connected (CONNECT NOTIFY) to the right ATC unit. An early version had a polling bug that stopped messages arriving in some setups — that has been fixed; if messages still don't show up, re-check your logon code and connection status first.

How do I request a PDC or an oceanic clearance?

From the ATC COMM suite on the MCDU MENU — both PDC and Oceanic Clearance requests auto-fill from your active flight plan, so you normally only need to review and send.

What is the DCDU for?

It's the dedicated screen for datalink uplink/downlink messages (clearances, PDCs, oceanic clearances) — separate from the MCDU's own message record.

Units and Display

Can I fly in metric units?

Yes — the EFB Settings page has crew-selectable KG/LB and M/FT units across both the EFB and the avionics. Selecting metric also switches QNH to read in hPa automatically.

Sound

Is the rumbling on the ground and in turbulence supposed to be that subtle?

Yes, largely — it's tuned against real MSFS turbulence data, which is much milder than the numbers you may expect from real-world reports. Taxi rumble and a three-layer altitude turbulence bed are both present and will be more noticeable on a subwoofer or headset than on laptop speakers.

I don't hear a click when I move the throttle levers through a detent.

Detent click sounds are present; if you ever notice them missing, that's worth reporting, as it has been a real (and fixed) issue before.