MSFS Blind Assist

Airbus Aircraft

This is the guide for the preview build 10.0.1-pre.97, which has features the released version does not have yet. Read the guide for the released version.

Chapter 1 of 2 in Part 8: Aircraft Guides of the MSFS Blind Assist user guide.

BA supports four Airbus aircraft: the FlyByWire A320neo (often called the A32NX), the Fenix A320 CEO, the FlyByWire A380X and the Headwind A330-900neo. Three of them come from the same family of code. The Headwind A330 is built on top of the FlyByWire A320, and the A380X is made by the same FlyByWire team, so once you have learned one of these three, the others will feel familiar. The Fenix is a separate product with its own way of working, and BA treats it differently in a few places.

A few things are true of all four:

FlyByWire A320neo (A32NX)

The FlyByWire A32NX is a free, highly detailed A320neo, and it is the most complete Airbus in BA. Almost every switch in the cockpit is reachable from the panels, the MCDU is fully readable, the flyPad tablet is a browsable document, and you can even answer ATC datalink messages.

Before you fly

You need:

You do not need SimBridge (FlyByWire’s companion program) for normal flying. BA reads the MCDU straight from the aircraft’s own display. SimBridge is only used for MCDU printouts, and as a backup if BA cannot reach the display directly. You do not need Developer Mode or any Community-folder add-on from BA.

The aircraft’s displays must be powered (battery on, or a powered preset loaded) before there is anything to read.

How the panels are organised

Press Ctrl+1 to reach the Sections list and Ctrl+2 to reach the Panels list. The A32NX has four sections.

Overhead holds the overhead panel, in this order:

Glareshield holds:

Instrument holds the main instrument panel:

Pedestal holds:

The RMP panel is where you tune the COM radios. For COM 1, 2 and 3 there is a Standby Frequency field, an Active Frequency field and an XFER (swap) button, followed by the RMP power and mode switches. Type a frequency such as 121.500 and press Enter. BA then announces the result, for example “COM 1 active 121.500”, and after a swap you hear both the new active and the new standby frequency.

There is no Doors or Ground Services panel on the A32NX. Door states are announced automatically as they change (“Forward Left Door open”, for example), and ground services such as the jet bridge, stairs, catering and fuel truck are handled on the flyPad’s Ground page.

Autopilot / FCU windows

In Input mode, each of these opens a small window with a value box, the knob’s push and pull buttons, and the relevant mode toggle. Type a value in the box and press Enter, and BA confirms the value it sent, for example “FCU heading 270, selected”. In the altimeter window (Ctrl+B), Enter applies only from the value box; choosing a mode or a unit in its lists applies at once.

Key Window
Input Ctrl+S Speed: 100 to 399 knots or Mach 0.10 to 0.99, Speed Push (managed), Speed Pull (selected), SPD / MACH toggle
Input Ctrl+H Heading: 0 to 360, Heading Push and Pull, HDG·V/S / TRK·FPA toggle
Input Ctrl+A Altitude: 100 to 49,000 feet, Altitude Push (managed) and Pull (selected), Increment 100 and Increment 1000
Input Ctrl+V Vertical speed (plus or minus 6000 feet per minute) or flight path angle (plus or minus 9.9 degrees), V/S Pull (engage), V/S Push (level off)
Input Ctrl+P Autopilot panel: AP 1, AP 2, LOC, APPR, EXPED, A/THR, AP disconnect, A/THR disconnect, and a Flight Director status line
Input Ctrl+B Altimeter: Mode (QNH or STD), Unit (hPa or inHg), and one value that sets both sides

The buttons in the Autopilot panel always show their live state, for example “AP 1 (on)” or “LOC (off)”. The A/THR button says whether autothrust is Disengaged, Armed or Active. The altimeter window confirms with “Altimeter set to 1013 hectopascals, both sides”.

The engage shortcuts, the push and pull keys and the Output Shift+H, Shift+S, Shift+A and Shift+V readouts are described in Autopilot Windows. Turning an FCU knob on hardware or in the cockpit speaks the new value as it settles.

MCDU

Open the MCDU with Input Shift+M. The window shows the screen as a list, one line at a time. It is the Captain’s MCDU. The aircraft draws both MCDU screens from one instrument, so there is no separate First Officer MCDU to switch to.

To read and move around:

To type into the scratchpad:

  1. Press Alt+S to jump to the scratchpad input field.
  2. Type your entry, for example a waypoint name or a cruise level.
  3. Press Enter. BA sends it to the MCDU scratchpad.
  4. Press Alt+Home to return to the display, arrow to the line you want, and press its line select key.

Backspace clears the scratchpad.

The line select keys are Ctrl+1 to Ctrl+6 for the left side and Alt+1 to Alt+6 for the right side (or F1 to F12 with the alternate setting). The page keys are all on Alt:

Key Page Key Page
Alt+I INIT Alt+U FUEL PRED
Alt+D DIR Alt+K ATC COM
Alt+P PROG Alt+M MCDU MENU
Alt+F F-PLN Alt+A AIRPORT
Alt+E PERF Alt+T DATA
Alt+R RAD NAV Alt+O OVFLY
Alt+Shift+F SEC F-PLN Alt+C CLR

What you hear: the page title when the page changes, and the scratchpad when a message appears there, such as an FMS warning. Once you have opened the MCDU window, it keeps reading out FMS messages such as DEST EFOB BELOW MIN even after you close it, but a closed window does not announce page changes. If SimBridge is running, printouts are read too, starting with “Printer:”. The window’s status line says “MCDU: Connected” or “MCDU: Disconnected”.

EFB

The FlyByWire flyPad opens with Input Shift+T, in a window called “A320 flyPad EFB”, and works as described in Aircraft EFBs. The current page is shown as “(current page)” in the navigation, and selected Ground tabs and options read “(selected)”. The flyPad is the same on the A32NX, the Headwind A330 and the A380X. Some highlights:

Note: The flyPad’s Pushback tab has not been specially adapted for screen readers, so its controls may be hard to use. For pushback we recommend GSX; see Gates, GSX and Docking.

Special windows

DCDU (datalink): Input Ctrl+Shift+D. The DCDU is the small screen below the glareshield where controller-pilot datalink (CPDLC) messages arrive. On the A32NX it is the only place you can answer them; the MCDU only shows the message history.

Before it will work, you need a datalink connection:

  1. In the flyPad Settings, choose an ACARS provider: Hoppie, SayIntentions or BeyondATC.
  2. On the MCDU, go to the ATC COM pages (Alt+K) and log on to ATC. The NOTIFY key needs the ATC flight number, the ATC centre, and a FROM/TO on the INIT page.

In the DCDU window, each soft key appears as a line starting with its key number, with an arrow showing the side. “1 <STBY” is left key 1, and a line ending “RECALL>” is a right key. The keys use the same chords as the MCDU: Ctrl+1 and Ctrl+2 for the left keys, Alt+1 and Alt+2 for the right keys (or F1, F2, F7 and F8 in alternate mode). Long messages are split into the unit’s own lines, exactly as a sighted pilot sees them.

Answering is a two-step process, just like the real unit:

  1. Read the message to the end. PageDown moves to the next page of a long message, PageUp goes back.
  2. Press the answer key, for example Alt+2 for WILCO. The keys change to CANCEL and SEND.
  3. Press Alt+2 again to send.
  4. After sending, right key 2 becomes CLOSE, which dismisses the message.

Ctrl+PageUp and Ctrl+PageDown move to older and newer messages. F5 refreshes and Escape closes.

On a long message, the answer keys stay inactive until you have paged to the end. If you press one too early, you hear for example “WILCO not available yet. Page 1 of 2. Press page down to read on.” If a key still will not work after you have read to the end, you may hear “WILCO not available. The message may still be transmitting.” If the window cannot reach the DCDU it shows “DCDU unavailable. Retrying…”.

E/WD window: Output Alt+E. This opens the engine and warning display as a window: the thrust rating and limit, each engine’s N1, EGT, N2 and fuel flow, fuel on board, and the ECAM memo and warning lines. Read it with the arrow keys. It refreshes by itself; F5 refreshes it at once and Escape closes it.

PFD, ND, ISIS and System Display. These have no window of their own. Read them from the panels in the Instrument section: the PFD panel (flight mode annunciator, speeds, minimums), the ND panel, the ISIS standby instruments and the Status panel. Press Ctrl+3 to jump straight to the status display of the panel you are on. For the System Display, open the System Display panel and choose a page in its System Display Page combo: Upper E/WD, Electrical, Hydraulics, Pressurization, APU, Air Conditioning, Wheel / Brakes, Bleed, Fuel, Doors, Engine and Flight Controls. The status box then lists that page’s values. Choosing a page here only changes what BA reads, not the page on the aircraft’s screen.

First Officer: Output Shift+C. Flows and checklists from cold and dark to securing the aircraft. See The First Officer and Checklists.

Aircraft-specific hotkeys and callouts

The FlyByWire Airbuses answer the full set of Readout Hotkeys, including Shift+1 to Shift+6 (Green Dot, S, F, VLS, VS and VFE Next), Ctrl+W (the active ND waypoint) and Ctrl+0 (approach capability). Output Ctrl+E switches the automatic E/WD callouts on and off (“E W D monitoring enabled” or “disabled”). The rest are in the Hotkey Reference.

BA announces these automatically:

Every one of these can be muted in the Monitor Manager (Output Ctrl+M).

Things to know

Fenix A320 CEO

The Fenix A320 is a payware A320 (the older “CEO” model) with a very deep systems simulation. Fenix v3 also flies as the A319 and the A321, with CFM or IAE engines, and the “Fenix A320 CEO” profile covers them all. BA gives you access to more than 300 switches and knobs, monitors over 470 lights, gauges and switch states, and reads both MCDUs. Its own Fenix windows (Input Ctrl+Shift+F) give you the Fenix’s engine readings, the flight attendant panel, failures, documents and options. BA reads the Fenix’s main displays, the PFD, navigation display, E/WD, SD, ISIS and DCDU, from the Fenix’s own display data into live windows, announces FMA changes, warnings, cautions and memos as they happen, and uses AI vision when it cannot read a display directly.

Before you fly

You need:

About a second after the aircraft has loaded, BA says which Fenix it is, for example “Fenix A321, IAE engines, 2 extra tanks”. The panels then offer only the controls that aircraft has (see below).

How the panels are organised

The Fenix has five sections. Some controls are only on some Fenix aircraft; the lists say which, and “Controls that depend on your Fenix”, after the lists, says how BA handles them.

Overhead:

Pedestal:

Main Instrument Panel: Auto Brakes (Low, Medium, Max, brake fan), Landing Gear (gear lever and anti-skid), Clock (see below), Switching, Console Floor Lights, ISIS (on aircraft with the digital ISIS: its buttons, its baro knob and ISIS Baro Push, the knob’s push; Input Ctrl+B sets the ISIS baro along with both sides, and on the ISIS’s bugs page the knob sets the selected bug’s value), GPWS/Terrain, Warnings/Messages (master warning, master caution, ATC message and chronometer buttons for both sides), Autoland, Main Instrument Lights and Audio (loudspeakers).

Glareshield: EFIS Left, EFIS Right (ND mode and range, the baro knob’s Pull (STD) and Push (QNH), baro mode and adjust, navaid selectors, map filters, flight director, LS) and FCU (every FCU button and the four knobs, each with decrease, increase, push and pull). The flight director and LS buttons read their state in their names, for example “EFIS Left LS: On”.

Cockpit: Cockpit Door (see below), Captain Seat and First Officer Seat (height, distance and armrests), Windows and Shades, Standby Instruments (the standby compass, and the attitude cage on aircraft with the round standby gauges) and Cockpit Other (Headset first, then the jumpseat and its headrest, the oxygen mask covers and gravity gear extension).

Cockpit Door holds everything about the door: Cockpit Door (Closed or Open; the door the First Officer closes before start and opens at shutdown), Overhead Video (the overhead VIDEO pushbutton) and Pedestal Video (the video button on the pedestal). As in the Fenix’s own cockpit, the door does not open while the jumpseat is out, and the jumpseat does not deploy while the door is open: you hear “Stow the jumpseat first.” or “Close the cockpit door first.” The door says when it moves, whoever moves it, for example “Cockpit Door: Open”.

Gravity Gear Extension (Cockpit Other) is one control, Stowed or Extended. Choose Extended and BA raises the handle and turns the crank three times, which takes about six seconds, then says “Gravity gear: cranked 3 turns.” Choose Stowed and it turns the crank back and stows the handle: “Gravity gear: crank stowed.” The control keeps your choice while the crank turns; a second choice before it finishes is refused with “Gravity gear: crank already turning.”

Clock (Main Instrument Panel): Chronometer Start/Stop, Chronometer Reset, Elapsed Time (Run, Stop, Reset), UTC Selector (GPS, Internal, Set) and Date. Its status display reads the chronometer on the “CLOCK CHRONO” line (“2 minutes 5 seconds”) and the elapsed time on the “CLOCK ELAPSED” line (“1 hours 12 minutes”), each “Reset” when blank. Elapsed Time springs back from Reset to Stop by itself, about half a second after you choose Reset. The UTC Selector’s Set position does nothing yet, because the clock’s SET knob, which sets the time and date with it, is not in BA.

Headset (Cockpit Other, Off or On): On puts the headset on, and the Fenix’s noise cancelling quiets the cockpit sound.

Controls that depend on your Fenix. BA offers each Fenix aircraft its own controls:

A control your aircraft does not have is left out of its panel. A panel whose controls your aircraft has none of is not listed at all, for example ISIS with the round standby gauges. Until BA knows which Fenix you are flying, it shows everything: a section you opened before then lists every panel until you move to another section and back, and a panel you opened before then shows every control until you open it again. Pressing a control your aircraft does not have says “Not fitted on this aircraft.”

A note on the seats: the height and distance controls are three-position switches, Down, Stop and Up (or Aft, Stop and Forward). Choose Up and the seat keeps moving until it reaches its limit, then the switch returns to Stop by itself. The combo follows that, but quietly; seat movement is not announced by default.

Cargo Discharge 1 and 2 (Cargo Smoke panel) spring back to the middle like the real ones: a moment after you choose an end, the control shows Rest again, so you can choose the same end again.

Autopilot / FCU windows

The Fenix has its own set of FCU windows, opened in Input mode:

Key Window
Input Ctrl+S Set FCU Speed: 100 to 399 knots or Mach 0.1 to 0.99, Speed Push, Speed Pull, SPD/MACH
Input Ctrl+H Set FCU heading: 0 to 360, Heading Push, Heading Pull, HDG/VS TRK/FPA
Input Ctrl+A Set FCU altitude: 100 to 49,000 feet, Altitude Push, Altitude Pull
Input Ctrl+V Set FCU vertical speed: minus 6000 to 6000, V/S Push, V/S Pull
Input Ctrl+P Autopilot window: AP1, AP2, ATHR, APPR, LOC, EXPED, and the A/THR and AP disconnect buttons for each side
Input Ctrl+B Set Altimeter: Mode (QNH or STD), Unit (QNH (hPa) or Inches (inHg)) and value

In each window, type the value and press Enter; in the altimeter window, only Enter in the value box applies it. The Fenix’s FCU and baro knobs are rotary encoders, so BA turns them click by click towards your value, counting from where the knob really is, even after you have turned it in the cockpit. A big change can take a moment to finish. With the Fenix’s Encoder Acceleration option on, BA turns the heading, speed, altitude and vertical speed knobs in small steps and checks the value after each one, so a big change takes a few seconds; the altimeter is not affected. You hear only where a set ends: the new FCU value once, as when you turn the knob yourself, or, if a set stops anywhere but the value you typed, a sentence such as “Altitude set to 7100, not 7000.” Altitudes are set in steps of 100 feet; if you type 4550, BA says “Rounding to 4500 feet”. A vertical speed goes to the 100 feet per minute step toward zero without a word: 1050 sets 1000, minus 1050 sets minus 1000. If the V/S window shows dashes (a managed climb or descent) and still does after BA’s first click, BA stops and says, for example, “Vertical speed still dashed, not -1000.” If the knob is already where you asked, you hear for example “Already at heading 270”. If you press Enter in the altimeter window while the previous setting is still being dialed in, BA says “Altimeter set in progress, press Enter again when it finishes” and keeps the first value.

The altimeter window sets both sides. A typed value always ends in QNH, and choosing QNH or STD in its Mode list pushes or pulls both baro knobs. When the setting is done, BA reads both sides back: “Both altimeters set: 1015, 29.97.” when both are set to the same QNH, or each side by name otherwise (a side still in STD included), for example “Captain altimeter 1015, 29.97. First officer altimeter still in STD.”

The FCU and baro knobs and their push and pull all go through the MobiFlight WASM module, so they need it installed. The push and pull keys and the Output FCU readouts work as on the FlyByWire aircraft.

MCDU

Open the MCDU with Input Shift+M. The Fenix has two MCDUs and BA reads both. A selector at the top chooses between “Left (Captain)” and “Right (First Officer)”, and you can switch from anywhere in the window with Ctrl+Shift+L (left) and Ctrl+Shift+R (right). You hear “Left MCDU” or “Right MCDU”, then the page title. Each MCDU keeps its own page.

Reading, typing, the line select keys and the page keys all work as in the A32NX MCDU, except that there is no Alt+C key (Backspace clears the scratchpad) and Left and Right switch between page sections, such as INIT A and INIT B.

The selected option in a group is marked with a star. For example, on the failures page “←NONE/MINOR/*ALL” means ALL is selected. The window announces “MCDU connected” or “MCDU disconnected” when the connection changes.

EFB

The Fenix tablet opens with Input Shift+T (in Output mode, Shift+T toggles trim announcements instead), in a window called “Fenix EFB”. On its own, the Fenix v3 tablet cannot be used with a screen reader, so BA adds what it lacks: every app is a button you can Tab to, every switch, box and list says its name, and selections and open chapters say their state. Read it in browse mode, like a web page; the window itself is described in The Fenix and iFly EFBs.

For documents, failures and options, the Fenix windows below are quicker: they search when you press Enter, open the pinned ECAM procedure with one key, and tell you what the Fenix did.

Special windows

The display windows. BA reads the Fenix’s main displays from the Fenix’s own display data and lists them in live windows, in Output mode:

Key Window
Alt+P PFD (the captain’s)
Alt+N Navigation display (the captain’s), see The ND window
Alt+E E/WD (engine and warning display)
Alt+S SD (system display), see The SD window
Alt+I ISIS (the digital standby instrument)

The DCDU window opens with Input Ctrl+Shift+D. All six are in the Fenix windows list too.

Each window is called, for example, “Fenix PFD”, and holds a list called “PFD display”, one row for each thing the display shows, in the display’s own words. Colors are said after the words they belong to, for example “Thrust: MACH, green”, and a value the display draws as crosses reads “XX”. The list follows the display every second and keeps you on your row. F5 refreshes it without a word, and Escape closes it.

While a display is dark, for example cold and dark, its key opens the window on one row, “E/WD: not available, display off”, and the rows appear by themselves when the display comes on.

When BA cannot read a display. For any other reason the key reads the display with AI vision instead, so you need an AI provider for it. BA moves the camera for you, as described in AI Display Reading. These reads need Fenix v3: on an older Fenix the camera frames the wrong displays, so update the Fenix. Alt+N’s AI read is the captain’s navigation display, the one whose range and mode you set on the left EFIS. Alt+P’s is the First Officer’s PFD; the two PFDs differ only in the altimeter setting and in which side’s autopilot and flight director are shown. With the three round standby gauges there is no ISIS to read, so Alt+I is always the AI read, and the ISIS entry in the Fenix windows list says “This Fenix has no ISIS.” Alt+D, describing the outside scene, is always an AI read. In the rare case that a display shows something BA does not recognize, its window opens on one row saying so, rather than leave anything out.

The Fenix version matters. A Fenix update can change the display data, so BA reads it only on Fenix versions it has been checked against, and a Fenix update can turn the windows and announcements off until a BA update has checked the new version. When that happens, BA tells you once each time the Fenix loads, for example “Fenix display channel not available for Fenix build 3.0.0.7613: displays use AI reading; FMA and E/WD announcements are off.” Everything else keeps working, and the display keys give the AI read. fenix_channel.log, in BA’s logs folder, says why.

PFD window. The FMA by column (“Thrust: MACH, green”, and a message as “FMA message: LVR CLB, white”), the airspeed and its trend arrow, the speed target, the tape’s speeds from the highest down, the Mach, the altitude with its baro setting, the vertical speed, the attitude, the flight director bars, the heading and track and the radio altitude. From your minimum down the altitude says amber, as the PFD draws it: “Altitude 700 feet, amber, QNH 1013”. At a BARO minimum that is the only sign the PFD gives. An instrument the PFD has lost reads its flag instead, for example “SPD flag”. With the LS button on come the LS information and the deviations. These name the diamond, so you cannot read them as the aircraft’s side: “Localizer diamond 0.4 dots right”, “Glideslope diamond 1.3 dots above”, “Localizer diamond at full scale, left”, “Localizer centered”. With LS off and an ILS approach armed, the window adds “LS flag: ILS, amber”, the PFD’s own reminder to press LS.

E/WD window. The engines, one row per value with engine 1 then engine 2, in the screen’s order for your engines (N1, EGT, N2 and FF on the CFM; EPR, FF, EGT, N2 and N1 on the IAE); the thrust limit; the fuel on board; the flaps (“Flaps: 1+F, green”); then the warning lines and memos, in their colors. After the list come T.O CONFIG, CLR left, CLR right, RCL and EMER CANC, which press the panel’s own keys, so you can press one and read what it did. Use this window for what the E/WD shows, and the Engines window for oil and air temperatures.

ISIS window. The speed column with each speed bug that is on and the Mach from .50, the attitude (“Pitch 2.6 degrees up, bank 1 degree left”), the localizer and glideslope while the ISIS’s LS scales show, and the altitude with the baro setting and each altitude bug that is on. While the ISIS aligns it shows its flags and “INIT 90 seconds”, and “ATT 10 seconds” in a quick realignment: these are the lengths the ISIS draws, not a countdown. On the ISIS’s bugs page, the rows list its bugs. After the list come the ISIS panel’s controls: BUGS, LS, Plus, Minus, RST, Baro Inc, Baro Dec and Baro Push, so you can press one and read what it did: the bugs page, the LS scales, the baro setting. On the bugs page, Plus and Minus choose a bug, Baro Inc and Baro Dec step its value (an altitude bug by 100 feet), and Baro Push switches it on. RST holds the button for 3 seconds, as a quick realignment needs, and says “ISIS Reset pressed”; Baro Push says “ISIS Baro Push pressed”, and the altitude row shows the baro setting it left.

DCDU window: Input Ctrl+Shift+D. The DCDU’s screen in a window called “Fenix DCDU”, laid out like the MCDU and with no colors named: the header, the message and info lines, then a row for each pair of keys. On a Fenix with no DCDU you hear “This Fenix has no DCDU.”

With the window open or not, BA calls each new message (*“DCDU: <header>, "*), a waiting message (*"DCDU: 3 messages"*) and every new info line. A message that arrives within 3 seconds of your own key press is not called, though the count still is. The row "DCDU messages" in the Fenix Monitor Manager mutes these.

Fenix windows: Input Ctrl+Shift+F. This opens a list called “Fenix windows”. Each row gives a window’s name and what it holds, for example “Engines. N1, EGT, N2, fuel flow, oil and air temperatures, from the Fenix’s own values”. Arrow to a row and press Enter: the list closes and that window opens. Escape closes the list. The list holds the display windows above and the five windows described below: Engines, Cabin, Failures, Fenix documents and Fenix options. Those five read the Fenix’s own data service, so the Fenix must be loaded. None of them speaks when it opens, each has a read-only status box you can Tab to, and they all close when you change aircraft. On any other aircraft, Input Ctrl+Shift+F says “This aircraft has no extra windows.”

Engines window. The Fenix’s own engine readings, in a window called “Fenix engines”: the same numbers its screens show, where the simulator’s own engine values do not match the Fenix. The list has one value per line, with the two engines on neighboring lines: first whether each engine is running (“Engine 1: running”, “Engine 2: not running”), then each engine’s N1, EGT, N2, fuel flow, oil quantity, oil pressure and oil temperature (“Engine 1 N1: 22.4 percent”), then the total and outside air temperatures. Fuel flow is in the weight unit set in the Fenix EFB, kilograms or pounds per hour; oil quantity is in quarts and pressure in psi. A value the Fenix does not give reads “–”. The values update every second without moving your place. F5 reads them all again and says “Engines refreshed”; if the Fenix gives nothing, you hear “No engine data from the Fenix. Is the Fenix loaded?” While the window is open, BA says “Engine 1 running” or “Engine 1 stopped” when the Fenix’s own engine state changes; “running” comes when the start is complete, not at light-up. The status box names your Fenix and the fuel flow unit. Escape closes.

Cabin window. The Fenix’s flight attendant panel (FAP), in a window called “Fenix cabin”. The status box at the top says whether the cabin system has started; once it has, it reads “Cabin system ready.” Below it are five tabs; Ctrl+Tab moves between them. Each tab has a list of values, one per line, with its controls after the list:

After a press, the window speaks only what your screen reader cannot: the new volume, temperature or preselect, for example “Water preselect: 75 percent”, with ”, unchanged” added when nothing moved; a door’s line once it has opened or closed; the announcement now playing (“Now announcing: Safety Briefing”); and the memo (“Memo: After Takeoff”). A press that cannot act says why, for example “The Fenix is not answering.” or “The memo is already empty.” Escape closes.

Failures window. The Fenix’s manual failures, in a window called “Fenix failures”: a tree of ATA chapters, title first (“Air Conditioning, ATA 21”), with each failure under its chapter and group, named as the Fenix names it. A failure that is failed or armed says so, for example “CPC 1, failed”, “CPC 1, armed: above IAS 250” or “CPC 1, armed: fails in 30 seconds”.

The status box shows your Fenix, how many failures are armed and failed, and the Fenix’s automatic failure settings, which you change in the Fenix options window. While the window is open, a failure that triggers is spoken, for example “Failure triggered: CPC 1.” Escape closes.

Fenix documents window. The Fenix EFB’s documents: the ECAM procedures, the QRH, checklists, delay codes, the Fenix user guide and your own documents, in folders as in the EFB, in a window called “Fenix documents”. The Pinned group is always first in the tree (“Pinned (0)” when nothing is pinned). Press Enter on a document to open it in the reader, a page your screen reader reads in browse mode, where H moves by heading and T by table. Colors the Fenix shows are said as words, “(amber)” and “(red)”; the flight-phase picture reads, for example, “Flight phases: 3, 4, 5”; checklist lines are check boxes; and every section starts open. In the QRH tables, PF means Pilot Flying and PM Pilot Monitoring.

Your own Markdown documents go in the Fenix’s documents folder (C:\ProgramData\Fenix\EFB\Documents, according to Fenix’s guide) and appear under My Documents. PDFs are listed but cannot be read; BA tells you so. One known issue: the first document you open with Enter after opening the window may read only “document” until you press Tab once; later documents read normally.

Fenix options window. Every option in the Fenix EFB’s Settings, with its value in the Fenix’s own words, as a tree in a window called “Fenix options”. A row reads “Label: value”. The first group, “Options that affect MSFS Blind Assist”, holds the options that can change how BA works, each with a note on what it changes. Then come the Fenix’s own setting categories, in the EFB’s order, and last “Other, not in the Fenix EFB”. Your Hoppie, Navigraph, Pushover and SimBrief credentials read “set, hidden”.

After a change, BA waits for the Fenix to show it, which can take a few seconds, then updates the row, and your screen reader reads it. If the row’s text did not change, for example when you make the current value permanent, your screen reader has nothing new to say, so BA reads you the row itself, the option’s name and value. If the Fenix did not take the change, BA says so, for example “Not made permanent:” followed by the option as it now is. The status box gives the Fenix version, the three keys and, after “Not what MSFS Blind Assist is tested with”, any option that affects BA and is set to a value BA was not tested with. Today that is Control Position set to First Officer, because BA’s audio panel controls were only checked from the Captain seat. EFIS Linking: Baro, EFIS Linking: FD/LS, Channel Spacing and FCU Readouts work with either setting, and their notes say what was heard when they were checked; Enter on an option speaks its note. Escape closes.

First Officer: Output Shift+C. Flows and checklists. See The First Officer and Checklists.

The SD window

Output Alt+S opens the System Display in a window called “Fenix SD”. The list starts with the name of the page the SD shows, then that page’s values, then the bottom line: “TAT °C: +17, green”, “SAT °C: +17, green”, “UTC: 18:16” and the gross weight. After the list, Tab reaches the ECAM panel’s page keys, ENG to F/CTL, ALL and STS. Each presses the panel’s own key, and the list shows the new page at its next refresh. ALL moves one page per press and says “ECAM ALL pressed”.

The words are plain: valves read “open”, “closed”, “in transit”, “failed open” or “failed closed”, buses “powered” or “not powered”, and pumps “running”, “off” or “LO”. A row says a color or a pulse only where the Fenix sends one, for example “NORM BRK, amber”, “ΔP: 8.2 PSI, pulsing” or “LP valves: open, closed amber”. A value BA cannot read on a page says “not available” and leaves the rest of the page alone.

The ND window

Output Alt+N opens the captain’s navigation display in a window called “Fenix ND”. The list says what the screen shows and where, each row starting with its place on the screen: “Top left:”, “Top center:”, “Top right:”, “Center:”, “Right side:”, “Map:”, “Bottom left:” and “Bottom right:”. It lists only what the ND draws, so a row comes and goes as the mode and range change. The rows follow the range and mode you have set.

Where a thing is on the map reads as its distance and bearing from your nose: “10.0 NM ahead”, “8.1 NM, 103° left”, “8.1 NM behind”. In PLAN mode, which is north-up, it is a compass point from the center waypoint: “5.0 NM north-west of VAKSU”. A symbol the edge of the display cuts off ends ”, at the edge”.

The rows, top of the screen first:

A color is named only where it tells you something: amber and red always, the magenta navaids against the cyan tuned one, the white TO waypoint against the green route, and the green route, yellow temporary and cyan missed approach lines.

Under the list are the captain’s EFIS controls: a Mode list (LS, VOR, NAV, ARC, PLAN), a Range list (10 to 320) and the CSTR, WPT, VOR.D, NDB, ARPT and LS buttons, each reading on or off. They work as the panel’s own do, and a press is heard once: your screen reader reads the button’s new state, and BA does not repeat it. The Mode and Range lists follow the ND, so a change made in the cockpit shows there, even with your cursor on the list. A second Alt+N brings the window forward.

Output Ctrl+W reads the next waypoint, its bearing, distance and time, in the ND’s order: “VAKSU, 318 degrees, 84 nautical miles, 17:29”, or “No active waypoint” with no flight plan.

With the window open or not, BA announces the ND’s messages, “ND message: GPS PRIMARY” and “ND message gone: GPS PRIMARY”, and a new next waypoint while the ND shows it, “ND: RONII, 8.1 NM”. MODE CHANGE and RANGE CHANGE are not announced, because you just made the change. The row “ND messages” in the Fenix Monitor Manager mutes these.

Aircraft-specific hotkeys and callouts

The usual Readout Hotkeys and FCU readouts work. Output Ctrl+M opens the Fenix Monitor Manager.

Output Shift+1 to Shift+6 read the captain’s PFD speed tape in whole knots: Shift+1 green dot, Shift+2 S, Shift+3 F, Shift+4 VLS, Shift+5 alpha prot (VSW while the tape draws one) and Shift+6 VFE next, for example “Green dot 237 knots”. A speed the tape does not show says, for example, “Green dot not available”.

Output D and Shift+D say how far it is, and how long at your ground speed, to your destination and to the top of descent, worked out from the Fenix’s flight plan: “398 miles to destination”, “96 miles to top of descent: 00:12:00”. Shift+D says “Past top of descent” once the descent has begun. It says “Top of descent not available” at the gate, where the ND draws no top of descent, before a cruise level is entered, and from glideslope capture on. With no flight plan D says “Distance to destination not available”.

The TO CONFIG key on the ECAM panel works like the real test. BA presses it, then watches the master warning and master caution lights. The Fenix’s warning computer deliberately takes a moment to light them, so “Takeoff config normal.” comes only once both lights have stayed dark for about two seconds. A bad configuration is announced as soon as a light comes on: “Takeoff config: check configuration.” for the master warning, or “Takeoff config: caution. Check the ECAM.” for the master caution. If BA could not read the lights, you hear “Takeoff config: no result read. Check the ECAM.” The First Officer’s takeoff config test says the same.

On the take-off roll, BA calls “V1”, “Rotate” and “V2” from the speeds on the MCDU’s PERF TAKE OFF page, whether or not Takeoff Assist is on. You can enter or change the speeds any time before the roll. The Fenix itself also calls V1, so you hear V1 twice. Each call is muted with its speed’s row in the Fenix Monitor Manager (“MCDU V1 Speed”, “MCDU VR Speed”, “MCDU V2 Speed”), which also mutes BA reading that speed when you enter it; a cleared speed is read as “not set”. See Takeoff Speed Callouts.

Automatic announcements cover the master warning and caution, the cockpit’s annunciator lights and switch states, COM frequency changes, the altimeter, and the cockpit door (“Cockpit Door: Open”). The lights of Econ Flow and ACT Pump, and the lamps of the EFIS flight director and LS buttons, stay quiet right after you change their control in BA’s panels, because your screen reader already says the new state. When the change comes from anywhere else, such as a click in the cockpit, the First Officer, or the other side of linked flight directors, you hear it, for example “EFIS Right FD: On”. The FCU vertical speed is spoken only while its window shows a selected value, with its sign, for example “FCU VERTICAL SPEED: +300”; a managed climb or descent stays quiet. Two things are monitored but kept silent by default: the clock’s chronometer and elapsed-time counters (they tick every second) and the four seat switches. You can switch any of them back on in the Monitor Manager.

FMA changes are spoken once they have settled, read from the captain’s PFD in its own words and colors: “FMA: Thrust: THR CLB, green”, “FMA: Vertical: ALT*, green”, and each message as “FMA message: LVR CLB, white”. Column 5 (AP, FD and A/THR) is never spoken, because the FCU’s lights are. The Lateral column stays silent while LAND, FLARE or ROLL OUT shows. Nothing is spoken while the PFD cannot be read. The row “FMA changes” in the Fenix Monitor Manager turns this off.

ECAM warnings, cautions and memos are spoken from the Fenix’s own list, with the color of their line on the E/WD. A warning interrupts what is being said (“ENG 1 FIRE, red”); a caution waits its turn (“ELEC GEN 1 FAULT, amber”). The list updates about every 4 seconds, so a warning can come up to 4 seconds after the master warning, and a very short one can go unsaid. About 5 to 8 seconds after a failure leaves the E/WD you hear “ENG 1 FIRE cleared”. LAND ASAP is heard by its color after the failure that caused it, and memos use the E/WD’s own words. The rows “E/WD warnings”, “E/WD cautions” and “E/WD memos” in the Fenix Monitor Manager turn each kind off. These rows, “FMA changes”, “DCDU messages” and “ND messages” all start on, and all need the display data, as Special windows explains.

With the Fenix loaded, BA also announces these from the cabin, whether or not the Cabin window is open:

Each has its own row at the end of the Fenix Monitor Manager: “Cabin ready”, “Cabin doors opening and closing”, “Cabin slides armed and disarmed” and “Cabin cautions”.

Things to know

FlyByWire A380X

The FlyByWire A380X is a free simulation of the Airbus A380-842 by the same team as the A32NX. Its cockpit is a newer generation than the A320’s, and BA handles it differently in important ways. BA reads the real cockpit displays live, with no add-on to install and no Developer Mode. BA also ships its own detailed A380 manual, “a380-manual.html”, in its Guides folder. Some of its details are older than this guide; where they disagree, this guide describes the current version.

Before you fly

You need:

When BA first connects to the A380 it stays silent for a moment, so you are not flooded with the whole starting cockpit state. Only changes after that are spoken.

How the panels are organised

The A380 has five sections.

Overhead: ELEC (four batteries, four external power connections, generators, IDGs, bus tie and emergency generator), APU, Fuel (tank transfers, jettison and every feed tank pump), Hydraulics, Bleed Air, Air Conditioning (cockpit and cabin target temperatures), Pressurization, Ventilation, Cargo Air, Anti Ice (probe and window heat, wing, four engines), Fire, Oxygen, Calls (including evacuation and “Signal Cabin Ready”), Signs, Wipers, ADIRS, Flight Control Computers (PRIMs, SECs, rudder trim and the nosewheel steering pedal disconnect), Engine FADEC and Manual Start, Recorder and Misc, GPWS, Reset (the computer reset buttons, such as Reset FMC A), Interior Lighting and Exterior Lighting.

Glareshield: FCU, EFIS Captain, EFIS First Officer, Warnings and OIT.

Instrument: Gear (including gravity extension), Autobrake (Disarm, BTV, Low, L2, L3, High, and RTO arm), ISIS, Source Switching and Clock (chronometer start and stop, reset, and the elapsed time knob).

Pedestal: Engines (engine mode selector and four masters), Thrust Levers, Flaps and Brakes (flaps, parking brake, anti-skid), Speed Brake, ECAM Control Panel, Weather Radar, Transponder, RMP, Audio Control Panel Captain, Audio Control Panel First Officer, and Cockpit (sliding windows, sunshades, tables, footrests, keyboard trays, the cockpit door and the seats).

Displays: PFD, ND, Status, Speeds and Minimums, which are read-only status displays.

Some A380 controls are worth knowing about:

Autopilot / FCU windows

The A380 has the same set of FCU windows as the A32NX, in Input mode: Ctrl+S speed, Ctrl+H heading (with HDG·V/S and TRK·FPA), Ctrl+A altitude, Ctrl+V vertical speed or flight path angle, Ctrl+P the autopilot panel and Ctrl+B the altimeter (“Set A380 Altimeter (both sides)”). Two differences:

Pushing or pulling the altitude knob announces “Altitude Mode: Managed” or “Selected”, and Output Shift+A tells you which one you are in.

The shortcut and push and pull keys are the same as on the A32NX.

MCDU

The A380 does not have a classic MCDU. It has two large MFDs (multi-function displays), operated with a keyboard and trackball called the KCCU. BA hides all of that: Input Shift+M opens the MFD as a flat list you arrow through, and BA drives the real display underneath. You never need the cursor or trackball.

The window title says which side you are using, for example “A380X MCDU (Captain)”. The Active MCDU side selector switches between Captain and First Officer, which are independent on the real aircraft.

Each line ends with a word that tells you what you can do with it:

To enter a value:

  1. Arrow to the field.
  2. Type the value. It goes into the scratchpad (Alt+S also jumps there).
  3. Press Enter. BA sends the scratchpad to the selected field.

To clear: Backspace (or Alt+C) works like the Airbus CLR key. It clears your scratchpad first, then a displayed message (“Info cleared”), then the selected field. Delete always clears the selected field. A field that cannot be emptied says “Cannot be cleared”. A value typed into a pick list that does not offer it is reported as “Not in list”.

To move between pages there are three ways:

F5 refreshes. Alt+N switches BA’s weight readouts between kilograms and pounds.

Reading the flight plan: on F-PLN each waypoint is one line that includes the leg leading to it and any constraint, for example “BI613, via BASU1D, 5 NM, track 294°, at or below 5000 feet”. The page shows about a dozen waypoints at a time with the destination at the bottom, so press Ctrl+Down to see the next part of the route.

Changing the flight plan: press Enter on a waypoint to open its revision menu (direct to, insert next waypoint, delete, hold, airways, overfly, departure, arrival). Some changes create a temporary plan; scroll to the bottom and press Enter on the insert option to keep it, or the erase option to cancel it. To clear a discontinuity, press Enter on the “DISCONTINUITY” line and choose DELETE.

Loading a SimBrief route: set your SimBrief ID in the flyPad first and do not set a destination on the MSFS world map. Then on INIT (Alt+I) press Enter on “CPNY F-PLN REQUEST”, wait for the scratchpad to say the company flight plan has been received, press Enter on the received flight plan, and choose INSERT.

The MFD WIND page works too. Every wind field says its phase, row and column, so you can enter winds and request, insert or clear a company wind uplink.

ATC COM (Alt+A) gives you the datalink pages: connection, message record (open it when BA announces an ATC message waiting) and D-ATIS. Some ATC COM pages are still unfinished on FlyByWire’s side and show an error page.

EFB

The flyPad opens with Input Shift+T in a window called “A380X flyPad EFB”. It works exactly as on the A32NX: a browsable web page with headings, links and real edit fields. See the A32NX section above and Aircraft EFBs.

On the A380, the door tiles use the aircraft’s real door names, such as “Main Door 1 Left” and “Upper Door 1 Left”. The flyPad’s own checklist page is only a tracker on the tablet; ticking things there does not touch the aircraft. For the real cockpit checklist, use the live ECL below. BA does not make the flyPad’s pushback page accessible; use GSX for pushback (Input Alt+G opens the Access GSX window).

The flyPad is also where you log in to Navigraph, which the airport map needs.

Special windows

Radio Management Panel: Input Ctrl+Shift+R. This window reads the live RMP screen as text, and you operate it entirely with keys. The Side selector chooses Captain, First Officer or Overhead; the screen, announcements and keys all follow it. The status line shows, for example, “Live — Captain — VHF page”.

To tune a VHF radio:

  1. Press Alt+V for the VHF page.
  2. Press Ctrl+1, Ctrl+2 or Ctrl+3 to select radio 1, 2 or 3 (or F1 to F3 with alternate keys). You hear “Radio 1”.
  3. Type the frequency without a decimal point. It completes itself: 118500 or just 1185 both give 118.500. Backspace deletes a digit.
  4. Press Enter. The frequency goes into standby and BA reads it back, for example “VHF standby 1, 118.500”.
  5. Press Alt+1, Alt+2 or Alt+3 to swap that radio’s standby and active frequencies. You hear “Swapped”.

Alt+C fully clears a stuck entry.

To set the squawk:

  1. Press Alt+T for the transponder page.
  2. Type the four digits (0 to 7). It sets on the fourth digit and reads back, for example “Squawk 2222”.
  3. Alt+I sends IDENT.

Alt+Home returns to the screen from a button. The HF, TEL, NAV and MENU keys do nothing, because FlyByWire does not model them yet. Any message the RMP shows, such as an invalid frequency, is announced.

Note that Ctrl+Shift+R in Output mode reads your last landing rate instead.

Live Electronic Checklist (ECL): Output Ctrl+Shift+C. The A380’s real checklists, as the cockpit uses them, including any abnormal procedure an ECAM alert raises. The checklist appears on the aircraft’s display when the window opens and is hidden again when it closes.

Sensed items tick themselves when the aircraft detects the action. Set the parking brake, for example, and you hear the item followed by “checked”. If the window shows “Checklist not reachable”, make sure the aircraft is loaded and its displays are powered, then press Refresh.

Output Shift+C opens the A380’s First Officer, with its flows and its own checklists. See The First Officer and Checklists.

Airport Map and BTV (OANS): Output Ctrl+Shift+B. On the real A380 you arm Brake-To-Vacate (BTV) by tapping the runway and exit on a moving airport map. This window lets you pick them from lists instead and reads the predicted stopping distances. It never changes or zooms your navigation display. It has three tabs:

The top line tells you what is available, for example “OANS: full” followed by the airport, or “OANS: Navigraph maps NOT loaded — manual BTV only. Log in via the flyPad EFB (Shift+T) → Navigraph.” Without Navigraph maps, a manual BTV section lets you type a stop distance in metres and press Apply, then select the landing runway in the FMS. The maps only fill in once the ADIRS are aligned and an airport is loaded.

Arming BTV takes two steps, and both are needed:

  1. Arm a runway and an exit in this window, choosing an exit beyond the predicted wet stopping distance.
  2. Set the Autobrake combo (Instrument section, Autobrake panel) to BTV.

Only then does the aircraft arm BTV, and BA announces “Brake To Vacate: Armed”. If you never hear that, check the autobrake. For taxi directions after landing, use BA’s own Landing Exit Planner and Taxi Guidance; they do not need Navigraph.

E/WD window: Output Alt+E. Engine readings, memos and the active warnings with their action lines, read with the arrow keys. F5 refreshes, Escape closes.

PFD, ND, ISIS and System Display. Read the PFD (flight mode annunciator, approach capability, PFD messages), ND, Speeds and Minimums panels in the Displays section, and the ISIS panel in the Instrument section. For the System Display, use the System Display Page combo on the ECAM Control Panel (Pedestal). It lists the A380’s 16 system pages. Choosing one switches the real system display and reads that page’s values: per-tank fuel, temperatures, pressures, door states, engine readings and so on.

Aircraft-specific hotkeys and callouts

The Output readouts are the same as the A32NX’s (Shift+1 to Shift+6 for the characteristic speeds, Ctrl+W, D, Shift+D, B and so on), with these differences:

The A380 announces everything the A32NX does, and also:

All of these can be muted in the A380 Monitor Manager (Output Ctrl+M); for example “BTV Distance to Exit”, “Runway Remaining” and “Brake To Vacate” each have their own row.

Things to know

Headwind A330-900neo

The Headwind A330-900neo is a free widebody built on FlyByWire’s A32NX code. BA treats it as an A32NX with a few differences, so almost everything in the A32NX section above applies here unchanged: the same panels and sections, the same FCU windows, the same MCDU, the same flyPad, the DCDU and the E/WD window. Its hotkey list is the A32NX list.

Before you fly

You need the Headwind A330-900neo, the MobiFlight WASM module, and the displays powered. SimBridge is optional, as on the A32NX. Headwind’s A330 is an early release, so some of BA’s features on it have been checked less thoroughly than on the A32NX. Report anything that reads wrong.

How the panels are organised

Exactly as on the A32NX: Overhead, Glareshield, Instrument and Pedestal, with the same panels. See the A32NX panels. The PFD status box leaves out a few rows the A320 shows (the stall warning and alpha protection speeds and VAPP), because the A330 does not publish them.

Autopilot / FCU windows

The same windows and keys as the A32NX.

MCDU

Input Shift+M opens the MCDU, with the same keys as the A32NX MCDU. It reads the A330’s own MCDU display.

EFB

Input Shift+T opens the flyPad in a window called “A330 flyPad EFB”. It is the same flyPad as on the A32NX.

Special windows

Aircraft-specific hotkeys and callouts

The hotkeys and automatic callouts are the A32NX’s, including “V1”, “Rotate” and “V2”. The differences are in how a few readouts get their data:

Things to know