MSFS Blind Assist User Guide

This guide covers MSFS Blind Assist 10.0.0. The guide for the newest release is online at msfsblindassist.com/guide.

The whole guide is on this page. Parts are headings at level 2, chapters level 3, sections level 4 and subsections level 5, so with a screen reader you can press 2 to move by part and 3 by chapter.

Part 1: Getting Started

Welcome and How to Use This Guide

Welcome to MSFS Blind Assist. This guide takes you from a fresh download to your first flight, and then on through every feature the app offers. It is written for blind and visually impaired pilots, and it assumes no experience with the app. If you have never flown a simulator before, that is fine too: Part 9 explains the general flying ideas the rest of the guide relies on.

What MSFS Blind Assist Is

MSFS Blind Assist (we call it BA in this guide) is a Windows application that makes Microsoft Flight Simulator usable with a screen reader and a keyboard. It runs beside the simulator, connects to it, and gives you three things a sighted pilot gets from looking at the cockpit:

BA speaks through your screen reader. It works with NVDA directly, and with JAWS and other screen readers through a standard helper library. If no screen reader is running, BA falls back to Windows' built-in speech (often called SAPI), so you still hear everything.

BA works alongside your screen reader, not instead of it: when you press a button or change a list in BA's windows, your screen reader already says what happened, so BA stays quiet. How BA Talks to You explains when BA does speak.

Finding Your Way Around This Guide

The guide is long, because it is the complete manual. You do not need to read it from start to finish. It is built so you can jump straight to what you need using headings.

To move by heading in your web browser:

Many sections share the same pattern of sub-headings: "What it is", "When to use it", "How to use it", "What you will hear", "Settings" and "If something goes wrong". Once you know the pattern, you can jump straight to the part you want.

Some conventions used throughout:

Getting Started

What You Need

Note: On the FlyByWire A320neo, the FlyByWire A380X, the Headwind A330-900neo, the TFDi MD-11 and the BlueBird 757-200, if the module is missing, BA tells you a short while after connecting: "MobiFlight calculator path unavailable. Some cockpit controls may not respond." If you hear that, install or reinstall the module and restart the simulator. The Fenix A320 and the HorizonSim 787-9 do not give this warning, so on those check the module yourself if a control never responds.

Some features also need their own free accounts or keys, such as SimBrief for flight plans or an AI provider key for reading cockpit displays aloud. You do not need any of these to start; each is explained in its own chapter.

Installing

BA has no installer. It comes as a zip file that you extract to a folder of your choice.

  1. Download BA from the project's GitHub page. There are two builds:
    • The stable release, named MSFSBA.zip. This is the one most pilots should use.
    • The preview build, named MSFSBA-preview.zip. It is rebuilt every time a change is finished, so it has the newest work. Every change is reviewed and tested before it gets there, but it has had far less flying time than a release, so bugs are more likely.
  2. Extract the zip to a folder you will remember, for example a folder called MSFS Blind Assist in your Documents. Avoid extracting it inside the simulator's own folders.
  3. Open the folder and run MSFSBlindAssist.exe.

To update by hand later, close BA and extract the new zip over the same folder. Most of the time you will not need to: BA can update itself (see Updates).

Inside the folder you will also find a folder called HotkeyGuides, holding the hotkey list for every aircraft as plain text files, and a Guides folder holding a separate manual for the FlyByWire A380X.

Only one copy of BA can run at a time. If you start it twice, you hear a message box saying "MSFS Blind Assist is already running. Only one instance can run at a time."

Where BA keeps your files

Everything BA stores about you lives in one folder: %APPDATA%\MSFSBlindAssist. You can open it by pressing Windows+R, typing %APPDATA%\MSFSBlindAssist and pressing Enter. Inside it are:

Because your settings live there and not in the program folder, updating or reinstalling BA never loses them.

Your First Launch

When BA starts, it opens its main window. After about two seconds you hear "Initializing, please wait", and BA begins looking for the simulator. You can start BA before or after the simulator; it keeps trying until it finds it.

On the very first launch, and on every launch while something is missing, BA may open one or two setup windows before anything else. They appear one at a time, never stacked on top of each other.

The Set up MSFS Blind Assist window

This window opens when BA is missing data it needs:

Focus lands on a read-only text box headed What is missing, which lists only what is missing. It begins "Some data MSFS Blind Assist needs is not set up yet." For the navigation database it says that it is not built, that building takes 2 to 5 minutes, and that for MSFS 2024 the simulator must be running at the main menu. For location data it tells you the current state, such as how much disk space the download needs.

The buttons are:

BA never remembers that you dismissed this window: it comes back on every launch until the data is there. If you would rather it did not, turn off Check for missing data when the app starts on the Updates tab of the Settings window.

Tip: While a location data download started from this window is still running, BA skips that launch's automatic update check. An update would restart the app and cancel your download. It checks again next time.

The location data and its options are covered in Location Info and Nearest City.

The PMDG SDK Setup Check

This applies only if you fly the PMDG 737 or the PMDG 777.

What it is

PMDG aircraft share their cockpit information with outside programs through a feature PMDG call the SDK data broadcast. It is switched off unless a few lines are present in the aircraft's options file. Without those lines, BA's CDU window and many cockpit readouts for the PMDG stay empty.

BA checks this for you whenever you choose the PMDG 737 or 777 from the Aircraft menu, and when you start BA with one of them already selected. If any installed variant (for example the 737-800, or the 777-300ER) is missing the lines, a window opens titled PMDG 737 SDK setup or PMDG 777 SDK setup.

BA never changes PMDG's files itself. The window tells you exactly what to do.

How to use it

Focus lands on the Instructions box, which your screen reader reads. Below it are:

The steps the window gives are:

  1. Close Microsoft Flight Simulator first. PMDG rewrites this file when the simulator exits and can drop lines added while it runs.
  2. For each file in the list, select it, press Open folder, then press Enter on the selected file to open it (usually in Notepad).
  3. If the file already has an [SDK] section, replace it with the lines; otherwise paste them at the end. Keep only one [SDK] section.
  4. Save the file and start the simulator.

If BA cannot find an options file at all, the instructions explain that PMDG creates it the first time you load that aircraft in the simulator. Load the aircraft once, then pick it again from BA's Aircraft menu (or restart BA) and the window will list where the file is.

Like the startup data window, this one appears every time while anything is missing.

What it is

BA keeps its own database of airports, runways, taxiways, gates, navaids and instrument procedures, built from the scenery and navigation data installed in your simulator. Taxi guidance, the landing exit planner, teleporting to runways and gates, the flight planning window, approach guidance and airport lookups all read from it. Without it, those features cannot work.

There is a separate database for each simulator: one for MSFS 2020 and one for MSFS 2024. BA automatically uses the one that matches the simulator it is connected to, so if you fly both, build both.

The database is built by a tool included with BA, called navdatareader (written by Alexander Barthel, the author of Little Navmap).

When to build it
How to build it

Open the window from the File menu, Nav Database. You can also reach it from the Set up MSFS Blind Assist window's Build navigation database button.

The window contains:

The two simulators are built differently, and this matters:

To build:

  1. Close or start the simulator as described above.
  2. Press the build button for your simulator. A confirmation message box reminds you of the requirement and says the build takes 2 to 5 minutes. Choose Yes.
  3. A progress window opens, titled for example Building FS2020 Database, with a progress bar, a status line and a Cancel button. Leave it to finish. If you press Cancel, BA asks "Are you sure you want to cancel the database build?"
  4. When it finishes, BA speaks the result, for example "FS2020 database built successfully", and shows it in a message box titled Build Complete. If the result includes a warning, BA reads the warning in full: it matters.
  5. Press Close to return to the main window. BA then says something like "Database settings saved. Using FS2020 - 41,804 airports".

If the build fails or is cancelled, a message box titled Build Not Completed explains why.

If your simulator has Navigraph's navigation data installed, the database includes it, and the status line says "Navigraph data available". Otherwise it says "No navigraph, using Microsoft's Native nav data". Nothing else changes: every feature simply reads the one database, whichever data it holds. If you install or update Navigraph's data, rebuild the database so BA sees it.

The Database Mismatch Warning

Sometimes the simulator you are running and the database BA is using do not match — most often because you have only built the database for the other simulator. When you use a feature that depends on accurate airport positions (teleporting to a runway or gate, choosing a destination runway, or importing a SayIntentions taxi route), BA stops and opens a window titled Database Mismatch Warning. It says, for example, "Warning: You are running Flight Simulator 2024 but have FS2020 database selected. This may provide incorrect runway coordinates and airport data. Would you like to switch to FS2024 database now?"

If something goes wrong

Connecting to the Simulator

BA connects to the simulator on its own. You do not press a connect button.

  1. Start the simulator and load a flight. You can do this before or after starting BA.
  2. While BA is looking, its main window's status line reads Waiting for simulator, and BA tries again every few seconds.
  3. Once the flight is loaded and BA has identified the aircraft, you hear "Connected to" followed by the aircraft's title from the simulator, and its airline and flight number or its registration if the simulator has them. Then BA says which BA profile is active, for example "FlyByWire A320neo Profile and panels active". The status line shows the same text.

For about five seconds after connecting, BA holds back its automatic announcements. This stops it from reading out every light and system state at once when you connect to an aircraft that is already set up. Hotkeys you press still speak straight away.

If you press a hotkey before BA has finished connecting, you hear "Not connected to simulator, please wait".

If the simulator closes or the connection drops, BA says "Disconnected from simulator" and goes back to looking for it. When you load a flight again, it reconnects by itself.

Choosing Your Aircraft

BA has a separate profile for each aircraft it supports: its own panels, hotkeys and announcements. BA does not switch profiles for you when you load a different aircraft in the simulator. Choose the matching profile from the Aircraft menu. BA remembers your choice and uses it the next time it starts. The first time you run BA, the FlyByWire A320neo is selected.

The Aircraft menu lists the ten supported aircraft, in this order:

  1. FlyByWire Airbus A320neo
  2. FlyByWire Airbus A380X
  3. Headwind Airbus A330-900neo
  4. Fenix A320 CEO
  5. PMDG Boeing 737 (the 737-600, -700, -800 and -900)
  6. PMDG Boeing 777
  7. HorizonSim Boeing 787-9
  8. iFly Boeing 737 MAX8
  9. TFDi Design MD-11
  10. BlueBird 757-200

To open the menu, press Alt, then use Right Arrow to reach Aircraft and Down Arrow to move through the list; the current aircraft is marked as checked. Press Enter on the one you are flying. You hear "Switched to" and the aircraft name, and the main window's Sections list fills with that aircraft's sections.

Note: If the profile you choose does not match the aircraft loaded in the simulator, panels and hotkeys will not work properly. Always pick the profile for the aircraft you actually loaded.

Each aircraft has its own chapter in Part 8: see Airbus Aircraft and Boeing Aircraft and the MD-11.

The Main Window

The main window is where you operate the aircraft's panels. Take a few minutes to learn it before your first flight; everything else builds on it.

Layout

From top to bottom and left to right, the window contains:

The window title is normally MSFS Blind Assist. On some aircraft it also shows the current flight phase.

Moving around

The Tab key moves from the Sections list, to the Panels list, to the first control in the panel, and on through the controls. Shift+Tab goes back. Three shortcuts jump directly, as long as the main window has the focus and you are not in Input mode:

Key What it does
Ctrl+1 Focus the Sections list
Ctrl+2 Focus the Panels list
Ctrl+3 Focus the Status Display of the current panel (and fill it if it is empty)
F5 Refresh the current panel's Status Display without moving away from where you are

A typical way to operate something:

  1. Press Ctrl+1, and arrow up or down to the section, for example Overhead.
  2. Press Tab (or Ctrl+2) to reach the Panels list, and arrow to the panel, for example Lights.
  3. Press Tab to move into the controls, and keep pressing Tab to reach the control you want.
  4. Change it (see below). Your screen reader tells you the new value.

If there is no Status Display on the panel you are in, Ctrl+3 says "No status display on this panel."

The kinds of controls you will meet

Each control in a panel has a label ending in a colon, followed by the control itself. You will meet these types:

The Status Display

Many panels end with a Status Display: a read-only list (its screen reader name is Status display, updates live (F5 to refresh now)) that shows live readings for that panel, one per row — for example voltages, pressures, temperatures, quantities, or the pages of a system display. Below it is a Refresh button.

On the Airbus aircraft in particular, Status Displays are where you read much of what a sighted pilot reads off the cockpit screens.

When the simulator is not connected

You can browse sections, panels and controls before BA connects, but controls have no live values yet and changing them has no effect. Values appear once BA connects.

Output Mode and Input Mode

This is the most important idea in BA, and the one that beginners most often find confusing at first. Read this section slowly, and try each step as you go.

Why there are two modes

BA's hotkeys have to work while the simulator has the focus, and the simulator itself uses almost every key on the keyboard. If BA permanently took over keys such as A, S or H, you could no longer use them in the simulator. So BA owns only two keys all the time: the two square bracket keys. Pressing one of them puts BA into a mode for a moment, during which the other keys mean BA commands. After one command, the mode ends and your keyboard goes back to normal.

A simple way to remember it: Output is information coming out of the aircraft to you; Input is you putting something into the aircraft.

How to use a mode
  1. Press ] (for Output) or [ (for Input). You hear "output" or "input".
  2. Press the command key or key combination, for example A, Shift+H or Ctrl+T.
  3. BA carries out the command, and the mode ends by itself.

For example, to hear your altitude: press ], hear "output", then press A. In this guide that is written "Output A"; "Input Shift+R" means press [, then Shift+R.

Cancelling a mode

If you pressed a bracket key by mistake, or changed your mind:

The mode does not time out. It stays on until you give it a command, cancel it, or press Escape. If you press a key that is not a command in that mode, nothing happens and the mode stays on, so if you are not sure whether you are still in a mode, press the bracket key again: if you hear "cancelled", you were.

While you are in one mode, the other bracket key does nothing. Cancel the first mode before entering the other.

Warning: While a mode is active, BA has taken over its command keys across the whole computer. If you then try to type in the simulator or another program, those letters will trigger BA commands instead. If keys seem to stop working, a mode is probably still active: press the bracket key you last used to cancel it.

Keys that work without a mode

A few keys are not part of either mode:

Suspending hotkeys

If another program needs the bracket keys — for example while you type a chat message to ATC — open the File menu and choose Suspend Hotkeys. BA says "Hotkeys suspended" and stops listening to the brackets entirely. Choose it again to turn hotkeys back on; you hear "Hotkeys resumed". If BA cannot take the keys back because another program is now using them, it warns you: "Warning: failed to re-register hotkeys. Another application may be using the bracket keys."

Different aircraft, different keys

The two modes are the same on every aircraft, and many keys are shared. Output A, S and H read altitude, indicated airspeed and heading on every supported aircraft. But each aircraft also has its own keys for its own systems, and the same key can do different things on different aircraft. The Hotkey List (next section) always shows the keys for the profile you have selected.

Note: BA listens for the keys Windows calls the bracket keys on a US or UK keyboard (the two keys to the right of P). On some other keyboard layouts Windows gives those codes to different physical keys. If pressing your bracket keys never turns a mode on, try the two keys to the right of P, or ask for help on the Discord.

The Hotkey List

What it is

The Hotkey List shows every hotkey for your current aircraft profile, grouped into categories, with Output mode keys and Input mode keys clearly separated. It is the quickest way to find a key while you are learning.

How to use it
  1. Open the File menu and choose Hotkey List.
  2. The window opens with focus on the Search box (named Search by category or keyword). Type a word such as fuel, autopilot, taxi or heading, and the list below shows only the matching entries. You can also arrow through the box to pick a category; the first choice, All Categories, shows everything.
  3. Press Enter in the Search box to jump into the list itself.
  4. Shift+Tab back to the Show box (named Show Hotkey Mode) to show All hotkeys, only Output hotkeys, or only Input hotkeys.
  5. Read the list with the arrow keys. It is a read-only text box, so you can also use your screen reader's normal reading commands.
  6. Press Ctrl+F at any time to return to the Search box, and press OK or Escape to close the window.

If nothing matches, the list says so, for example No hotkeys match "fuel" in input hotkeys., which tells you to try the other mode.

The same lists are in the HotkeyGuides folder inside BA's program folder, as text files you can open in any editor, and the full set for every aircraft is reproduced at the end of this guide in the Hotkey Reference.

The Menus

BA's menu bar has four menus. Press Alt to reach it, then use the arrow keys.

The File menu
The Aircraft menu

Lists the ten supported aircraft, with the current one checked. See Choosing Your Aircraft.

The Extras menu

Holds tools that work alongside the simulator. It currently has one item, Volanta…, which opens a text view of Volanta's live map: Volanta users and network pilots around you, your friends, and online ATC. You can also open it with Output Shift+O. It is described in Volanta.

The Help menu

The Settings Window

Open the Settings window from the File menu, Settings…. It holds nearly every option in BA, organised into tabs. Each tab is explained in full in the chapter for its feature; this section gives you the map.

How to use it
The tabs
Tab What it covers
Announcements Whether BA speaks through your screen reader or through Windows speech, and general announcement options: the nearest-city auto-announce, seconds in time readouts, GSX tooltips, 1,000-foot crossings.
Weather ActiveSky integration, the automatic weather, turbulence, icing and SIGMET/AIRMET announcements, and outside-temperature units.
VATSIM Announcing VATSIM activity from vPilot.
GeoNames Downloading the offline location data used by Output C and Location Info, and the distance ranges and units it uses.
SimBrief Your SimBrief username, for loading flight plans.
AI Your AI provider (Gemini or Claude), its key and model, for reading cockpit displays and describing scenery and routes.
Audio Which sound device BA's guidance tones play through.
Hand Fly Hand-flying feedback, visual guidance tones, Takeoff Assist and the rollout centreline tone.
Taxi Guidance The taxi steering tone, taxi callouts, distance units, docking guidance, online taxiway names, airport buildings, and SayIntentions taxi import.
First Officer The First Officer's automation (gear, flaps, autopilot, landing lights, altimeters, seat belt signs, center fuel pumps), the PMDG 737 GPWS test type, and whether flows speak each step.
Updates Release or preview builds, automatic update checks, the startup data check, and the version you are running.

The Announcements tab, including the screen reader or Windows speech choice, is described in Announcement Settings.

Updates

What it is

BA can find, download and install new versions for you from GitHub, without you visiting the website.

How it works

When Check for updates automatically when the app starts is on (it is on by default), BA checks once, just after its main window appears. The check never delays startup and is completely silent when there is nothing new, or when it cannot reach the internet. If an update is available, BA says, for example, "Update available: version 8.1.0", and opens the update window. It does this on every launch while an update is waiting; turn the check box off if you would rather check by yourself.

To check at any time, choose Update Application from the File menu. BA says "Checking for updates...". If you are up to date, it tells you, for example "You are running the latest version (8.0.0)." If the check fails, it tells you why.

The Update Available window

The window, titled Update Available, shows:

Press Update Now to download the update. The status line shows the download's progress, then "Download complete. Ready to install." BA says "Launching updater. Application will close and restart.", closes, installs the update into the same folder, and starts again. Your settings and databases are not touched.

Release builds and preview builds

On the Updates tab of the Settings window, under Which builds should MSFS Blind Assist offer?, you can choose:

To go back from a preview to the release, set the channel back to Release builds, then choose Update Application from the File menu. BA offers the current release even though its version number is lower than your preview. The window is then titled Return to Release Build, says so plainly, and its button reads Install Release.

Note: A newer build can store settings an older build does not know about. If you go back to an older build, those particular options are reset to their defaults; everything else is kept.

The Updates tab also shows Version you are running, the exact version and build. Include it whenever you report a problem.

Logs and Getting Help

Logs

BA writes diagnostic logs as it runs. They do not affect how it flies, but they are what lets the developers understand a problem you report. All logs are in one folder:

%APPDATA%\MSFSBlindAssist\logs

To open it, press Windows+R, type %APPDATA%\MSFSBlindAssist\logs and press Enter. The main log is debug.log. Others cover particular features, for example startup.log (replaced on every launch), taxi_guidance.log, taxi_router.log, landing_exit.log, takeoff_assist.log, ground_traffic.log, gsx.log and sayintentions.log. Logs are kept to a sensible size automatically, with older entries rotated away.

Reporting a problem

When something does not work as this guide describes:

  1. Note what you did, what you expected, and what happened instead — including what BA said.
  2. Note your BA version and build. It is on the Updates tab of the Settings window and in Help, About, for example v8.0.1-pre.7 (build 4f7e7ba). The build part names the exact code you were running.
  3. Note the aircraft and the simulator (2020 or 2024), and the airport if it is a ground problem.
  4. Collect the logs folder. The easiest way is to zip the whole %APPDATA%\MSFSBlindAssist folder, which contains your settings and logs together. If that is too large because of the databases, zip just the logs folder.
  5. Share it with the BA community on the project's Discord server, or on the project's GitHub page.

Before reporting, it is worth checking Troubleshooting and FAQ in the appendices, and the "If something goes wrong" part of the feature's own section.

Getting help

The BA community meets on Discord, where you can ask questions, get help setting up, and talk with other blind pilots. The invitation link is in the README on the project's GitHub page. The Glossary explains aviation and BA terms you may meet in this guide.

Your First Ten Minutes

If you want to try BA straight away, follow these steps. Each links to the section with more detail.

  1. Install the .NET 10 Desktop Runtime and, if your aircraft needs it, the MobiFlight WASM module. See What You Need.
  2. Extract BA and run MSFSBlindAssist.exe. See Installing.
  3. If the Set up MSFS Blind Assist window opens, start the location data download, then build the navigation database for your simulator. Remember: close MSFS 2020 before building its database; have MSFS 2024 running at its main menu before building its database. See The Navigation Database.
  4. Start the simulator and load a flight, parked at a gate, in an aircraft BA supports.
  5. In BA, open the Aircraft menu and choose that aircraft. You hear "Switched to" and its name.
  6. Wait for "Connected to" and "Profile and panels active".
  7. Press ], hear "output", then press A. BA reads your altitude. Try Output H for heading and Output S for airspeed.
  8. Switch to BA's window (Alt+Tab), press Ctrl+1, and arrow through the Sections list. Tab into the Panels list and then into a panel's controls to explore. Press Ctrl+3 to jump to a panel's Status Display.
  9. Open File, Hotkey List, and search for something you want to do.
  10. Press Output Shift+C to open the First Officer, if your aircraft has one. Press Ctrl+Tab to move between its Flows and Checklists tabs, and Escape to close it. See The First Officer and Checklists.

When you are comfortable with those, read Core Concepts to learn what BA announces and what its tones mean, then follow the guide through Planning Your Flight and on to the ground.

Part 2: Core Concepts

Core Concepts

This part explains the ideas that run through the whole of MSFS Blind Assist (BA). If you read only one section, make it The Audio Language: What the Tones Mean: every guidance tone in BA follows the same small set of sound rules.

A Flight with BA, Start to Finish

This walk-through follows one imaginary flight and shows which BA features you might use at each step; each one has its own chapter, linked from the text. The hotkeys named are the ones most aircraft use; check your aircraft's list in the Hotkey Reference. If you are new to airliners, General Flying Concepts explains the flying behind it.

At the gate

You start the simulator with the aircraft parked at a stand. BA announces "Connected to" and the aircraft's title, then that the aircraft's profile and panels are active. If you prefer to start somewhere else, you can teleport to a runway or gate.

You plan first. If you use SimBrief, Output Shift+B opens the SimBrief briefing, and the SimBrief section explains how to load your plan and hear an AI route briefing. The Flight Planning Window (Output Shift+E) lets you look at your route, SID, STAR and approach, and look up runways and frequencies. You check the weather with the METAR report (Output Shift+M) and the Weather Radar (Output Shift+R).

Then you set up the aircraft: its panels in the main window, its flight computer (Input Shift+M opens the MCDU, CDU or FMC on every aircraft), and its own tablet through Aircraft EFBs (Input Shift+T on most aircraft) for fuel, payload and takeoff performance. The First Officer (Output Shift+C on most aircraft) runs the flows with you and keeps you from missing a step on the checklists. If you use GSX for ground services, the accessible GSX window is covered in Gates, GSX and Docking.

Pushback and taxi out

After pushback, you want to know where you are. Output Alt+Y (Where Am I) tells you the taxiway, stand or runway you are on, and Output Alt+L describes what is around you.

ATC gives you a taxi clearance, something like "Taxi to holding point runway 27L via A, B, hold short of runway 27R." You open the Taxi Planner with Input Shift+Y and enter exactly that, as explained in Entering an ATC Clearance. BA builds a route and starts Taxi Guidance: a steering tone that pans towards the way you need to turn, plus spoken turns and stops. At each hold short line it stops you, and you press Input Y to continue only once ATC has cleared you. Ground Traffic callouts warn you about other aircraft near your route.

Takeoff

At the runway, taxi guidance lines you up on the centreline and tells you "Lined up". Takeoff Assist switches itself on at lineup (or you start it with Output Ctrl+T). Its tone keeps you on the centreline through the takeoff roll. On aircraft that support it, BA calls "V1", "Rotate" and "V2" from the speeds you entered in the flight computer.

Climb and cruise

After liftoff you climb on the autopilot or hand fly with Hand Fly Mode (Output Ctrl+H), which gives you a tone for pitch and bank. You set speeds, headings and altitudes through the Autopilot Windows (Input Ctrl+S, Ctrl+H, Ctrl+A, Ctrl+V on every aircraft). BA announces each thousand feet you cross if that setting is on, and on many aircraft it reads the flight mode annunciator to you as modes change.

In the cruise you build a listening scan, keep an ear on TCAS Traffic, check the weather ahead, and use Location Info and Nearest City to hear what you are flying over.

Descent and approach

Output Shift+D on most aircraft tells you the distance and time to top of descent. Before you start down, you choose your landing runway with Input Shift+D (Choosing a Destination Runway), which lets Output Ctrl+D read your distance to that runway and Output Ctrl+I give you an ILS report. If you want a manual landing, you can tick the manual landing assist there to get flare and rollout tones. You can also pick your runway exit in advance with the Landing Exit Planner (Input Shift+X).

If you plan to fly the final approach by hand, Visual Guidance (Output Ctrl+V) gives you two tones to match: one for where the aircraft should be pointing, one for where it is pointing.

Landing and taxi in

After touchdown, because you set a destination runway, the rollout tone keeps you on the centreline, and if you planned an exit, taxi guidance tells you when to turn off. Once you are clear of the runway, BA can route you on to your stand, and Docking Guidance brings you to the exact stop mark with a beep that speeds up as you get closer. Output Ctrl+Shift+R tells you how firm your landing was.

How BA Talks to You

BA speaks through your screen reader. When you are working in BA's own windows, two different things are talking to you, and it helps to know which is which.

Your screen reader reads everything you touch: the name of a button as you Tab to it, the new value of a combo box as you arrow through it, the text of a list item. That is ordinary Windows behaviour and BA does not interfere with it.

BA adds its own announcements on top, but only for things your screen reader cannot know about. BA deliberately does not repeat what you have just done. When you choose "On" in a combo box, your screen reader has already said "On", so BA stays quiet rather than saying it a second time. BA speaks in only three situations:

Note: One aircraft is a deliberate exception. On the TFDi MD-11, pressing a cockpit button is confirmed once with the control's resulting state, because the aircraft itself gives no other way to know whether the press did anything. The Boeing and MD-11 chapter explains this.

Some announcements are urgent and interrupt whatever is being spoken (a "Stop" from ground traffic, a hold-short instruction, a flare-assist go-around). Most are queued politely behind the current sentence, so a routine readout never cuts off something important.

BA also reports what the simulator itself is doing. See Pause, Slew and Sim Rate below.

Announcement Settings

The general speech options live on the Announcements tab of the Settings window (File menu, then Settings; see The Settings Window).

How announcements are delivered

The first group asks you to "Choose how announcements are delivered":

Below the two choices is a status line that tells you whether BA found a screen reader, for example "Screen reader detected: NVDA". If it says no screen reader was detected, BA recommends SAPI mode so that you still hear speech.

Other announcement options

Pause, Slew and Sim Rate

BA tells you when the simulator changes state, because a blind pilot has no other way to notice that the world has stopped moving or sped up. You will hear:

When two things happen at once they are joined in one sentence. Opening the Escape menu while active pause is on ends active pause, so you hear "Sim paused. Active pause off".

Nothing is spoken while a flight is loading, and BA does not announce the state the simulator is already in when BA first connects. You only hear about changes.

The Monitor Manager

What it is

As you fly, BA watches hundreds of cockpit values and announces them when they change: lights, switches, flight modes, warnings, autopilot states and more. Most pilots want most of these, but nobody wants all of them all the time. The Monitor Manager is a checklist of every automatic announcement for the aircraft you are flying, where you can silence any one of them.

Every aircraft has its own Monitor Manager, because every aircraft announces different things. Its title names the aircraft, for example "A320 Monitor Manager", "A380 Monitor Manager", "Fenix Monitor Manager", "PMDG Announcement Monitor", "787 Monitor Manager", "iFly 737 Monitor Manager", "757 Monitor Manager" or "MD-11 Monitor Manager". The Headwind A330 uses the A320 one.

When to use it

Muting only affects automatic announcements. The on-demand readout hotkeys always work, and the value still appears in BA's panels and Status Display.

How to use it
  1. Press Output Ctrl+M. The Monitor Manager opens with the cursor in the Search box.
  2. Type a few letters of the announcement you want, for example "flap" or "seat belt". The list below narrows to the matching rows as you type.
  3. Press Tab to move to the Show combo box, and Tab again to reach the list. As you enter the list, your screen reader tells you what it holds and how many rows, for example "All variables, 12 of 300".
  4. Arrow up and down through the rows. Each row is a checkbox. Checked means BA announces it; unchecked means it is muted.
  5. Press Space to untick a row and mute it, or tick it again to bring the announcement back.
  6. Press Escape to close the window.

Your choices are saved the moment you tick or untick a row, and they are remembered separately for each aircraft. Inside the window you can also press Alt+S to jump to the Search box and Alt+H to jump to the Show combo box.

The Show combo box has three choices:

Each time you open the Monitor Manager it starts fresh, with an empty search and Show set to All, so you never mistake a filtered list for missing rows. It does remember the row you were last on.

Tip: On the aircraft where BA calls the take-off speeds (the FlyByWire Airbuses, the Fenix A320, the iFly 737 MAX8 and the MD-11), V1, Rotate and V2 each have their own row (V1, VR, V2; on the Fenix, "MCDU V1 Speed", "MCDU VR Speed" and "MCDU V2 Speed"), so you can keep some and mute others. The FlyByWire aircraft also have a separate quick toggle for their ECAM call-outs, Output Ctrl+E. See your aircraft's chapter.

If something goes wrong

Readout Hotkeys

What they are

Readout hotkeys let you ask for any instrument reading at any moment, the way a sighted pilot glances at a gauge. They are all in Output mode: press ], then the key. Each speaks one short answer and returns you to normal.

The common set below works on most aircraft. Each aircraft adds its own keys, and a few aircraft leave some out, so always check the hotkey list for the aircraft you are flying: File menu, then Hotkey List, or the Hotkey Reference at the end of this guide.

Altitude, speed and heading
Key What it reads
Output A Altitude above sea level (MSL)
Output Q Altitude above the ground (AGL)
Output V Vertical speed
Output S Indicated airspeed
Output T True airspeed
Output G Ground speed
Output M Mach number
Output H Magnetic heading
Output U True heading
Aircraft state
Key What it reads
Output F Fuel on board in pounds (on the PMDG Boeings, the 787, the BlueBird 757 and the MD-11, tank by tank)
Output Shift+F Fuel in kilograms
Output W Gross weight in pounds (on the FlyByWire aircraft, with centre of gravity)
Output Shift+W Gross weight in kilograms
Output L Flap position
Output Shift+G Landing gear position
Output B Altimeter setting, in hectopascals and inches, or "Standard"
Output X Transponder squawk code
Weather and time
Key What it reads
Output I Wind
Output O Outside air temperature in Celsius
Output Z Local time at the aircraft's position, with the time zone name
Output Shift+Z Zulu (UTC) time

The local time is worked out from where the aircraft is on the globe, including daylight saving, so you hear something like "16:38 Eastern Daylight Time" near New York. Zulu time is spoken like "03:30Z". Tick Include seconds in time announcements on the Announcements tab to hear "20:30:45 British Summer Time" and "00:15:30Z" instead.

Key What it reads
Output D Distance to destination, from the aircraft's FMS (not on the MD-11; on the Fenix, worked out from its flight plan)
Output Shift+D Distance and time to top of descent, once the FMS has worked it out in flight (not on the MD-11; on the Fenix, worked out from its flight plan)
Output N NAV 1 and NAV 2: frequency, station ident, localiser, glideslope and DME
Output Ctrl+W The active waypoint on the navigation display: name, distance and bearing (FlyByWire aircraft and the Fenix)
Output C Nearest city or town, or the water you are over (see Location Info and Nearest City)

Top of descent is spoken like "145 miles to top of descent: 00:16:58". Once you have passed it you hear "Past top of descent", and before the FMS has worked it out, "Top of descent not yet computed". On the FlyByWire Airbuses, when the FMS has not worked out top of descent yet but does know your top of climb, Shift+D gives the distance to top of climb instead, for example "85 miles to top of climb". On the PMDG 777, D and Shift+D can read the FMC's PROG page instead; see FMC Settings.

Characteristic speeds and approach capability

The Shift+number keys read the speeds your aircraft cares about. What they mean depends on the aircraft:

Output Ctrl+0 reads the approach capability (the CAT rating for an autoland) on the FlyByWire A320neo, Headwind A330-900neo and FlyByWire A380X; see Approach capability.

Landing and trim

Note: Values that have no real unit are read as a bare number, for example "V1: 0" when a speed has not been entered yet.

Hand Fly and Visual Guidance keys

When Hand Fly or Visual Guidance is active, a set of single-letter keys works without pressing ] first: A, S, D, H, P, B, Q and V (and F for the target vertical speed in Visual Guidance). They are described in Hand Fly Mode and Visual Guidance.

The Audio Language: What the Tones Mean

Why tones

Speech is slow. By the time BA has said "two degrees left of centreline" the aircraft has moved on. A tone is instant and continuous: you hear the correction you need the whole time, without a single word, while your hands are busy with the rudder, the throttle or the stick. That is why BA's guidance features use sound.

All of BA's tones follow one shared set of rules. Learn them once and you can use every guidance feature.

The rules
  1. Left and right (stereo pan) tells you which way to steer. By default the tone plays on the side you should steer toward. Tone in your right ear: steer right. Tone in your left ear: steer left. The further off you are, the further the tone moves to that side.
  2. Silence means "on profile". When you are doing exactly what is needed, most steering tones go quiet. Silence is good news, not a fault. BA never just goes silent to mean "I have given up": when guidance genuinely stops, it says so in words (for example "Go around detected. Flare assist rearmed." or "Rollout guidance complete").
  3. Pitch (high and low) means up and down, where a tone uses it. A higher note means more nose-up, or "come up". A lower note means nose-down, or "go down". Steering tones that only guide left and right (taxi, takeoff, rollout) keep a fixed note.
  4. Pulsing means "you need to act". A tone that turns on and off rhythmically is asking you to do something you are not doing yet. On runway lineup, the steering tone pulses about three times a second when you are stopped but not yet lined up. Docking uses a beep that speeds up as you close on the stop.
  5. A solid tone means "here". At a gate, the docking beep becomes a steady tone at the exact stop point: brake now.

Two features use the tone as an attitude indicator rather than a steering cue, so rule 1 works the other way round for them:

Each tone-using feature

The Tone Cheat Sheet in the appendices lists every tone on one page: what its pan, pitch, silence and pulsing mean. Each feature's own section has the details: Taxi Guidance, Takeoff Assist, Hand Fly Mode, Visual Guidance, Flare and Rollout Tones and Docking Guidance.

BA keeps different features' tones from playing over each other. When docking guidance takes over at the gate, the taxi steering tone goes quiet; when Visual Guidance is on, the Hand Fly tone is muted; on the landing rollout, the centreline tone and the exit guidance tone take turns.

Settings that change the tones

Each feature has its own tone settings, on the Taxi Guidance tab (taxi steering and docking) or the Hand Fly tab (hand fly, visual guidance, takeoff assist, and the flare and rollout tones, which share the takeoff assist sound). The same kinds of setting appear in each place:

Choosing where the tones play

You can send BA's guidance tones to a different audio device from the simulator. Many pilots keep the simulator on their speakers and put the guidance tones in a headset.

  1. Open the Settings window and go to the Audio tab.
  2. In Guidance tone output device, choose a device. Windows default device follows whatever Windows is using.
  3. Press Test Tone to hear a short tone sweep left and right on the selected device. This lets you compare devices before you commit to one.
  4. Read the Status box below for confirmation, for example "Using Headset Earphone.". If the device you chose could not be opened, the status box says so and names the device the test actually played on.
  5. Press OK to save.

This one setting covers every guidance tone: taxi, takeoff assist, hand fly, visual and landing guidance, and the docking beeps. It does not change where your screen reader speaks; NVDA and JAWS choose their own output device.

The tones follow your hardware by themselves. If you unplug the chosen device, the tones move to the Windows default device and you hear "Guidance tone device Headset is not available. Using the Windows default device." (naming your device). Plug it back in and they return, with "Guidance tone device Headset is back. Moving the guidance tones to it." If no audio device at all is available you hear "No audio device available for guidance tones." A device you saved but is not plugged in is still shown in the list, marked "(not connected)", so your choice is never lost.

If something goes wrong

AI Display Reading and Scene Description

What it is

Some cockpit screens have no text behind them that BA can read directly: the picture is drawn by the aircraft and nothing else. For those, BA can take a picture of the simulator and ask an AI service to read it for you. The same idea lets BA describe the view out of the window.

You choose between two AI services: Google Gemini or Anthropic Claude. You use your own account and your own key with either, and the service bills you directly, not BA.

What it can read

The AI is also used for the route briefing in the flight planning window; see The Flight Planning Window.

You do not need to look at the display first

On the Fenix A320, the PMDG 737 and 777, the iFly 737 MAX, the BlueBird 757 and the TFDi MD-11, BA moves the simulator's camera to the cockpit view that shows the display, takes the picture, and puts your own view straight back, including a saved custom view such as a cabin or wing view. The camera is away for well under a second, and your view is back before the AI is even asked. On the HorizonSim 787 the camera is not moved for you, so switch to a cockpit view that shows the display first.

You may hear:

BA takes its picture of the simulator window itself, so a BA window sitting on top of the simulator does not end up in the picture.

How to use it
  1. Set up an AI provider once (see Settings below).
  2. Press Output and the display key, for example ] then Alt+P. You hear "Capturing PFD..." (the display's name).
  3. Wait a few seconds while the AI reads the picture. You then hear "PFD analysis ready." and a result window opens with the cursor at the start of the text. For a scene, you hear "Capturing scene..." and then "Scene description ready".
  4. Read the result with the arrow keys like any text.
  5. Press Escape, or the Close (ESC) button, to close the window and return to the simulator.

Only one read runs at a time. If you press another while one is still working you hear "A display read is already in progress."

Warning: An AI reading is a description of a picture, not a reading from the aircraft's systems. It can occasionally misread a small or partly hidden number. Use it to understand the display, and confirm anything critical with a direct readout hotkey where one exists.

Settings

The AI tab of the Settings window:

Note: Costs depend on your provider and model and are charged to your own account. Display reads and scene descriptions are single pictures and cost little each; web searches during route briefings cost extra. Check your provider's pricing page for current figures.

If something goes wrong

Location Info and Nearest City

What it is

Two tools tell you where you are over the world, as opposed to where you are on an airport (for that, see Where Am I):

Both answer instantly and work offline, from location data you download once.

Getting the location data

The data comes from GeoNames (place names) and Natural Earth (seas, coastlines, lakes, regions and state outlines). You download it once; after that, nothing is looked up online when you press a key, and no account is needed.

  1. Open the Settings window and go to the GeoNames tab.
  2. Press Download location data. The download is about 440 megabytes; the finished data takes about 330 megabytes on disk. Make sure you have about 1.5 gigabytes free while it builds.
  3. BA speaks its progress: "Downloading location data, about 440 megabytes to download.", then 25, 50 and 75 percent, then "Download finished. Building location data; this takes about a minute.", and finally "Location data ready, 8.4 million places." (the number may differ slightly).

The download keeps running if you close the Settings window. If you press Cancel download, or lose your connection, the next press picks up where it stopped. The status box on the GeoNames tab always shows the latest state. If the location data is missing when BA starts, BA also offers to download it then (see Part 1).

Until the data is installed, Output C tells you "Location data not downloaded. Download it in Settings, GeoNames tab." While it is still downloading or building you hear "Location data is still downloading." or "Location data is still being built."

Output C: the nearest place

Press ] then C. Over land you hear the nearest town with its state or province and country, the distance and direction, and the sea coast if it is close, for example "Near Brighton, England, United Kingdom, 0.5 miles north, English Channel coast 1.2 miles south".

Over water BA tells you what you are over and how far land is, then the nearest town: "Over Chesapeake Bay, nearest land 5.2 miles west. Near Dares Beach, Maryland, United States, 5.4 miles west." Over a lake it gives the shore: "Over Lake Michigan, shore 24 miles east".

If no town is within range you hear "No town within 25 miles" followed by the region and country.

The automatic nearest-city announcement (Announcements tab) speaks this same sentence on a timer.

The Location Information window

Press ] then Shift+L. The window opens already filled in, with the cursor in its first box, Where you are. Over land it shows the state or province you are in (for example "In: Bavaria, Germany"), the mountain range or desert if you are over one, the named coast if it is within range, and the time zone. Over water it shows the sea or lake, the nearest land or shore, and the nearest region.

Press Tab to move through the other boxes, each a read-only text you can arrow through:

A box with nothing in range says so, for example "No major cities found." Press Escape to close the window and return to the simulator.

Settings

The rest of the GeoNames tab controls how far each search reaches and how much it lists:

The ranges are capped at 310 miles (500 kilometres), and the Coast Range at 1,000, so a press never searches half a continent.

Note: The coastline data is accurate to roughly a kilometre. It is right for "the coast is 5 miles west" in flight, but not for judging a few hundred metres on a coastal airport.

If something goes wrong

Part 3: The First Officer

The First Officer and Checklists

What it is

Output Shift+C opens the First Officer, a crew member who works the flows and checklists with you. Its window has two tabs:

The First Officer is on the PMDG 777 and 737, the iFly 737 MAX8, the Fenix A320, the FlyByWire A32NX and A380X, the Headwind A330-900neo, the BlueBird 757-200 and the TFDi MD-11. You can also open it from the File menu, where the First Officer item is named after your aircraft, for example "Fenix A320 First Officer". On any other aircraft the item is not there, and Output Shift+C says "No checklist for this aircraft." and opens nothing.

The First Officer never programs the MCDU, CDU or FMC: you still enter the flight plan and performance yourself. Items only the Captain can judge, such as the landing autobrake setting, are spoken as reminders and left to you.

Note: The A380X also has a live Electronic Checklist, read from the aircraft's own display and ticked by the aircraft's own sensing, on Output Ctrl+Shift+C. See Airbus Aircraft.

When to use it

Open it at the start of each flight, before you power up the aircraft. Once opened, it keeps working for the rest of the flight, even with its window closed: it switches the landing lights at 10,000 feet and sets the altimeters at the transition (see Settings). Run each flow at its point in the flight, then read the matching checklist. If you would rather set everything yourself, skip the flows and use the checklists to check your work.

If you first open it in flight, it marks the checklists up to After Takeoff complete and says "In flight: checklists through After Takeoff marked complete."

How to use it

  1. Press Output Shift+C. The first time, the window opens on its tab strip; after that it returns to the control you left.
  2. Press Ctrl+Tab to switch between the Checklists and Flows tabs, or use the arrow keys on the tab strip.
  3. Press Escape to close the window. You go back to where you were, usually the simulator. Your ticks are kept, and a running flow carries on.

The window opens before BA has connected to the simulator; its checklists come to life once it connects. Loading a new flight in the simulator stops a running flow and unticks every checklist.

The Flows tab

The Flows tab has:

To run a flow, select it in Available flows and press Enter, or Tab to Start Flow and press it. The First Officer works through the steps about two seconds apart. Pause / Resume holds the flow and continues it; Stop Flow ends it after the current step. Only one flow runs at a time.

Before it switches anything that could stop an engine, a flow checks that it is safe. The power-up flows that check the engine controls (Electrical Power Up on the Fenix A320, A32NX, Headwind A330 and 777, Cockpit Preparation on the A380X and 777, and Power Up on the MD-11 and the BlueBird 757) and the 737 and 757 Preflights stop if an engine is running or the aircraft is in the air, and the shutdown, parking and securing flows stop unless the aircraft is on the ground. The securing flows also stop if an engine is still turning. A shutdown or parking flow cuts the engines first, then waits up to two minutes for them to spin down ("Waiting for: Engines stopped" when flow progress is spoken) before it switches the fuel pumps off. Either way you hear why.

On the Fenix A320 the First Officer goes by the Fenix's own engine readings. Engine Start moves on to the second engine once the Fenix says the first start is complete, and allows up to 3 minutes for each engine. Shutdown's "Engines stopped" waits for the Fenix's engines to spin down, usually about 20 seconds, before the fuel pumps go off. On the Fenix A321, the Preflight flow leaves out the pack flow selector, which the A321 does not have; set its Econ Flow button as you need it.

The BlueBird 757

The BlueBird 757's First Officer has twelve flows: Power Up, Preflight, Before Start, Engine Start, After Start, Before Takeoff, After Takeoff, Descent, Before Landing, After Landing, Shutdown and Final Securing. The Checklists tab has a list of each flow's own actions and, between them, the cards of BlueBird's Normal Checklist: the Before Start, After Start, Before Takeoff, After Takeoff, Descent and Approach, Before Landing, After Landing and Shutdown Checklists. The arrival is two flows, Descent and Before Landing, and BlueBird's In Range and Approach cards are one Descent and Approach Checklist. The Captain's items, spoken as reminders, are the FMS, the altimeters, the landing altitude on the Pressurization panel, the MCP values, the flaps, the trims, the gear lever's OFF position after takeoff, the landing autobrake and the missed approach altitude.

With the window opened once, the First Officer also works by itself in flight, as the Settings allow. With Auto-engage autopilot on climbout on, it presses LNAV and VNAV at 400 feet if their lights are not on: "400 feet. LNAV and VNAV on." With Auto-manage center fuel pumps on, the center pumps go on during ground setup when the center tank has fuel, and off when it runs dry: "Center tank low. Center fuel pumps off." At the transition altitude it sets all three altimeters to standard ("Transition altitude. Altimeters standard."); at the transition level it only reminds you. The 757's First Officer does not set the flaps or the pressurization panel from SimBrief.

The Checklists tab

The checklists are a tree. Each checklist is named with its progress, for example "Before Start — Not started", "Before Start — 3 of 7 complete" or "Before Start — Complete". Press Right Arrow to open one and Up and Down Arrow to read its lines; opening one closes the others.

On the Fenix A320, these lines take their live value from the Fenix itself:

The buttons below the tree:

Loading SimBrief

Load SimBrief fetches your latest SimBrief plan, so set your SimBrief username first. The First Officer uses the plan's transition altitude and level for the altimeters, its takeoff flaps in the flows, and on the PMDG 737 and iFly 737 MAX8 its cruise altitude and destination elevation for the pressurization panel. You hear one announcement, for example "SimBrief flight plan loaded. Transition altitude 5000 feet, transition level 6000 feet. Takeoff flaps 5. Pressurization plan: flight altitude 36000 feet, landing altitude 400 feet."

With your username set, the plan loads by itself whenever you open the window with no plan loaded. A plan belongs to one flight: it is forgotten after you land or load a new flight. If SimBrief still has the flight you have just flown, you hear "SimBrief still has the flight just flown. Generate the next flight plan, then press Load SimBrief." Without a plan, a step that needs one, such as setting the takeoff flaps, becomes a Captain reminder.

What you will hear

While a flow runs:

These lines wait their turn and do not cut off your screen reader. To hear fewer of them, untick Speak flow progress in Settings.

With the window closed, the First Officer still speaks what it does, for example "Above ten thousand. Landing lights off.", "Transition altitude. Altimeters set to standard." and, at the transition level, "Transition level. Set local altimeter pressure now." The exact words vary a little by aircraft.

Settings

The First Officer tab of Settings (File menu, Settings) has these options:

Setting What it does Default
Auto-raise gear on positive rate (climb) Raises the gear after a takeoff BA watched from the ground: "Positive rate. Gear up." Off
Auto-lower gear at 2000 ft AGL (descent) Lowers the gear on a real descent below 2,000 feet above the ground, at 250 knots or less: "Gear down." Off
Auto-manage flaps (FBW A380, A32NX, Headwind A330) Extends and retracts the flaps by the speed tape, on those three aircraft only. Off
Auto-engage autopilot on climbout Engages the autopilot climbing through the height below, after a takeoff BA watched, for example "350 feet. Autopilot engaged." On the BlueBird 757 it also has the First Officer press LNAV and VNAV at 400 feet (see The BlueBird 757). Off
Autopilot engagement altitude (feet AGL) The height for the setting above, 100 to 3,000 feet. An aircraft with a higher minimum uses its own, such as 400 feet on the PMDG 737. 350
Automatically switch landing lights at 10,000 feet Landing lights off climbing through 10,000 feet and on descending through it. On
Automatically set altimeters at transition altitude and level Standard climbing through the SimBrief transition altitude, local pressure descending through the transition level. When off, the First Officer only reminds you. On the BlueBird 757 the transition level is always a reminder. On
Auto seat belt signs Disabled; At 10,000 feet; or Top of climb and top of descent. Disabled
GPWS test type (PMDG 737) Which GPWS self-test the 737's Preflight flow and checklist run: Short test or Long test. Short test
Auto-manage center fuel pumps (PMDG 737/777, iFly MAX8 and BlueBird 757) Center tank pumps on during ground setup when the center tank has fuel, and off when it runs dry. Off
Speak flow progress Speaks each step as a flow runs. When off, a flow speaks only "flow started", Captain actions, skipped or failed steps and "flow complete". On

The gear and autopilot options work on every aircraft, including the HorizonSim 787, whether or not the First Officer window has been opened. The landing lights, altimeters, seat belts, flaps and center pumps work once you have opened the First Officer window, and keep working with it closed until you change aircraft.

If something goes wrong

Part 4: Planning and Preflight

Planning Your Flight

A typical routine before you push back: build or load a plan in SimBrief, open the Flight Planning window to check the route and procedures, ask for the AI briefing if you have an AI key, then work through the aircraft's EFB and, with the First Officer, its flows and checklists. Most of these tools read the navigation database.

Tip: The Flight Planning window and the SimBrief briefing work before BA has connected to the simulator, and the First Officer window opens then too, so you can plan while the sim is still loading.

Teleporting to a Runway or Gate

What it is

Teleporting moves your aircraft instantly to a chosen runway or parking spot at any airport in your navigation database. It is handy for practising take-offs, getting to the right stand after loading at the wrong one, or skipping a long taxi while you learn.

Warning: Teleporting moves the aircraft; it does not reset it. Teleport only with the aircraft stopped on the ground, and expect the aircraft's systems to stay exactly as they were. Online networks such as VATSIM do not allow teleporting while you are connected.

Runway teleport (Input Shift+R)
  1. Press Input Shift+R. The Runway Teleport window opens with the focus in Airport ICAO Code.
  2. Type the four-letter code. The Runway List fills, and the status line says, for example, "Found 4 runways for London Heathrow".
  3. Press Enter to jump to the list, and arrow to the runway you want.
  4. Press Enter (or the Teleport button). A Confirm Teleport box asks "You're about to reposition your aircraft to Runway 27R at London Heathrow. Are you sure?". The focus starts on No, so you cannot teleport by accident; choose Yes to go.

BA places you at the start of the runway, lined up with it and on the ground. It also tells Takeoff Assist which runway you are on, so Ctrl+T guides you on that runway straight away; see Takeoff Assist.

Gate teleport (Input Shift+G)
  1. Press Input Shift+G. The Gate & Parking Teleport window opens with the focus in Airport ICAO Code.
  2. Type the four-letter code. The Gate and Parking List fills with every stand and parking spot, and the status line says, for example, "Found 120 gates and 45 parking spots for London Heathrow".
  3. To narrow the list down:
    • Type part of a stand name in Search, then press Enter to jump to the matches. If nothing matches, BA says "No matching gates.". Search also finds the real-world names of stands that online data adds, so you can search for the gate number on your ticket even when the scenery calls it something else.
    • Choose a type in Filter by parking type: All, Gate Small, Gate Medium, Gate Large, Gate Heavy, Gate Extra, Ramp GA, Ramp Cargo, Ramp Military, Dock or Other (only the types the airport has are listed).
    • Leave Show only fitting stands ticked to hide stands too small for your aircraft. It is ticked automatically when BA knows your aircraft's wingspan.
  4. Arrow to the stand and press Enter (or Teleport). Confirm with Yes in the Confirm Teleport box.

For how stand names, sizes and GSX gates work, see Gates, GSX and Docking.

If something goes wrong

SimBrief

What it is

SimBrief is a free online flight planner used by most simulator pilots. It works out a route, fuel, weights, take-off and landing performance and weather for your flight, and publishes the result as an operational flight plan (OFP). BA connects to your SimBrief account so you can load that plan into the Flight Planning window, read every page of the OFP in an accessible window, and even start a new SimBrief plan with the fields filled in for you.

Setting your SimBrief username

BA needs only your SimBrief username, not your password.

  1. Open File, then Settings, and move to the SimBrief tab.
  2. In the SimBrief Username field, type the username you use to log in to www.simbrief.com.
  3. Press OK to save.

From now on, the first time you open the Flight Planning window in a session, BA fetches your latest SimBrief plan automatically.

Opening your briefing in the browser (Output Shift+B)

Press Output Shift+B. BA says "Opening your SimBrief briefing" and opens your latest SimBrief briefing page in your web browser. This is SimBrief's own website, so you need to be logged in to SimBrief in that browser. Use this when you want the full original OFP exactly as SimBrief presents it; for an accessible, tabbed view of the same plan, use the SimBrief Flight Planner window below.

The SimBrief Flight Planner window

The SimBrief Flight Planner window has two tabs, Create and View. You open it from the Flight Planning window:

  1. Press Output Shift+E to open the Flight Planning window.
  2. Press Ctrl+Tab until you reach the SimBrief tab (it is the last tab).
  3. Press Create SimBrief Plan to open the planner on its Create tab, or View Detailed Plan Info to open it on its View tab.

Every time you open the planner, BA fetches your latest plan again, so what you read is never stale.

Creating a new plan (Create tab)

The Create tab lets you fill in the basics in an accessible form and then hands them to the SimBrief website, which does the actual planning. The fields are:

Field What to enter
Origin ICAO The four-letter code of your departure airport, for example EGLL. Required.
Destination ICAO The four-letter code of your destination, for example KJFK. Required.
Aircraft Type An ICAO type code such as B77W or A20N. You can type it, or choose from the list, which loads from SimBrief.
Alternate ICAO Your alternate airport, optional.
Cruise Level (ft) For example 36000 or FL360, optional.
Airline ICAO Code Three letters, for example BAW, optional.
Flight Number The number without the airline prefix, for example 178, optional.
Cost Index 0 to 999; it starts at 30.
Route (optional) A route string such as MATCH DCT WOBUN. Leave it empty to let SimBrief choose.
Number of Passengers Optional.
Freight Weight Optional, in the units below.
Weight Units lbs or kgs.

When you are ready, press Plan on SimBrief Website. Your browser opens on SimBrief's dispatch page with your details already filled in, and the status line below the button says "Opened SimBrief in your browser. You may need to log in first." Finish the plan on the website and generate it. If you left Origin or Destination empty, the status line says "Origin and Destination are required." instead.

Once SimBrief has generated the plan, go back to the Flight Planning window and press Load SimBrief on its Route Viewer tab to load it into BA.

Reading your plan (View tab)

The View tab shows your latest OFP. At the top are a Fetch Latest Plan button and a status line, which reads, for example, "Plan loaded: EGLL → KJFK" once the plan has arrived. Below them is a set of tabs, one per part of the plan. Use Ctrl+Tab to move between them and Tab to move into each one.

Note: The SimBrief Flight Planner shows SimBrief's plan exactly as SimBrief made it. It does not change anything in your aircraft. You still enter the route and performance into the aircraft's own FMC, MCDU or EFB.

If something goes wrong

The Flight Planning Window

What it is

The Flight Planning window, titled Electronic Flight Bag, is BA's own route viewer, procedure planner and airport reference. It shows your flight plan as a table of waypoints with distances and bearings from your aircraft, lets you choose a departure runway, SID, STAR, approach and arrival runway from the navigation database, looks up detailed airport and runway information, and produces the AI route briefing.

It is a planning and reference tool. It does not program your aircraft's FMC or MCDU; you still enter the route and procedures there. What it gives you is a clear, readable picture of the plan, so that when you enter it into the aircraft, or hear ATC give you a SID, you know what it means.

Note: This window is not the same as your aircraft's own tablet (the flyPad, the PMDG tablet and so on). Those are covered in Aircraft EFBs.

When to use it
Opening and closing it

Press Output Shift+E. The window opens with the focus on the waypoint list. If you have a SimBrief username set and no plan loaded yet, BA loads your latest SimBrief plan straight away and says "SimBrief flight plan loaded".

Close the window with Alt+F4. Your flight plan is kept: the next time you press Output Shift+E it is still there, including any procedures you changed, and so is any route description you generated.

How the window is laid out

The window has eight tabs. Press Ctrl+Tab to move to the next tab and Ctrl+Shift+Tab to go back. In order they are:

  1. Route Viewer — your flight plan, with the Load SimBrief, Refresh Position and Describe Route buttons.
  2. SID — choose a standard instrument departure.
  3. STAR — choose a standard terminal arrival route.
  4. Approach — choose an approach procedure.
  5. Departure — set the departure airport and runway.
  6. Arrival — set the arrival airport and runway.
  7. Airport Lookup — detailed airport and runway information.
  8. SimBrief — open the SimBrief Flight Planner.

At the bottom of the window a status line (named Status) reports what just happened, such as "Flight plan: 42 waypoints"; read it with your screen reader's review commands.

Every procedure tab works the same way: you type a four-letter ICAO code, and as soon as the fourth letter is in, the lists below fill in by themselves. There is no Search button to press. The first item in each list is selected automatically, and choosing an item in one list fills the next list along.

The Route Viewer tab

This tab holds your flight plan.

The buttons along the top are:

Below the buttons is the Waypoint Navigation List. It is a table: each row is a waypoint, and each column is a piece of information about it. BA reads the cell you move to, saying the column name and the value, for example "Waypoint, DET" or "Dist (NM), 23.4". An empty cell is read as the column name followed by "blank".

Key What it does
Up Arrow / Down Arrow Previous or next waypoint, staying in the same column
Left Arrow / Right Arrow Previous or next column on the same waypoint
Home / End First or last column of this waypoint
Ctrl+Home / Ctrl+End First waypoint, or last waypoint
Page Up / Page Down Move a screenful of waypoints at a time
F5 Refresh distances and bearings from your current position
Applications key (or Shift+F10) Track this waypoint in one of the five tracking slots

The waypoints run in flight order: the departure airport and runway, the SID, the en-route part, the STAR, the approach, and the arrival airport. The first two columns, Waypoint and Region, are always there. Other columns appear only when at least one waypoint has something to show in them, so a simple plan has fewer columns than a detailed one. The possible columns are:

Some legs of a procedure are not flown to a named waypoint at all. The first leg of most SIDs, for example, is "climb on this heading until a certain altitude", and the missed approach often begins the same way. BA keeps these legs in the list and gives them a plain description instead of a waypoint name, such as "Climb heading 071° to 600 feet". They have no position, so their distance and bearing cells are blank.

To track a waypoint, arrow to it, press the Applications key (or Shift+F10) and choose Track Slot 1 to Track Slot 5. BA says, for example, "Waypoint DET tracked in slot 1". See Tracking Waypoints for what to do next.

Once you have generated a route briefing, a read-only Route Description box appears below the list. Tab to it and read it line by line with the arrow keys.

The SID tab

A SID (standard instrument departure) is the published route from the runway to the start of the en-route part of your flight.

  1. In SID Airport ICAO, type the departure airport's code.
  2. The SID Runways list fills with ALL first, then each runway that has SIDs. Choose your departure runway, or ALL to see every SID at the airport.
  3. The SID Procedures list fills with the SIDs for that runway. Choose one.
  4. The SID Transitions list fills with None first, then the SID's transitions. A transition joins the SID to a particular airway or waypoint; SimBrief and ATC will tell you which one, if any. Leave it on None if you do not need one.
  5. Press Load SID. BA says, for example, "Loaded CPT5J RWY 27R" and the SID replaces any SID already in your plan.

Choosing ALL loads the part of the SID that is common to every runway. Choosing a runway loads the version for that runway, including its runway-specific first legs, so pick your actual runway whenever you know it.

The STAR tab

A STAR (standard terminal arrival route) is the published route from the end of the en-route part down towards the approach.

The STAR tab works exactly like the SID tab: type the arrival airport in STAR Airport ICAO, choose a runway (or ALL) in STAR Runways, choose a STAR in STAR Procedures, choose a transition or None in STAR Transitions, then press Load STAR. BA says, for example, "Loaded ARTIP1A RWY 18R" and the STAR replaces any STAR already in your plan.

The Approach tab
  1. In Approach Airport ICAO, type the arrival airport's code.
  2. The Approaches list fills with every approach at that airport, named by type and runway, for example "ILS RWY 18R". Circling approaches, which serve the airport rather than one runway, are included too.
  3. The Transitions list fills with None first, then the approach's transitions. Choose one or leave None.
  4. Press Load Approach. BA says, for example, "Loaded approach ILS RWY 18R". The approach, including its missed approach legs, replaces any approach already in your plan.
The Departure tab

This tab sets the departure airport and runway at the very start of the plan.

  1. In Departure ICAO, type the airport's code.
  2. The Departure Runways list fills with every runway, each with its length, width, surface and, if it has one, its localizer: "ILS" (localizer and glideslope), "Localizer" (no glideslope), or "LDA" or "IGS" for an offset approach that does not line up with the runway, with its frequency and magnetic course. Lengths are shown in the ground distance unit you chose in Settings (Use feet for distances (default: metres) on the Taxi Guidance tab).
  3. Choose the runway and press Load Departure. BA says, for example, "Loaded departure EGLL runway 27R".

The departure runway you set here is also the runway the taxi-out part of the AI briefing plans to.

The Arrival tab

This tab sets the arrival airport and runway at the end of the plan. It works like the Departure tab: type the code in Arrival ICAO, choose a runway in Arrival Runways, and press Load Arrival. BA says, for example, "Loaded arrival EHAM runway 18R". The arrival runway you set here is the one the taxi-in part of the AI briefing plans from.

Note: Setting the arrival runway here does not set BA's destination runway for approach and landing guidance. That is done separately with Input Shift+D; see Choosing a Destination Runway.

The Airport Lookup tab

This tab is a reference page for any airport in your navigation database. You can find an airport by its ICAO code, or by part of its name or city.

  1. In Airport Lookup ICAO, type the airport's code. As soon as the fourth letter is in, the Airport Information box fills in, the Airport Lookup Runways list fills with the runways, and the first runway's details appear in the Runway Information box. Nothing is spoken: press Tab, and the first line of the Airport Information box gives the airport's code and name, for example "KATL, Hartsfield - Jackson Atlanta I". A code with no airport reads "Airport ROME not found in database."
  2. To search, type a code or part of an airport's name or city, and press Enter. Case, accents and apostrophes don't matter: "Zürich" finds "Zurich" and "ohare" finds "Chicago-O'Hare". With several words, each must appear somewhere in the code, name or city. Letters in the middle of a word count too, so "LAX" finds KLAX.
    • When what you typed is an airport's exact code, or only one airport matches, it loads at once and its code and name are spoken. KATL loads, even though other airports' names contain those letters. A code with no runway, usually a helipad's, loads at once only when nothing else matches: "MCO" on MSFS 2024 is a helipad named Orlando International Airport, so it opens the list, where you also find Orlando's KMCO.
    • Otherwise a list opens, best match first, and its title says how many airports match. Arrow to an airport and press Enter to load it, or press Escape to close the list; either way you are back in the field. The list shows at most 50 airports, and its title says when more matched: "50 of 70 airports match LONDON". An exact code also opens the list when another airport is named exactly what you typed, or a town is: "LIMA" lists Turin-Aeritalia, whose code it is, then the airports of Lima, Peru.
    • When nothing matches, you hear "No airports match" and what you typed.
  3. The tab order is the field, Airport Information, the runway list, then Runway Information. Arrow through the runway list: the Runway Information box updates for each runway as you move.
  4. Read either information box line by line with the arrow keys. Both boxes are read-only.

Towns. With the offline location data installed (see Getting the location data), a town's name finds the airports around it, so "Gothenburg" lists Landvetter and Säve, each "11 nm from Gothenburg, Västra Götaland, Sweden". Each town adds up to 10 airfields within 30 nm, open ones and the longest runways first. A helipad is never added for a town; you find it by its own name or code. A town with no airfield within 30 nm lists its 3 nearest within 100 nm. When several towns share a name, the most populous comes first: "London" lists London, England, then London, Ontario, and so on. Only towns of 500 people or more are searched, and only by their whole name.

On MSFS 2024, the navigation data has no city names, so a city is found only through an airport's own name ("Atlanta" finds Hartsfield - Jackson Atlanta) or through the location data. Without the location data installed, a search that finds nothing tells you: "Searching by city on MSFS 2024 needs the location data."

Distance from you. When connected to the simulator, each line of the list, the spoken airport and the Airport Information box say how far the airport is from you and in which direction, for example "212 nm southwest". With the simulator closed they leave it out.

The Airport Information box starts with the airport's code and name, then is grouped under headings: basic information (ident and name), from aircraft (the distance and direction, when connected), location (coordinates, elevation and magnetic variation), frequencies (Tower, ATIS, AWOS, ASOS and UNICOM), status (closed, military, add-on scenery), fuel, a count of facilities (gates, ramps, runways, approaches and so on), a runway summary, parking, the tower position, the transition altitude and level where the navigation data has them, and the scenery file the airport comes from.

The Runway Information box starts with the runway's localizer under Localizer and glideslope. Its first line says what it is, in the same words as the runway lists: "ILS 110.10, course 171", "Localizer 108.70, course 152", "LDA 111.35, course 147", or "No localizer". A glideslope that is not 3 degrees is added, and CAT II or CAT III is named. The details follow (ident, frequency, localizer heading and width, glideslope angle and DME). Then it gives the dimensions, surface, true and magnetic heading, threshold position, displaced threshold, blast pad and overrun, pattern altitude and runway elevation, lighting, markings, whether the runway is used for take-off and landing, and any VASI or PAPI.

A localizer heading is marked as a true heading ("0.5° true"), so do not mistake it for the magnetic course. Fields the navigation data leaves empty are left out or read "N/A".

Note: Approach minimums (the decision altitude, minimum descent altitude and visibility) are not in any navigation data, whether from the simulator or Navigraph. They exist only on the printed approach chart, so BA cannot show them. Get them from your chart source or your virtual airline, and enter them in the aircraft yourself.

Tip: The Airport Lookup lists only five main airport frequencies. For the airport's frequencies as a list you can tune straight into COM 1, use the Surroundings window (Output Ctrl+Shift+L); see The Surroundings Window.

The SimBrief tab

This tab has two buttons, Create SimBrief Plan and View Detailed Plan Info, which open the SimBrief Flight Planner on its Create or View tab. See SimBrief.

Worked example: building a departure and an arrival

Here is a complete example. You are flying from London Heathrow (EGLL) to Amsterdam (EHAM). SimBrief planned you off runway 27R, but the ATIS says Amsterdam is landing on runway 18R and you want to look at your arrival before you go. The procedure names below are only an illustration; your list will show whatever your navigation data contains.

  1. Press Output Shift+E. The Flight Planning window opens on the Route Viewer and your SimBrief plan loads: "SimBrief flight plan loaded".
  2. Arrow down the Waypoint column to hear the route. Press Right Arrow to hear a waypoint's Region, Airway and so on, then Home to come back to the Waypoint column.
  3. Press Ctrl+Tab four times to reach the Departure tab. Type EGLL. The runway list fills. Arrow to "Runway 27R", Tab to Load Departure and press Space. You hear "Loaded departure EGLL runway 27R".
  4. Press Ctrl+Shift+Tab three times to go back to the SID tab. Type EGLL. The runway list fills, starting with ALL. Arrow to 27R. Tab to the SID Procedures list and arrow to the SID on your clearance, say CPT5J. Tab to the transitions list and leave it on None. Tab to Load SID and press Space: "Loaded CPT5J RWY 27R".
  5. Press Ctrl+Tab to reach the STAR tab. Type EHAM, choose 18R in the runway list, choose your STAR, leave the transition on None, and press Load STAR.
  6. Press Ctrl+Tab to reach the Approach tab. Type EHAM. Arrow through the Approaches list to "ILS RWY 18R", choose a transition if your STAR needs one to join the approach, and press Load Approach: "Loaded approach ILS RWY 18R".
  7. Press Ctrl+Tab twice to reach the Arrival tab. Type EHAM, choose runway 18R and press Load Arrival: "Loaded arrival EHAM runway 18R".
  8. Press Ctrl+Tab to reach Airport Lookup. Type EHAM, arrow to runway 18R and read the Runway Information box: its length, ILS frequency and course, and lighting. These are the numbers you will set up for the approach.
  9. Press Ctrl+Tab until you are back on the Route Viewer tab (Ctrl+Tab wraps round after the last tab). Your plan now runs from EGLL 27R through the SID, the en-route waypoints, your STAR and the ILS to EHAM 18R. Press F5 to fill in distances and bearings from where you are parked.

You can now enter the same procedures into your aircraft's FMC or MCDU, and press Describe Route if you want the AI briefing.

If something goes wrong

The AI Route Briefing

What it is

The Describe Route button on the Route Viewer tab asks an AI service (Google's Gemini or Anthropic's Claude, whichever you set up) to write a narrative briefing of your whole flight from your SimBrief plan. It is written for a blind pilot: it describes the geography and terrain you fly over, what a sighted pilot would see out of the window, the SID and STAR, the weather, and the NOTAMs, and it ends with your expected taxi out and taxi in, worked out by BA on your own simulator scenery.

The briefing is in plain text with a heading for each part, about 600 to 900 words, so it reads well with a screen reader.

Before you start
How to use it
  1. Open the Flight Planning window (Output Shift+E) and make sure your SimBrief plan is loaded.
  2. Tab to Describe Route and press Space. BA says "Generating route description, please wait". The status line shows "Computing taxi routes..." and then "Generating route description...".
  3. When it is done, BA says "Route description ready" and moves you to the Route Description box. Read it with the arrow keys.

A briefing usually takes from several seconds to about a minute, depending on your AI service and whether web search is on. You can close the Flight Planning window while it is being prepared: the briefing carries on, BA says "Route description ready" when it finishes, and it is waiting for you when you reopen the window. If you reopen the window before it finishes, the status line says "A route description is still being prepared. Describe Route is available again when it finishes."

The briefing is kept until you load a new SimBrief plan. Closing and reopening the window, or switching the navigation database, does not lose it.

What is in the briefing

The briefing has seven parts:

  1. Flight overview — origin and destination, distance and flight time, cruise altitude, direction of flight, and the countries or regions you cross.
  2. Departure and SID — the area around the departure airport, terrain and noise-abatement concerns, what you would see on the climb-out, and the SID you filed with its waypoints and top altitude.
  3. En route — the cities, mountains, coastlines, borders and other features along the way.
  4. Arrival and STAR — the same for the destination and your STAR, with its bottom altitude.
  5. Weather — departure and arrival weather from the METARs in your plan, and any significant weather or SIGMETs along the route.
  6. NOTAMs — significant notices for both airports, such as closed runways, an ILS out of service or taxiway closures, in plain language. Current NOTAMs can only be found when web search is on (see Settings below).
  7. Taxi out and taxi in — described next.
The taxi out and taxi in

For the last part, BA plans both taxi routes itself before it asks the AI, using the same routing that taxi guidance uses, on your own scenery:

For each leg you hear the taxiways in order, the turns, the distances in your ground distance unit, every hold-short point and every runway you cross. For the arrival you also hear which side to leave the runway, the exit taxiway and its distance from the threshold, and the next exit if you miss it. Each route ends by reminding you that it is the expected route on your scenery and that SayIntentions or ATC will give the actual taxi clearance.

After each route comes a one-sentence check against the real airport. It begins "Real-world check, from memory rather than live charts:" or, only when a web search actually found and read the airport's current charts, "Real-world check, against current charts:". It says whether the route matches real-world practice, or names what differs. It may be followed by up to three tips, beginning "Real-world suggestions, not from your scenery:", such as a preferred exit, a size restriction for your aircraft, or a NOTAM affecting your taxi.

When your scenery has no taxiway data for an airport, the route may be planned on OpenStreetMap or X-Plane airport data instead, and the briefing says so: this is for planning only, and taxi guidance cannot use it. When something cannot be planned, the briefing says so plainly, for example a closed runway, a gate your scenery does not have, or a runway with no taxiway at its full-length start.

Note: The taxi part of the briefing is a preview, not a clearance. On the day, follow ATC or SayIntentions, and build the route you are actually given in the taxi planner; see Taxi Guidance.

Settings

The AI tab settings are described in AI Display Reading and Scene Description. For the briefing, the two web search options (Enable Grounding with Google Search (paid feature) for Gemini, Enable web search for NOTAM route grounding (extra cost) for Claude) matter most: without them, the NOTAM section cannot be current and every taxi check is from memory.

If you turned on Claude's web search but the Claude model you chose does not support it, BA still writes the briefing, and it begins "Note: web search is not available for the selected Claude model, so this briefing is not grounded with current NOTAM or weather data."

The distances in the taxi part follow Use feet for distances (default: metres) on the Taxi Guidance tab.

If something goes wrong

Aircraft EFBs

What it is

Most modern airliners in the simulator come with an electronic flight bag: a tablet in the cockpit with pages for performance calculation, weight and balance, ground services, charts, settings and more. On their own these tablets are drawn as pictures inside the simulator and cannot be read by a screen reader. BA opens each aircraft's tablet in an accessible window instead, so you can read it and press its buttons with your screen reader.

The tablet you get depends on the aircraft:

Aircraft Key What opens
FlyByWire A320neo Input Shift+T A320 flyPad EFB
Headwind A330-900neo Input Shift+T A330 flyPad EFB
FlyByWire A380X Input Shift+T A380X flyPad EFB
PMDG 737 and 777 Input Shift+T, or Input Ctrl+Shift+T for the First Officer's tablet PMDG 737 EFB or PMDG 777 EFB (with "(First Officer)" for the First Officer's tablet)
TFDi MD-11 Input Shift+T MD-11 EFB
Fenix A320 Input Shift+T Fenix EFB
iFly 737 MAX8 Input Shift+T iFly 737 EFB
BlueBird 757-200 Input Shift+T 757 EFB
HorizonSim 787-9 none BA says "787 E F B not available."

Note: On every aircraft, Output Shift+T toggles trim announcements. The EFB is on Input Shift+T, so check which mode you are in.

The aircraft must be loaded and its tablet working; nothing needs installing in your Community folder. Each tablet's pages are described in Airbus Aircraft and Boeing Aircraft and the MD-11.

The flyPad, PMDG and MD-11 tablets

The FlyByWire flyPad, the PMDG tablet and the MD-11 EFB all open in the same kind of window. BA reads the live tablet page and shows it as a simple web page inside the window, so your screen reader treats it exactly like a web page in your browser.

At the top of the window are two status lines: the connection status (for example "flyPad connected (42 elements)") and the current page ("Page: Ground"). Below them is the page itself.

The page always follows the tablet. Whatever page is open on the tablet is what you see, and when it changes, your screen reader announces the new page name, for example "flyPad page: Payload". You move around the tablet by pressing its own menu buttons, just as a sighted pilot taps them.

Reading the page:

Using controls:

Keys in these windows:

Key What it does
F5 Re-read the tablet now
F6 Say the connection status, for example "flyPad connected. Page Dashboard. 42 elements."
Alt+F4 Close (hide) the window; it reopens on the same page

BA keeps the window up to date by itself, several times a second, and changes values in place so your position on the page is not lost while you read. If the page looks out of date, press F5.

If BA cannot reach the tablet, F6 says, for example, "flyPad not connected. Make sure the aircraft is loaded and the tablet is powered on." Wait until the aircraft has fully loaded and try again.

Note: The web view these windows use is Microsoft's free Edge WebView2 Runtime, which comes with Windows 11 and most Windows 10 installations. On a computer where it cannot start, these windows fall back to a plain list of controls: press Tab and Shift+Tab to move between them, and type in a field and press Enter to send it (BA says, for example, "Set Passengers to 150"). Installing or repairing the WebView2 Runtime from Microsoft's website restores the normal window.

The Fenix and iFly EFBs

The Fenix A320 and the iFly 737 MAX8 serve their tablets as real web sites on your own computer. BA shows the live site in its window, so you read and use it exactly like a web page, with browse mode and quick keys. The iFly site already works with a screen reader; the Fenix v3 site does not on its own, so BA adds the names, states and keys it lacks.

Both windows hide rather than close, so when you reopen them you are back on the page you left.

Flows and Checklists

Before you push back, the First Officer (Output Shift+C) works the aircraft's flows and checklists with you. It has its own chapter: The First Officer and Checklists.

Tracking Waypoints

What it is

BA has five tracking slots. Put a waypoint in a slot, and from then on one key press tells you how far away it is and which way to fly to reach it. This is useful for a fix ATC asks you to report, the start of a hold, a waypoint you need to cross at a certain altitude, or simply keeping track of your progress towards top of descent.

Putting a waypoint in a slot

There are two ways.

From the Track Fix Window:

  1. Press Input Shift+F. The Track Fix Window opens with the focus in Waypoint Name.
  2. Type the waypoint's name, for example DET.
  3. Tab to Tracking Slot and choose Slot 1 to Slot 5.
  4. Tab to Track and press Space.

If there is only one waypoint with that name, BA says "Waypoint DET tracked in slot 1" and the window closes. Many waypoint names are used more than once around the world. If there are several, BA says, for example, "3 waypoints found for DET, select one", and shows a list titled "Multiple waypoints found. Select one:". Each entry gives the name, region and distance from you, for example "DET - Region EG - 23.4 NM", with the nearest first. Arrow to the right one and press Enter (or press Select).

If the name is not in the database, BA says "Waypoint DET not found". Press Escape to close the window without tracking anything. The window searches the navigation database's named waypoints; to track a waypoint on your route, the Route Viewer method below is often easier.

From the Route Viewer in the Flight Planning window: arrow to the waypoint, press the Applications key (or Shift+F10), and choose a Track Slot.

Hearing a tracked waypoint

Press Output 1, 2, 3, 4 or 5. BA reads the waypoint, its distance and its magnetic bearing from your aircraft right now, for example "DET, 23 nautical miles, 120 degrees". If the slot is empty, it says "Track slot 2 empty". Putting a new waypoint in a slot replaces the old one.

Tip: The bearing is the magnetic heading that would take you straight to the waypoint with no wind. Compare it with your heading (Output H) to tell whether the waypoint is ahead, to the left or to the right.

NAV Radios

Reading the NAV radios (Output N)

Press Output N to hear both NAV radios. For each one BA reads the frequency and, if it is receiving a station, its ident and name, the localizer course if it is an ILS, the glideslope angle, and the DME distance, for example "Nav 1: 110.90, localizer course 271, glideslope 3.0 degrees, DME 5.2 nautical miles. Nav 2: 113.10, no signal". This is a quick way to confirm you have tuned the right ILS before the approach. Some aircraft read their radios in their own way; see your aircraft's chapter.

Setting the NAV radios (Input Ctrl+N)

On the PMDG 737 and the iFly 737 MAX8, Input Ctrl+N opens the NAV Radios window. It has four fields, already filled with the current settings:

Change what you need and press Enter in any of the four fields to apply all four and close the window; unchanged values are simply set again. Press Escape, or the Cancel button, to close it without changing anything. You can type a frequency as 110.30, 110.3 or 11030, with a dot or a comma, and BA rounds it to the nearest valid channel. If a value is out of range, BA tells you and puts you back in that field, for example "NAV 1 frequency must be between 108.00 and 117.95 megahertz".

On the iFly, BA keys each frequency on the NAV control panel keypad, transfers it to active and sets the MCP course; read the result back with Output N. On other aircraft, tune the radios from their panels, or from the aircraft's own radio windows described in Airbus Aircraft and Boeing Aircraft and the MD-11.

FMC Settings

What it is

File, FMC Settings holds two settings for BA's FMC, CDU and MCDU windows. The menu item appears only while a PMDG aircraft, the Fenix A320 or the HorizonSim 787 is loaded.

Press OK to save. BA says "FMC settings saved", and the change takes effect at once.

Weather

Weather matters at every stage of a flight: the wind decides which runway you use, the temperature and altimeter setting decide your performance and your safe altitudes, and clouds, rain, icing and turbulence decide how the flight will feel and whether you need to change your plan. A sighted pilot glances at a weather display. BA gives you the same information in words, through a few hotkeys, two windows, a calculator and a set of optional spoken alerts. The weather keys are all in Output mode and work the same on every aircraft.

Key What it does
Output I Speaks the wind where you are, and at your destination
Output O Speaks the outside air temperature
Output Shift+M Opens the METAR Report window
Output Shift+R Opens the Weather Radar window
Output Ctrl+Shift+T Opens the Cold Temperature Altitude Correction calculator

Note: On aircraft with a CDU or MCDU window, Input Shift+M opens that window; Output Shift+M always opens the METAR window.

Where BA Gets Its Weather

BA can read weather from three places. Knowing which one is answering helps you understand what you hear.

BA never mixes sources for the same reading. Each readout tells you, or makes it clear, which source answered.

Wind: Output I

Press Output I to hear two winds separated by a comma: the wind at your aircraft right now, then the wind reported at your destination. For example, "270 at 12, 250 at 8, gusting 15" means the wind here is from 270 degrees at 12 knots, and at your destination from 250 degrees at 8 knots with gusts to 15.

What you will hear
With and without ActiveSky

If you are not connected to the simulator you hear "Not connected to simulator."

Outside Temperature: Output O

Press ], then O. BA speaks the outside air temperature at the aircraft, for example "-42 degrees Celsius" in cruise or "15 degrees Celsius" on the ground. This always comes from the simulator. It is useful for checking engine and wing anti-ice conditions and for the cold temperature calculator later in this chapter (use the airport's reported temperature for that, not the temperature at cruise altitude).

To hear Fahrenheit, open File, Settings, Weather and tick Use Fahrenheit for outside temperature (default: Celsius) in the Temperature units group, the last setting on the tab. Save with OK. Output O then says, for example, "59 degrees Fahrenheit" for 15°C, on every aircraft. Untick it to return to Celsius. The choice is remembered after restarting BA. This setting applies to Output O; weather reports, cockpit displays and the cold temperature calculator keep their existing units.

The METAR Report Window

What it is

A METAR is the standard written weather report an airport issues, usually every half hour or hour. It gives the wind, visibility, weather, cloud, temperature, dew point and altimeter setting in a compact code. The METAR Report window lets you look up the METAR for any airport by its four-letter ICAO code.

When to use it
How to use it
  1. Press ], then Shift+M. The METAR Report window opens with focus in the Airport ICAO Code box.
  2. Type the four-letter code, for example EGLL. Letters are capitalised for you.
  3. Press Enter. BA fetches the report and moves focus to the VATSIM METAR box with the whole report selected, so your screen reader reads it straight away.
  4. Read the report with the arrow keys. Press Shift+Tab to go back to the code box and look up another airport.
  5. Press Escape, or Alt+C for Close, to close the window. Focus returns to the simulator.

The report is shown exactly as issued, in METAR code. For example: "EGLL 181150Z 27012KT 9999 FEW030 15/09 Q1013 NOSIG" means Heathrow at 11:50 UTC on the 18th, wind 270 degrees at 12 knots, visibility 10 kilometres or more, a few clouds at 3,000 feet, temperature 15, dew point 9, pressure 1013 hectopascals, no significant change expected. If you want the same kind of report spoken in plain English, the Weather Radar's Closest Station box (with ActiveSky) decodes it for you.

What you will hear and see

A short status line above the report says, for example, "METAR for EGLL".

With ActiveSky: the ActiveSky METAR and forecast

If ActiveSky integration is switched on and ActiveSky is running when you open the window, the window grows two extra controls below the VATSIM box:

The tab order is: code box, VATSIM METAR, ActiveSky METAR, Forecast, Close. The forecast list only affects the ActiveSky box. If ActiveSky has no report for that airport, its box says "No ActiveSky METAR found for" the code.

If ActiveSky was not running when you opened the window, close it and reopen it after starting ActiveSky.

The Weather Radar

What it is

The Weather Radar window is BA's complete weather picture. Despite the name it does not draw a radar image; instead it gathers everything known about the weather around you into a set of lists you read line by line: the conditions at your aircraft, nearby hazard advisories, pilot reports, and the winds above and below you. With ActiveSky it adds a decoded station report, a vertical profile of the cloud and winds, and the advisories along your planned route.

When to use it
How to use it
  1. Press ], then Shift+R. The Weather Radar window opens and fetches everything at once. Focus starts in the Weather at Current Position list.
  2. Use the Down and Up arrow keys to read a list one line at a time. Each line is one fact, one advisory line, or one wind level.
  3. Press Tab to move to the next list, Shift+Tab to go back.
  4. The window refreshes itself every 30 seconds, changing only the lines that changed and keeping your reading position, so you can leave it open during the flight.
  5. Press F5, or Alt+R for Refresh (F5), to fetch fresh data immediately.
  6. Press Escape, or Alt+C for Close, to close. Focus returns to the simulator.

The controls, in Tab order, are:

  1. ActiveSky status (only when ActiveSky integration is on)
  2. Weather at Current Position
  3. Closest Station Weather (ActiveSky only)
  4. Vertical Profile (ActiveSky only)
  5. Route Advisories (ActiveSky only)
  6. Nearby Advisories
  7. Winds Aloft
  8. Decode advisories into plain English checkbox (Alt+D)
  9. Refresh (F5) button
  10. Close button
  11. Status, a single line that says "Fetching weather data..." during a fetch, then "Last updated:" with the time, or "Error:" with the reason if something failed.

The ActiveSky-only parts are hidden completely when the integration is off.

The Weather Radar without ActiveSky

With the ActiveSky integration switched off (the default), you have four parts: Weather at Current Position, Nearby Advisories, Winds Aloft and the Status line.

Weather at Current Position

This list comes straight from the simulator and describes the air around your aircraft. You will read lines like these:

If BA is not connected to the simulator, the list says "Not connected to simulator."

Nearby Advisories

This list shows real-world hazard warnings around your position, downloaded from aviationweather.gov. It covers at least 300 nautical miles around you (or your proximity range from the Weather settings tab, if you have set it larger). There are two kinds of entry:

The list starts with a header line giving your position and the range, for example "Position: 51.47°, -0.45° | Range: 300 nm", then a divider line. Next comes "SIGMETs / AIRMETs" with the count, then each advisory:

Then "Pilot Reports" with the count, each one as "[PIREP]" followed by the hazard and the flight level, then the bearing and distance, the time of the report and the aircraft type.

If there are none, you read "No active SIGMETs or AIRMETs found." and "No pilot reports (turbulence/icing) found within 300 nm." (with your actual range).

The Decode advisories into plain English checkbox, just after the Winds Aloft list, changes how these entries are written. Unchecked, you get the short aviation abbreviations as published (for example "FL300" and "MOD"). Checked, BA spells them out: heights in feet, intensities and qualifiers as words. The choice is remembered. It takes effect on the next refresh (press F5 to see it at once).

Note: Nearby Advisories are always real-world data. They match the simulator's weather when you fly with live weather. With preset or custom weather they may describe storms that are not in your sky.

Winds Aloft

This list gives the wind every 1,000 feet from 5,000 feet below you to 5,000 feet above you. On the ground, that means from the ground up to 5,000 feet. It starts with a line such as "Aircraft: 35,000 ft | forecast winds:", then a divider, then one line per level:

"36,000 ft: 280° / 95 kts"

The level closest to your current altitude is marked "(nearest)". The last line says where the figures came from: "Source: Open-Meteo". Open-Meteo is a free internet weather forecast, so these are forecast winds at your position, not a measurement from the simulator.

Use this list to choose a cruise level: if the headwind is much weaker 2,000 feet lower, it may be worth asking for that level. It also helps on descent, to expect how the wind will change as you come down.

If BA cannot get the data you read "Winds aloft data unavailable." If the simulator has not given BA a position yet, the advisories and winds lists say "Aircraft position unavailable — connect to simulator first."

The Weather Radar with ActiveSky

When you switch on the ActiveSky integration (see ActiveSky) and ActiveSky is running, the Weather Radar becomes much richer. ActiveSky knows things the simulator does not report, such as the surface wind and gusts, the cloud ceiling, the altimeter setting, the turbulence level and the full weather report of the nearest station. Every part of the window is described below in Tab order.

ActiveSky status

The first line in the window. It says which mode ActiveSky is in and its weather clock, for example "ActiveSky: Live Real time mode, weather time 1935Z". Live mode means ActiveSky is showing today's real weather. Other modes, such as a historical date or custom weather, mean the weather in your sky is not today's real weather; the Nearby Advisories list warns you about that (see below).

If the integration is on but BA cannot reach ActiveSky, this line explains why, for example "ActiveSky: not detected" followed by the technical reason. In that case the rest of the window falls back to the simulator, exactly as in the previous section, and the three ActiveSky-only lists say "unavailable".

Weather at Current Position, from ActiveSky

The same list as before, but now filled from ActiveSky and with more lines:

Tip: Some of these lines, such as the cloud ceiling, QNH and surface gust, only exist when ActiveSky is answering. If they disappear from the list, ActiveSky has stopped responding and BA has quietly fallen back to the simulator. The ActiveSky status line at the top tells you for certain.

Closest Station Weather

This list reads the METAR of the reporting station nearest to you, decoded into plain English, followed by the raw report. For example:

"Decoded weather at EGLL. Wind: 270 at 12 knots. Visibility: 10 kilometres or more. Clouds: Few at 3,000 feet. Precipitation: None. Temperature: 15. Dew point: 9. Altimeter: 1013 (29.91 inches)."

Then a blank line, "Raw METAR:", and the report in code.

Wind gusts are read as "gusting" and a varying wind as "varying between" two directions. United States reports give visibility in statute miles and are read that way; elsewhere it is kilometres or metres. Cloud layers are listed from lowest to highest (few, scattered, broken, overcast, or vertical visibility in fog). "Clouds: Clear" means the report said CAVOK, ceiling and visibility OK. If ActiveSky cannot name a station the list says "Decoded weather at your position", and if no report is available at all it says "unavailable".

This is exactly the same text, word for word, as the spoken "Active sky weather updated" announcement described later, so what you read on demand and what you hear automatically never disagree.

Vertical Profile

This list describes the column of air above and below you, like a cross-section a meteorologist would draw. It has two parts.

First, "Cloud layers:", each layer from lowest to highest, for example:

Each line gives the coverage (few, scattered, broken or overcast), the base and top in feet, and only if present the icing (light, moderate, heavy or severe), the precipitation (rain or snow) and the turbulence inside that layer. This is the best place to find out how thick a cloud layer is and whether you will pick up ice climbing through it. If there are none you read "No cloud layers reported below FL560."

Second, "Winds and temperatures aloft:" at the surface, around 5,000, 10,000, 18,000, 24,000 and 34,000 feet, plus the level nearest you, for example:

Each line is direction, speed in knots, then the temperature in degrees Celsius ("minus" for below zero), and a turbulence word if there is any at that height.

If ActiveSky cannot give a profile for your position the list says "unavailable".

Route Advisories

This list shows the SIGMETs and AIRMETs that lie along the flight plan loaded in ActiveSky. It is different from Nearby Advisories: Nearby Advisories is everything around you now; Route Advisories is everything on your planned route, however far ahead. For it to work, ActiveSky must have your flight plan. If you link ActiveSky to SimBrief, ActiveSky downloads your plan itself; otherwise load the plan in ActiveSky. BA does not send a plan to ActiveSky.

Nearby Advisories, with ActiveSky

This list stays exactly as described in the previous section, using real-world data from aviationweather.gov, because that data gives the precise bearing and distance. The one difference: if ActiveSky is in any mode other than Live, a note appears under the header: "Note: nearby advisories are live real-world data; ActiveSky is in" followed by the name of its current mode. It reminds you that today's real storms may not be in the sky ActiveSky is showing you.

Winds Aloft, with ActiveSky

The same levels as before, but ActiveSky answers instead of Open-Meteo, so these are the winds the simulator is really flying you through right now. The header says "current winds" instead of "forecast winds", each line also gives the temperature ("36,000 ft: 280° / 95 kts, -52°C"), and the last line says "Source: ActiveSky". If ActiveSky does not answer this particular request, BA uses Open-Meteo instead and the last line says so.

Weather Radar Troubleshooting

ActiveSky

What it is

HiFi ActiveSky is a separate paid weather program for MSFS. It replaces the simulator's weather with its own, built from real-world reports or from historical or custom scenarios. BA can read weather directly from ActiveSky while it is running on the same PC.

Do I need it?

No. Everything in this chapter except the parts marked ActiveSky works with the simulator's own weather. If you do not own ActiveSky, leave the integration off; BA then never even looks for it, so nothing slows down.

If you do fly with ActiveSky, switch the integration on. Under ActiveSky the simulator's own weather values can be wrong (precipitation stuck on snow, a wind that does not match), and reading ActiveSky directly fixes that.

How to switch it on
  1. Open the Settings window (see The Settings Window) and go to the Weather tab.
  2. In the ActiveSky (HiFi) group, check Enable ActiveSky integration (Alt+A).
  3. Press OK.

From then on Output I, the Weather Radar, the METAR window and the precipitation announcement use ActiveSky, as described above, and the ActiveSky settings appear on the Weather tab. The spoken ActiveSky updates also need Auto-announce weather state changes, described next.

The Weather Settings Tab

All weather settings are on the Weather tab of the Settings window. Some only appear when another setting they depend on is checked, so a setting that would do nothing is never in your way. Hidden settings keep their values.

Setting Default What it does
Enable ActiveSky integration Off Reads weather from ActiveSky when it is running.
Auto-announce weather state changes Off The master switch for spoken weather changes: cloud, precipitation, visibility, icing, and with ActiveSky the decoded weather updates, turbulence and mode changes.
Announce turbulence changes On Speaks turbulence getting worse or easing. Shown only when the master switch and ActiveSky are both on.
Announce icing On Speaks ice starting to build and clearing. Shown only when the master switch is on.
Auto-announce approaching SIGMETs and AIRMETs Off Speaks real-world SIGMETs and AIRMETs that come within the proximity range.
Auto-announce approaching pilot reports (PIREPs) Off Speaks significant pilot reports of turbulence or icing within the proximity range.
Announce route advisories by proximity (ActiveSky) On Speaks advisories on your ActiveSky route as you approach, enter and leave them. Shown only when ActiveSky is on.
Proximity range (nautical miles) 100 How close a SIGMET, AIRMET or PIREP must be to be announced. 10 to 500.
En-route advisory distance (nautical miles) 100 How far ahead a route advisory is announced. 10 to 500. Shown only when ActiveSky is on.
Weather announcement interval Active Sky download interval The shortest gap between spoken ActiveSky weather updates. Shown only when the master switch and ActiveSky are both on.

The proximity range and the en-route advisory distance are separate settings for separate features; changing one never changes the other.

Each announcement is spoken only when something changes. When BA starts watching (and after you switch aircraft or reconnect), it quietly notes the weather you are already in and only speaks later changes.

Automatic Weather Announcements

Cloud, precipitation and visibility

With Auto-announce weather state changes on, BA speaks:

Cloud and visibility always come from the simulator, with or without ActiveSky.

Icing

With the master switch and Announce icing on, BA watches how much ice is actually building on the airframe, on any aircraft:

BA waits for the ice to clear properly before saying it has cleared, so a reading hovering on the edge does not make it repeat itself.

Note: The FlyByWire A380X has its own icing callout, taken from its ice detector: "Icing conditions" and "Icing conditions cleared". On that aircraft BA uses that one only, so you never hear icing twice. The Announce icing setting does not switch the A380X's own callout off.

Turbulence

With ActiveSky, the master switch and Announce turbulence changes all on, BA speaks the turbulence level as it changes, in words only:

The words follow the standard pilot categories, the same ones the Weather Radar shows. To stop the callout flipping back and forth at a boundary, BA moves up a level as soon as the turbulence reaches it, but only moves back down once it has dropped clearly below. In moderate or worse turbulence, slow to your aircraft's turbulence penetration speed, make sure the seat belt sign is on and consider asking for a different level; the Vertical Profile and pilot reports help you choose one.

ActiveSky weather updates

With ActiveSky and the master switch on, every time ActiveSky downloads new weather and the nearest station's report has changed, BA reads the new decoded report:

"Active sky weather updated. Decoded weather at EGLL. Wind: 270 at 12 knots. Visibility: 10 kilometres or more. Clouds: Few at 3,000 feet. Precipitation: None. Temperature: 15. Dew point: 9. Altimeter: 1013 (29.91 inches)."

This is the same text as the Weather Radar's Closest Station Weather list. It is a good way to keep track of a changing altimeter setting in the descent.

If these updates come too often, for example while you teleport around, use the Weather announcement interval setting. The choices are Active Sky download interval (no extra limit: BA speaks whenever ActiveSky has new weather), 5, 10, 15, 20, 30 or 45 minutes, or 1 hour. A change that arrives during the waiting time is spoken once the time is up, not lost.

BA also tells you if ActiveSky switches mode, for example "ActiveSky weather mode changed to Live Real time mode." It never announces the mode ActiveSky was already in when you started; you can always read it at the top of the Weather Radar.

SIGMET, AIRMET and pilot report alerts

These two settings work with or without ActiveSky and do not need the master switch. They use the same real-world data as the Weather Radar's Nearby Advisories list.

With Auto-announce approaching SIGMETs and AIRMETs on, each new advisory within your proximity range is spoken once, for example:

"SIGMET: Thunderstorms, FL250 to FL450, bearing 240 degrees, 85 nautical miles"

That is the type, the hazard, the heights if known, and the bearing and distance from you to the nearest part of the area.

With Auto-announce approaching pilot reports (PIREPs) on, each significant pilot report within range (moderate or worse turbulence or icing; light reports are skipped) is spoken once, for example:

"Pilot report: MOD turbulence at FL350, bearing 310 degrees, 60 nautical miles"

If an advisory or report is still within range, it is spoken again about every 15 minutes as a reminder.

Route advisories (ActiveSky)

With ActiveSky on and Announce route advisories by proximity (ActiveSky) on, BA watches the SIGMETs and AIRMETs on the route loaded in ActiveSky (the same ones as the Weather Radar's Route Advisories list) and speaks them as they become relevant. This setting does not need the master switch.

Each area is only announced as approaching once. After you have been inside it, BA only tells you about entering and leaving it again. When an advisory expires or is replaced, BA says nothing; the Weather Radar always shows what is currently active. On a new flight after a turnaround (at least five minutes on the ground and then a takeoff), BA starts afresh, so an advisory you crossed on the way out will be announced again on the way back.

If announcements do not come

Cold Temperature Correction

What it is

Your altimeter assumes the air is at a standard temperature. In very cold air, the air is denser than standard, and the altimeter reads higher than you really are. On a cold day, an approach flown exactly at the published altitudes can put you hundreds of feet lower than intended, closer to terrain. Pilots correct for this by adding a margin to the published approach altitudes. The Cold Temperature Altitude Correction window does that sum for you. It uses the same standard EUROCONTROL formula as the FlyByWire flyPad's performance page.

It is a calculator only. It needs no simulator connection and no particular aircraft, so you can use it while planning on the ground.

When to use it

When the temperature at your destination is at or below 0°C, and especially well below, before you brief the approach. Correct the altitudes that keep you clear of terrain: the initial and intermediate approach altitudes, the final approach fix altitude, the minimum descent altitude or decision altitude, and the missed approach altitudes. Many airlines and countries require it below a set temperature, and some approach charts state a lowest temperature at which the procedure may be flown.

How to use it
  1. Press ], then Ctrl+Shift+T. The Cold Temperature Altitude Correction window opens with focus in the first box.
  2. In Aerodrome (field) elevation, feet, type the destination airport's elevation, for example 790. Negative values are allowed for the few airports below sea level.
  3. Press Tab. In Reported temperature, Celsius, type the airport's reported temperature, for example -25. Use the METAR temperature or, with ActiveSky, the surface temperature, not the temperature at your cruise altitude.
  4. Press Tab. In Published altitudes (feet), one per line, type each altitude from the approach chart on its own line, pressing Enter between them. For example 3000, then 2200, then 1010.
  5. Press Tab to the Calculate button and press Space, or press Alt+A from anywhere. You can also press Enter in the elevation or temperature box (Enter in the altitudes box starts a new line instead).
  6. Focus moves to the Corrected altitudes box. Read it line by line with the arrow keys.

If you entered only one altitude, BA also speaks the answer straight away.

What you will hear and see

The results start with a heading line, for example "Cold temperature correction at 790 ft field elevation, -25 Celsius:", then one line per altitude:

The last line reminds you: "Advisory only — verify against official sources." Corrected altitudes are rounded up to the next 10 feet. The correction grows with the height above the airport, so the high initial approach altitudes get the biggest additions.

Error messages are spoken and shown in the results box, and focus returns to the box you need to fix:

Type numbers without thousands separators (3000, not 3,000). Either a full stop or a comma works as the decimal point.

Warning: If you fly corrected altitudes under ATC control, tell the controller, because their radar shows your uncorrected altitude. Remember to set the corrected minimum, not the published one, as your decision or minimum descent altitude.

Press Escape, or Alt+C for Close, to close the window.

Part 5: On the Ground

Part 5 is about the airport, from the gate to the runway and back: knowing where you are, Taxi Guidance, Ground Traffic, and Gates, GSX and Docking.

Knowing Where You Are

A sighted pilot glances out of the window and knows at once that they are on taxiway Bravo, next to Concourse C, with the fuel farm behind them. BA gives you the same picture in words, when you ask and as you taxi. These are ground features; in the air, use Location Info and Nearest City instead.

Where Am I

What it is

Where Am I tells you, in one short sentence, what is under your aircraft right now and which airport you are at. It works whether or not taxi guidance is running, so you can use it at any time on the ground: parked at the gate, holding short of a runway, or lost on an apron.

How to use it
  1. Make sure you are on the ground.
  2. Press Output Alt+Y.
  3. BA speaks your location, for example:
    • "Taxiway B at KJFK."
    • "Gate A25 at KJFK."
    • "Runway 22L at KJFK."
    • "Near taxiway K at EGLL."
What you will hear

BA checks in a fixed order, so the most useful answer wins:

When nothing matches, you hear "Not on a known taxiway or ramp at" followed by the airport code. Other answers you may hear:

Tip: Where Am I always uses the airport you are actually standing at, even a small field with a three-character code, never a nearby heliport or a neighbouring field.

Look Around

What it is

Look Around answers a bigger question: not just "what am I on?" but "what is around me?". In one sentence you hear your Where Am I line, the apron or concourse you are in, and up to four nearby buildings and places, each with its direction and distance.

How to use it
  1. On the ground, press Output Alt+L.
  2. Listen. A typical answer sounds like this:

"Gate B12 at KATL. At Concourse B. Concourse A, ahead and to the left, 180 metres. Control tower, to the right, 420 metres. Fuel, behind and to the left, 350 metres."

The first time at an airport the answer can take a few seconds; you hear "Looking around." first. A late answer waits its turn rather than cut off a taxi instruction.

What you will hear

The answer has three parts.

  1. Where Am I. The same line Output Alt+Y gives.
  2. Where you are. One of these, if BA can tell:
    • "On the Commercial Ramp." You are on a named apron or de-ice pad.
    • "On the GA ramp." You are among the stands of a ramp.
    • "On the Apron." You are inside an apron that has no name.
    • "At Concourse B." You are within about 120 metres of a concourse or terminal.
  3. What is nearby. Up to four features within 600 metres, nearest first, each as name, direction, distance. You never hear two of the same kind, except hangars and FBOs, because a general aviation field can be lined with hangars. Several unnamed hangars are grouped into one entry, for example "Hangars, to the left, 80 metres." Anything you are standing right next to is described as "here" instead of with a direction.

Directions are always relative to the way your aircraft is pointing:

You hear Means
ahead Within about 20 degrees of your nose
ahead and to the right / left Between about 20 and 70 degrees off your nose
to the right / left Roughly abeam, between about 70 and 110 degrees
behind and to the right / left Between about 110 and 160 degrees
behind Within about 20 degrees of your tail

Ground traffic callouts use exactly the same words, so "ahead and to the left" always means the same thing in BA.

The kinds of place BA knows about are terminals, concourses (including piers and satellites), FBOs, hangars, the control tower, fuel, cargo areas, fire stations, helipads, aprons, de-ice pads and airport offices. When a place has no name of its own, BA uses the kind word: "Fuel", "Control tower", "Cargo ramp", "De-ice pad".

Other answers:

Distances follow the Use feet for distances (default: metres) setting on the Taxi Guidance tab.

The Surroundings Window

What it is

The Surroundings window is a fuller, browsable version of Look Around. It lists everything within about a kilometre of you, and it also shows two things a pilot often needs at an unfamiliar airport: whether fuel is available, and every radio frequency the airport has. You can tune any of those frequencies into COM 1 with a single key.

How to use it
  1. On the ground, press Output Ctrl+Shift+L.
  2. The window opens, titled "Surroundings at" followed by the airport code. BA does not speak a summary when it opens. Your screen reader reads the window and the first list item.
  3. The window has up to three lists. Press Tab to move between them and the Up and Down arrows to move through a list. Each list announces its name and your position in it, for example "3 of 12". A list that would be empty is left out.
    • Airport: the fuel line, for example "Fuel available", "Avgas available" or "Jet fuel available". This list is missing when the airport has no fuel.
    • Frequencies: one row per frequency, each starting with its kind, in the order you would normally use them: ATIS, clearance delivery, ground, tower, departure, approach, center, CTAF, UNICOM and the rest. For example "Ground 121.9" or "Tower 118.3". Where an airport has several frequencies of one kind with different names, the name is added to tell them apart: "Ground 129.25, RAMP CONTROL". Because every row starts with its kind, you can press a letter to jump, for example G for ground or T for tower.
    • Nearby, 12 items (the number changes): every place within about a kilometre, nearest first, as name, detail, direction, distance. The detail adds useful extras where BA knows them, such as the airline that uses a concourse or the operator of an FBO.
  4. To tune a frequency, move to it in the Frequencies list and:
    • press Enter to put it into COM 1 standby, or
    • press Shift+Enter to put it straight into COM 1 active.
  5. Press Escape, or use the Close button (Alt+C), to close the window. Focus goes back to the window you were in when you pressed the hotkey.

The window stays open after you tune, so you can tune several frequencies one after another. It is a snapshot: it does not update as you move. Press Output Ctrl+Shift+L again for a fresh one, and the new window replaces the old one.

What you will hear when you tune

A list cannot tell you that anything happened, so BA reads COM 1 back after tuning and tells you what it actually holds:

Some aircraft cannot be tuned this way. On the FlyByWire A380X you hear "This aircraft tunes its radios only through its RMP window, input mode Ctrl+Shift+R."

When there is nothing to show at all, BA speaks instead of opening an empty window: "No surroundings data for" the airport, or "Nothing within 1000 metres."

Taxiing to a place

When you have found a place you want to go to, for example an FBO after landing, the fuel island or a cargo ramp, you can taxi straight to it. In the taxi planner, choose the destination type Place and pick it by name. BA takes you to the stand in front of it, or to the nearest taxiway point when there is no stand, with docking guidance where the scenery gives a stop position. See The Taxi Planner for the details.

Callouts While You Taxi

As well as answering when you ask, BA can tell you things as you taxi. Each of these has its own setting on the Taxi Guidance tab of the Settings window, so you can choose how much you hear.

Buildings you pass

With Announce airport buildings as you taxi past them switched on, BA tells you when a building comes abeam:

"Passing Concourse B, on the left."

The side is "on the left" or "on the right". BA calls a building at the moment you are closest to it, once you have driven past rather than stopped beside it. It names terminals, concourses, FBOs, the control tower, fuel, cargo areas, fire stations, and hangars that have a real name. It does not say "Passing Hangar" for an anonymous hangar, because that names nothing you could look for.

To keep things calm:

This setting is off by default.

Taxiways you cross

While taxi guidance is running, BA names the taxiways you cross at junctions where your route goes straight on: "Crossing taxiway Link 53." or, for more than one, "Crossing taxiways C, D." This helps you check your progress against the clearance. It is controlled by Announce crossing taxiways (e.g., "Crossing taxiway Link 53"), which is on by default. Turn it off for a quieter taxi. The rest of what taxi guidance says is described in Everything Taxi Guidance Says.

Ground speed

Taxi speed is hard to judge without seeing the ground move. BA can speak your ground speed whenever it reaches a new step:

"15 knots."

Set Announce ground speed every: to Every 5 knots or Every 10 knots. The default is Off. Speeds are rounded to the nearest step, so with 5-knot steps anything from about 13 to 17 knots reads as "15 knots." BA leaves a little margin before it changes the number, so the callout does not flicker when you are right on a boundary.

Ground speed callouts work in every ground phase: taxiing, the takeoff roll and the landing rollout. They work whether or not taxi guidance is running, and they stop in the air. They are queued, so they never cut off an instruction.

During the takeoff roll you may want fewer of them, so that they do not crowd out the takeoff assist callouts. During takeoff assist, announce ground speed every: has these choices:

See Takeoff Assist for the rest of the takeoff callouts.

The Off-the-Pavement Alerts

A blind pilot cannot see the edge of the taxiway. BA has two alerts that tell you when you have left the hard surface.

"Off the pavement, on grass" (optional)

With Tell me when I leave the paved surface switched on, BA watches what the simulator says is under your wheels:

BA only speaks when you have travelled about 12 metres on the new surface, so a wheel clipping the grass at a corner is not announced. It ignores changes between paved surfaces, such as asphalt to concrete, because those do not matter. It stays silent when you are stopped, when you have just been placed somewhere, and after a teleport.

Unlike the other surroundings callouts, this one is still spoken during the takeoff roll and the landing rollout, because running off the side is most dangerous exactly there. It is off by default. We recommend switching it on.

"Off pavement" during the landing roll

During the landing roll and while you follow a landing exit, BA has a second, built-in alert that needs no setting:

"Off pavement."

It means you have left the runway you landed on and every mapped taxiway, for example by running off the side during the rollout or cutting a corner on the exit. You hear it after about one second off the pavement while moving at 5 knots or more, and again every six seconds while you stay off and keep moving. It does not say which way to turn: the steering tone is the only guide to direction, so a spoken "left" could never contradict it. Follow the tone back to the pavement. When both alerts are on, you only hear one of them for each excursion. See The Landing Exit Planner for the rest of the rollout guidance.

Where the Names Come From

Everything above depends on names: taxiway names, stand names and building names. BA combines several sources.

The navigation database

Your navigation database, built from the simulator's own scenery, is the foundation. It provides the taxiway map, the stands, the runways, the fuel information and the frequencies. It has no buildings in it, though, and at some airports many taxiways have no names. See The Navigation Database.

Online names: OpenStreetMap and X-Plane

With Online taxiway, gate and airport building names (OpenStreetMap + X-Plane) switched on, which is the default, BA fetches real-world data from OpenStreetMap and the X-Plane Scenery Gateway:

Online data only ever fills gaps. A name your navigation database already has is never replaced, and online data never moves a taxiway, a stand or a hold line. The steering always follows your simulator's own scenery.

BA fetches this data in the background, before you need it: for the airport you are at when you connect or load a flight, for your destination when you choose it, and for both ends of a SimBrief plan when you load one. It is kept for the whole session, even if you switch navigation databases.

If you switch the setting off, BA uses only the navigation database and your installed scenery, and makes no online requests at all. The change applies immediately.

Refreshing the names. If an airport's names seem incomplete, open the Settings window, go to the Taxi Guidance tab and press Refresh Taxiway Names. BA downloads fresh data for the airport you are at (within about 5 nautical miles) and tells you the result:

The tab also shows the attribution for this data: "Online names: © OpenStreetMap contributors (ODbL) + X-Plane Scenery Gateway."

Your installed scenery (offline)

At add-on airports, BA can also read the scenery package installed on your computer. Named hangars, concourses, cargo buildings and the tower are read straight from the package, so a hangar that OpenStreetMap leaves unnamed can still be called by name. This uses no internet at all.

It is controlled by Read installed scenery for airport buildings (offline), which is on by default. On MSFS 2024 BA looks in both the Community and Community2024 folders. The first time, it does a one-time scan to find which package belongs to which airport.

Under the checkbox there is a read-only Scenery index status box you can Tab to. It says "Scenery index is off.", "No airport scanned yet this session.", or a short report on the last airport read, starting with its code and the number of features found in which package.

Settings for This Chapter

Every setting named in this chapter is on the Taxi Guidance tab of the Settings window and applies immediately. Ground traffic distances have their own unit setting, described in Ground Traffic.

If Something Goes Wrong

Taxi Guidance

Taxi guidance is how MSFS Blind Assist gets you from a stand to a runway, from a runway exit to a stand, or anywhere else on an airport, following the route ATC actually gave you. It is the feature most pilots use on every flight.

How Taxi Guidance Works

Taxi guidance gives you two things at once.

Follow the tone, and listen for the words.

Here is how the pieces fit together on a typical departure:

  1. You open the taxi planner (Input Shift+Y). Its window is titled "Taxi Guidance". You choose where you are going, and enter the taxiways ATC gave you, in order.
  2. You press Calculate Route. BA works out the route over your scenery's real taxiways, adds a stop before every runway the route crosses, and tells you what it has built.
  3. Guidance starts straight away. You release the parking brake, taxi, and follow the tone and the callouts.
  4. At each runway hold line BA tells you to stop. When ATC clears you across or onto the runway, you press Continue (Input Y).
  5. At the departure runway, BA lines you up on the centreline, tells you when you are lined up, and can hand you over to Takeoff Assist automatically.

After landing it works the same way in reverse: you plan a route from the runway exit to your stand, and BA takes you there and hands you to docking guidance at the gate.

Taxi guidance works at any airport your navigation database covers, and every name in its lists is what that airport's scenery calls things.

Before You Start

Taxi guidance needs:

A few things make the experience better.

The Taxi Planner

Open the taxi planner with Input Shift+Y. The window is titled Taxi Guidance, and its controls run in the order a controller reads a clearance: where you are, where you are going, and the taxiways in between. Some controls appear only when they apply (stand filters for a stand, runway options for a runway), so the Tab order changes with the destination type.

Pressing Escape closes the window. Closing the window does not stop guidance; use the Stop Guidance button or Input Ctrl+Y for that. When you open the planner again it still holds what you entered, so amending a clearance mid-taxi is quick.

Here is every control, in Tab order.

Airport (ICAO)

The airport's identifier, filled in for you with the airport you are standing at. Type a different one and Tab away to load another airport. The status line under the Calculate button shows progress while it loads, for example "EGLL: fetching taxiway names…", then "EGLL: building taxi graph…", then a line such as "EGLL: 6085 nodes, 9120 paths." when the airport is ready. If the airport is missing you will see "Airport XXXX not found in database.", and if the scenery has no taxiway data at all, "No taxi data for XXXX."

Destination type

A list with five choices:

Each one is explained in Choosing Your Destination.

Only shown for Gate / Parking. Type a gate letter or number, such as "B12" or just "12", and the destination list shrinks to the stands that match. It also matches the names stands are known by online, so if ATC calls a stand by its real-world name and your scenery spells it differently, typing the real-world name will usually still find it.

Destination

The list of places you can go, which depends on the destination type.

When you pick a runway and BA has online data for that airport's painted holding points, it may also tell you which painted line the normal full-length departure uses, for example "Full length holding point A1." Without that data it names the taxiway the full-length departure enters by, for example "Full length entry via N9." Either helps you check the default matches your clearance before you calculate.

Intersection departure

Runway only. A checkbox. Tick it when ATC clears you to depart from an intersection partway down the runway rather than from the full length. A list appears beneath it, with one entry for each taxiway that meets the runway, such as "B3, 2400 metres remaining, 650 metres from threshold". The first number is how much runway you will have ahead of you; the second is how far that point is from the start of the runway. Choose the one ATC gave you.

If the runway has no usable intersections, you hear "No runway intersections available. Full length departure." and the box unticks itself.

Depart from named holding point

Runway only. A checkbox. Controllers often name the painted holding point you should use, such as "hold short A2", even when the taxiway in your scenery is not called A2. Tick this box to choose the painted line by name. A list appears, with entries such as "A2 (runway hold), 3600 metres remaining, 0 metres from threshold". The word in brackets says what kind of line it is: "(runway hold)" for the normal line, "(ILS hold)" for a line set further back to protect the ILS, and "(intermediate hold)" for a line out on the taxiway system.

BA then routes you through that exact painted line, not just to the runway entrance it shares with its neighbours. These names come from online data, so this needs the online names setting switched on and the airport's data loaded. In Progressive Taxi, where the online data has no name for a line ATC uses, BA can also offer one from the scenery's own signs, marked "(from sign, approximate)": it stops you at the sign's position, which may not be exactly on a painted line. When there is nothing to offer, you hear "No named holding points available for this runway. Full length departure." and the box unticks itself.

CAT III / low-visibility hold (LVP)

Runway only. A checkbox. By default BA holds you at the line closest to the runway, which is what a normal clearance means. When low-visibility procedures are in force, ATC holds you further back at the CAT II/III line, to keep you clear of the ILS critical area. Tick this box when ATC says so, or when you hear "low visibility procedures in force" on the ATIS.

If BA knows the name of that line from online data, choosing a runway with this box ticked tells you, for example "CAT three hold A3.", or "CAT three hold not named in online data. Full length holding point A1." After you calculate, the route summary tells you what it actually found: "Holding at the CAT three ILS hold.", "No CAT three ILS hold found at this holding point. Holding at the full-length line.", or "No CAT three ILS hold found before the runway."

Full-length departure (requires backtrack)

Runway only. A checkbox. Some runways have no taxiway reaching their very end. To use the full length you enter partway down, taxi along the runway to the end (a backtrack, or "backtaxi"), turn around, and line up. Tick this box when you need that. It is off by default, and nothing about backtracking happens unless you tick it. See Backtracking for a full-length departure.

Show fitting only and Hide occupied stands

Gate / Parking and Place only. Two checkboxes that hide stands too small for your aircraft and stands already occupied. Untick them if a stand you need is missing. See Choosing a Stand.

First taxiway

The first taxiway of your clearance. The list starts with (None - calculate shortest path), then every taxiway at the airport, nearest first.

Warning: When the planner loads, BA preselects the nearest taxiway in the direction you are facing, as a guess. Always check this box and set it to the first taxiway ATC actually said. If ATC gave you no taxiways, or you just want BA to find the way, choose (None - calculate shortest path).

Hold short (after the first taxiway)

A checkbox beside the first taxiway. Tick it to make guidance stop at the end of this taxiway, where it meets the next one, and wait for you to press Continue. Use it for an instruction such as "hold short of taxiway C". The stop is announced as "Stop. Hold short of end of taxiway A. Press continue when cleared."

Hold short of runway (after the first taxiway)

A list beside the first taxiway, starting with (none), then every runway at the airport. Use it when ATC explicitly tells you to hold short of a runway after this taxiway: "via A, hold short of runway 22R". BA already stops you before every runway your route crosses, so this is optional, but it makes sure the stop is exactly the one ATC named, labelled the way you selected it. Leave it at (none) to rely on BA's automatic runway holds.

After the runways the same list holds every taxiway and every named holding point at the airport, together in name order. A taxiway is listed by its name alone, and a holding point has "(holding point)" after its name: "L", "L1 (holding point)", "L2 (holding point)", "M". Press the first letter of a name to jump to it.

If your route never reaches the taxiway or holding point you chose, the route still loads and the summary ends with a note such as "Note: requested hold-short(s) not on route — holding point L2 (route does not pass it after taxiway L)."

Two more notes tell you a holding point you chose gets no stop of its own:

When the holding point you chose is your runway's own hold line, the countdown names both: "Hold short Runway 16 at holding point A1 in 100 metres."

Add Taxiway

A button that adds another taxiway row below the first. It only works once the first taxiway is set to a real taxiway. You can add up to 20 more rows. Each new row is labelled "Taxiway 2", "Taxiway 3" and so on, and has its own taxiway list, Hold short checkbox, Remove button and Hold short of runway list, exactly like the first row.

In each new row's taxiway list, the taxiways that connect to the previous one come first, nearest first, followed by every other taxiway at the airport in alphabetical order. The list also starts with (None - end here). The taxiway in the row just above is left out, because choosing the same taxiway twice in a row usually means a slip of the finger. The exception is when the row above holds short, which is how clearances such as "N, hold short of runway 15R, N" are entered (see Worked examples).

The Remove button deletes that row and every row after it.

Progressive Taxi controls

Only shown for Progressive Taxi. Below your last taxiway row you get a Terminator list, saying how this leg ends, and one or two more lists for the target. They are explained in Progressive Taxi.

Fill from SayIntentions

A button that fills the whole planner from your latest SayIntentions taxi clearance. It does the same as Input Ctrl+Shift+Y. See SayIntentions taxi import.

Calculate Route

Builds the route and starts guidance immediately. See Calculating the Route.

Stop Guidance

Stops taxi guidance. The status line says "Guidance stopped."

Last route summary

A read-only text box at the end of the window holding the summary of your last route, or the reason the last calculation failed. Arrow through it with your screen reader whenever you want to hear the route again. It is the most reliable way to read the full summary, because the first guidance instruction often begins before BA has finished speaking it.

Keyboard shortcuts in the planner

The planner has Alt shortcuts that jump straight to a control.

Shortcut Goes to
Alt+A Airport (ICAO)
Alt+T Destination type
Alt+G Gate search
Alt+E Destination
Alt+I Intersection departure
Alt+P Depart from named holding point
Alt+L CAT III / low-visibility hold
Alt+B Full-length departure (requires backtrack)
Alt+F First taxiway (also Show fitting only)
Alt+H Hold short checkboxes
Alt+O Hold short of runway lists (also Hide occupied stands)
Alt+D Add Taxiway
Alt+2 to Alt+9 Taxiway 2 to Taxiway 9
Alt+R Remove buttons
Alt+N Progressive Taxi terminator
Alt+U Progressive Taxi runway target
Alt+W Progressive Taxi taxiway or holding point target
Alt+Y Fill from SayIntentions
Alt+C Calculate Route
Alt+S Stop Guidance (also Last route summary)

Where a letter is shared, as with Alt+F, Alt+O, Alt+H, Alt+R and Alt+S, pressing it again moves on to the next control with that letter, and Windows may move to a button rather than press it. When in doubt, Tab to the button and press Space or Enter.

Choosing Your Destination

Gate or stand

Choose Gate / Parking, then the stand. Use the Gate search box to narrow the list. When you calculate, BA routes you to the stand, lines you up with it, and, if docking guidance is switched on, hands you to docking for the final metres. See Arriving at a Stand and Docking Guidance.

If another aircraft is parked on the stand when you calculate, BA warns you, for example "Warning: BAW123 is at the destination gate.", or "Warning: an aircraft is at the destination gate." if it has no callsign.

With GSX, calculating the route can also prepare the stand in GSX; see Letting BA Prepare Your Stand in GSX.

Runway, full length

Choose Runway, then the runway, leave the runway checkboxes unticked, and enter your taxiways. BA takes you to the hold line before the full-length entrance, stops you there, and after you press Continue lines you up at the start of the runway. This is the normal departure.

BA works out the full-length start point from the airport's data, and makes sure the route ends at a real runway entrance. It never silently swaps in an entrance further down the runway, so you can never be handed less runway than you asked for. If no taxiway reaches that point, BA warns you instead of guessing.

Runway, intersection or named holding point

Tick Intersection departure or Depart from named holding point and choose the entry (see the planner controls above). BA routes you there, holds you short, and confirms after you calculate, for example "Intersection B3 departure, runway 27L. About 2400 metres of runway ahead." or "Holding point A2, runway 28. About 3600 metres of runway ahead." A holding point partway down the runway is treated like an intersection departure; at a full-length holding point the lineup is still at the full length, and the choice just decides which entrance you use.

Any runway destination can also have the CAT III / low-visibility hold (LVP) box ticked, which only changes where you stop before the runway.

Runway, full length with a backtrack

Choose the runway and tick Full-length departure (requires backtrack). BA finds the entrance nearest the departure end, routes you there and holds you short with "Stop. Hold short of Runway 32. Press continue when cleared to enter and backtrack." When ATC clears you onto the runway, press Continue. You hear "Entering Runway 32. Backtrack to full length, heading 140, then turn around to heading 320."

The tone now steers you down the runway centreline towards the far end. As you approach it you hear "Approaching runway end. Slow down, prepare to turn around to heading 320.", then "Runway end. Turn around to line up, heading 320." The tone stays on through the whole turnaround. It pans hard to whichever side you are turning and settles down as you straighten, so silence always means you are lined up, never that BA has given up. You then hear the normal "Lined up, Runway 32. Hold position."

If BA cannot find a suitable entrance, it says "No backtrack entrance found for this runway. Full length departure." and plans a normal full-length departure.

Progressive Taxi

Choose Progressive Taxi when ATC gives you part of a route at a time. See Progressive Taxi.

Deice Area

Choose Deice Area to taxi to a remote de-icing pad. The pads come from GSX airport profiles, so this list is empty at airports with no GSX de-icing data, and you hear "No deicing areas at this airport."

Place

Choose Place to taxi to a building or facility by name: an FBO after landing, a hangar, a fuel island, a terminal or a cargo area. BA takes you to the stand in front of it, with docking included where the scenery gives a stop. The list depends on what BA knows about the airport, from its database, from online map data and from your installed scenery. While it is being built you may hear "Loading places for KXYZ." If nothing can be routed to, you hear "No places to route to at KXYZ.", and if the data could not be read, "Places could not be loaded for KXYZ." The places themselves are described more in The Surroundings Window.

Entering an ATC Clearance

This is the heart of taxi guidance. The rule is simple: enter the taxiways in the order ATC said them, and put each hold short on the row of the taxiway it comes after.

BA follows your clearance in order. It does not take a shortcut down some other taxiway just because it is shorter. If you enter A, B, K, the route really does go along A, then B, then K, and then on to your destination.

The basic method
  1. Open the planner with Input Shift+Y.
  2. Check the airport.
  3. Choose the destination type and the destination: the runway or stand ATC gave you.
  4. Tick any runway option ATC gave you: intersection, named holding point, low visibility, or backtrack.
  5. Set First taxiway to the first taxiway ATC said.
  6. If ATC said to hold short of something after that taxiway, tick Hold short (for a taxiway) or choose the runway in Hold short of runway.
  7. Press Add Taxiway and choose the next taxiway. Repeat until you have entered them all.
  8. Press Calculate Route, then listen to the summary, or read it in the Last route summary box, and check it matches what ATC said.

You do not need to enter runway crossings as taxiways, and you do not need to tell BA to stop before them. BA stops you before every runway your route crosses or enters, automatically, whether or not ATC mentioned it.

Tip: You do not have to enter the little unnamed links between stands and taxiways. Leave them out, just as a controller does. BA finds its own way from your stand onto the first taxiway you entered. When that first taxiway is some distance away, the summary tells you how you will reach it, for example "First taxi onto A." or "First taxi via L1 to reach A."

Taxiway names you can't find

The lists only contain taxiways that exist in your scenery's data. If ATC names a taxiway you cannot find:

Worked Examples

The airports in these examples are made up, but the phraseology is real.

Example 1: a standard departure with a runway hold short

ATC: "Speedbird 123, taxi to holding point runway 27L via A, B, hold short of runway 22R."

  1. Destination type: Runway. Destination: Runway 27L.
  2. First taxiway: A.
  3. Add Taxiway, then Taxiway 2: B. On the Taxiway 2 row, set Hold short of runway to 22R, because the hold short comes after B.
  4. Calculate Route.

You will hear a summary along the lines of "Route to Runway 27L via A, B. 1450 metres, crossing runway 22R." As you near the 22R hold line on B, BA counts you down (see Hold Shorts and Continue) and stops you with "Stop. Hold short of runway 22R. Press continue when cleared." When ATC says "cross runway 22R", press Input Y. You hear "Continuing. Taxiway B." and carry on to the 27L hold.

Example 2: a clearance that includes a crossing

ATC: "Taxi to holding point runway 27L via A, cross runway 22R, B."

Enter it exactly as in Example 1, but with no hold short on the B row: First taxiway A, Taxiway 2 B. Do not try to enter "cross runway 22R" anywhere.

You will still be stopped at the 22R hold line, because BA cannot hear ATC and rolling across an active runway unannounced is the most dangerous mistake on an airport. Check the clearance (and the Ground Traffic callouts or Output Alt+G if you are unsure about traffic), then press Input Y to cross.

Example 3: a taxiway used twice, "A, C, A"

ATC: "Taxi to runway 09 via A, C, A." This happens where the controller wants you off A for a short stretch, round a parked aircraft or a closed section, and then back onto it.

  1. Destination: Runway 09.
  2. First taxiway: A.
  3. Add Taxiway, Taxiway 2: C.
  4. Add Taxiway, Taxiway 3: A. It is in the list, because only the taxiway immediately above, C, is left out.
  5. Calculate Route.

Check the summary: it should say "via A, C, A". If the second A turns out to be very short, that is just the geometry of the airport.

Example 4: the same taxiway on both sides of a runway

ATC: "Taxi to runway 22R via N, hold short of runway 15R." Then later, "Cross runway 15R, continue on N, hold short of runway 22L."

When you know the whole clearance, enter it in one go:

  1. First taxiway N, and on that row set Hold short of runway to 15R.
  2. Add Taxiway. Because the row above holds short, N is offered again. Choose N, and set its Hold short of runway to 22L.
  3. Add Taxiway, choose N again.

Each runway gets its own stop, and Continue at each one clears just that runway.

Example 5: an intersection departure

ATC: "Taxi via A, B3, line up runway 27L at B3."

  1. Destination: Runway 27L. Tick Intersection departure and choose B3 in the list that appears.
  2. First taxiway A, Taxiway 2 B3.
  3. Calculate Route. You hear "Intersection B3 departure, runway 27L. About 2400 metres of runway ahead."

If you only need a different painted line at the full-length end ("hold short A2"), use Depart from named holding point instead.

Example 6: a low-visibility departure

ATIS: "Low visibility procedures in force." ATC: "Taxi to CAT 3 holding point runway 27L via A, B."

Enter the route as in Example 1, and also tick CAT III / low-visibility hold (LVP). The summary tells you whether a CAT III line was found.

Example 7: a gate after landing

ATC, after you vacate: "Speedbird 123, taxi to stand B12 via K, L."

  1. Stop clear of the runway. If you were using the Landing Exit Planner, it has already told you where you are; see The Landing Exit Planner.
  2. Open the planner with Input Shift+Y. The airport is filled in.
  3. Destination type: Gate / Parking. In Gate search, type B12, then choose the stand in Destination.
  4. First taxiway K, Taxiway 2 L.
  5. Calculate Route. BA routes you from where you are actually stopped, and at the stand hands you to docking guidance.

If your route crosses a runway on the way in, you will be stopped before it, exactly as on departure.

Example 8: no taxiways given

ATC: "Taxi to stand 40." or you are flying offline and just want to get to the runway.

Set First taxiway to (None - calculate shortest path) and calculate. BA finds the shortest route over the taxiways, still stopping you before every runway.

Changing a Clearance on the Move

ATC often amends a clearance while you are taxiing. Open the planner again with Input Shift+Y, change the taxiways (Remove deletes a row and everything after it), and press Calculate Route. The new route starts from where you are right now, not from where you were when you first opened the window.

SayIntentions Taxi Import

If you fly with SayIntentions, BA can fill in the planner from the taxi clearance SayIntentions gave you. Press Input Ctrl+Shift+Y, or the Fill from SayIntentions button in the planner. BA fills in the destination, the taxiways and any runway hold shorts, and names anything it could not apply, so you can check it against what you heard.

By default the import only fills the form, and you press Calculate Route yourself after checking it. If you would rather it started guidance straight away, tick SayIntentions import starts taxi guidance immediately in the SayIntentions section of the Taxi Guidance settings tab. After landing, when SayIntentions has assigned you an arrival gate, the import always routes you to a gate, never back to a runway.

The details, including how BA reads the clearance and SayIntentions' own ground track, are in SayIntentions.

Progressive Taxi

Some controllers give a clearance one piece at a time: "taxi via A, B, hold short of runway 09", then later "cross runway 09, taxi via C, hold short of taxiway D". Progressive Taxi lets you follow each piece without pretending to know where you will end up.

  1. Choose Progressive Taxi as the destination type. The Destination list disappears, and the Hold short of runway lists on each row are hidden, because the end of the leg is set separately.
  2. Enter the taxiways for this leg as usual. You need at least one, unless the leg ends at a named holding point or after crossing a runway; otherwise you hear "Select at least one taxiway for progressive taxi."
  3. Below your last taxiway row, choose how the leg ends in the Terminator list:
    • Hold short of runway: then choose the runway in Runway to hold short of. Guidance ends at that runway's hold line on your last taxiway.
    • Hold short of taxiway or named holding point: then choose the target in Hold short of taxiway or holding point. The list holds every taxiway at the airport with the named holding points among them, each marked "(holding point)", for example "L2 (holding point)". For a taxiway, guidance ends where your last taxiway meets it. For a holding point, such as "hold short of L2" or "hold at VIKAS", guidance ends at that point, and you do not need to enter a taxiway first. The holding points come from online data.
    • After crossing runway: then choose the runway in Runway to cross, and optionally the taxiway to cross at in Cross at taxiway (optional). Leave that at (none) to cross at the nearest point. Use this when ATC has already cleared you across: BA does not stop you before that runway, and the leg ends just past it.
    • End of last taxiway: guidance ends at the end of your last taxiway.
  4. Press Calculate Route.

When you reach the end of the leg, the tone stops and you hear one of:

When ATC gives you the next piece, open the planner, enter the next leg, and calculate again. Pressing Continue does nothing at the end of a Progressive leg, because there is no further route to continue along.

Other runways on a Progressive leg are still protected. If the leg crosses any runway other than one you chose under After crossing runway, BA still stops you before it.

If BA cannot find the end point you chose, you hear something like "Could not find taxiway D from C. Check your entry.", and for a named holding point you cannot reach, "Cannot taxi to VIKAS from your position. Check your entry."

Calculating the Route

When you press Calculate Route, BA:

  1. Takes your aircraft's current position.
  2. Builds a route that follows your taxiways in order.
  3. Adds a stop before every runway the route crosses or enters, placed at the scenery's painted hold line where it has one, and never on a runway.
  4. Speaks a summary and writes it into the Last route summary box.
  5. Starts guidance.
Reading the route summary

A summary has the form "Route to (destination) via (taxiways). (distance), (runways and holds)." For example:

What each part means:

Warnings in the summary, and what to do

Most routes produce a clean summary. When something is not right, a warning is added. These are the ones you may meet.

"... with no hold short point for runway 06L" (added to the runway list). The route crosses or enters that runway, but there is nowhere safe to stop before it. BA will not stop you there. You must judge that runway yourself: slow down, check with ATC, and listen for traffic. Every other runway named without this warning will get a proper stop. Because guidance starts talking straight away and can cut the summary short, BA also says it again once you are stopped and guidance has started, "Warning: no hold short point for runway 06L.", so you hear it whatever happens to the summary. A stop you have already rolled past is never reported missing.

"Warning: this route does not reach Runway 27L. Check your taxiway entry and reprogram." You hear this short form; the box holds a longer explanation, such as "Warning: this route ends about 450 metres to the side of Runway 27L and does not reach the runway. You may be missing the taxiway that connects to the runway." or "Warning: this route stops short of Runway 27L ... The last taxiway you entered does not connect to it." Usually the clearance's last taxiway runs beside the runway, and you have left out the short link taxiway onto it. Add it and calculate again. If you carry on anyway and BA is still far from the centreline during lineup, it repeats: "This route does not reach Runway 27L. Reprogram the taxi route, including the taxiway that connects to the runway."

"Warning: could not follow specified taxiways. Using shortest path. Reason: ..." BA could not make a route out of the taxiways you entered, for example because two of them never meet, and has used the shortest route instead. The reason is technical, such as "Step 2: No intersection between 'B' and 'Z'", but it tells you which pair failed. Check you picked the right taxiways, in the right order.

"Warning: route via A, B is 3.2 kilometres; direct route is 900 metres. Check taxiway selection." The route follows your clearance but is far longer than the direct route, which often means a taxiway was picked by mistake, or was in the wrong order. Sometimes it adds "Taxiway A is 600 metres from your position.", meaning your first taxiway is a long way from where you are. If the clearance really is that long, ignore the warning.

"Note: requested hold-short(s) could not be set — runway 22R (route does not cross it after taxiway B)." You asked for a runway hold short that the route never reaches after that taxiway. Check you put the hold short on the right row. If it says "(no safe place to hold short after taxiway B)", the route does meet that runway, but there is nowhere safe to stop before it.

"Could not compute a path onto taxiway A along the apron; route starts on A." BA could not find its own way from your stand to the first taxiway, so the route begins on that taxiway. Taxi onto it carefully; the tone will guide you to it.

"Your position isn't connected to the taxiway network. The first 40 metres to taxiway A aren't mapped." Your stand, or the spot you are on, is not joined to the taxiways in the airport's data. BA will steer you straight across that unmapped stretch towards the start of the route, so check it is clear. A similar warning, "Gate X isn't connected to the taxiway network you're on. The first N of the route aren't mapped.", means the destination is the part that is cut off.

When a route cannot be built at all

If Calculate fails, BA tells you why and puts the same reason in the summary box. Any route you were already following carries on unchanged. Common reasons:

Starting Guidance

Guidance starts as soon as the route is calculated. You do not need to press anything else. The status line says "Route loaded. Guidance active."

The first thing you hear is one of:

Straight after that, BA may add:

When a warning is spoken at the start, BA holds back its other early callouts for about twelve seconds so they do not talk over it. The tone works throughout.

Now release the parking brake and start rolling. If you are already moving onto your first taxiway, you will hear "Taxiway A." when you join it.

The Steering Tone

The steering tone follows the rules in The Audio Language: What the Tones Mean: a fixed pitch, panned to the side you should steer toward, further to the side for a bigger correction (fully to one side at about 30 degrees off course), and silent once you are pointing within a few degrees of where you should be. Steer until it goes quiet; you do not need to centre it exactly. For steering away from the tone, or a hard-panned tone on speakers, see Taxi Guidance Settings.

Turns

The tone looks ahead along the route, so as you approach a turn it starts drifting towards the new direction before you reach the junction, just as a pilot looking out of the window would start the turn a little early. Follow it into the turn.

During a turn, the tone allows for the way the aircraft keeps swinging after you ease off the tiller. It goes quiet slightly before your nose reaches the new heading. That is deliberate: when it goes quiet mid-turn, hold that rate of turn and start unwinding, and you will roll out on the line. If it swings to the other side, you are turning too far; unwind.

How early it goes quiet depends on how fast you are turning: the faster the turn, the earlier. In the Fenix A320 family it also depends on how far you have already turned. A big turn, such as a 90-degree corner, goes quiet a little earlier than a small one, because the Fenix carries more swing out of a big turn. Unwind when you hear it go quiet.

After a long turn, once the route ahead is straight, you may hear "Straighten." That is your cue to roll out now.

On the runway: lineup precision

When you are lining up on a runway, or at a stand, the tone becomes much more precise.

Pulsing tone. If you stop, or nearly stop (3 knots or less), on the runway while still not lined up, either because you are pointing the wrong way or because you are well off the centreline, the tone pulses on and off three times a second instead of playing steadily. It means "you're stopped and not lined up yet". Follow its direction and roll forward gently; the pulse stops as soon as you are moving.

When the tone stops

The tone pauses at every hold short (silence there means "stay put", not "on track"), once you are lined up, and when you arrive. It resumes when you press Continue.

Tip: The tone volume is quiet by default (5 percent), so ATC is easy to hear over it. Adjust it on the Taxi Guidance settings tab, using Test Tone to try it.

Following the Guidance

Here is what happens along the way, and what you do.

Turns

For each turn, you normally get two callouts:

  1. Advance notice, typically 10 seconds ahead at your current speed: "In 100 metres, turn left onto taxiway B.", "In 80 metres, slight right onto taxiway C.", or for a turn of 60 degrees or more, "In 150 metres, sharp right onto taxiway D, 90 degrees." Where the taxiway name changes but the route goes straight on, you hear "In 100 metres, continue onto taxiway E."
  2. Turn now, a few seconds before the turn: "Left now, taxiway B.", "Slight right now, taxiway C." or "Sharp right now, taxiway D."

"Slight" means a turn of between about 20 and 60 degrees. The direction word is worked out from the way you are actually pointing at the time, so it always agrees with the tone, even if you have drifted off line.

When you join the new taxiway you hear its name: "Taxiway B."

Curves

Some taxiways bend gradually rather than turning at a junction. When the next 100 metres or so curve by 30 degrees or more, you hear "Curving left." or "Curving right." Follow the tone round the bend.

Crossing taxiways

When you go straight across another taxiway, you hear "Crossing taxiway K.", or "Crossing taxiways K, L." for more than one. These help you keep track of where you are, and match the taxiway names a controller may use ("give way to traffic on K"). You can switch them off on the Taxi Guidance settings tab.

Speed reminders

BA reminds you if you are going too fast:

These repeat at most every eight seconds. If you would like to hear your speed regularly, turn on Announce ground speed every on the Taxi Guidance settings tab.

Checking where you are

At any time:

Other traffic

Taxi guidance steers you along your route, but it is not what watches for other aircraft. That is the ground traffic monitor, which calls out traffic ahead, on your route and on the runway as you hold. See Ground Traffic.

Hold Shorts and Continue

A hold short is a point where guidance stops you and waits for you to say you have been cleared. BA places one:

The countdown

As you approach a hold short, BA counts you down in three steps, starting earlier the faster you are going:

  1. "Hold short runway 22R in 120 metres."
  2. "Hold short runway 22R in 60 metres. Slow down."
  3. "Hold short runway 22R in 30 metres. Stop."

If you come to a stop before the last step, you hear "Hold short runway 22R. Stop." The runway name may include the taxiway the line is on, such as "runway 15R at N". A taxiway hold reads "Hold short end of taxiway A in 60 metres."

At the line

When you reach the line, the tone stops and you hear "Stop. Hold short of runway 22R. Press continue when cleared." Bring the aircraft to a stop and set the parking brake if you are waiting. Output Y reminds you: "Holding short of runway 22R. Press continue when cleared."

Continue

When ATC clears you across or onto the runway, press Input Y (left bracket, then Y). You hear "Continuing. Taxiway B.", the tone comes back, and you carry on.

If the route started behind you and you have been holding at its start, the continue callout includes the turn you need, for example "Continuing. Sharp turn left onto taxiway K."

Warning: Only press Continue when you have actually been cleared. BA cannot hear ATC. If you are flying offline, treat every runway hold as a moment to stop, listen for traffic, and check the runway is free before you cross.

One stop that guards two runways

Sometimes two runways are so close together that there is nowhere to stop between them, so one hold line guards both. BA names both and clears them one at a time, the way a controller would:

  1. At the line: "Stop. Hold short of runway 09 and runway 01. Press continue when cleared for runway 09."
  2. When cleared for 09, press Continue. You hear "Runway 09 cleared. Still holding. Press continue when cleared for runway 01." Stay where you are.
  3. When cleared for 01, press Continue again, and you move off.
Two runways close together

Where two parallel runways sit close together, ATC often clears you across both at once ("cross runways 28L and 28R at F"), but your route still has a stop before each. When you press Continue at the first and BA sees the second stop a short way ahead, it offers to clear both:

  1. Press Continue at the first hold line. You hear something like "Continuing. Taxiway F. Next hold short of runway 28R at F in 120 metres. Press continue again if cleared across both."
  2. If ATC cleared you across both, press Continue again once you have heard that. You hear "Also cleared across runway 28R at F. No stop between the runways.", and BA does not stop you between them.
  3. If you were cleared across the first runway only, do nothing. BA stops you at the second hold line as normal.

A second press only counts once the offer has been spoken, about two seconds after the first, so a key that bounces or a quick double tap never clears the second runway by mistake. The offer stands for about twelve seconds.

At the departure runway

At the hold for your departure runway you hear "Stop. Hold short of Runway 27L. Press continue when cleared." Continue here means "cleared to line up" (or cleared for takeoff). See Lining Up on the Runway.

Runway Crossings

Every runway your route crosses or enters gets a stop, as described above, including your own departure runway if you cross it on the way to its threshold. A recalculated route gets its runway stops too, and a stop you have already rolled past is dropped, so you are never told to stop on a runway you were cleared across.

Reminders and warnings near hold lines

BA watches for runway hold lines as you move, whether or not they are on your route.

Lining Up on the Runway

At the departure runway, guidance takes you from the hold line onto the centreline.

  1. At the hold: "Stop. Hold short of Runway 27L. Press continue when cleared." As you approach the runway you may also hear "Runway 27L ahead."
  2. When ATC says "line up and wait" or "cleared for takeoff", press Input Y. You hear "Entering Runway 27L, heading 268.", with "Turn right." or "Turn left." added if you are more than ten degrees off the runway heading. Where the hold line is set back from the runway and the taxiway runs on before meeting it, you hear "Continue onto the runway, then turn left." instead: the tone first follows the taxiway onto the runway, and only then turns you onto the centreline, so you never cut across the grass. If the stop before your runway also guards a runway you cross on the way in, both are named at the hold line, for example "Hold short of Runway 32 and runway 35."
  3. Follow the precise lineup tone onto the centreline (see On the runway: lineup precision). Roll forward gently while you turn; if you stop before you are lined up, the tone pulses.
  4. When you are within one degree of the runway heading and within about 10 feet (3 metres) of the centreline, the tone stops and you hear "Lined up, Runway 27L. Hold position." This is the same position the runway teleport puts you in.

While lining up, Output Y says "Lining up Runway 27L, runway heading 268. Follow the tone. 40 metres to go.", and once lined up, "Lined up Runway 27L, heading 268. Aligned — hold position."

If you drift out of alignment again before taking off, the tone comes back.

If guidance is replaced by something else while you are lining up, you hear "Lineup interrupted. No longer aligning with the runway."

Handing over to Takeoff Assist

When you line up, BA can switch on Takeoff Assist for you. You hear "Lined up. Activating takeoff assist.", taxi guidance ends, and the takeoff roll tone takes over. This is controlled by Auto-activate Takeoff Assist on lineup on the Hand Fly tab in Settings, which is on by default. It fires once per route: if you switch Takeoff Assist off afterwards, it will not switch itself back on until your next route. You can always switch Takeoff Assist on or off yourself with Output Ctrl+T. See Takeoff Assist.

Going Off Route and Recalculation

If you leave your route, for example by missing a turn or taking the wrong taxiway, BA notices and plans a new route from where you are.

When BA decides you are off route

You count as off route when you are clearly away from the taxiway you should be on for a few seconds while moving. To avoid false alarms, BA does not judge this until you have joined the route at least once (so the taxi from your stand onto the first taxiway never counts), nor during and just after a turn.

"Route changed"

When BA builds a new route, you hear "Route changed. Now via C, D, crossing runway 26R. 900 metres to Runway 27L." It names the taxiways of the new route and every runway it crosses, so you are never surprised by a hold short. BA keeps as much of your original clearance as still applies, starting from the latest cleared taxiway you are on. The new route gets stops before every runway, just like the original.

If the new route would be exactly the same as the rest of your old one, for example after cutting a corner wide, BA says nothing and simply carries on.

When BA cannot recalculate

Arriving at a Stand

As you near your stand, BA counts you down: "Gate B 12 - Gate Heavy (Jetway) in 15 metres.", "10 metres.", "5 metres. Stop." (in feet: 50, 20 and 10). If you stop early, you hear "Stop. Hold position."

Then BA turns you to face the stand: "Align with Gate B 12 - Gate Heavy (Jetway), heading 270.", with "Turn left." or "Turn right." if needed. The precise lineup tone guides you round. When you are lined up, you hear "Aligned with Gate B 12 - Gate Heavy (Jetway). Parking brake."

In these callouts BA uses the stand's full name exactly as it appears in the destination list, which is why it can be long. The examples below shorten it to "Gate B 12".

With docking guidance

If Docking guidance (auto-engage at the gate) is switched on in Settings and the stand has a known stop position, taxi guidance hands over to docking guidance for the last part, which takes you precisely to the stop mark with its own tone, beeps and distances. In that case the callouts change to tell you to keep going:

While docking is in charge, Output Y reports docking's own distance to the stop. See Docking Guidance.

Where a route ends somewhere with no stand heading, such as the end of a taxiway, you simply hear "(destination) reached."

After landing

If you used the Landing Exit Planner, exit guidance ends once you have left the runway, with a message such as "Off the runway at B4. Stop and hold position. Open the taxi planner to set a route to your gate." That is your cue to open the planner (Input Shift+Y) and enter your taxi-in clearance, as in Example 7. After backtracking off a runway you hear "Runway vacated. No route set — use the taxi planner for a route to your stand." See The Landing Exit Planner for everything that happens between touchdown and that point.

Taxi Routes in the Route Briefing

The AI route briefing also previews your expected taxi out and taxi in. It is a briefing, not live guidance; see The AI Route Briefing.

Hotkeys During Taxi

These keys are the same on every aircraft. For how Output and Input modes work, see Output Mode and Input Mode.

Key What it does
Input Shift+Y Open the taxi planner
Input Y Continue past the current hold short
Input Ctrl+Y Stop taxi guidance (you hear "Taxi guidance stopped.")
Input Ctrl+Shift+Y Build a taxi route from your latest SayIntentions clearance
Input Shift+X Open the Landing Exit Planner
Output Y Taxi status: taxiway, next turn, distance to go
Output Ctrl+Y Repeat the last taxi instruction
Output Alt+Y Where Am I: your taxiway, stand or runway
Output Alt+L Look Around: what is near you
Output Ctrl+Shift+L The Surroundings window
Output Alt+G Nearest ground traffic
Output Ctrl+T Switch Takeoff Assist on or off

Taxi Guidance Settings

Open Settings from the File menu and choose the Taxi Guidance tab.

Two related settings live elsewhere:

Everything Taxi Guidance Says

This is a reference list of every taxi guidance callout, grouped by when you hear it. Names, numbers and distances are examples. Where a stand is named, BA uses its full name from the destination list; it is shortened to "Gate B 12" here.

When you plan and start a route
You hear What it means What to do
"Full length holding point A1." The painted line a normal departure from this runway uses (heard when you choose a runway). Check it matches your clearance; if not, use Depart from named holding point.
"CAT three hold A3." With the LVP box ticked, the low-visibility line for this runway. Nothing; for information.
"No runway intersections available. Full length departure." The runway has no intersections to offer. Plan a full-length departure, or check the runway.
"No named holding points available for this runway. Full length departure." No online holding-point names for this runway. Use the normal full length, or an intersection.
"No deicing areas at this airport." No GSX de-icing pads here. Choose another destination type.
"Route to Runway 27L via A, B. 1450 metres, crossing runway 22R." The route summary. Check it matches your clearance.
"Warning: this route does not reach Runway 27L. Check your taxiway entry and reprogram." The route ends away from the runway. Add the missing link taxiway and recalculate.
"Warning: BAW123 is at the destination gate." Your stand is occupied. Check with ATC; choose another stand if needed.
"Intersection B3 departure, runway 27L. About 2400 metres of runway ahead." Confirms your intersection. Check the runway length is enough.
"Holding point A2, runway 28. About 3600 metres of runway ahead." Confirms your named holding point. Nothing.
"No backtrack entrance found for this runway. Full length departure." No entrance suited to a backtrack. Plan a normal departure.
"Taxiway A. Steering guidance active." Guidance has started; you are on A. Start taxiing.
"Steering guidance active. Join taxiway A in 60 metres." Guidance has started; A is ahead. Taxi onto A, following the tone.
"Taxiway A is behind you. Turn left to come around." The route starts behind you. Turn round in the direction given.
"Make a U-turn to the right." The same, with no taxiway name. Turn round to the right.
"Sharp turn left onto taxiway K." or "Sharp turn left." The route starts at a sharp angle. Make the turn.
"Your position isn't connected to the taxiway network. The first 40 metres to taxiway A aren't mapped." You start off the mapped taxiways. Taxi carefully onto the route, checking it is clear.
While taxiing
You hear What it means What to do
"Taxiway B." You have joined taxiway B. Nothing; for information.
"In 100 metres, turn left onto taxiway B." A turn is coming. Get ready, slow if needed.
"In 80 metres, slight right onto taxiway C." A gentle turn (20 to 60 degrees) is coming. Get ready.
"In 150 metres, sharp right onto taxiway D, 90 degrees." A big turn, with its angle. Slow well before it.
"In 100 metres, continue onto taxiway E." The name changes but you go straight. Carry straight on.
"Left now, taxiway B." Start the turn now. Turn, following the tone.
"Curving left." The taxiway bends gradually. Follow the tone round.
"Straighten." You have turned enough; the route is straight ahead. Roll out of the turn.
"Crossing taxiway K." You are going straight across K. Nothing; for information.
"Slow for turn." / "Slow for sharp turn." Too fast for the coming turn. Slow down.
"Taxi speed, 32 knots." Faster than 30 knots. Slow down.
"Runway 27L ahead." Your destination is close. Get ready to stop.
"Crossing runway 22R at B." A runway crossing on your route is just ahead. Make sure you are cleared.
"Warning: approaching runway 36L at M8, off route." You are heading for a runway that is not on your route. Stop, check your position.
At hold shorts
You hear What it means What to do
"Hold short runway 22R in 120 metres." A runway hold is coming. Prepare to stop.
"Hold short runway 22R in 60 metres. Slow down." It is close. Slow down.
"Hold short runway 22R in 30 metres. Stop." / "Hold short runway 22R. Stop." Stop now. Stop.
"Stop. Hold short of runway 22R. Press continue when cleared." You are at the line; the tone is paused. Wait for clearance, then Input Y.
"Stop. Hold short of end of taxiway A. Press continue when cleared." A taxiway hold you asked for. Wait for clearance, then Input Y.
"Stop. Hold short of runway 09 and runway 01. Press continue when cleared for runway 09." One stop guards two runways. Input Y when cleared for 09.
"Runway 09 cleared. Still holding. Press continue when cleared for runway 01." First runway cleared; still waiting. Stay put; Input Y when cleared for 01.
"Continuing. Taxiway B." You pressed Continue; guidance resumes. Taxi on.
Lining up and departing
You hear What it means What to do
"Stop. Hold short of Runway 27L. Press continue when cleared." At your departure runway hold. Input Y when cleared to line up.
"Entering Runway 27L, heading 268. Turn right." You are cleared on; turn onto the runway. Follow the lineup tone.
"Lined up, Runway 27L. Hold position." You are on the centreline, aligned. Wait for takeoff clearance.
"Lined up. Activating takeoff assist." Takeoff Assist is taking over. Prepare for takeoff.
"Lineup interrupted. No longer aligning with the runway." Lineup guidance was stopped by a new route. Check what you intended.
"This route does not reach Runway 27L. Reprogram the taxi route, including the taxiway that connects to the runway." You are far from the runway centreline during lineup. Stop and plan a new route.
"Stop. Hold short of Runway 32. Press continue when cleared to enter and backtrack." Backtrack departure hold. Input Y when cleared to backtrack.
"Entering Runway 32. Backtrack to full length, heading 140, then turn around to heading 320." Taxi down the runway to its end. Follow the tone.
"Approaching runway end. Slow down, prepare to turn around to heading 320." The turnaround is close. Slow down.
"Runway end. Turn around to line up, heading 320." Turn around now. Follow the tone through the turn.
Progressive Taxi
You hear What it means What to do
"Hold short of runway 09. Set a new route when cleared." End of the leg. Plan the next leg when ATC gives it.
"Hold short of taxiway D. Set a new route when cleared." End of the leg. Plan the next leg.
"Across runway 09. Hold position. Set a new route when cleared." You are across the runway you were cleared over. Plan the next leg.
"Hold at VIKAS. Set a new route when cleared." At the named holding point. Plan the next leg.
"Route ended. Hold position. Set a new route when cleared." End of your last taxiway. Plan the next leg.
Arriving
You hear What it means What to do
"Gate B 12 in 15 metres.", "10 metres.", "5 metres. Stop." Distance to the stand. Slow and stop.
"Stop. Hold position." You stopped before the last step. Stay stopped.
"Align with Gate B 12, heading 270. Turn left." Turn to face the stand. Follow the tone.
"Aligned with Gate B 12. Parking brake." You are parked and aligned. Set the parking brake.
"5 metres. Continue ahead for docking." / "Docking guidance ahead. Continue forward." Docking guidance will take you the rest of the way. Keep rolling slowly.
"Aligned with Gate B 12. Continue ahead. Docking guidance will take over." Aligned; docking takes over. Follow docking guidance.
The destination's name, then "reached." You have arrived somewhere with no stand heading. Stop.
Off route
You hear What it means What to do
"Route changed. Now via C, D, crossing runway 26R. 900 metres to Runway 27L." A new route from where you are. Follow it; check it agrees with ATC.
"Off route. Unable to recalculate." No new route could be found. Stop and plan a route.
"Off route. Could not follow clearance. recalculated route too long. Continuing on original route." The new route would be a big detour, so it kept the old one. Return to your route or plan a new one.
"Off route. Unable to recalculate. The way to Gate C 9 crosses runway 13." The only way crosses an unmapped runway. Stop and ask ATC.
Hotkey answers
You hear When
"Taxiway A, right onto taxiway B in 150 metres, 1200 metres to Runway 27L." Output Y while taxiing.
"Holding short of runway 22R. Press continue when cleared." Output Y at a hold.
"Lining up Runway 27L, runway heading 268. Follow the tone. 40 metres to go." Output Y while lining up.
"Backtracking Runway 32 to full length. 600 metres to go, then turn around to heading 320." Output Y during a backtrack departure.
"Arrived at Gate B 12." Output Y after arriving.
"No route loaded." Output Y when guidance has nothing to follow.
"No taxi guidance active." Output Y or Ctrl+Y with guidance off.
"No taxi instruction yet." Output Ctrl+Y before anything has been said.
"Taxi guidance stopped." Input Ctrl+Y.

If Something Goes Wrong

I can't hear the tone. The tone is silent whenever you are on track, at a hold and once lined up, so silence is usually good news. Check the volume and use Test Tone on the Taxi Guidance tab. Check which device it plays on, on the Audio tab. If you have a hold-short cue, press Continue only once cleared; the tone resumes then.

The tone tells me to turn the opposite way to the words. It should not: both are worked out from your actual heading. If you have the Invert steering tone direction box ticked, the tone means steer away from it.

I followed the tone and ended up going in circles after a wide turn. Stop, press Output Y to hear where you are, and if necessary recalculate from the planner. Guidance always picks up your real position on the taxiway again.

The first taxiway in the planner isn't the one ATC said. BA guesses the nearest taxiway in front of you. Always set First taxiway yourself.

A taxiway ATC named isn't in the list. Your scenery's data does not have it under that name. Switch on online taxiway names, rebuild your database if you have changed scenery, or pick the nearest equivalent. See Taxiway names you can't find.

The summary says the route does not reach the runway. The last taxiway you entered runs beside the runway without joining it. Add the short link onto the runway as the last taxiway.

The summary says it used the shortest path. Two of your taxiways do not meet in the scenery's data, or they are in the wrong order. Check each pair; the reason names the pair that failed.

I'm stopped at a hold line and nothing happens. BA is waiting for you. Press Input Y when cleared. At a Progressive Taxi end point, plan the next leg instead.

BA stopped me at a runway ATC had already cleared me across. That is by design: BA cannot hear ATC. Press Input Y and carry on. For a Progressive leg you can choose After crossing runway so it does not stop you there.

I heard "Route changed" when I didn't expect it. You strayed far enough from the route for BA to replan. Check the new taxiways against your clearance; if they are wrong, stop and recalculate from the planner with the right ones.

I closed the planner and guidance is still running. Closing the window only hides it. Use Input Ctrl+Y or Stop Guidance to stop.

The stand I need isn't in the list. Untick Show fitting only and Hide occupied stands, and clear the Gate search box. If the stand is listed with "(no taxi route)", the scenery's taxiways do not reach it; teleporting there may be the only option (see Teleporting to a Runway or Gate).

Distances are in the wrong units. Use Use feet for distances on the Taxi Guidance tab. Ground traffic distances have their own setting.

For anything else, see Logs and Getting Help. Taxi guidance writes its own logs, which help a lot when reporting a problem at a particular airport.

Ground Traffic

At a busy airport you share the taxiways with dozens of other aircraft. A sighted pilot watches them: the airliner stopped ahead in the queue, the one crossing at the next junction, the aircraft on short final to the runway they are about to cross. BA's ground traffic monitor watches them for you: aircraft close to you, traffic on your route, your place in the departure queue, and who is on or approaching the runway you are about to use. At any time on the ground, Output Alt+G gives a summary of the nearest traffic.

The traffic BA can see is the traffic the simulator shows you: AI traffic, and other pilots on an online network when your network software shows them in the simulator. BA never calls out your own aircraft.

Warning: BA never says a runway is "clear". It only ever says it has seen no traffic: "no traffic seen on the runway or on final." BA cannot see everything a controller can. An aircraft the simulator is not showing, a vehicle, or traffic further out on final may still be there. Always follow your ATC clearance. The runway watch is an extra pair of ears, not permission to enter a runway.

When Ground Traffic Speaks

The automatic callouts run while taxi guidance is running: from the moment you start guidance until you stop it, including after you arrive and while holding short. When you have no taxi guidance running at all, the automatic callouts stay quiet. The summary on Output Alt+G always works on the ground, whatever else is happening.

There are a few deliberate quiet times:

To start taxi guidance, see Taxi Guidance. The landing exit planner starts it for you automatically after landing; see The Landing Exit Planner.

How Aircraft Are Named

BA names other aircraft the way a controller would. If it knows the airline, you hear the airline and the type:

If it knows only the callsign, you hear the callsign and the type, for example "DAL 123, A320". If it knows only the type, you hear just the type, for example "737". If it knows nothing, you hear "traffic".

Types are spoken the way pilots say them, not as codes: a B77W is a "777", an A20N an "A320", and a B38M a "737 MAX".

In the Alt+G summary, BA also adds the callsign when the airline name hides it, for example "Delta A320, DAL 1234". At a hub where several Delta A320s are taxiing, that is how you and ATC tell them apart.

The Proximity Callouts

BA measures the distance to each aircraft on the ground near you and uses three zones. The further out zones grow with your speed: BA adds roughly seven seconds of travel at your current ground speed, so that you have time to react and brake. At 15 knots that adds about 180 feet to each zone.

Zone Starts at (stopped) What you hear
Awareness About 600 feet The aircraft's name, direction, distance and what it is doing
Caution About 400 feet "Slow down", with the aircraft's name, direction and distance
Warning About 250 feet "Stop", with the aircraft's name, "very close", direction and distance

Distances are measured from the centre of your aircraft to the centre of the other one. With two large jets, the real gap between nose and tail is much smaller than the number you hear.

Awareness

"Delta A320, ahead and to the left, 500 feet, stopped."

An aircraft is nearby. There is nothing to do except keep it in mind. The last part tells you what it is doing:

The direction words are the same ones Look Around uses. Awareness callouts are given for traffic in any direction, including behind you.

Slow down

"Slow down, Delta A320 ahead, 380 feet."

You are closing on an aircraft. Reduce your speed and be ready to stop. You only hear this while you are moving at 2 knots or more; if you are stopped, the same aircraft gives an awareness callout instead.

Stop

"Stop, Delta A320 very close, ahead, 200 feet."

An aircraft is very close. Stop now, then find out what is happening: press Output Alt+G for the traffic around you, or ask ATC.

How the zones behave

Traffic on Your Route and Converging Traffic

These two callouts need taxi guidance with a route, because they depend on knowing where you are going.

On your route

"Delta A320 on your route, taxiway B, 800 feet ahead, stopped."

There is an aircraft on the path you are about to taxi, up to about 600 metres ahead. The taxiway is named when BA knows it. The distance is measured along your route, not in a straight line, so round a bend it tells you how far you will actually taxi before you reach it. The last word tells you what it is doing:

You hear this once for each aircraft, until it leaves your route and comes back. You only hear it while you are moving, unless the aircraft is coming toward you. An aircraft on your route that is pulling away faster than you are moving is not announced.

Converging

"Delta A320 converging from the left, about 20 seconds."

A moving aircraft that is not on your route is on a course that will bring it close to you, in about the number of seconds given. The side is "from the left", "from the right", "from ahead" or "from behind". Look for it with Output Alt+G, be ready to stop and give way, and follow ATC's instructions about who goes first. You hear this before the aircraft gets close, typically 5 to 40 seconds ahead. You hear it when the traffic is ahead of you, or at any angle while you are moving.

The Departure Queue

On the way to the runway, the queue can be long. BA tells you where you are in it and helps you keep it moving.

Your place in the line

"Number 3 in the departure queue."

When you are stopped or creeping along your route, BA counts the aircraft lined up ahead of you on the route: those stopped or slowly moving along it, pointing the same way. Aircraft parked beside the route, crossing it or coming the other way are not counted. BA only counts the line you are actually in. A big gap ends the line, so a second queue further on is not added to yours.

You hear "departure queue" only when your route ends at a runway and the front of your line is close to the runway hold. Elsewhere you hear just "queue", for example "Number 2 in the queue." BA waits until the count is steady before saying it, and says it again only when it changes.

The aircraft ahead is moving

"Delta A320 ahead is moving."

The aircraft directly in front of you, which was stopped, has started to move. Get ready to follow it, keeping a safe distance.

Move up

"Move up. 400 feet to the traffic ahead." or "Move up. The traffic ahead has taxied on."

A gap has opened in front of you and you have not moved. This is only a prompt from BA, not an ATC instruction. Move up only if you are cleared to taxi and it is safe. BA is careful with it:

The Runway Watch

What it is

Runways are where the most serious accidents happen. Whenever you are about to use a runway, or are on one, BA watches that runway and its final approach and tells you what it sees.

When it runs

The runway watch starts on its own when you:

Holding short, lining up and waiting for takeoff on the same runway count as one watch, so you are not told the same thing again at each step. Crossing a runway is also one watch, from the hold line until you are clear on the far side.

What you will hear

The first status. When a watch starts, BA always speaks the runway's status once, when its first fresh look at the traffic is in. For example:

If you are near two runways at once, for example at an intersection, each one is described in turn.

Changes while you watch. After the first status, BA tells you about each change:

Each aircraft is announced once. One that disappears for a moment and comes back is not announced again.

What to do
Interrupting or waiting

How runway news is delivered depends on where you are:

If you stop on the runway after landing, or press Continue at a hold and roll onto the runway, the situation has changed. If there is traffic on the runway or on short final, BA may repeat the status once, interrupting, because the status you heard at the hold could have been cut off by the instruction that moved you.

The Traffic Summary: Output Alt+G

What it is

Press Output Alt+G at any time on the ground to hear the nearest traffic. It works whether or not taxi guidance is running. Use it after a "Stop" or "Slow down" to find out what is around you, or before you start taxiing.

Note: In Input mode, Alt+G opens the Access GSX window instead. See Gates, GSX and Docking.

What you will hear

BA reads up to three aircraft on the ground within about 2,000 feet, nearest first, each with its name and callsign, direction, distance and what it is doing:

"2 aircraft nearby. Delta A320, DAL 1234, ahead and to the left, 800 feet, stopped. Lufthansa 747, DLH 400, behind and to the right, 1500 feet, crossing left to right."

Then, when they apply:

Other answers:

What Interrupts and What Waits

Taxiing is busy, and taxi guidance has a lot to say. To keep the important things audible:

Callout Quick Reference

You hear It means What to do
"Delta A320, ahead and to the left, 500 feet, stopped." An aircraft is nearby Be aware of it
"Slow down, Delta A320 ahead, 380 feet." You are closing on it Slow down, be ready to stop
"Stop, Delta A320 very close, ahead, 200 feet." It is very close Stop now
"Delta A320 on your route, taxiway B, 800 feet ahead, stopped." It is on the path you are about to taxi Expect to stop behind it or be rerouted
"Delta A320 converging from the left, about 20 seconds." A moving aircraft will come close Be ready to stop and give way
"Number 3 in the departure queue." Two aircraft are ahead of you in the line Wait your turn
"Delta A320 ahead is moving." The aircraft in front has moved off Get ready to follow
"Move up. 400 feet to the traffic ahead." A gap has opened Move up if cleared and safe
"Runway 27L: no traffic seen on the runway or on final." BA saw no traffic there Still wait for your clearance
"Delta A320 short final runway 27L, 1.8 miles." An aircraft is about to land Do not enter the runway; query any clearance
"Delta A320 landing runway 27L." An aircraft is landing now Stay off the runway; tell ATC if you are on it

Settings

The ground traffic monitor has one setting of its own, on the Taxi Guidance tab of the Settings window:

This setting is separate from Use feet for distances (default: metres), which sets the units for taxi guidance and Look Around. The TCAS window (Output Ctrl+R) also has an On Ground Traffic list; see TCAS Traffic.

If Something Goes Wrong

Gates, GSX and Docking

This chapter is about the stand at each end of the flight: choosing one, working with GSX Ground Services Pro (the add-on that brings jet bridges, buses, fuel trucks, pushback and a marshaller to the ramp), and docking guidance, BA's audio version of the parking guidance display.

You do not need GSX to use stands or docking guidance. Without GSX, BA still lists every stand in your scenery and still docks you onto it. GSX adds the ground services, a more precise stop position at many gates, and the confirmation "GSX docking complete." at the end.

Note: The GSX parts of BA need GSX 4.0.8 or newer. If you have an older GSX, run FSDT Live Update (Virtuali's own updater) to install the latest version.

Choosing a Stand

What it is

In the taxi planner (Input Shift+Y), set Destination type to Gate / Parking and the Destination list fills with the airport's stands. This section explains that list and the controls beside it.

How the stands are listed

Each stand is one item in the list. A typical item reads like this:

"A 12 - Gate Medium (Jetway) [SafeDock]"

In order, that is:

When BA knows where your aircraft is, the list is sorted nearest first, measured in a straight line, so the stands you are most likely to want are at the top. Before BA has your position, the list is sorted by type (small gates first, then larger gates, then ramps) and then by number.

Finding a stand quickly

Use the Gate search box to type part of a stand's name. Type a letter to narrow the list to one concourse ("C"), a number ("18"), or a full name ("C18"). The search also matches online names, so you can type exactly what ATC said — "B04" finds the stand your scenery calls B 6. Then Tab to the Destination list and arrow through what is left.

Show fitting only

The Show fitting only checkbox hides stands that are too small for your aircraft's wingspan. GSX stands are judged against the maximum wingspan GSX publishes for them; other stands against the size your scenery records. A stand with no size information at all is never hidden.

Scenery stand sizes are sometimes wrong. If a stand you were cleared to is missing, untick Show fitting only and look again. BA does this for you automatically when SayIntentions assigns you a gate: the assigned gate is found even if the scenery claims your aircraft is too big for it.

Hide occupied stands

The Hide occupied stands checkbox (ticked by default) leaves out stands that already have an aircraft parked on them. When it hides any, the planner's status line says how many, for example "84 listed, 6 hidden (occupied by traffic)." This is shown on the status line only, not spoken, so it never talks over your screen reader while you type or arrow. Untick the box to see every stand again.

An arrival gate assigned to you by SayIntentions is always offered, occupied or not.

If you choose a stand that does have an aircraft on it, you are warned when you press Calculate Route: "Warning: an aircraft is at the destination gate." — or the other aircraft's callsign instead of "an aircraft" when BA knows it.

Stand names, GSX and World of Jetways

Your stand names come from your navigation database, which BA builds from your installed scenery (see The Navigation Database). When GSX is running and has a profile for the airport, BA also reads GSX's own list of stands, with their exact stop positions, sizes and jet bridges. At an airport where the GSX profile covers only some of the stands, you still see every stand — the GSX information is added to the stands it covers, and the rest keep their real heading, size and jet bridge from your scenery.

Note: If you use GSX World of Jetways with MSFS 2020, older BA databases could replace an add-on airport's stands with default ones, so a gate the sim and ATC call "Gate 20" was announced as "G 6". This is fixed, but an existing database keeps its old names until you rebuild it. Rebuild your database from the Nav Database window (File menu) to pick up the fix.

Online stand names are controlled by the online names setting described in Online names.

The Access GSX Window

What it is

GSX normally works through a menu drawn inside the simulator, which a screen reader cannot see. The Access GSX window shows that same menu, GSX's status and its messages as ordinary text your screen reader can read, and lets you choose menu options with the keyboard.

Opening it

Press Input Alt+G. The Access GSX window opens. It has:

If no GSX menu is open, the menu field reads "GSX Menu hidden. Press F5 to open it."

Keys inside the window
Key What it does
F5 Open, or reopen, the GSX menu
1 to 9, and 0 Choose that menu option (the same layout as the in-sim GSX menu)
A Customize Airport positions
B Customize Airplane
C Open the accessible GSX Settings window (while a GSX menu is open)
D Restart GSX
E Reload SimBrief
Escape Hide the Access GSX window (GSX keeps running)

The menu is read out the way it is shown: the menu title, then each option with the key that chooses it — "1. Request Deboarding", "2. Request Catering" and so on. The letters A to E are always listed at the end. They work even when no menu is open, which matters for D, Restart GSX: that is the standard fix when GSX stops responding, and a stuck GSX will not open a menu.

An option can carry a state after a dash, such as "— In progress", "— Completed", "— Requested" or "— unavailable". These are the colours the sighted menu uses, spelled out in words. If you choose an unavailable option you hear "That option is unavailable." and nothing is sent.

When you pick an option, BA does not announce the key press itself — your screen reader already knows what you did. What you hear next is GSX's response: usually its next menu.

Tip: Long menus, such as a list of stands, are split by GSX into pages of up to ten options. The last option on a full page is "Next Page". Choose it with its number key to hear the next page.

While a service runs, GSX keeps refreshing its menu — an option can contain a live counter such as a passenger count. BA only reads the menu out again when something meaningful changes: a new menu opens, its title changes, options appear or disappear, or an option's wording changes for a real reason (for example "Request Boarding" becoming "Boarding no longer possible"). A counter ticking up on its own updates the list silently. Arrow through the menu at any time to hear the current numbers.

Read the latest GSX message without opening the window

Press Output Ctrl+G from anywhere to hear GSX's latest message. If GSX has not said anything yet you hear "No GSX tooltip yet."

Active services

When GSX is running two or more services at the same time — boarding and refuelling, say — an Active services list appears above the tooltip. Choosing a service decides which service's message is shown in the Tooltip field. It does not change what is announced: you still hear every service's own progress, whichever one you pick here. The list is hidden when zero or one service is running, so it stays out of your way.

If GSX cannot be reached

If GSX is not running, is too old, or has just restarted, the window still opens and the status line says why. Pressing F5 speaks the same reason. You will hear one of these:

BA never announces these at startup. You are only told when you ask for GSX.

GSX Settings

What it is

GSX has many settings of its own — how its vehicles behave, sounds, timings and much more. BA presents GSX's settings page as an ordinary accessible window, so you can change them without the in-sim menu.

How to use it
  1. Open the Access GSX window with Input Alt+G.
  2. Press F5 to open the GSX menu.
  3. Press C. The GSX Settings window opens.
  4. At the top is the Settings sections list — GSX's own tabs. Use the Left and Right arrow keys (or Up and Down) to move between sections.
  5. Press Tab to move into the section's settings. Each setting is a normal control: checkboxes for on/off settings, lists for choices, number boxes for ranges, text boxes for text, buttons for actions, and read-only boxes for information.
  6. Press Close or Escape when you are done.

Changes go straight to GSX and GSX saves them itself. Number and text settings are sent as you change them, and again when the window closes. When GSX confirms a change, the control updates where it is, without moving your focus.

If you press C before GSX has published its settings, the window shows "No GSX settings were available." Open the GSX menu with F5 and press C again.

What GSX Tells You

What it is

While services run, BA reads out the meaningful changes GSX reports, so you can follow your turnaround without watching the screen. You are never read the state GSX was already in when BA connected — only what changes afterwards.

What you will hear
Hearing GSX with the window closed

While the Access GSX window is visible, its announcements are always spoken. When it is hidden, they follow a setting: Announce GSX tooltips when Access GSX window is closed, on the Announcements tab of Settings. It is off by default. Turn it on if you want to hear boarding, fuel, pushback and the ground crew while you work in other windows. A menu GSX opens on its own — a pushback confirmation, an operator question — is also read out with the window hidden when this setting is on; with it off, you find that menu waiting the next time you open the window.

If something goes wrong

If GSX announcements misbehave — something you expected is never spoken, or something repeats — BA records what it decided and why in a log file called gsx.log. Attach it to your bug report. See Logs and Getting Help for where the logs are.

Letting BA Prepare Your Stand in GSX

What it is

Normally you tell GSX which stand you are parking at by working through its menu. BA can do this for you: when you calculate a taxi route to a stand, BA asks GSX to prepare that stand, so the jet bridge, marshaller and parking guidance display are ready there when you arrive. It then tells you what GSX actually did.

How to use it

There is nothing extra to do. The setting Auto-select arrival gate in GSX on route calculation is on the Taxi Guidance tab of Settings, and it is on by default. With it on, every time you press Calculate Route with a Gate / Parking destination (or a Place destination that is a GSX stand), BA sends the stand to GSX in the background. Your route loads straight away; it does not wait for GSX.

What you will hear

If GSX is not running, or no airport is loaded in GSX yet (for example you calculated the route while still far away), nothing is said. Calculate the route again closer to the airport.

Tip: Calculate your taxi-in route after landing, or on approach, rather than at the gate before departure. GSX needs to have your arrival airport loaded to prepare a stand there.

Docking Guidance

What it is

Docking guidance gets you from the end of the taxi route onto the stand, square with the gate and stopped at the right spot for the jet bridge. Real airports do this with a parking guidance display or a marshaller. BA does it with sound:

When it is used

Docking guidance starts by itself. You only need to have taxi guidance running to a stand: choose a Gate / Parking (or Deice Area) destination in the taxi planner and start guidance. It works with or without GSX. It never starts for a runway destination.

With GSX, the stop is GSX's own stop position for your aircraft type at that gate, which is where the jet bridge expects your door. Without GSX, the stop is the centre of the parking spot in your scenery, which is usually close but less exact.

Step by step: docking at a gate
  1. Taxi in on taxi guidance as normal. Taxi guidance steers you along the taxiways and around the turn onto the stand. When the stop position is still ahead of the point where taxi guidance would normally stop you, taxi guidance says so instead of telling you to stop — you hear, for example, "Align with Gate A 12, heading 270. Then continue ahead for docking guidance." or "10 metres. Continue ahead for docking." Keep rolling slowly.

  2. Docking engages. When you are within about 50 metres of the stop, roughly in line with the stand, and slower than 15 knots, docking takes over. (Some GSX gates set their own engage distance, between 20 and 70 metres.) You hear one sentence, for example "Docking guidance. SafeDock display. 40 metres to stop. Slight right, 5 degrees. Jetway on your left." That tells you the parking system installed at the gate (when there is one), the distance to the stop, how much you need to steer right now, and which side the jet bridge or door is on (when BA knows). The steering amount is rounded to 5 degrees and worded "Slight" for 5 to 10 degrees, plain for 15 to 20, and "Sharp" for 25 or more. It is said up front because the tone reaches full pan at 15 degrees: on a big, slow-turning aircraft you need the number to judge how much tiller to use.

  3. Steer with the tone. From now on docking owns the steering tone, and taxi guidance's own tone goes quiet so you never hear two. Steer toward the tone (or away from it if you have inverted it in Settings). The tone is very precise here: it stays silent only when you are within half a degree of the correct line, and comes back as soon as you drift more than a degree. Near the stop, the guidance gradually turns you square with the gate, so a centred tone in the last few metres means you are both on the line and straight.

  4. Listen to the beeps. The beeping starts slowly — about once a second around 30 metres out — and gets faster as you close in, until it is a rapid patter just before the stop. When you are on the stop, it becomes one solid tone. Creep forward until you hear the solid tone, then stop.

  5. Distance and speed calls. On the way in you hear the distance at fixed points: "30 metres to stop.", "20 metres to stop.", "10 metres to stop.", "5 metres to stop." (or 100, 60, 30 and 15 feet if you use feet). If you are still faster than 3 knots in the last 6 metres, you hear "Slow down." once. And, unless you have turned it off, your ground speed is spoken every time it changes by a knot — "4 knots.", "3 knots.", "1 knot.", "Stopped." — because at gate speeds the normal speed announcements are silent, and both your hands are busy.

  6. The closing phrase. When you stop on the spot, on the centre line and square with the gate, you hear "GSX docking complete. Aligned with gate. Parking brake." At a stand with no GSX stop position, the first word is "Stop." instead: "Stop. Aligned with gate. Parking brake." The solid tone keeps sounding for about three seconds, as a reference while you come to a halt, then fades. Guidance is now finished: set the parking brake. Taxi guidance stops too.

Docking at a deicing pad

If your taxi destination is a Deice Area, docking works the same way but the wording changes. The opening call is "Deicing guidance." with the distance and steering, there is no jet bridge or door call, and the closing phrase is "Stop. Parking brake." — without any claim about being aligned with a gate, because a deicing pad is wide and BA does not check your alignment there.

When the park goes wrong: "Back up and try again"

Docking only calls a park complete when it really is good. If it cannot be, it stops you with a clear instruction instead of letting you creep into a bad position. There are three cases:

In each case the tone and beeps stop at once. No solid "docked" tone sounds over a bad park, so silence after one of these calls means "not parked correctly", never "done".

Why not just turn the last bit? Because at the stop there is only about a metre of rolling left, which is far too little to turn out a heading error — and GSX will not treat a crooked aircraft as parked, so the jet bridge will not come.

To try again:

  1. Stop and set the parking brake.
  2. Back the aircraft up a few metres, straight back along the stand line — for example with GSX pushback, or the aircraft's reverse if it supports it.
  3. Open the taxi planner (Input Shift+Y) and calculate the route to the same stand again. This starts guidance afresh, and docking engages again as you roll forward onto the stand.
Stopped short

If you stop between the 5-metre call and the stop and sit still for about four seconds, docking reminds you how far is left: "5 metres to stop. Continue forward." Roll on slowly until you hear the solid tone. (Distances are rounded, so very short gaps are given to the nearest 5 metres or 25 feet.)

Checking your status: Output Y

Press Output Y at any time during docking for a status in one sentence, for example:

This replaces the normal taxi status while docking is in control, so you never hear two different distances. After a good park, Output Y says "Parked at the stop. Guidance complete." (or "Parked at the deicing pad. Guidance complete."). After one of the failed endings it says "At the stop. Hold position."

Stopping docking

Docking ends by itself when you park, when you taxi well away from the stand (more than about 75 metres), or when you stop taxi guidance with Input Ctrl+Y (you hear "Taxi guidance stopped."). Starting a takeoff, or a new route to a runway, also clears it.

Settings

All the docking settings are on the Taxi Guidance tab of Settings, in the Docking guidance group.

The steering tone itself uses the taxi guidance tone settings on the same tab: Steering tone type, Volume, Invert steering tone direction (steer AWAY from the tone) and Hard-pan steering tone (full left or full right; speaker-friendly). See Taxi Guidance for those.

Distances follow Use feet for distances (default: metres), also on the Taxi Guidance tab.

If something goes wrong
Worked example: arriving at a GSX gate

You have landed and vacated the runway. You open the taxi planner, set Gate / Parking, type "A12" in the Gate search box, choose "A 12 - Gate Medium (Jetway) [SafeDock]", enter your taxi clearance and press Calculate Route. A moment later you hear "GSX prepared Gate A 12." — the jet bridge will be waiting.

You taxi in on the tone. On the turn onto the stand you hear "Align with Gate A 12, heading 270. Then continue ahead for docking guidance." Rolling slowly forward, you hear "Docking guidance. SafeDock display. 40 metres to stop. Slight right, 5 degrees. Jetway on your left." and the slow beeping starts. You ease right until the tone falls silent. "30 metres to stop." ... "20 metres to stop." ... "5 knots." ... "10 metres to stop." The beeps get faster. "3 knots." ... "5 metres to stop." ... "2 knots." ... "1 knot." The beeps blur into a solid tone, you stop, and you hear "GSX docking complete. Aligned with gate. Parking brake." You set the parking brake, open the Access GSX window with Input Alt+G, press F5, and request deboarding.

Part 6: Flying

Takeoff, Climb and Cruise

A typical departure with BA looks like this:

  1. Taxi to the runway with Taxi Guidance. When you line up, Takeoff Assist switches itself on.
  2. Roll down the runway following the Takeoff Assist tone, listening to the speed and V-speed calls.
  3. At liftoff BA hands you over to Hand Fly mode, which gives you a tone for pitch and bank.
  4. Engage the autopilot when you are ready, using the autopilot windows to set speed, heading, altitude and vertical speed.
  5. In the climb and cruise, BA calls each 1,000 feet and tells you about anything that changes.

Each step can also be done by hand, and each automatic step can be switched off.

Takeoff Assist

What it is

Takeoff Assist keeps you on the runway centreline during the takeoff roll. It plays a steady tone in your headphones that moves left or right to show which way to steer, calls out your pitch as you rotate, and calls out speeds as you accelerate. It works on every aircraft BA supports.

When to use it

Use it for every takeoff. It is switched on for you when taxi guidance lines you up on your departure runway. If you got onto the runway another way, for example by teleporting, press Output Ctrl+T once you are lined up and pointing down the runway.

How BA knows which runway you are on

Takeoff Assist steers you along the real centreline of the runway, so it needs to know which runway that is. It finds out in this order:

  1. If you teleported to a runway with Input Shift+R (see Teleporting to a Runway or Gate), it uses that runway.
  2. If taxi guidance just lined you up, it uses the runway taxi guidance took you to.
  3. Otherwise, if you are on the ground at an airport in your navigation database, BA works out which runway is under the aircraft from your position and heading.
  4. If none of these works, it draws an imaginary centreline straight ahead of you from where you are now, along the heading you are pointing.

When it switches on you hear which of these it used:

The runway is forgotten every time Takeoff Assist switches off, so your next flight always starts fresh and never reuses the last airport's runway.

The heading check

When BA knows the real runway, it compares your heading with the runway heading the moment Takeoff Assist switches on. If you are more than about 3 degrees off, you hear a warning such as "Warning: heading 262, runway heading 270. Turn right to align before rolling." Turn the way it says before you advance the thrust levers. Sighted pilots make this same check by looking down the runway; this gives you the numbers.

How to use it
  1. Line up on the runway. If taxi guidance brought you here, you hear "Lined up. Activating takeoff assist." followed by the runway announcement. Otherwise press Output Ctrl+T.
  2. Listen for the heading warning. If there is none, you are aligned.
  3. Advance the thrust levers and start the roll.
  4. Steer with the rudder toward the tone (see below). When the tone is silent, or centred, you are tracking the centreline.
  5. Listen for "80 knots", "100 knots" and the V-speed calls.
  6. Rotate. Takeoff Assist calls your pitch every time it changes by a degree: "+3", "+7", "+12".
  7. After liftoff, if Hand Fly auto-activation is on (it is by default), BA turns Takeoff Assist off and Hand Fly on for you, and says "Airborne, hand fly." If it is off, press Output Ctrl+T to switch Takeoff Assist off yourself; you hear "Takeoff assist off".

You can press Output Ctrl+T at any time to switch Takeoff Assist off, for example after a rejected takeoff. Pressing it again switches it back on.

Note: Takeoff Assist needs the simulator connected. If it is not, Ctrl+T says "Not connected to simulator."

The centreline tone

The Takeoff Assist tone is a steering tone with a fixed pitch (see The Audio Language): it sits on the side you should press rudder toward, fully to one side for a correction of about 5 degrees or more. With the default setting it only sounds when you need a correction of 1 degree or more; if you choose to hear it all the time, it sits in the centre when you are on track.

The tone does more than tell you whether the nose points down the runway. It also knows how far you are from the centreline. If you have drifted to one side, the tone asks you to point slightly back toward the centreline (up to 10 degrees, gently, so you never get a sharp swerve at speed), and as you close in it eases you back onto the runway heading. Within about 8 feet of the centreline it simply asks you to hold the runway heading. So if you follow the tone until it goes quiet, you end up both on the centreline and pointing straight down it.

Tip: Make small, smooth rudder inputs and wait a moment for the tone to respond. Chasing the tone with big inputs at high speed causes a swing from side to side.

If you learnt the older Takeoff Assist where you steered away from the tone, you can reverse it in Settings (see below).

What you will hear
The handover to Hand Fly at liftoff

Once you are flying you need pitch and bank, not centreline, so by default BA switches over for you shortly after liftoff. It waits long enough that a bounce on the runway or a rejected takeoff never turns your centreline guidance off by mistake.

When it switches you hear one short phrase:

The Hand Fly tone starts immediately.

Legacy mode

Legacy mode is the original Takeoff Assist. It plays no tone. Instead it speaks how far your heading is from the runway heading, in whole degrees, whenever that changes by a degree: "3 right" means you are pointing 3 degrees right of the runway heading, so steer left; "center" means within 1 degree. It knows nothing about your distance from the centreline, so a small heading error can still let you drift sideways. Use it only if you prefer speech to tones. When it switches on you hear "Takeoff assist active legacy mode, runway 27L at EGLL" or "Takeoff assist active legacy mode, reference heading 272".

Settings

These are on the Hand Fly tab of the Settings window (see The Settings Window):

Ground speed calls during the roll are set on the Taxi Guidance tab; see Ground speed.

The tone, volume and steering settings here are also used by the rollout centreline tone after landing; see Flare and Rollout Tones.

If something goes wrong

Takeoff Speed Callouts

Several aircraft get spoken "V1", "Rotate" and "V2" calls on the takeoff roll from BA, timed to the moment your airspeed reaches each speed. These are action cues, so they speak immediately, even over other speech.

Aircraft Who makes the calls Where the speeds come from
FlyByWire A320 and Headwind A330 BA The MCDU PERF TAKE OFF page
FlyByWire A380 BA The PERF page
iFly 737 MAX 8 BA The FMC
TFDi MD-11 BA, plus "N1 70 percent" The FMS
Fenix A320 BA (the Fenix also calls "V1" itself, so you hear it twice) The MCDU PERF TAKE OFF page

How they work:

Takeoff Assist's "80 knots" and "100 knots" come on top of these on every aircraft. The BlueBird 757-200 plays its own "80 knots", so Takeoff Assist calls only "100 knots" there (see BlueBird 757-200). Details for each aircraft are in Airbus Aircraft and Boeing Aircraft and the MD-11.

Autopilot Windows

What they are

The autopilot windows let you set the autopilot by typing a number instead of turning a knob. Each window sets one value — speed, heading, altitude or vertical speed — and also carries the buttons that belong with it, such as push and pull or the mode switches. A separate autopilot window holds the main engage buttons. Every aircraft BA supports has them; their exact contents follow the real aircraft's panel. Airbus aircraft call the panel the FCU, Boeing aircraft the MCP, and the MD-11 the flight control panel.

Opening them

The keys are the same on almost every aircraft, all in input mode:

Key Window
Input Ctrl+S Speed
Input Ctrl+H Heading
Input Ctrl+A Altitude
Input Ctrl+V Vertical speed (or flight path angle)
Input Ctrl+B Altimeter (barometric setting)
Input Ctrl+P Autopilot panel: autopilot, autothrust or autothrottle, approach modes, disconnects

Not every key exists on every aircraft; each aircraft's guide in Part 8 lists what it has. To read the values back without opening a window, Output Shift+S, Shift+H, Shift+A and Shift+V read the speed, heading, altitude and vertical speed windows on every aircraft.

Using a value window
  1. Press the key, for example Input Ctrl+A. The window opens with the cursor in the value box.
  2. Type the value, for example 12000, and press Enter. There is no Set button; Enter in the value box is how a value is set.
  3. BA confirms the value it set. On the FlyByWire Airbuses, for example, the speed window says "FCU speed 250, selected".
  4. Tab on to the other buttons if you need them, such as Altitude Pull (selected).
  5. Press Escape or the Close button. Focus goes back to where you were.

On the Airbus aircraft the windows stay open alongside your other windows, so you can leave one open while you work in another. If you type something the aircraft cannot accept, BA tells you why, for example "Invalid number format", and selects the text so you can type again.

A typical speed window contains a value box, push and pull buttons (or Speed Intervene on a Boeing), a speed or Mach toggle, and Close. Buttons that have a state say it in their name, for example "SPD / MACH toggle — now knots (press for Mach)".

Push, pull, managed and selected

On Airbus aircraft each FCU knob can be pushed or pulled:

The same idea exists on Boeing aircraft in other words: LNAV and VNAV are the flight computer flying the route and profile; HDG SEL, LVL CHG or FLCH and V/S are you choosing the numbers; and Intervene lets you change a value without leaving VNAV.

When an Airbus FCU window is managed it shows dashes, and BA's readouts say "managed" rather than inventing a number. With the FCU unpowered they say "not available".

On the FlyByWire Airbuses and the Fenix A320 you can also push and pull the knobs straight from the keyboard, without opening a window:

Key Action
Input Shift+1 / Input Ctrl+1 Push / pull heading
Input Shift+2 / Input Ctrl+2 Push / pull altitude
Input Shift+3 / Input Ctrl+3 Push / pull speed
Input Shift+4 / Input Ctrl+4 Push / pull vertical speed

The TFDi MD-11 has the first three pairs (heading, altitude and speed); its vertical speed wheel is in the Ctrl+P and Ctrl+V windows.

Autopilot shortcut keys (FlyByWire Airbuses)

On the FlyByWire A320, Headwind A330 and FlyByWire A380, these keys work the engage buttons directly:

Key Action
Input Shift+A Autopilot 1 on or off
Input Ctrl+O Autopilot 2 on or off
Input Shift+P Approach mode (APPR)
Input Ctrl+J Autothrust: arm or disconnect
Input Ctrl+L Localizer (LOC)

The result is announced by the aircraft's flight mode announcements, which are spoken automatically whenever a mode changes.

The autopilot panel window

Input Ctrl+P opens the autopilot panel. It is a list of buttons, each of which says its current state. On the FlyByWire A320 you find AP1 and AP2, A/THR (which says Disengaged, Armed or Active), AP disconnect, A/THR disconnect, the approach and localizer buttons, and a Flight Director status line. On the Boeings you find the A/P and A/T buttons, LNAV, VNAV and the other mode buttons, with a separate disconnect button that always disconnects. The MD-11's window also carries a live status list of all four windows.

What you will hear

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

If something goes wrong

Hand Fly Mode

What it is

Hand Fly mode helps you fly the aircraft by hand without the autopilot. It gives you a tone that shows your pitch and bank at every moment, spoken pitch and bank calls, and a set of single-letter keys that read your flight instruments instantly.

When to use it

Use it whenever you are flying by hand: after takeoff until the autopilot is engaged, during manual climbs and turns, and any time you want to keep an ear on your attitude. It comes on automatically at liftoff when Takeoff Assist is active (see The handover to Hand Fly at liftoff). You can also turn it on or off at any time with Output Ctrl+H. You hear "Hand fly mode active" or "Hand fly mode off".

The Hand Fly tone

The Hand Fly tone is a single continuous note that carries two pieces of information at once:

So a centred tone at the middle note is level flight with wings level. A tone sitting in your right ear at a higher note is a climbing right turn. To level the wings, roll away from the side the tone is on until it comes back to the centre.

Note: This is different from the Takeoff Assist tone, which never changes note and points to where you should steer. The Hand Fly tone shows what the aircraft is doing now. See The Audio Language: What the Tones Mean for how all of BA's tones fit together.

If you also turn on Visual Guidance (Output Ctrl+V), the Hand Fly tone goes quiet so that you only hear Visual Guidance's two tones, which use the same pitch and pan rules. Hand Fly's spoken calls carry on. When Visual Guidance ends, the Hand Fly tone comes back.

What you will hear

Depending on the feedback type you choose, Hand Fly speaks:

Quick-access keys

While Hand Fly mode (or Visual Guidance) is on, these single letters work on their own, without pressing a bracket first:

Key What it reads
A Altitude above sea level
Q Altitude above the ground
S Indicated airspeed
H Magnetic heading
V Vertical speed
P Pitch
B Bank
D Distance to your destination runway
F Target vertical speed (Visual Guidance only)

Pressing F when Visual Guidance is off says "Visual guidance not active". D needs a destination runway; see Choosing a Destination Runway.

Warning: These letters are taken over for the whole computer while Hand Fly or Visual Guidance is on. Typing an A, B, D, F, H, P, Q, S or V into another program, such as a chat window, will not work until you turn the mode off.

How to use it
  1. Take off with Takeoff Assist. At liftoff you hear "Airborne, hand fly." and the tone starts. Or press Output Ctrl+H.
  2. Hold your takeoff pitch by keeping the note steady at the right height. Listen to the pitch calls to confirm the number.
  3. To turn, roll until the tone moves to the side you are turning and the bank call says the angle you want, for example "right 15". Roll back toward the centre to level the wings.
  4. Press the quick keys for anything else: S for speed, A for altitude, V for climb rate.
  5. When the autopilot is engaged, press Output Ctrl+H to turn Hand Fly off.
Settings

On the Hand Fly tab of the Settings window:

The same tab holds the Visual Guidance and Takeoff Assist tone settings; those are covered in their own sections.

If something goes wrong

Altitude Callouts

While you are airborne, BA calls each 1,000 feet you cross, climbing or descending, as a plain number: "5000", "10000", "36000". It is the thousand you just crossed, so passing 4,000 feet says "4000" both on the way up and on the way down. The call comes at the moment you reach the round number.

To keep things quiet in the cruise, BA never repeats the thousand it just called. If you level off at 36,000 feet and turbulence takes you a few feet above and below it, you hear "36000" only once. The call comes back once you cross a different thousand, and everything resets when you land.

Nothing is called on the ground, and nothing is called when you first connect in mid-air: BA notes where you are silently and calls the next crossing.

On the FlyByWire A380 with the metric altitude (MTRS) button on, the calls are every 300 metres instead and say the unit: "3000 meters".

Turn these calls on or off with Announce 1,000-foot altitude crossings on the Announcements tab of Settings. They are on by default.

Other Automatic Callouts in Flight

Liftoff and touchdown

On every aircraft BA says "Airborne" when the wheels leave the ground and "On ground" when they touch down again, so you always know the moment of liftoff and touchdown, including a bounce. If you find it chatty during circuits, mute it in the Monitor Manager (Output Ctrl+M), where it is listed as Ground State.

Speed brake

On the PMDG 737, PMDG 777 and iFly 737 MAX 8, BA announces the speed brake lever once it comes to rest, rather than at every position it passes on the way:

You can also move the lever on those aircraft from the Control Stand panel. Turning the speed brake off in the Monitor Manager (Output Ctrl+M) keeps it quiet.

Trim

BA announces stabiliser trim as it changes. On most aircraft it is spoken in degrees with a direction, in steps of a tenth of a degree, for example "Trim up 1.4". It stays quiet while the trim only wobbles on the ground. Some aircraft use their own trim units, to match the number the FMC asks for and the trim indicator shows:

On the Fenix A320 family the degrees are the Fenix's own stabiliser, the same number as the MCDU's take-off trim and the ECAM, so you can trim until BA says the value on your MCDU.

On every aircraft, press Output Shift+T to turn trim announcements on or off; you hear "Trim announcements on" or "Trim announcements off". Trim announcements can also be muted from the Monitor Manager.

Thrust lever detents

On the FlyByWire A380, BA tells you when the thrust levers reach a detent: Idle, Climb, Flex MCT, TOGA or Reverse. This is a background announcement: if you pick a detent from the Thrust Levers control yourself, your screen reader reads your choice and BA then tells you once the levers actually arrive. On the FlyByWire A320 and Headwind A330, picking a detent from the Thrust Levers control is not repeated back, because your screen reader has already read it.

Cockpit warnings: ECAM and EICAS

Airliners show warnings, cautions and status messages on a central display: ECAM on Airbus aircraft, EICAS on Boeings. BA reads these to you so you know when something needs attention.

On the FlyByWire A320, Headwind A330 and FlyByWire A380, BA speaks ECAM warnings, cautions and memos as they appear. Press Output Ctrl+E to turn these call-outs off or on; you hear "E W D monitoring disabled" or "E W D monitoring enabled". Master Warning and Master Caution are always announced. To read the whole display at any time, press Output Alt+E to open the E/WD window.

Other aircraft work in a similar way: the PMDG aircraft announce Master Warning and Master Caution and their annunciator lights, and the HorizonSim 787 announces Master Warning and Master Caution and lists the full EICAS alerts in its Alt+E window. Each aircraft's guide in Part 8 gives the details, and every one of these announcements can be muted in the Monitor Manager.

TCAS Traffic

What it is

BA's TCAS Traffic window lists the other aircraft around you — AI traffic, multiplayer and network pilots — with their distance, direction and height. You can pick aircraft to track and then hear where they are with one key. On the FlyByWire Airbuses, BA also speaks the aircraft's own TCAS traffic and resolution advisories.

The TCAS Traffic window

Press Output Ctrl+R to open the window. It has a status line at the top, then two lists:

Both lists are sorted nearest first. Each line reads like this: "UAL 123 — 4.2nm, 2,000ft above, 2 o'clock — 310 knots — United — type B738 — KSFO to KLAX — heading 145 — 14,500 feet". The clock position is relative to your nose: 12 o'clock is straight ahead, 3 o'clock to your right, 6 o'clock behind and 9 o'clock to your left. Aircraft within 200 feet of your height are "same altitude". Ground traffic leaves out the height and adds the stand it is at, when BA can work it out. Parts that are not known, such as the route, are left out.

The lists show the traffic at the moment the window opened. While the window is open BA updates its traffic picture in the background every few seconds; press F5 to refresh the lists with the latest picture.

Tracking an aircraft
  1. In the TCAS Traffic window, arrow to the aircraft.
  2. Press the Applications key (or Shift+F10) to open the context menu.
  3. Choose Add to track list. You hear, for example, "UAL 123 added to track list."
  4. Later, from anywhere, press Output R. BA takes a fresh look and reads each tracked aircraft, for example "UAL123, 4.2nm, 2,000ft above, 2 o'clock, 310kts".

If a tracked aircraft has gone out of range, R reads its last known position followed by "last known". If it has not been seen yet, you hear "UAL123, not yet in range". With nothing tracked, R says "No tracked aircraft. Add aircraft to track list from the TCAS window." To stop tracking, choose Remove from track list from the same menu.

This is useful for following a friend on a network, or keeping track of the aircraft ahead of you in an approach sequence.

Note: The TCAS Traffic window is BA's own traffic list, not your aircraft's collision-avoidance system. It gives no warnings by itself. Traffic on the ground while you taxi is covered by Ground Traffic.

Traffic and resolution advisories (FlyByWire Airbuses)

On the FlyByWire A320, Headwind A330 and FlyByWire A380, BA announces the aircraft's own TCAS when its state changes: a traffic advisory, a resolution advisory, and clear of conflict.

During a resolution advisory it also tells you what to fly, because you cannot see the red and green bands on the vertical speed scale:

If the advisory strengthens or reverses, you hear the new instruction. Follow the instruction promptly with smooth control inputs, as a real crew would, and return to your clearance once you hear clear of conflict. These announcements can be muted in the Monitor Manager with the TCAS advisory row.

If something goes wrong

Approach and Landing

The last few minutes of a flight are the busiest. You need to know where the runway is, whether you are lined up with it, whether you are on the right slope down to it, and, once you are on the ground, where to turn off. BA gives you tools for every one of those questions, and almost all of them start with choosing a destination runway. Most need the navigation database, because BA has to know where the runway and its taxiways are.

Choosing a Destination Runway

What it is

The destination runway is the runway you tell BA you are going to land on. BA does not read it from your flight plan or your aircraft's FMS; you choose it yourself, in a small window. Once it is set, BA can measure your distance to it, give you an ILS report for it, fly Visual Guidance to it, and arm the landing tones for it.

When to use it

Set it as soon as you know your landing runway: at the top of descent, after listening to the ATIS, or when ATC tells you which runway to expect. You can set it again at any time if the runway changes; the newest choice always wins.

How to use it
  1. Press Input Shift+D. The Select Destination Runway window opens with the cursor in the Airport ICAO Code box.
  2. Type the four-letter ICAO code of the airport, for example EGLL. As soon as you type the fourth letter, BA loads that airport's runways. The status line says how many it found, for example "Found 4 runways for London Heathrow". If the code is wrong, it says "Airport EGXX not found in database".
  3. Press Enter. The cursor moves to the Available Runways list and the first runway is selected.
  4. Arrow up and down through the list. Each runway reads with its length, width and surface, then its localizer if it has one, for example: "Runway 27L - 3660 m long, 52 m wide - Asphalt - ILS CAT III 109.50, course 268". The course is the final approach course from the airport's approach procedure, the one on the chart. For a localizer that no procedure in your database uses, BA works it out from the localizer's heading instead, and it can be a degree or two off the chart. "ILS" means a localizer and a glideslope. "Localizer", as in "Localizer 108.70, course 152", means a localizer only: you get left and right guidance but no glideslope to capture. A glideslope that is not the usual 3 degrees is said, for example London City 27's "ILS 111.15, course 272, glideslope 5.5 degrees". So are CAT II and CAT III, for example "ILS CAT III 110.30"; CAT I, the usual kind, is not. An offset approach, whose course does not line up with the runway, is named for what it is: "LDA", as in KDCA 19's "LDA 111.35, course 147", where the runway itself is 186, or "IGS". You follow its course to a point near the runway, then turn to line up and land visually. An LDA that has a glideslope adds "with glideslope", and an IGS without one adds "no glideslope". With an MSFS 2020 database BA cannot tell these apart, so they read as ILS or Localizer. Distances follow your distance unit setting (see the Settings section below).
  5. If you want to hand-fly the flare with tones, Tab to the Manual landing assist (adds flare tones) checkbox and press Space to tick it. Leave it unticked for an approach you will fly on the autopilot or the ILS. The next section explains what it does.
  6. Press Enter (or Tab to Select and press Space). The window closes, focus goes back to the simulator, and BA confirms:
    • "Destination runway set: EGLL Runway 27L"
    • or, with the checkbox ticked, "Destination runway set: EGLL Runway 27L. Manual landing assist armed."

To close the window without changing anything, press Escape or choose Cancel.

Tip: Setting the destination also starts BA quietly fetching that airport's online taxiway names and building data in the background, so they are ready long before you land. The earlier you set it, the better.

If something goes wrong

Approach Readouts

Three one-key readouts tell you where you stand on the approach. The first two need a destination runway. Without one, BA says: "No destination runway selected. Press left bracket then shift+d to select a destination runway first."

Distance and bearing to the runway (Output Ctrl+D)

Press Output Ctrl+D for the straight-line distance in nautical miles and the magnetic bearing from you to the start of the runway:

"12.4 miles to runway 27L at EGLL, bearing 268 degrees."

The bearing is useful on a visual approach: if your heading is close to the bearing, the runway is roughly ahead of you.

Tip: While Hand Fly mode or Visual Guidance is on, the single key D gives the same distance without entering Output mode. See Hand Fly Mode.

The ILS report (Output Ctrl+I)

The ILS report is a snapshot of where you are relative to the runway's ILS: how far from the threshold, which side of the centreline, how far above or below the glideslope, and which headings to fly to join the localizer. It reads the ILS from the navigation database and your position from the simulator, so it works even if your radios are not tuned. It does not need an ILS approach to be armed on the autopilot.

Press Output Ctrl+I. If you are on the centreline (within about a tenth of a mile), you hear something like:

"6.2 nautical miles from threshold, on centerline. 40 feet below glideslope. Runway heading 273."

If you are off to one side, BA gives you the offset and three headings to choose from:

"14.0 nautical miles from threshold, 1.8 nautical miles left of centerline, 7 degrees left of centerline. 300 feet above glideslope. Fly heading 333 for 60 degree intercept, 318 for 45 degree intercept, or 303 for 30 degree intercept."

"Left of centerline" means your aircraft is to the left of the extended runway centreline as you face the runway. Pick the intercept that suits you: 30 degrees is the gentle, normal choice; 60 degrees closes the gap fastest.

Other things you may hear:

Separately from this report, BA says "Glideslope alive" on its own when your NAV 1 receiver starts picking up a glideslope signal, and "Glideslope lost" when the signal goes away. Hearing "Glideslope alive" after tuning an ILS tells you the receiver has the signal; it does not mean the autopilot has captured it. You can mute it in the Monitor Manager (Output Ctrl+M), where it is listed as Glideslope.

Approach capability (Output Ctrl+0)

On the FlyByWire A320neo, the Headwind A330-900neo and the FlyByWire A380X, Output Ctrl+0 tells you what kind of approach the autoflight system is currently able to fly, the same information the top of the aircraft's flight mode annunciator shows. You hear, for example, "Approach capability LAND 3 dual", "Approach capability LAND 3 single", "Approach capability LAND 2" or "Approach capability none computed". These aircraft also announce a change on their own while you are in flight, for example after a system failure lowers the capability.

On the other aircraft this key does nothing at the moment.

Wind at the destination

Output I, the wind readout described in Readout Hotkeys, adds the wind at your destination airport once a destination runway is set. It is a quick way to check for a tailwind before you choose a landing exit.

Visual Guidance

What it is

Visual Guidance is an audio instrument for hand-flying an approach. It is BA's equivalent of the flight director needles a sighted pilot follows: it works out what the aircraft should be doing to reach the runway centreline and a normal glide path, and plays it to you as sound. You do not need an ILS. Visual Guidance uses the runway's position and glide-path angle from the navigation database, so it works on any runway in the database, including ones with no instrument approach at all.

It is made of two tones playing together:

By default the two have different sounds: the guidance tone is a triangle wave, which sounds slightly buzzy, and the current tone is a sine wave, which sounds pure and smooth. Different sounds stop them blending into one note when they match, which is exactly when you need to hear that there are two.

The matching idea

Your whole job is to make the current tone sit on top of the guidance tone. You do not need to think about glide paths or angles; you fly the aircraft until the two tones agree.

Up and down (pitch). Listen to the two pitches. If the guidance tone is higher than the current tone, raise the nose a little. If it is lower, lower the nose. When the two are close in pitch you hear a beat: a wobble or flutter in the sound, caused by two nearly-equal notes rubbing against each other. The bigger the difference, the faster the flutter. A difference of half a degree of pitch is a clear fast flutter; a tenth of a degree is a slow, lazy wobble. When the wobble stops and you hear one steady chord, your pitch is exactly what the guidance wants.

Left and right (bank). Listen to where each tone sits between your ears. If the guidance tone is further to the right than the current tone, roll to the right. If it is further left, roll left. When both tones come from the same place, your bank matches what the guidance wants.

Both at once. The two axes are separate and you fly them together, not one after the other: roll to bring the positions together while you pitch to stop the beating, just as a sighted pilot keeps both flight director bars centred at once.

Remember what the guidance tone is telling you. It is not "where the runway is"; it is "the attitude that will get you there". When you are far left of the centreline, the guidance tone will sit to the right, asking for a right bank to turn back. As you close in, it moves back toward the middle, asking you to roll out. Follow it smoothly and it brings you onto the centreline without overshooting.

Tip: The tones are deliberately very sensitive near the matched state: small errors are clearly audible. For big corrections, such as the turn onto final, the guidance tone may sit fully over to one side. That is normal. The spoken bank callouts described below cover those big corrections.

When to use it

You do not need Hand Fly mode to use Visual Guidance. If it is on, its tone is muted while Visual Guidance runs and its spoken calls carry on.

How to use it
  1. Set a destination runway (Input Shift+D).
  2. Fly toward the runway. Visual Guidance can start from a long way out; it will lead you onto the extended centreline.
  3. Press Output Ctrl+V. BA says "Visual guidance active, runway 27L" and both tones start.
  4. Match the tones as described above. Listen for the phase callouts (below), which tell you which part of the approach you are in.
  5. At touchdown, Visual Guidance switches itself off and says "Visual guidance off". From there the rollout tones and the Landing Exit Planner take over, if you have set them up.

To switch Visual Guidance off yourself, press Output Ctrl+V again. If you press it with no destination runway set, BA says "No destination runway selected" and nothing starts.

Quick-access keys

While Visual Guidance is on, the single-letter keys of Hand Fly mode (A, S, D, H, P, B, Q and V) work with no bracket key first, plus F. F tells you the descent rate the guidance is asking for and how far you are above or below the ideal glide path, for example "target -700, 40 high" (aim for 700 feet per minute down; you are 40 feet above the path) or "target -500, 120 low". If you press F when Visual Guidance is off, BA says "Visual guidance not active".

When you press any of these keys, BA holds back its own per-second bank and centreline callouts for three seconds so your answer is not cut off.

If another program is already using one of these keys, BA tells you "Visual guidance active. Some quick-access keys unavailable; use output mode." The same readouts are still available through Output mode.

What you will hear

Phase callouts. Visual Guidance moves through phases and announces each one as you enter it:

Distance callouts. "5 miles", "3 miles" and "1 mile" from the runway threshold.

Bank callouts. About once a second, when the bank error changes, BA speaks how much more bank you need: "3 left" means roll 3 degrees further to the left than you are now; "2 right" means roll 2 degrees further right. "matched" means your bank is what the guidance wants. "On commanded path" means your bank matches and the guidance wants the wings level: you are tracking the centreline.

Centerline callouts. When your position changes by a tenth of a mile, BA says how far you are from the centreline, for example "0.4 nm left of center", or "on runway center" when you are within about 300 feet of it. Left and right here are your aircraft's position relative to the centreline.

Note: The vertical guidance is designed for a normal stabilised approach with the autothrust holding your speed. The guidance tone asks for pitch, and pitch controls your rate of descent only while something else holds the speed. If you are managing thrust by hand, keep your speed steady or the vertical guidance will feel inconsistent.

Settings

All Visual Guidance sound settings are on the Hand Fly tab of the Settings window (see The Settings Window):

If something goes wrong

Flare and Rollout Tones

What it is

The flare and rollout tones guide the very end of the landing: the last 50 feet above the runway, the touchdown, and the landing roll. They are separate from Visual Guidance and work whether or not you use it.

There are two parts:

The flare tones: two axes at once

From 50 feet above the runway (measured at the wheels) to touchdown, you hear two tones at the same time, one for each axis. They use different sounds so you can tell them apart.

The vertical tone: your sink rate. Its pitch says whether you are coming down at the right rate for your height. BA uses a smooth flare profile: at 50 feet it expects roughly a normal approach descent rate, and the expected rate shrinks as you get lower, down to a gentle 120 feet per minute at the moment the wheels touch.

This is deliberately a sink-rate tone, not a pitch target, because the right flare pitch differs from aircraft to aircraft while a good sink rate is the same for all of them.

The lateral tone: your position over the centerline. This tone moves left and right. It sits on the side you need to steer toward: if it is on your right, steer right with the rudder. It follows not only where you are but also how fast you are drifting, so if you are correctly crabbed into a crosswind and holding the centreline, it sounds centred instead of nagging you. A small band around the centre is quiet.

The rollout centreline tone

When the wheels touch, the vertical tone stops: there is no pitch task left. The lateral tone carries straight on and becomes a centreline steering tone for the landing roll. It works exactly like the Takeoff Assist tone and uses the same settings (see Takeoff Assist): steer toward the tone, or away from it if you have chosen that, until it goes quiet. If the aircraft starts to swerve, you hear which way to steer back before it leaves the runway.

You can get this rollout tone without the flare tones. As long as the setting Rollout centerline tone when a destination runway or landing exit is set is ticked (it is by default), any destination runway or any planned landing exit arms the rollout tone on its own. That includes an autoland.

How the rollout tone ends depends on whether you planned an exit:

What you will hear
How they behave
Settings

The Landing Exit Planner

What it is

Before you land, you choose the taxiway you want to leave the runway on. When you touch down, BA starts guidance automatically: it counts you down to the exit, tells you when to slow down and when to turn, steers you into the turn with a tone, and leads you off the runway until you are past the holding point. If you cannot make your exit, it finds the next one for you.

It is the landing half of taxi guidance. When it finishes, you use the normal taxi planner to get to your stand (see Taxi Guidance).

When to use it

Plan your exit during the descent or approach, once you know your landing runway. A good exit choice depends on your aircraft's landing distance, the wind and where your stand is. You can also plan on the ground before a circuit; guidance then starts on the next real landing.

How to use it
  1. Press Input Shift+X. The Landing Exit Planner window opens.
  2. Airport ICAO (Alt+A): this is filled in for you from your destination runway or, if you have not set one, from your loaded flight plan. To use another airport, type its code and press Tab. While the airport loads, the status line reads, for example, "EGLL: fetching taxiway names…" and then "EGLL: building taxi graph…".
  3. Runway (Alt+R): a list of runway directions, already set to your destination runway if you have one. If the runway BA was given is not in the list, it tells you, for example: "Runway 27R is not in this airport's runway list. Showing runway 09L instead — check the runway before you plan an exit."
  4. When a runway is selected, BA tells you how many exits it found, for example "6 exit options for runway 27L." If some exits have no taxiway mapped clear of the runway in your database, it adds "2 of them have no taxiway mapped clear of the runway."
  5. Exit taxiway (Alt+E): arrow through the exits. They are listed in order of distance from the landing threshold, nearest first. BA pre-selects a sensible one: never a turnaround, and one that leads clear of the runway if there is one.
  6. If ATC has given you a land and hold short instruction (LAHSO), tick Land and hold short (LA&HSO) of (Alt+H) and choose the crossing runway you must stop before. Each choice reads like "Runway 27 — hold point 1700 m from threshold (estimated)": BA estimates the stop point from the two runways' geometry, so treat it as a guide, not a painted line. Only runways that actually cross yours are listed. If your exit lies beyond that point, Plan Exit refuses it: "Exit B9 is at 3200 metres, beyond the LAHSO hold point at 1700 metres. Pick an earlier exit or uncheck land and hold short."
  7. Choose Plan Exit (Alt+P). The window closes and BA confirms, for example: "Landing exit planned: taxiway B5 at EGLL runway 27L, 2100 metres from threshold. Guidance will auto-start on touchdown." With a LAHSO, it adds "Land and hold short of runway 27: estimated hold point 1700 metres from the threshold."

To remove a plan, open the window again and choose Clear Plan (Alt+C). BA says "Landing exit plan cleared." Escape closes the window without changing anything.

Tip: At some airports the navigation database has few taxiway names and BA fetches the rest online. If the names arrive while the window is open, the list updates itself and BA says, for example, "Taxiway names updated for LSZH. Now 9 exits for runway 28." Your chosen exit stays selected.

Reading the exit list

Each exit reads like this:

"B5 — 2100 m from threshold (High-speed, right, 30°)"

Where the database has several entries for what is really one turn-off, the list shows it once.

If BA finds no exits at all, it says "No usable exits found on runway 27L in the database. Try another runway or update your navdata."

Note: Plan for the conditions. With a tailwind, a wet runway or a heavy aircraft, choose an exit further down the runway. BA warns you on the rollout if you are too fast for the exit, but it cannot make the aircraft stop sooner. Use Output I to check the wind at your destination before you choose.

Worked example

You are descending into an airport where you expect runway 27L. Your stand is on the north side, and the runway has a high-speed exit B5 on the right about 2,100 metres from the threshold, and normal exits B7 at 2,700 metres and B9 at 3,200 metres.

  1. You press Input Shift+D, type the airport code, choose runway 27L, and leave the manual landing assist checkbox unticked because you will autoland. BA says "Destination runway set: ... Runway 27L".
  2. You press Input Shift+X. The airport and runway are already filled in. You arrow to "B5 — 2100 m from threshold (High-speed, right, 30°)" and choose Plan Exit. BA confirms the plan.
  3. You fly the approach. The aircraft lands. Within a second you hear: "Touchdown. high-speed exit taxiway B5 in 1700 metres." At the same time, the rollout centreline tone starts; keep it quiet with the rudder.
  4. "Approaching high-speed exit taxiway B5, 500 metres." You keep braking normally.
  5. "Taxiway B5, 300 metres." This extra callout is only given for high-speed exits.
  6. "Taxiway B5, 150 metres. Slow down." "Slow down" is added because you are still faster than about 60 knots, too fast even for a high-speed exit. You brake harder.
  7. "Turn right now, taxiway B5." The steering tone swings right. You turn with the tone and let it guide you along the exit.
  8. When you are past the runway holding point you hear: "Off the runway at Taxiway B5. Stop and hold position. Open the taxi planner to set a route to your gate." You stop, call ground, and use Input Shift+Y to plan your taxi to the stand.

Now suppose you had been too fast at step 7. Instead of "turn now" you would hear "Too fast for taxiway B5. Continue to taxiway B7, 600 metres." and guidance would carry on to B7 with a new countdown.

How guidance starts

Everything the Rollout Says

Every callout between touchdown and leaving the runway, in roughly the order you meet them. Distances are spoken in metres or feet according to your setting; the feet versions are 1,500, 900 and 500 feet for the exit countdown and 1,500, 500 and 100 feet for the runway-end countdown. Any instruction you missed can be repeated with Output Ctrl+Y.

At touchdown

The touchdown sentence can end with a reminder about this landing: "LAHSO: hold short of runway 27." if you planned a land and hold short, "Sharp turn back, slow down early." for an exit marked "(sharp turn back)", or "Backtrack required, to taxiway A." for a turn-pad exit.

Approaching the exit

If BA cannot be sure which side the exit turns to, for example because the scenery draws the junction right on the centreline, it leaves the direction out and says "Turn now, taxiway B7." It never guesses a side, because a wrong side is worse than none.

Land and hold short

If you planned a LAHSO, BA counts you down to the estimated hold point whatever happens with your exit, even if you miss every exit and end up in the runway-end countdown:

When BA has to switch to another exit, it only ever picks one short of the hold point.

Changing your exit on the rollout

If ATC changes your exit while you are rolling out ("turn right at Hotel"), open the Landing Exit Planner (Input Shift+X), pick the new exit and choose Plan Exit. BA switches guidance to it: "New exit, taxiway H, 600 metres ahead." You can tick a LAHSO here too, and BA adds "Land and hold short of runway 27." A LAHSO you planned before landing stays in force; it cannot be cancelled on the roll.

BA refuses a change it cannot safely follow, says why, and keeps your current exit:

The steering tone on the rollout

During the middle of the rollout, the tone keeps you on runway heading and quiet. It only starts steering you toward the exit once you are close to it and turning its way. On an ordinary right-angle exit, it holds runway heading right up to "Turn ... now", so it never pulls you toward the exit before you should turn; after the callout it pauses briefly while you start the turn, then steers you along the exit. If you drift off the centreline while slowing down, the tone steers you back onto runway heading rather than pulling you at the exit early. Close to the exit, a drift toward the exit's side goes quiet, because you are plainly already making the turn.

Too fast, missed, or early
Leaving the runway

Exit guidance leads you down the exit taxiway until you are past the runway holding point, not just off the edge of the runway. When it ends, you hear one of these:

The runway-end countdown

When there is no exit left ahead, BA counts you down to the end of the runway instead:

The countdown ends according to what you do next:

While backtracking:

Warning: Backtracking on an active runway is something you only do with ATC permission. BA tells you how to do it safely; it does not know whether you are cleared.

Other things to know

Landing Rate and G-Force

After every landing, two Output keys tell you how firm it was. They work on every aircraft.

Both values are kept until your next landing. Before your first landing of the session, both say "No landing recorded this session.", even if you started the flight on a runway.

As a rough guide for an airliner, 100 to 200 feet per minute is a smooth landing, 200 to 400 is normal and firm, and more than about 600 is hard. A g-force around 1.1 to 1.3 g is typical.

Part 7: Networks and Integrations

Networks and Integrations

MSFS Blind Assist works alongside several other programs that many pilots already use: SayIntentions for AI air traffic control, vPilot for flying on the VATSIM network, Volanta for flight tracking, ActiveSky for weather, and an AI provider (Google Gemini or Anthropic Claude) for reading displays and describing routes. None of them is required. Each one simply adds something when it is there.

Program What BA does with it Key
SayIntentions Reads the last ATC call, shows your gate and runways, turns a taxi clearance into a taxi route Output Ctrl+S, Output Ctrl+Shift+S, Input Ctrl+Shift+Y
vPilot (VATSIM) Speaks connections, private messages, radio messages and SELCAL alerts Output Alt+V to mute
Volanta Shows Volanta's live map as text: traffic, friends, online ATC Output Shift+O
ActiveSky Richer weather in the weather windows and announcements (see the Weather chapter)
Gemini or Claude AI display reading, scene description, route briefing (see Core Concepts)

SayIntentions

What it is

SayIntentions is an AI air traffic control service. You talk to it, and it talks back like a real controller. BA reads the active SayIntentions flight on your computer so that you can:

There is no SayIntentions settings tab and no API key to enter. SayIntentions writes a small flight file on your computer while you are connected to a flight, and BA finds everything it needs in that file, including the key it uses to ask SayIntentions for the recent radio calls. If SayIntentions is not running, BA tells you so.

The keys
Key What it does
Output Ctrl+S Read the last SayIntentions ATC transmission
Output Ctrl+Shift+S Open the SayIntentions Flight Information window
Input Ctrl+Shift+Y Build a taxi route from the current SayIntentions taxi clearance

Note: Ctrl+S means different things in the two modes. In Output mode it reads the last SayIntentions transmission. In Input mode it opens the aircraft's speed window. Make sure you are in the mode you want.

The two readouts, Output Ctrl+S and Output Ctrl+Shift+S, work even when BA is not connected to the simulator, because they only read the SayIntentions flight. Building a taxi route needs your aircraft's position, so the simulator must be connected, and SayIntentions must be reachable over the internet.

Hearing the last transmission

Press Output Ctrl+S to hear the most recent call from the controller. This is handy when a long clearance went past too fast, or you were busy with a checklist.

Two kinds of message are left out on purpose:

What you might hear instead of a transmission:

The Flight Information window

Press Output Ctrl+Shift+S to open the SayIntentions Flight Information window. It is a read-only window built for looking things up quickly, not a block of text to read from the top.

How to use it:

  1. Press Output Ctrl+Shift+S. The window opens with the first section selected, and your screen reader reads the section name, its first item and how many items it has.
  2. Press Tab to move from one section to the next.
  3. Use the Up and Down arrows to move within a section. Typing a letter jumps to the next item starting with that letter.
  4. Press Escape to close the window and go back to the simulator.

The sections, each shown only when there is something in it:

Some details worth knowing:

The window deliberately leaves out the ATIS text, the METAR, the TAF, the wind and the visibility. You already get those by listening to the ATIS, or from the METAR window (Output Shift+M; see Weather). The window keeps only the runway picture and the altimeter, the things worth having on hand without sitting through the ATIS again.

If SayIntentions is not running, BA speaks the reason instead of opening an empty window.

Building a taxi route from a clearance

When the ground controller gives you a taxi clearance, BA can read it, work out the route over the airport's real taxiways, and fill in the taxi planner for you. You then check it and start guidance as usual.

How to use it
  1. Request taxi from SayIntentions and listen to the clearance as normal. Read it back if the controller expects you to.
  2. Press Input Ctrl+Shift+Y. You hear "Reading SayIntentions taxi clearance."
  3. Wait a few seconds. BA reads the recent radio calls, your position and the airport's taxiway names. The taxi planner opens, filled in with the destination, the taxiways in order, and any hold-short points the controller gave.
  4. Listen to the spoken summary. It ends with "Review the fields, then press Calculate Route to start guidance."
  5. Check the planner's fields against what you heard: the destination, the taxiway list, and the hold-shorts.
  6. Press Calculate Route (Alt+C) to start guidance.

You can also start the import from inside the taxi planner. The Fill from SayIntentions button (Alt+Y), just above Calculate Route, does exactly what Input Ctrl+Shift+Y does.

Warning: Always review an imported route before you roll. BA works hard to get it right, and it tells you about every part it could not apply, but it is reading a spoken clearance and matching it to scenery data that is sometimes incomplete. You are still the pilot. If the route does not match what you heard, fix the fields by hand before calculating.

What it fills in

An import replaces the whole route, including anything you had already set up by hand, such as an intersection departure or a CAT III hold. The clearance is the route.

Where the taxiway list comes from

SayIntentions publishes its own ground track for your taxi: the path over the pavement it expects you to follow. BA can use that track or the words of the clearance, and it chooses between them each time you press the key.

Whichever source is used, the destination and the hold-shorts always come from the clearance. The ground track carries neither.

What the summary tells you

The summary is spoken in a fixed order: the destination first, then where the route came from, then every warning, and only then the route itself. Warnings come early on purpose. If you start guidance straight away, the first turn instruction cuts off whatever is left of the summary, so the things you need to act on come first.

These are the lines you may hear, in order:

If BA cannot find any taxiways it can use, you hear "No taxiways from the clearance matched this airport. Using shortest path." (or the same about the ground track). Check that route very carefully against the clearance.

If you press Input Ctrl+Shift+Y again while an import is still running, you hear "SayIntentions taxi route already being built." Wait for the first one to finish.

A worked example

You are parked at your departure gate. SayIntentions Ground says: "Taxi to runway 27 via A, B, hold short of runway 22."

  1. You read back the clearance.
  2. You press Input Ctrl+Shift+Y. You hear "Reading SayIntentions taxi clearance."
  3. The taxi planner opens and BA says something like: "SayIntentions route to Runway 27. Route from SayIntentions ground track. Via A, B. Hold short of runway 22 after B. Review the fields, then press Calculate Route to start guidance."
  4. You Tab through the planner: destination Runway 27, taxiways A then B, a hold short of runway 22 after taxiway B. It matches what you heard.
  5. You press Alt+C to calculate the route and start guidance.
Arriving at your gate

After landing, SayIntentions usually has an arrival gate assigned. On an arrival with an assigned gate, the import only ever routes you to a gate, never to a runway, even if the controller mentioned the runway you just vacated.

If this scenery genuinely has no stand that matches the gate SayIntentions assigned, BA says so by name and stops, rather than guessing. You hear something like "SayIntentions assigned Gate A2, but no matching stand was found at KSTL. Pick the destination gate in Taxi Assist, then Calculate." Open the destination list in the taxi planner and search for the gate yourself. The planner's own search can often find a stand under a slightly different name.

BA also finds the gate even when the scenery says your aircraft is too big for it. Sceneries often get stand sizes wrong, so a gate the controller actually cleared you to is not hidden just because the size data disagrees.

Settings

The one SayIntentions setting lives on the Taxi Guidance tab of Settings, under the SayIntentions heading at the bottom:

If something goes wrong

Tip: SayIntentions can also act as the datalink provider for the FlyByWire aircraft's DCDU. That is set up in the aircraft, not in BA. See Airbus Aircraft.

VATSIM

What it is

VATSIM is a free online network where pilots fly together with real people acting as air traffic controllers. You connect with a program called vPilot. vPilot shows private messages, radio text and SELCAL alerts on screen, which is hard to follow without sight.

BA can speak those events for you through your screen reader, using a small plug-in it installs into vPilot for you. This replaces the old separate "vPilot to TTS" program, so you only need BA.

BA also uses VATSIM's public data in other places, whether or not you fly on VATSIM yourself:

What you will hear

Once set up, BA speaks five kinds of vPilot event:

Event What you hear
Connected to the network "Connected as" followed by your callsign
Disconnected from the network "Disconnected from network"
Private message "Private message from" the sender, then the message
Radio message on a frequency you are tuned to The sender, then the message
SELCAL alert "SELCAL alert from" the sender

These announcements wait their turn behind other speech. VATSIM chatter never interrupts something more urgent, such as a landing callout or a taxi instruction. On a very busy frequency BA may skip a message rather than let a backlog delay a more important warning.

BA only listens. It cannot send messages, tune frequencies or squawk on VATSIM; you still do those in vPilot.

Setting it up
  1. Install vPilot if you have not already.
  2. In BA, open Settings from the File menu and go to the VATSIM tab (the third tab, after Weather).
  3. Tick Announce VATSIM events from vPilot.
  4. Underneath are five checkboxes, one for each event: Connected to the network, Disconnected from the network, Private messages, Radio messages (on-frequency) and SELCAL alerts. All five are ticked by default. Untick any you do not want spoken.
  5. Press OK. BA installs its plug-in into vPilot and tells you what happened as part of the "Settings saved" confirmation.
  6. Restart vPilot. vPilot only loads plug-ins when it starts, so you must close and reopen it once after the first install.

vPilot does not need to be running for the install to work. BA also checks the plug-in every time it starts, so an update to BA never leaves an old plug-in behind. That check is silent unless something needs your attention.

The status box

The VATSIM tab has a read-only vPilot status box you can Tab to and read with your screen reader. It always tells you what to do next. You may read:

The box refreshes when you open the tab and when you tick or untick the main checkbox.

Muting the chatter

On a busy frequency you may want quiet for a while. Press Output Alt+V to mute or unmute VATSIM announcements without opening Settings.

The mute lasts until you close BA. Every time you start BA, VATSIM announcements are unmuted again, so a mute from your last flight is never carried into the next one by accident. Alt+V works even before BA has connected to the simulator.

If you used vPilot to TTS before

If you used the old "vPilot to TTS" program:

If something goes wrong

Turning VATSIM announcements off stops them at once, but leaves the plug-in in vPilot. That is deliberate and harmless; with BA not listening, the plug-in does nothing.

Volanta

What it is

Volanta is a flight tracker. It logs your flights and shows a live map of other Volanta users and online network pilots. The map is visual, so BA reads it for you and turns it into lists: the aircraft around you, your Volanta friends, and the online air traffic controllers.

BA reads Volanta's public web map by itself, in a hidden browser, so the Volanta app does not need to be open. It can stay in the notification area logging your flights.

When to use it
Opening the window

Press Output Shift+O, or choose Volanta from the Extras menu. The Volanta Live Map window opens. It works even when BA is not connected to the simulator.

The window has four tabs: Traffic, Friends, ATC and Connection. On each list tab the order of controls is: the list first, then the details for the selected item, then (on Traffic and Friends) the major-city checkbox, then the status line and the filters.

You need an internet connection and the Microsoft Edge WebView2 runtime, which is part of Windows 11. When the window first connects you hear "Connected to Volanta's live map." If the connection drops you hear "Lost the connection to Volanta's live map."

The Traffic tab

Every aircraft on Volanta's map around you, nearest first, one line each. A line gives the callsign, the clock position and distance from you, how far above or below you it is (or "on the ground"), whether it is climbing or descending, its speed, its type, who is flying it, its route, and where it is. For example the location might be "Location: Pike Lake, Wisconsin, United States", or "Location: over Lake Michigan" over water.

Below the list, the details box shows everything known about the selected aircraft, one item per line.

The filters:

Report location to nearest major city changes each location to how far and which way the aircraft is from the nearest major city, for example "92 miles west of Wichita, Kansas, United States". A "major city" uses your own Minimum Population for Major Cities and Major Cities Range from the GeoNames tab of Settings (see Location Info and Nearest City). The checkbox starts unticked every time you open the window.

The Friends tab

Once you are logged in to Volanta, this tab lists your Volanta friends. Friends who are flying come first, nearest first, placed like a traffic line. Then friends who are online in Volanta, with their status in words, for example "cruising over United States" or "taxiing to gate B12 at KGRB". Offline friends come last. It has its own Report location to nearest major city checkbox, which works on its own, separately from the Traffic tab's.

The ATC tab

Online VATSIM and IVAO controllers, nearest first, with their frequency. The details box adds the controller's name, the airport, when they came online and the ATIS text.

Its distance filter runs from 10 nautical miles to Any distance, and you can tick VATSIM and IVAO separately. The search finds an airport's controllers wherever they are: type an airport code, callsign, controller name or frequency. For US airports, "KATL" also finds stations VATSIM names without the K, such as ATL_TWR.

The Connection tab and logging in

The Connection tab shows whether the web map is running, whether you are logged in, what it downloaded in the last minute, and what has been received. It also has a short About the Volanta live map text, and one button.

Logging in is optional. Without it you get the traffic and ATC, but no friends list, and your own flight may appear in the traffic list. To log in:

  1. Go to the Connection tab and press Log in to Volanta.
  2. Volanta's own login page opens in a window of its own. Log in there.
  3. The login window closes by itself once you are logged in, and you hear "Logged in to Volanta." (Escape closes it sooner.) Your login is kept for next time.

The same button then reads Log out of Volanta. Pressing it logs you out and you hear "Logged out of Volanta."

How the lists update

Note: The map only downloads while the Volanta window is in front. Five seconds after you switch to another window it pauses, and it catches up within a few seconds when you come back. While it runs it uses roughly 415 megabytes of internet data an hour, so keep it closed when you do not need it if your data is limited.

If something goes wrong

ActiveSky

If you use the ActiveSky weather add-on, tick Enable ActiveSky integration on the Weather tab of Settings (off by default) and BA reads richer weather from it. Everything about it is in ActiveSky in the Weather chapter.

AI Providers

BA can use Google Gemini or Anthropic Claude, with your own key, to read cockpit displays aloud, describe the scene outside, and write a route briefing. BA always uses exactly the provider and model you chose. Setting it up on the AI tab is described in AI Display Reading and Scene Description; for the briefing, see The AI Route Briefing.

Part 8: Aircraft Guides

Everything you have read so far works in every aircraft. This part covers what changes in each one: how BA lays out its cockpit, the special windows it adds, its own callouts, and the quirks worth knowing before your first flight. The full key list for each aircraft is in the Hotkey Reference and in File, Hotkey List; the sections below pick out the highlights.

These guides do not teach you to fly the aircraft itself. For engine starts, flows and speeds, use the maker's own documentation; the standard procedures it describes are exactly what you carry out through BA's panels. General Flying Concepts gives a gentle overview of airliner flying.

Airbus Aircraft

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:

, "), 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

Boeing Aircraft and the MD-11

This chapter covers the PMDG 737 (NG3 family), the PMDG 777, the HorizonSim 787-9, the iFly 737 MAX8, the BlueBird 757-200 and the TFDi Design MD-11, describing only what differs on each. The complete key list for every aircraft is in the Hotkey Reference, and the shared autopilot window behaviour is in Autopilot Windows. All but the HorizonSim 787-9 have a First Officer on Output Shift+C.

PMDG 737 (NG3)

BA supports the whole PMDG 737 NG3 family — the 737-600, -700, -800 and -900 — with one set of panels. The panels, the autopilot windows, both CDUs and the EFB all work on every variant.

Before you fly

The PMDG 737 talks to BA through PMDG's SDK data broadcast, which PMDG ships switched off; until it is on, the CDU window and most cockpit readouts stay empty. It is set once per variant, in that variant's 737_Options.ini. BA checks every installed variant for you and opens the PMDG 737 SDK setup window when lines are missing; see The PMDG SDK Setup Check. The PMDG 737 does not need the MobiFlight WASM module.

How the panels are organised

Press Ctrl+1 for the Sections list and Ctrl+2 for the Panels list. The 737 has five sections:

A few panels deserve a word:

The MCP panel holds the engage buttons — the flight directors, autothrottle arm, bank limit, disengage bar, CMD A and B, CWS A and B, Approach and VOR LOC. The heading, speed, altitude and vertical speed values are not typed on the panel; you set them with the autopilot windows below.

Autopilot: the MCP windows

All in input mode:

Type a value and press Enter to set it. The windows stay open afterwards, so you can enter several values in a row. When the MCP value changes, BA reads it back, for example "MCP: heading 270" or "MCP: altitude 12000 feet".

In the heading, speed, altitude and vertical speed windows, a button press that works is confirmed three ways: your screen reader reads the button's new label, and you hear the MCP light, such as "MCP: Level Change: engaged", and the mode change on the FMA, such as "FMA: Pitch: MCP SPD". BA adds nothing, so none of them is cut off. If a press changes nothing, BA reads the button back about 3 seconds later, for example "Level Change Off". Altitude Intervene, and Speed Intervene outside VNAV, show no state, so pressing one is confirmed straight away, for example "Altitude Intervene pressed".

To read the MCP without opening anything, use output mode: Shift+H says, for example, "Heading 270, HDG SEL"; Shift+S says the speed with ", LVL CHG" when level change is on, or "Speed managed by FMC" when the window is blank; Shift+A adds VNAV, LVL CHG or ALT HOLD; Shift+V says "VS -1500 feet per minute, engaged" or "Vertical Speed window blank".

The CDU

Press Input Shift+M to open the PMDG 737 CDU window. The 737 has two CDUs; the CDU selector at the top switches between Left (Captain) and Right (First Officer).

The status line says CDU Connected, CDU Not Powered or CDU Not Connected. If it never connects, check the SDK setup above.

FMC Settings offers alternate line select keys (F1 to F12). Its enhanced PROG-page distance announcements apply to the 777 only, not the 737.

The EFB

Input Shift+T opens the Captain's tablet and Input Ctrl+Shift+T the First Officer's. The window is titled PMDG 737 EFB and works like the other EFB windows described in Aircraft EFBs. You get the whole tablet: Dashboard, Preferences, Navdata, Performance, Ground Ops, Weights and Balance and Manuals. Nothing needs installing in your Community folder, and no simulator restart is needed.

Some useful details:

Special windows and readouts
The Engine displays window

Output Alt+E opens Engine displays: the two engine display units in the middle of the panel, read straight from the aircraft, no AI needed. Press Tab to move through:

  1. Upper display and 2. Lower display: two lists that follow the real displays. The first line names what the display shows, for example "Upper display: primary engine page" or "Lower display: SYS page"; a page BA does not read is only named, such as "navigation display", "blank" or "off". The lines after it are the page's rows, in the display's order and wording, both engines on one line, engine 1 first: "N1: 21.0, 21.0", "EGT: 466, 466", "FF: 0.67, 0.67", "Alerts: engine 1 LOW OIL PRESSURE", "FUEL LB: 1: 8.63, CTR: 7.81, 2: 8.63, TOTAL: 25.1" on the upper display, and N2, fuel flow, oil pressure, temperature and quantity and vibration on the lower. Fuel and fuel flow are in thousands, as printed, in KG if PMDG is set to kilograms. A colour shows only when it is not normal, after its engine's value, as in "EGT: 960 red, 466", and so do messages such as REV, TAI, ENG FAIL, X-BLD START and LO. A reading the display leaves empty is blank. The lists update every second without losing your place.
  2. MFD ENG and 4. MFD SYS: choose the lower display's page; BA reads back what it shows.
  3. Lower DU Captain: ENG PRI, NORM or ND, as on the panel. The displays follow PMDG's logic: on ND the engine pages share the upper display ("compact engine page"); back on NORM the lower display stays blank until you press MFD ENG, sometimes twice.
  4. Fuel Flow Used and 7. Fuel Flow Reset, as in the Instruments panel.
  5. N1 SET: 2, 1, AUTO or BOTH.
  6. Manual N1: type the N1 reference and press Enter, as with the Instruments panel's Manual N1 button. Tab skips it while N1 SET is on AUTO.

Escape closes the window. On ground power the displays stay blank for about half a minute while they start, as in the real aircraft, and the lists say so. If BA cannot read the displays, Alt+E reads the upper display with AI instead, without saying anything first; while BA is still finding them, the window opens and says "Engine displays starting".

The Navigation display window

The navigation display (ND) is the Captain's second screen, beside the PFD: a moving map of the route ahead, with the aircraft's speeds and the wind in the top corners, the next waypoint at the top right, and whatever the map buttons add: navaids, fixes, airports, traffic. Output Alt+N opens Navigation display, read straight from the aircraft, no AI needed. It shows what the Captain's ND shows right now, so it is also a way to learn what the ND looks like and what each knob and button does to it.

The four modes. The mode knob on the EFIS control panel turns the ND into one of four pictures:

The list. The first item in the window, Captain ND, lists the screen from top to bottom, each line starting with where it sits, in the ND's own words. On the ground before departure it might read:

What the map lines name:

What the list leaves out. Three pictures on the ND are not described, only whether they are on:

In APP and VOR. These two pictures are heading-up: the top of the screen is where the nose points, so the top centre prints the heading, "Top centre: HDG 268 MAG", and every "left" or "right" below is measured from the nose. The header, the top left, the bottom corners and the messages read as in MAP. In place of the map, the list has the approach picture, and what is drawn across the compass starts with "Centre:". With an ILS tuned in APP it might read:

If a PMDG update changes how the ND draws these pictures and BA no longer recognises them, the list says "ILS data: not read: PMDG file not recognised" in APP, or "VOR data: not read: PMDG file not recognised" in VOR, between the top centre line and the bottom corners. MAP and PLN still work. In the same way, if BA no longer recognises the bearing pointers and POS, the list says "Pointers and POS: not read: PMDG file not recognised" wherever the ND would draw them.

The list updates every second without losing your place, and speaks only when you move through it.

The controls. Press Tab after the list to reach them:

  1. Mode: APP, VOR, MAP or PLAN, as on the EFIS panel.
  2. Range: 5 to 640 nautical miles. In MAP that is the distance to the compass arc ahead; centred, the arc around the aircraft covers half of it.
  3. CTR: changes the map in three presses: centred (the aircraft in the middle, the full compass rose around it), then centred with the vertical situation display (VSD) at the bottom, then back to normal. The button shows which: "CTR: normal", "CTR: centred", "CTR: VSD on".
  4. TFC, WXR, STA, WPT, ARPT, DATA, POS, TERR: the map buttons, each showing on or off. TFC shows traffic, WXR the weather radar picture, STA navaids, WPT fixes (up to range 40), ARPT airports, DATA each waypoint's constraint and time, POS the lines toward the VORs and ADFs and the IRS and GPS positions, TERR the terrain picture. The window does not describe the weather or terrain pictures, only that they are on (see "What the list leaves out" above).
  5. VOR/ADF 1 and VOR/ADF 2: VOR, OFF or ADF, the bottom corners' switches.

When you press a button, its label changes to the new state as the aircraft reports it, and your screen reader reads it, for example "STA: on". If the press does not take, the label stays as it was, and after 3 seconds BA says the state that stayed, for example "STA off", so a press is never silent. The EFIS control panel in the panels is unchanged; CTR and the map buttons are in this window. Escape closes it.

Output Ctrl+W says the active waypoint as the ND's top right shows it, "EMPAD, 1533.3Z, 6.8 NM", or "No active waypoint", even when no display is showing the ND.

If BA cannot read the ND, Alt+N describes it with AI instead, without saying anything first; while BA is still finding it, the window opens and says "Navigation display starting".

The Primary flight display window

The primary flight display (PFD) is the Captain's main flight instrument, the screen in front of the Captain. It shows how the aircraft is flying right now: the speed on a tape down the left side, the attitude in the middle (how far the nose is above or below the horizon, and how far the wings are banked), the altitude on a tape down the right side with the vertical speed beside it, the heading along the bottom, and the flight mode annunciator (FMA) across the top. Output Alt+P opens Primary flight display, read straight from the aircraft, no AI needed.

How the PFD shows numbers. The speed and the altitude are each a ruler that slides up and down behind a fixed box. The box in the middle prints the current value; the ruler above the box holds higher values, below it lower ones. Marks on the ruler, called bugs, show values that matter, such as the speed you selected on the MCP, V1 or a flap speed. A bug sits on the ruler at its value, so as the aircraft speeds up the ruler slides down and the bug slides toward the box. Coloured stretches of the ruler, bands and bars, mark speeds or altitudes to stay away from. Only part of each ruler is visible at a time. The list says where each bug or band is compared with the box: "selected speed bug, 150, 10 below" is 10 knots below the current speed, and "at the current speed" means it is level with the box. A bug whose value is off the visible part is not drawn, except a few that PMDG parks at the end of the ruler, which the list gives as "at the top edge" or "at the bottom edge". The heading scale along the bottom works the same way, sideways: "3° right" of the heading. The ruler's own numbers are never listed.

The list. The first item in the window, Captain PFD, lists the screen part by part, each line after the FMA starting with the part it is in, in the PFD's own words. On final approach on an ILS with the autopilot on, flaps 15 and about 1,500 feet above the ground, it might read:

When an instrument fails, or has no data yet, PMDG removes it and draws an amber flag in its place, and the list puts the flag there too: "Speed tape: SPD flag", "Attitude: ATT flag" (before the IRS is aligned), "Altitude tape: ALT flag", "Vertical speed: VERT flag", "Heading: HDG flag", and FPV, F/D, RA, LOC, G/S and DME in the attitude. "Attitude: PULL UP" and "Attitude: WINDSHEAR" are listed where PMDG draws them.

Some states replace the whole list with one line: "Captain PFD: off" while the displays are dark, "Captain PFD: not on any display" when the display selectors have moved it off every screen, "Captain PFD: classic EFIS display, not read" if the Captain's screen switches to PMDG's classic EFIS look, "Primary flight display starting" while BA finds it, and "Primary flight display stopped" and the reason when it cannot read it for a moment. The list updates every second without losing your place, and speaks only when you move through it.

What the list leaves out: the ruler's numbers, where the single-cue flight director points, the angle of attack dial's arc, the heading marks along the horizon, and the FMC's runway line in the approach info.

The controls. Press Tab after the list to reach them, all on the Captain's side:

  1. MINS mode: RADIO or BARO, as on the EFIS panel. PMDG moves the First Officer's selector with it, so you may hear the First Officer's line as well.
  2. Minimums: type the minimums in feet and press Enter. BA turns the knob and says what the PFD then shows, "Minimums: BARO 300", with ", not shown" when the minimums display is off. The EFIS Captain panel's Captain Minimums field does the same. Both need this reader: without it they say "Minimums need the PFD reader".
  3. MINS RST: on the 737 this button turns the minimums display on or off; with no minimums set it sets BARO 200 or RADIO 50. BA says what the PFD then shows, "Minimums: BARO 200" or "Minimums: off".
  4. Baro units: IN or HPA.
  5. Altimeter: type the setting and press Enter, as in the Ctrl+B dialog: "Altimeter: 1013, 29.91".
  6. STD, FPV, MTRS and Flight director (the Captain's FD switch): each shows on or off as the aircraft reports it, and your screen reader reads the new state when you press it. If the press does not take, the label stays as it was, and after 3 seconds BA says the state that stayed, for example "FPV off". STD also gets the altimeter callout, and waits with "Still setting altimeter, please wait." while the altimeter knob is turning.
  7. Speed reference: SET, AUTO, V1, VR, WT, VREF or BUG, the speed reference selector.
  8. Speed reference value: with the selector on V1, VR, WT, VREF or BUG, type the value and press Enter. BA turns the knob until the PFD shows it and says it, "V1 140". Tab skips the field on SET and AUTO.

Escape closes the window, and a speed reference value still turning stops.

What BA says by itself. Each message as it appears and goes, "PFD message: ALT DISAGREE", "PFD message gone: ALT DISAGREE", including the flags that replace an instrument, "PFD message: SPD". WINDSHEAR and PULL UP are not spoken, since the aircraft calls them out. Nothing interrupts anything else, and BA is quiet while the displays are dark, while the Captain's PFD is on no screen, and for the first ten seconds after the displays light up. Mute PFD messages in Ctrl+M to silence all of it, BA's own "PFD announcements stopped", "unavailable" and "resumed" messages included.

If BA cannot read the PFD, Alt+P describes it with AI instead, without saying anything first. With PMDG's classic EFIS look on the Captain's screen, it says "Classic EFIS is selected, falling back to AI reading", then uses AI. While BA is still finding the PFD, the window opens and says "Primary flight display starting".

With an AI provider set up, the other output mode keys describe the displays, moving the camera for you as described in AI Display Reading: Alt+S the lower display unit, and Alt+I the standby (ISFD); Alt+P, Alt+N and Alt+E use AI only when BA cannot read those displays itself. Alt+S names which page the lower display is showing first, since it can show engine data or a navigation display.

Aircraft-specific hotkeys and callouts

Highlights (the full list is in the Hotkey Reference):

What BA announces by itself:

Some engine messages come from three different places in the cockpit, and you hear each of them, for example during an engine start or on landing:

What you hear Where it comes from
"Upper DU alert: engine 1 START VALVE OPEN" The message printed on the upper engine display, as the crew sees it.
"Engine 1 REVERSER: on" The amber light on the overhead engine panel.
"Engine 1 Start Valve: Open" The valve's real position from PMDG's data; no cockpit light shows it.
Things to know

PMDG 777

BA supports the PMDG 777 variants — the 777-200ER, 777-200LR, 777F freighter and 777-300ER — with one set of panels, three CDUs, the EFB, an MCP set of windows and a System Display that reads the synoptic pages as text.

Before you fly

The 777 needs the same one-time SDK setup as the 737, in each variant's 777_Options.ini, plus the extra EnableCDUBroadcast.2=1 line for its centre CDU. BA checks for you and opens the PMDG 777 SDK setup window; see The PMDG SDK Setup Check. The 777 does not need the MobiFlight WASM module.

How the panels are organised

The 777 has seven sections:

Things that help when you are finding your way:

Autopilot: the MCP windows

All in input mode:

The output mode readouts work as on the 737: Shift+H, Shift+S, Shift+A and Shift+V, including the HDG/TRK mode and the VS/FPA state. Turning a hardware MCP knob also speaks the new value.

The CDU

Input Shift+M opens the PMDG 777 CDU window. The CDU selector offers Left (Captain), Center and Right (First Officer). Everything else works as on the 737 CDU. The 777's page keys are Alt+I Init Ref, Alt+R RTE, Alt+D Dep/Arr, Alt+A Altn, Alt+V VNAV, Alt+F Fix, Alt+G Legs, Alt+H Hold, Alt+O FMC Comm, Alt+P Prog, Alt+M Menu, Alt+N Nav Rad, Alt+E Execute and Alt+C CLR/DEL. The alternate line select keys and enhanced distance announcements in File, FMC Settings apply here too.

The EFB

Input Shift+T opens the Captain's tablet and Input Ctrl+Shift+T the First Officer's, in a window titled PMDG 777 EFB. The 777 tablet is the same application as the 737's, so everything said in The EFB for the 737 applies: Dashboard, Preferences, Navdata, Performance, Ground Ops, Weights and Balance and Manuals, all readable and usable.

The System Display

The real 777 has synoptic pages on its lower display. BA gives you the same pages as text, read live, with no AI needed.

  1. Open the Displays section (Ctrl+1) and the System Display panel (Ctrl+2).
  2. Choose a page in the System Display Page list: Engine, Status, Electrical, Hydraulics, Fuel, Air, Doors, Gear or Flight Controls.
  3. Press Ctrl+3 to move to the status display and arrow through the lines. They refresh by themselves while you read.

What each page shows:

Weights and fuel are given in both pounds and kilograms, for example "85000 pounds (38555 kg)". Some things simply are not available from the aircraft, so they are not on these pages: oxygen, water, brake temperatures, tyre pressures, APU details, generator loads and the EICAS message text.

Aircraft-specific hotkeys and callouts

The automatic announcements are the same family as the 737's: MCP values and modes (with FLCH, HDG HOLD, VS/FPA and LOC), Master Warning and Caution, annunciators on and off, V-speeds as entered, speed brake at rest, flaps, APU, IRS, altimeter, COM and squawk changes. Stabiliser trim is spoken in units, matching the FMC and the control stand indicator, to the nearest quarter unit: "Trim 5.25 units".

Things to know

HorizonSim 787-9

BA supports the HorizonSim 787-9 in both MSFS 2020 and MSFS 2024. It reads the FMC and the alerting system straight from the aircraft's own displays.

Before you fly

No Community folder bridge and no SDK file are needed. Older versions of BA installed a bridge package for the 787; BA now removes it automatically if it finds it.

Install the free MobiFlight WASM module all the same (see Installing). The FMC, the EICAS and most controls work without it, but a number of switches are worked through it: the batteries, the engine and APU generators, the avionics master, probe heat, antiskid, the logo and wing lights, the bleed air and hydraulic pump switches, and the altitude intervention (Alt INTV) button. Without the module those do nothing, and on the 787 BA does not warn you, so if one of them never moves, check MobiFlight first.

The FMC window needs the aircraft's displays powered, and the CDU showing on one of the multi-function displays (it appears on the third MFD by default).

How the panels are organised

Some highlights:

Autopilot: the MCP windows

All in input mode:

Turning an MCP knob on your own hardware speaks the new selected value, so you get the same confirmation whether you use BA's windows or a physical panel.

The FMC

Input Shift+M opens the 787-9 FMC window. It works like the PMDG CDU windows: Up and Down arrow read the lines, Page Up and Page Down change pages, Ctrl+1 to 6 and Alt+1 to 6 are the line select keys (or F1 to F12 with the alternate keys from File, FMC Settings), Alt+S goes to the scratchpad and Enter sends, and Alt+Home goes back to the display.

The 787 adds:

The status line tells you what is wrong if the screen is empty: "FMC not connected — load the HorizonSim 787 and power its displays." or "FMC connected — show the CDU on an MFD screen (it renders on MFD 3 by default)."

The EFB

There is no EFB support on the 787. Its tablet's input fields cannot be filled in from outside the simulator, so it could not be made usable. Input Shift+T says "787 EFB not available." Use The Flight Planning Window (Shift+E) and SimBrief for planning instead.

Special windows: EICAS and the synoptic display

The 787 does not need an AI key to read its main engine and alert display:

With an AI provider, Output Alt+P, Alt+N and Alt+I describe the PFD, navigation display and standby instrument. On the 787 BA does not move the camera for you, so first set the simulator to a cockpit view where those displays are on screen.

Aircraft-specific hotkeys and callouts

Automatic announcements include Master Caution and Warning, autopilot modes, hydraulics, anti-ice, the IRS ("IRS Left On", "IRS aligning", "IRS aligned"), selected MCP values, and the usual altimeter, COM and squawk changes. Some one-off events have their own short callouts: "TOGA Active", "Autopilot Disconnected", "Glideslope active" when the approach captures the glideslope, "Fuel Balance Fault", and "Fire Bottle 1 discharged" (or 2) and "Cargo Fire Discharged" after a fire bottle is fired.

Things to know

iFly 737 MAX8

BA connects to the iFly 737 MAX8 through iFly's own official SDK, which comes with the aircraft. It reads the aircraft directly and sends commands through the iFly plugin.

Before you fly
How the panels are organised

Highlights:

Autopilot: the MCP windows

All in input mode:

Output Shift+S reads blank when the FMC owns the speed.

The FMC

Input Shift+M opens the iFly 737 FMC window, laid out like the PMDG 737 CDU. The CDU Unit list switches between Left (Captain) and Right (First Officer).

The EFB

Input Shift+T opens the iFly SP1 tablet, titled iFly 737 EFB, in a built-in browser. It loads by itself — there is no address or Connect button — and says "iFly EFB loaded." The tablet's own pages are proper web pages, so your screen reader reads them normally: Performance, Navigraph and SimBrief, Payload and Balance, Ground Services (including pushback), Doors, Failures, Cabin Voice and Settings. F5 reloads.

Fuel and payload on the iFly are set from the EFB's Payload and Balance page.

If the tablet cannot be reached — the simulator is not running, the aircraft is still loading or the iFly EFB program has not started — the window shows a message explaining why and puts focus on a Retry button. Press it once the EFB is ready.

Aircraft-specific hotkeys and callouts

What BA says by itself:

Things to know

BlueBird 757-200

BA supports the BlueBird Simulations 757-200, with either engine type, with one set of panels that follows the real cockpit, MCP value windows and an autopilot window, an altimeter and minimums window, a nav radios window, both CDUs read as text, BlueBird's tablet read aloud and operated like a web page, windows that read the ADI, the upper EICAS, the lower EICAS and the EHSI straight from the aircraft, spoken flight mode annunciations, ADI flags and EICAS messages, and a First Officer. Read Things to know before your first flight.

Before you fly

The 757 needs two things running besides the simulator:

The aircraft always loads cold and dark, wherever you start. Bring it up from the panels, let the First Officer run its Power Up flow, or load one of BlueBird's cockpit presets on the tablet (the Aircraft app's Cockpit presets page in the EFB window). With BlueBird's Initial chocks in place setting on, the wheel chocks are on at every load: remove them on the tablet's Ground services page before you taxi. The Status panel's Chocks row says where they are.

BlueBird's own settings, such as your SimBrief ID, rudder or tiller steering and the callouts, can be changed with the simulator closed: see BlueBird's settings.

How the panels are organized

Press Ctrl+1 for the Sections list and Ctrl+2 for the Panels list. Every regular switch, knob and button of the cockpit is on a panel, named as on the aircraft and grouped as in the real cockpit. In each section the panels follow the preflight flow, and inside a panel the controls you use most come first. The 757 has six sections:

The aircraft comes with Pratt & Whitney or Rolls-Royce engines, and BA shows only what your aircraft has. It tells the two apart by the letters PW or RR in the aircraft's title. The Engines panel lists the fuel control switches of your engine type, and the Electronic engine control (RR) panel is there only on a Rolls-Royce. A livery whose title names neither gets both sets.

A few panels deserve a word:

How the controls behave:

Autopilot: the MCP windows

All in input mode:

Type a value and press Enter. Each window stays open for the next value, and Escape closes it. About a second later BA reads the value back from the MCP: "Heading 090", "Speed 250", "Altitude 12000" or "Vertical speed minus 1500". You hear what the MCP took, not what you typed, so a different number means the aircraft did not accept yours. BA sets a speed by turning the MCP's speed knob for you, which takes a few seconds; it checks the result and corrects it before it speaks.

Mach. In the speed window, type a Mach number as 0.78, .78 or M.78. If the MCP is showing knots, BA presses IAS/MACH for you first, then sets the Mach and reads it back: "Mach 0.78". A speed in knots typed while the MCP shows Mach changes it back the same way. When the aircraft does not change over, as on the ground, you hear "IAS/MACH changeover is not available now".

When VNAV has the speed. While VNAV controls the speed the MCP's speed window is blank, and the box in the speed window takes no value. The Speed Intervene button shows which it is: "Speed Intervene: Window blank" or "Speed Intervene: Window open". Press it to open the window, then type your speed.

The buttons are the MCP's own, and each one with a light shows it, for example "LNAV: On"; HDG SEL and IAS/MACH have no light and show none. Pressing one is the same as pressing it on the MCP panel: about a second and a half later you hear its light, for example "LNAV on", or at once "HDG SEL pressed". Alt and the button's underlined letter presses it from anywhere in the window.

The 757 has no altitude intervene: the MCP panel's ALT SEL Push button does nothing in BlueBird's aircraft. For a step climb, set the new altitude on the MCP and enter it as the cruise altitude on the CDU's CRZ page.

Output Shift+H, Shift+S, Shift+A and Shift+V read the same four values without opening a window, followed by the MCP mode buttons that are lit: "Heading 090, LNAV", "Speed 250, SPD", "Altitude 12000, ALT HOLD". These are the button lights, so an armed mode whose button is lit is named too, and heading select, which has no light, names nothing. In Mach mode Shift+S says "MCP Mach 0.78", and with the window blank "MCP speed window blank. Speed Intervene opens it." They read the MCP's own values, never the simulator's autopilot values, which disagree with BlueBird's MCP.

Input Ctrl+P opens the 757 Autopilot window. It starts on a list, Flight mode annunciator, with the four parts of the FMA as the ADI shows them: "A/T: SPD", "Roll: LNAV, armed LOC", "Pitch: VNAV PTH, armed G/S", "AFDS: CMD". A part with nothing showing reads none. The same four lines start the ADI window (Output Alt+P). Tab from the list to the buttons, or press a button's key from anywhere in the window; your screen reader says each button's key when you land on it. The buttons and their keys, in order:

Button Key
CMD L Alt+L
CMD C Alt+C
CMD R Alt+R
A/T Arm Alt+A
Captain F/D Alt+F
F/O F/D Alt+O
THR Alt+T
SPD Alt+S
LNAV Alt+N
VNAV Alt+V
FLCH Alt+H
HDG HOLD Alt+D
ALT HOLD Alt+E
V/S Alt+Y
LOC Alt+G
APP Alt+P
Speed Intervene Alt+I
A/T Disconnect Alt+X
A/P Disconnect Alt+B

Each button shows its state, for example "CMD L: On" or "A/T Arm: Off". The mode and CMD buttons show their light, and A/T Arm shows whether the autothrottle is armed, as the aircraft holds it. A press is the cockpit's own click, and the button then shows the new state. If the aircraft does not take the press, you hear so about a second and a half later, for example "CMD L did not engage" or "LNAV did not disengage"; for A/T Arm it is "A/T Arm did not arm" or "A/T Arm did not disarm". Speed Intervene, A/T Disconnect and A/P Disconnect say "… pressed". A/P Disconnect is the button on the Captain's yoke: it disconnects the autopilot, and a second press silences the warning. The MCP's disengage bar is on the MCP panel only. Escape closes the window.

What BA says by itself about the autopilot is listed under Aircraft-specific hotkeys and callouts.

Altimeters and minimums

Input Ctrl+B opens the Altimeter and minimums window:

Escape closes the window. Output B reads the same: "Altimeter: 1018, 30.05. DH 200". When the Captain's altimeter is changed from anywhere else, BA says the new setting once the knob stops.

Radios

The COM radios are on the Pedestal's COM radios panel, described under How the panels are organized. Every change of a COM frequency is spoken, for example "COM1 active 124.850".

The VORs are normally tuned by the FMC. To tune a station yourself, with its course, use the NAV RADIO page in the CDU window (Alt+N), as on the aircraft.

The ILS is a small panel of its own on the pedestal, with a frequency and a front course. Input Ctrl+N opens the 757 Nav Radios window to set it:

Enter applies only the box you are in. The window stays open, and Escape closes it. If BA cannot read the ILS panel's frequency, it goes by its own count of the clicks it has sent and says so, for example "ILS 110.50 set by count: the ILS display could not be read."

Output N reads the radios without opening a window, for example "VOR L 116.90 auto, GSU. VOR R 113.90 remote, course 095. ILS course 095. ILS 110.50.", or "ILS parked." at the end. A VOR's course is said only when that VOR is not tuned automatically.

To read the VORs and the FMC's runway ILS, the Ctrl+N window and Output N look them up on the First Officer's CDU and leave it on its NAV RADIO page. The Captain's CDU is never touched.

The CDU

Press Input Shift+M to open the BlueBird 757 CDU window. It shows both CDUs, read as text straight from the aircraft, starting on the Captain's; the window's title names the side. Ctrl+Tab switches to the other CDU, Ctrl+Shift+L picks the Captain's and Ctrl+Shift+R the First Officer's, and each says which one you are on: "Captain CDU" or "First officer CDU". The two are independent, as on the aircraft. The First Officer's CDU shows once its screen changes, so if its list says it is waiting, press a page key such as Alt+R.

What you hear. A new page says its title, for example "ACT RTE 1 LEGS 1/2", and puts you on line 1. When only the title changes, as when an entry turns ACT into MOD, the new title is said and you stay on your line. After you type an entry, BA reads the scratchpad back once the keys have gone in, so you hear what the CDU took, for example "KATL". If the CDU missed a key you hear what it shows instead: "Scratchpad shows KAT" or "Scratchpad is empty". A scratchpad that empties says "Cleared", and any message the FMC puts in the scratchpad is read aloud. Typed entries go in at about two to three characters a second, other keys a little over half a second apart, and holding a key down presses it once. If the link to the aircraft drops while keys are still going in, the rest are not sent and you hear "CDU connection lost, keys not sent".

CDU messages while the window is closed. With the window closed, BA speaks each new message in the Captain's scratchpad, starting with "CDU:", for example "CDU: TAKEOFF DATA UPLINK". The Speak CDU messages when closed check box at the end of the window turns this off, and so does the CDU Messages While Closed row in Ctrl+M; they are the same setting. This works from the moment you select the 757: you do not have to open the CDU window first.

The status box says "Waiting for the 757's CDU. Is the aircraft powered?" until the CDU has a screen.

A SimBrief flight and route come in through the CDU's ACARS pages. First set your SimBrief ID (see BlueBird's settings) and fetch the flight on the tablet (see Fuel, payload and boarding). Then, in the CDU window:

  1. Press Alt+M for MENU, then ACARS (the left 2 key, Ctrl+2), OPERATIONS (the right 2 key, Alt+2), PREFLIGHT (Ctrl+1), INIT FLT (Ctrl+1) and INIT (the right 6 key, Alt+6). The page shows "VHF IN PROG", then the flight's origin and destination.
  2. Press Alt+R for RTE, then REQUEST SEND (Ctrl+3). Within about 15 seconds the page says "ROUTE 1 UPLINK READY".
  3. Press LOAD (Ctrl+4), ACTIVATE (Alt+6) and EXEC (Ctrl+Enter). The page title then says "ACT RTE 1".

Read each page's numbered lines before you press a key: the line that reads "2:" on the left is the one Ctrl+2 presses, and on the right the one Alt+2 presses. Without a SimBrief ID, ACARS INIT does nothing.

The EFB

Input Shift+T opens the 757 EFB window: BlueBird's tablet itself, read aloud. It is a page you read with your screen reader's browse mode, like a web page, with headings, buttons, check boxes, lists and edit boxes, and everything a sighted pilot can press on the tablet you can press here. BA reads the tablet straight from the aircraft and taps it for you. (In output mode, Shift+T toggles trim announcements instead.)

With the simulator closed, Shift+T opens BlueBird's settings instead.

Reading the tablet

The page's main heading names the tablet page you are on, for example "BlueBird tablet: Aircraft, Fuel", and BA says each new page as it arrives: "BlueBird tablet page: Aircraft, Fuel". Below the heading, in this order:

  1. A question from BlueBird, when one is waiting, with its answer buttons.
  2. The tablet page itself, with its sections as headings and every value with its label.
  3. A Status bar heading: the tablet's top bar, with the time, the departure countdown and the boarding button, and under it a Notifications heading with BlueBird's notifications, newest first.
  4. A Sections heading: the side menu of the app you are in. The one you are on ends in "(current page)".
  5. A Home button, last on every page but the home screen.

The tablet's home screen has five apps: Aircraft (Cockpit presets, Fuel, Weight & balance, Ground services, Cabin & doors, Maintenance, Failures), Navigation (ACARS dashboard, Operating FP, Weather & NOTAM, Charts, Map, PERF calc), Systems, Checklist and Settings (General, Aircraft, Livery options, Callouts, Cabin audio, AIRAC data). Press an app on the home screen, then a section under Sections.

The page updates by itself while the window is open and keeps your place. F5 reads the tablet again. Alt+F4 closes the window; Escape is left to your screen reader.

Pressing, choosing and typing

Each kind of control on the tablet becomes the control your screen reader knows:

When a control is further down the tablet's page, BA scrolls the tablet to it before it taps; there is nothing for you to scroll.

After a press you hear what changed. A button whose words change says its new words. A press that changed nothing says ": no change on the tablet.", and a switch that did not follow says " did not change." A press that takes you to another page is confirmed by the new page's name. If the tablet ends up somewhere else you hear "The tablet did not show . Try again, or press F5 to read the tablet again."

A few things can be in the way, and BA then presses nothing and says why: " is under a BlueBird notification, not pressed." (a notification covers the top right corner of the tablet for about ten seconds; try again), " is under the tablet's keyboard, not pressed.", " could not be brought into view, not pressed." or " is no longer on the tablet."

Notifications and questions. While the window is open, BA speaks each new notification from BlueBird as it arrives, for example "GPU connected.", and each question once when it appears, such as whether to switch the weight units after a SimBrief fetch, or whether to defuel. Answer a question with its buttons at the top of the page. While a question is waiting, the rest of the page is shown as plain text and cannot be pressed.

The colors theme on the Settings app's General page is a line of text, not a choice: it says that other color schemes than the default are not supported.

Fuel, payload and boarding

You fuel and board with BlueBird's own buttons, and BA tells you when each is complete:

  1. Set your SimBrief ID once (see BlueBird's settings, or the Settings app's AIRAC data page on the tablet).
  2. On the Navigation app's ACARS dashboard, press Fetch SIMBRIEF OFP. If BlueBird asks about the weight units, answer it.
  3. With BlueBird's Automatic boarding setting on, BA starts listening for both the fueling and the boarding at the fetch. Otherwise press Import from SIMBRIEF on the Aircraft app's Fuel page, and Start boarding in the Status bar.

BlueBird then fuels and boards at its own pace; with its realistic load rate, boarding can take half an hour or more. You can close the window and carry on: BA checks the tanks and holds every 15 seconds and tells you once each, in the aircraft's weight units and rounded to 10, for example:

BA takes the target weights from your latest SimBrief plan. If it cannot read a 757 plan, you hear "The SimBrief plan could not be read, so the app won't say when fueling and boarding are complete.", after the reason when BA knows it: for example "No SimBrief ID is set in the 757's EFB settings.", "Your latest SimBrief plan is for A320, not a 757-200. Create a B752 plan, then try again.", "The plan's fuel is more than the tanks hold." or "SimBrief could not be reached. Check your internet connection and try again." If nothing has moved after three minutes you hear "BlueBird has not started loading. Is BBS Nest running? Check the fuel with F and the weight with W.", or the same about the fueling or the boarding alone. If one has not finished after an hour, you hear, for example, "Boarding has not finished after an hour. Check the weight with W." Loading another flight stops the checking.

On the Ground services page you call BlueBird's ground power and ground services and set or remove the chocks. Ground power, the aft stairs, the fuel truck, catering and the cargo service are also spoken when they change, whether or not the window is open: "Ground power connected", "Catering called", "Fuel truck removed".

Navigraph and nav data

The Settings app's AIRAC data page has your SimBrief ID, the Navigraph sign-in and the installed nav data cycle.

Warning: BlueBird shows the Update button and a Remove button in the same place, and the button's name tells you which one it is. Read it before you press: "Latest cycle: Remove" removes the nav data you have installed. If that happens you hear "BlueBird removed the installed nav data.", or, when an update was due, "BlueBird removed the installed nav data instead of updating it. With an active Navigraph subscription, reload the flight and update again."

BlueBird's settings, with the simulator closed

BlueBird reads its settings when the aircraft loads. With no simulator running, Input Shift+T (with the 757 selected in BA) opens the 757 EFB settings window, which changes them in BlueBird's own settings file, ready for the next load. With the simulator running, use the tablet's Settings app instead.

The window opens on a Status box that says whether the settings can be changed, for example "The simulator is closed. Changes are saved to BlueBird's settings at once and take effect when the 757 next loads." Then comes a Section list: General, Aircraft, AIRAC data, ACARS, Failures, Livery options, Callouts and Cabin audio. Tab on from it through the chosen section's settings:

Settings worth knowing: in AIRAC data, SimBrief ID number, which BlueBird's SimBrief fetch and the CDU's ACARS need; in Aircraft, Nosewheel steering (Rudder lets you steer on the ground with the rudder pedals, Realistic uses the tiller), Parking brake mode, IRS alignment time, Boarding & load rate, Automatic boarding, Automatic GPU/jetway and Initial chocks in place; in Livery options, Units (Imperial or Metric) and EHSI up reference (HDG or TRK); in Callouts, each of BlueBird's own callouts. Livery options, Callouts and Cabin audio are kept per aircraft registration, and a Registrations box at the top of those sections says which ones your change applies to.

In General, EFB colors theme is a note that other color schemes than the default are not supported. If the file holds another theme, a Set to Dark blue button beside the note sets it back.

Escape closes the window. If you start the simulator while it is open, you hear "Simulator started: BlueBird's settings are read-only."

If the tablet cannot be read
Special windows: the ADI, EICAS and the EHSI

BA reads four of the 757's displays straight from the aircraft, with no AI: the Captain's ADI, the upper EICAS, the lower EICAS and the Captain's EHSI. Each opens as a window with a list you arrow through, followed by the display's own controls, if it has any; press Tab to reach them. The lists update every second without losing your place and speak only when you move through them. Escape closes a window.

The ADI window

Output Alt+P opens ADI, with the list Captain ADI. It starts with the flight mode annunciator, the same four lines as the 757 Autopilot window: "A/T: SPD", "Roll: LNAV, armed LOC", "Pitch: VNAV PTH, armed G/S", "AFDS: CMD". Then comes the rest of the ADI, each line starting with where it sits on the display: Left is the speed tape, Center the attitude, Right the glideslope scale and the radio altitude, Bottom the localizer scale. A line is there only while the ADI shows its item, so the list grows and shrinks with the flight.

On the left, the speed tape:

In the center, the attitude:

On the right and at the bottom, the approach:

Flags. When an instrument fails or has no data, the ADI draws an amber flag in its place, and the list puts the flag there instead of the value: "Left: SPD flag" (the whole speed tape), "Center: ATT flag", "Right: G/S flag", "Right: RA flag" and "Bottom: LOC flag". While the IRS aligns the center reads "Center: no attitude": no horizon and no flag until the alignment is complete.

What you hear by itself. Only the flags, as they appear and go: "ADI flag: ATT", "ADI flag gone: ATT", and the same for SPD, LOC, G/S and RA. Speeds, attitude, needles, radio altitude and minimums are in the list only and never spoken: the 757 makes its own 80 knots, V1, rotate, minimums and altitude calls. To silence the flags, untick ADI messages in the 757 Monitor Manager (Output Ctrl+M); the window still lists them.

What the list leaves out: the FMC's target speed while VNAV controls the speed, the speed limit bands, the speed trend arrow, the pitch limit indicator, and the amber flashing of the minimums and of the localizer and glideslope scales close to the ground. The AUTOLAND STATUS annunciator beside the ADI is not in the list either: BA speaks it as it changes, and the Status panel shows it.

The window has no controls. While the ADI is off it reads "ADI display not powered". If BA cannot read the flight mode annunciator, the first line says why, and the rest of the ADI follows.

If you hear an AI description instead. When BA cannot read the ADI from the aircraft, Alt+P describes it with AI, without saying anything first; this needs an AI provider (see AI Display Reading). The flight mode annunciations are still in the Ctrl+P window whenever BA can read them. See When BA cannot read a display for why this happens and what to do.

The Upper EICAS window

Output Alt+E opens Upper EICAS. The list follows the display, left engine first:

After the list come three buttons of the EICAS control panel: Cancel (Alt+C), Recall (Alt+R) and Max Ind (Alt+M). Each says "… pressed", and Cancel and Recall are then confirmed by what the display did: "EICAS: 3 messages cancelled", "EICAS recall: L ENG SHUTDOWN, PARKING BRAKE" or "EICAS recall: no cancelled messages".

The Lower EICAS window

Output Alt+S opens Lower EICAS. The first line says which page the display shows: "Page: engine", "Page: STATUS" or "Page: engine off"; a blank display reads "Lower EICAS: blank".

After the list, the Engine and Status buttons press the EICAS control panel's ENGINE and STATUS keys. BA confirms a press by the page change: "Lower EICAS: STATUS page".

The EHSI window

The EHSI is the Captain's map display. Output Alt+N opens EHSI, with the list Captain EHSI. What it holds depends on the mode.

In MAP and PLAN, from the top of the screen down:

The map lines name:

In VOR and ILS, the list has the approach picture instead of the map:

What the list leaves out: the weather radar picture and the terrain picture.

The controls. After the list, each with its key: Mode (Alt+M: VOR, APP, MAP or PLAN; APP is the ILS picture), Range (Alt+R, 10 to 320 NM), CTR (Alt+C), TFC (Alt+T), and the map options as check boxes: WXR (Alt+W), TERR (Alt+E), NAV AID (Alt+N), APRT (Alt+A), DATA (Alt+D) and WPT (Alt+P). They are the Captain's EFIS controls, and they show the cockpit's real state.

Output Ctrl+W says the active waypoint as the EHSI's top corners show it, "KOLM, 37.5 NM, 1521.4z", or "No active waypoint", whether or not the window is open. In VOR or ILS mode it says, for example, "KOLM, EHSI in ILS mode". For the first ten seconds after the displays power up it says "EHSI waypoint unavailable: starting".

When BA cannot read a display

BA reads the displays, the flight mode annunciations and the tablet through files made for each version of BlueBird's 757. If it cannot load them, for example after a BlueBird update, you hear once: "BlueBird display files could not be loaded; the display keys fall back to AI reading." Alt+P, Alt+E, Alt+S and Alt+N then describe the display with AI instead, until a BA update brings the files for the new version.

While a reader is still finding its display, its window opens and says so, for example "EHSI reader starting"; with the display dark it says "EHSI display not powered". If a reader loses its display during a flight you hear, for example, "EICAS announcements stopped: aircraft memory not found", and "EICAS announcements resumed" when it is back, followed by anything that changed meanwhile. While a reader is stopped or unavailable, its key gives the AI description instead of the window. BA keeps looking for a display it lost, so wait for "resumed"; after "announcements stopped: unexpected values", reload the flight to start that reader again.

The standby instruments have no read on the 757, so Output Alt+I does nothing here: what they show is on keys of their own. Output S gives the airspeed, Output A the altitude, Output B all three altimeter settings, the standby's included, and the attitude is in the ADI window (Output Alt+P). Alt+P, Alt+E, Alt+S and Alt+N fall back to an AI read (it needs an AI provider; see AI Display Reading); Alt+P's describes the attitude, the flight mode annunciations and the AUTOLAND STATUS annunciator. BA moves the simulator's camera to the display and puts your own view back afterwards; from an outside or drone view you hear "Switch to a cockpit view first."

The First Officer

Output Shift+C opens the 757's First Officer, with BlueBird's Normal Checklist and twelve flows: Power Up, Preflight, Before Start, Engine Start, After Start, Before Takeoff, After Takeoff, Descent, Before Landing, After Landing, Shutdown and Final Securing. What is particular to the 757, from the cockpit tests in the Preflight flow to the engine start on each engine type, is described in The BlueBird 757.

Aircraft-specific hotkeys and callouts

Readouts, in output mode (the complete key list is in the Hotkey Reference):

What BA announces by itself:

The 757 does not say "glideslope alive": listen for "FMA: Pitch: G/S" instead.

Output Ctrl+M opens the 757 Monitor Manager, where you untick anything you do not want to hear. Besides a row for each announcement above, it has CDU Messages While Closed, All Annunciator Lights and All Switches From Any Source to silence a whole kind at once, a "Switches:" row for each panel, a "Light:" row for each light and a "Switch:" row for each switch, and at the end the rows for the displays: Flight Mode Annunciator, EICAS messages, Thrust reference, Engine gauge colors, EICAS status messages, EHSI messages and ADI messages. A display's row also silences BA's own "stopped", "unavailable" and "resumed" messages for it; the windows still list everything. Your choices persist across sessions. See The Monitor Manager.

Take-off callouts. The 757 plays its own "80 knots", V1 and rotate calls, and its own altitude callouts. So on this aircraft Takeoff Assist does not call "80 knots". Its "100 knots", centerline tone and pitch calls work as on every other aircraft.

Things to know

TFDi MD-11

The TFDi Design MD-11 is a three-engine airliner with a cockpit unlike any other aircraft in BA. Its six display units are drawn inside the aircraft's own code with no text behind them, so BA cannot read the PFD, navigation display or engine display directly. What it can read — and read very well — is everything else: all three MCDUs as text, the EFB, the flight control panel windows, the numbers TFDi publishes for external tools, and over 500 indicator lights. Together these replace the screens.

Before you fly
How the panels are organised

The panels follow the order you prepare the aircraft in, and use the names TFDi's own Systems Guide uses:

How the panels behave:

The three engine fire handles are read-only rows: BA reads their position but cannot work them from the panel yet, and says "... cannot be operated from this panel yet." if you try.

The flight control panel

The MD-11's flight control panel is what other aircraft call the MCP or FCU.

Input Ctrl+P opens the MD-11 Flight Control Panel window. It opens on the Autoflight button, which reads its state, such as "Autoflight: AP 1, ATS on" or "Autoflight: off". The other buttons:

The value windows, all in input mode, take typed values — no knob-winding:

The output readouts say what is selected: Shift+H "Selected heading dashed, NAV engaged" when NAV is flying; Shift+S "FMS speed engaged" when the window is dashed; Shift+A the selected altitude in feet or metres; Shift+V the vertical speed or flight path angle, or "not engaged".

Note: PROF and Approach/Land have no cue on the panel — their state exists only on the flight mode annunciator on the PFD — so BA never reports them as engaged. A mode button only tells you it was pressed, not that the mode engaged. To hear the annunciator, use Output Alt+P (below).

The MCDUs

Input Shift+M opens the MD-11 MCDU window, on the Left (Captain's) unit. All three MCDUs read fully, live, as the real screen. (In output mode, Shift+M reads the METAR instead.)

The MD-11 has no EXEC, DEL or PREV PAGE key — the real aircraft does not have them. It confirms with the line select keys and slews with the up and down keys instead. If a screen is momentarily empty, the window says "MCDU is blank - nothing on this screen."

The EFB

Input Shift+T opens the MD-11 EFB, which works like the other tablet windows (Aircraft EFBs). All of it reads: Dispatch, Payload, Perf, Charts, Services, State and Options. Some examples of how it reads:

Pages the aircraft locks in flight, such as ground services, are still readable, but their controls are dimmed and cannot be pressed — exactly as on the real tablet.

Flaps and Dial-A-Flap

The MD-11 has one handle for flaps and slats together, plus a Dial-A-Flap thumbwheel that chooses the exact take-off flap angle. The handle detents, from clean to fully extended, are:

Dial-A-Flap sets the take-off angle anywhere from 10 to 25 degrees, one degree at a time. Because the handle position and the angle are two separate things, every flap readout tells you both: "Dial-A-Flap, 15 degrees". Output L reads the handle, and always includes the Dial-A-Flap angle when the handle is in that detent. When the flaps move, BA says "flaps moving" and then the new position — on an aircraft with no flap gauge you can read, that is your confirmation the selection took.

Special windows: AI display reading

With an AI provider set up, these output mode keys read the screens by AI vision, moving the camera for you as described in AI Display Reading:

Aircraft-specific hotkeys and callouts

Take-off callouts: "V1", "Rotate", "V2" and "N1 70 percent", as described in Takeoff Speed Callouts (TFDi's MD-11 plays no callouts of its own).

When the FMS sets the speeds, BA announces them in one sentence: "V1 145, VR 150, V2 158, slat retraction speed 190, flap retraction speed 210 knots". Starting BA with speeds already entered says nothing; a change does.

Also announced as they change: autopilot and autothrottle engagement, the captain's altimeter (once the knob stops moving), the APU, the COM radios (active and standby for COM 1, 2 and 3), the squawk, the flaps, and every indicator light.

Things to know

Part 9: General Flying Concepts

General Flying Concepts

This chapter steps back from individual aircraft: how an airline flight is put together, how airliner automation thinks, what ATC expects of you, and how to keep a picture of the flight in your head with BA. Nothing here is specific to one type. Where Airbus and Boeing do things differently, both are described. Everything is written for the simulator: real-world flying needs real training, real manuals and a real instructor, and nothing in this guide replaces them.

Tip: You do not need to read this chapter in one go. If you are brand new to airliners, read the phases of flight first (and the example flight in A Flight with BA, Start to Finish, in Part 2), then come back to automation and the FMA once you have flown a few circuits.

The Phases of a Flight

Every airline flight follows the same broad shape. Knowing which phase you are in tells you what to expect next and which BA features matter right now.

Building a Listening Scan

A sighted pilot keeps a "scan": the eyes move over the instruments in a pattern, again and again, so nothing drifts unnoticed. You can do the same with your ears. BA gives you two kinds of information: automatic announcements, which come to you, and readout hotkeys, which you ask for. A good scan uses both.

Let the automatic announcements do the watching for you. Master warnings and cautions, mode changes, gear and flap movement and altitude crossings are announced as they happen on most aircraft. If an announcement is too chatty for you, silence just that one in the Monitor Manager (Output Ctrl+M) rather than ignoring the lot.

Then ask for what matters in each phase. The readout keys are listed in Readout Hotkeys. A sensible pattern:

Two habits make the scan work. First, after you change anything, read it back: set 5,000 feet, then press Output Shift+A to hear that the FCU or MCP really says 5,000. Second, whenever you hear a mode change, ask yourself whether it is the one you expected. Surprises are where mistakes begin.

Tip: Fewer, well-chosen checks beat constant ones. If you press a key every few seconds in the cruise, the important announcement you are waiting for may get talked over.

Automation: Who Is Flying the Aircraft?

A modern airliner has layers of automation. Understanding them is the single most important thing for flying one well, sighted or not.

The autopilot needs to know what to follow. That is where modes come in.

Selected and managed modes

Every axis (speed, lateral path, vertical path) can be told what to do in one of two ways:

Pilots mix the two all the time. A common example: ATC gives you a heading to fly away from your route, so you select a heading, and later they clear you back "direct to" a waypoint, so you return to managed or LNAV navigation.

Airbus FCU and Boeing MCP

Airbus and Boeing put the same ideas on very different panels.

On an Airbus, the panel is the FCU (Flight Control Unit). Each knob can be pushed or pulled. Pushing a knob usually hands that axis to the FMS (managed); pulling it means "use the number I have dialled" (selected). So pulling the heading knob flies the selected heading, and pushing it returns to the flight plan route. Pushing the altitude knob climbs or descends in managed mode, respecting the route's altitude constraints; pulling it climbs or descends in open mode straight to the selected altitude. BA's Airbus aircraft give you push and pull keys and windows for each knob — see Autopilot Windows.

On a Boeing, the panel is the MCP (Mode Control Panel). There is a button for each mode: LNAV and VNAV for the flight plan, HDG SEL for a selected heading, LVL CHG or FLCH for a climb or descent at a set speed, V/S for a set vertical speed, ALT HOLD to stay level, and LOC and APP for the approach. You press the button for the mode you want, and the windows hold the numbers it uses.

Autothrust and autothrottle

The two makers also differ on thrust. On a Boeing, the autothrottle physically moves the thrust levers, so the levers always show the thrust the engines are making. On an Airbus, the thrust levers sit in fixed positions called detents, and in normal flight they stay in the CLB detent from shortly after takeoff until just before landing; the autothrust changes the thrust without moving them. That is why Airbus pilots talk about "thrust levers to CLB" after takeoff and "idle" at touchdown. On some Airbus aircraft, such as the FlyByWire A380X, BA announces each lever detent as you reach it.

Warning: In both designs, disconnecting the autothrust or autothrottle without a plan can leave you with the wrong thrust. Know what the engines will do before you disconnect anything.

The Flight Mode Annunciator (FMA)

The FMA is a strip at the top of the primary flight display that tells you, at every moment, exactly which modes are active and which are armed (waiting to become active). It is how a pilot answers the question "what is the aircraft going to do next?"

On an Airbus, the FMA has five columns, read left to right:

Active modes are shown in green on the top line; armed modes are shown underneath in blue or magenta.

On a Boeing, the FMA shows the autothrottle mode on the left, the roll (lateral) mode in the middle and the pitch (vertical) mode on the right, for example SPD, LNAV, VNAV PTH. Armed modes appear underneath. Above it, the autopilot status shows FD, CMD, or LAND 3 during an autoland.

Why it matters to you: the FMA is the truth, and the panel is only a request. Pressing APPR or APP does not mean the aircraft will capture the glideslope; the FMA showing G/S armed, and then G/S active, does. On aircraft where BA reads the FMA aloud, listen for each change and check it against what you expected. On aircraft where it does not, use the engaged-mode readouts in the autopilot panel or window your aircraft provides.

Approach Types in Plain Terms

An approach is a published path from the end of the arrival down to the runway. There are three kinds you will fly most often.

Every instrument approach has a minimum: a decision altitude or height (DA or DH), or a minimum descent altitude (MDA). At that point you must be able to see the runway, or go around. Minimums are printed on the approach chart and are not part of the navigation data BA reads, so BA cannot tell you what they are; you set them in the aircraft from the chart or your flight plan.

Stable Approach Basics

Airlines require an approach to be stable by a set height, typically 1,000 feet above the runway in cloud and 500 feet in good weather. If it is not stable by then, the crew goes around. That rule exists because unstable approaches cause a large share of landing accidents, and it is just as useful in the simulator.

Typical stable approach criteria are:

With BA, check these with Output Shift+G (gear), Output L (flaps), Output S (speed), Output V (vertical speed) and Output Ctrl+D or Ctrl+I (distance and path) as you pass through about 1,500 feet above the ground.

Tip: A go-around is a normal manoeuvre, not a failure. If your approach is not stable, go around, climb away, and try again. BA's flare assist even tells you "Go around detected. Flare assist rearmed." so you are ready for the next attempt.

ATC Basics

Air traffic control keeps aircraft apart and tells you where to go. In the simulator you might talk to the simulator's own ATC, to an AI service such as SayIntentions, or to real people on a network such as VATSIM. The principles are the same everywhere.

Frequencies and who you talk to

At a large airport you will typically speak to several controllers in turn:

When a controller says "contact Tower on 118.7", you change to that frequency and call them.

Clearances and readbacks

A clearance is permission to do something specific. Until you are cleared, you do not do it. When you receive a clearance you read it back, repeating the important parts so the controller can check you heard them correctly.

Always read back:

End your readback with your callsign. If you did not understand something, say "say again". It is always better to ask than to guess.

Taxi phraseology

These are the words you will hear most often on the ground, and what they mean.

BA's Taxi Planner is built around these clearances: you enter the taxiways in the order ATC gave them and tell it which runways to hold short of. Entering an ATC Clearance has worked examples. If you fly with SayIntentions, BA can even fill the planner in from the controller's last taxi instruction — see SayIntentions.

The altimeter setting

The altimeter needs to know the air pressure to show your height correctly. Near the ground, ATC gives you the local pressure, called QNH, in hectopascals (for example 1013) or inches of mercury (for example 29.92). Above the transition altitude you change to the standard setting (1013 hPa or 29.92 inches) so everyone at high level uses the same reference; heights are then flight levels, such as FL350 for about 35,000 feet. On the way down you switch back to QNH at the transition level. Output B reads your altimeter setting on most aircraft.

Runway Safety for a Blind Pilot

Runways are the most dangerous place on an airport. A runway incursion, an aircraft on a runway where it should not be, is one of the most serious events in aviation. In the simulator it costs you nothing but your flight, but on an online network it can spoil someone else's, and good habits here are good habits everywhere.

Checklists

Airline crews work from two kinds of procedure. Flows are the sequences of actions you do from memory as you work around the cockpit, such as setting up the overhead panel. Checklists are short lists read afterwards to confirm the most important items were done. They are read at fixed points: before start, after start, before takeoff, after takeoff, approach, landing, after landing and shutdown.

Use checklists in the simulator even when nobody is watching. They catch the forgotten item — the parking brake still set, flaps not selected for takeoff, the altimeter not reset — before it matters. The First Officer and Checklists explains the flows and checklists BA's First Officer runs with you, and some aircraft, such as the FlyByWire A380X, have their own electronic checklists that BA can read.

Note: BA's built-in checklists are a convenience, not an official procedure. For the real sequence, use the documentation that came with your aircraft.

Where to Learn More

You will learn fastest by flying, but these kinds of resources help a great deal:

Appendices

Tone Cheat Sheet

BA uses a small family of tones. They follow a few shared rules, explained in full in The Audio Language: What the Tones Mean:

All guidance tones play on the device chosen on the Audio tab of Settings (Guidance tone output device). Screen reader speech is not affected by that setting.

Tone What the pan means What the pitch means What silence means Pulsing or beeps
Taxi steering tone Turn towards the tone. The further it is to one side, the bigger the turn; full pan at about 30 degrees off. Fixed. Pitch carries no information. Your heading is right (within a few degrees; tighter on narrow taxiways). None while taxiing.
Runway lineup (taxi guidance, on the runway) Turn towards the tone to line up with the centreline. Much more precise than taxiing. Fixed. Lined up on the centreline, within about half a degree. A steady pulse, about three times a second, means you are stopped on the runway but not yet lined up. Keep turning, or move forward slowly, until it stops.
Docking steering tone (at the gate) Turn towards the tone to line up with the gate's centre line. As precise as runway lineup. Fixed. Lined up with the gate. None. See the docking beep.
Docking beep (at the gate) Not panned. Fixed. Silence before docking engages, and again after a good park. Beeps get faster as you near the stop mark: about one a second 30 metres out, rapid beeping close in. A solid, continuous tone means you are on the stop mark: stop. After a good park the solid tone holds for about three seconds, then BA speaks the closure, for example "Aligned with gate. Parking brake." If you overshoot there is no solid tone; you hear "Stop. You have passed the stop position."
Takeoff Assist centreline tone Steer towards the tone to get back to the centreline. It points you onto the line, not just parallel to it. Full pan at about 5 degrees of correction needed. Fixed. With Play steering tone set to a threshold (for example At 2 degrees error), silence means you are tracking the centreline. With Always, the tone keeps sounding, centred when you are on the line. None.
Rollout centreline tone (after touchdown) Same as Takeoff Assist: steer towards the tone to the centreline. Uses the Takeoff Assist tone settings. Fixed. On the centreline (follows the Play steering tone setting, as Takeoff Assist does). None. It hands over to taxi guidance's tone when you turn off for an exit.
Flare tone, vertical (manual landing assist, 50 feet to touchdown) Not used for this tone. High tone: you are sinking too fast, raise the nose. Low tone: you are floating, ease the back pressure. Your sink rate is on the flare profile. None. Stops at touchdown.
Flare tone, lateral (manual landing assist, 50 feet to touchdown) Steer towards the tone to the centreline. It already allows for drift, so a correctly crabbed approach is silent. Fixed, and a different waveform from the vertical tone so you can tell them apart. On the centreline and holding it. None. Carries on into the rollout tone.
Hand Fly tone Shows your bank: a tone in the right ear means right wing down, fully right at about 10 degrees of bank. This is your attitude, not a command. Shows your pitch: higher tone is nose up, lower is nose down. Level pitch sits in the middle. Hand Fly's tone does not go silent while it is on; it is muted while Visual Guidance runs. None.
Visual Guidance, desired tone Where the guidance wants your bank to be. Where the guidance wants your pitch to be. Both tones always play while Visual Guidance is on. None.
Visual Guidance, current-attitude tone Your actual bank. Your actual pitch. Not applicable. When the two tones are at different pitches you hear them beat (a wobble). Match the pitch until the beating stops, and match the pans until both tones sit in the same place.

Where to change each tone:

Tip: Keep the two Visual Guidance tones on different waveforms. If both use the same one, they can blend into a single tone exactly when they match, which is when you most need to hear them as two.

Glossary

Troubleshooting and FAQ

Most problems have a simple cause. Work through the matching section below. If nothing helps, collect your logs (see the last section) and ask on the MSFS Blind Assist Discord server.

BA Is Silent, or Speech Sounds Wrong

Hotkeys Do Nothing

BA Will Not Connect, or Uses the Wrong Aircraft

Cockpit Controls Do Not Respond (MobiFlight)

On several aircraft, including the FlyByWire A320neo and A380X, the Fenix A320, the Headwind A330, the TFDi MD-11 and the BlueBird 757-200 (and for a handful of switches on the HorizonSim 787-9), BA needs the free MobiFlight WASM module to operate switches and knobs. Without it, reading and announcements still work, but many controls do nothing.

If you hear "MobiFlight calculator path unavailable. Some cockpit controls may not respond.", install or reinstall the module in your Community folder and restart the simulator (see What You Need). Only the FlyByWire A320neo and A380X, the Headwind A330, the TFDi MD-11 and the BlueBird 757-200 give that warning. The Fenix A320 and the HorizonSim 787-9 do not warn you, so if one of their switches never moves, check MobiFlight first.

PMDG: CDU Window or Readouts Are Empty

The PMDG 737 and 777 only share their data with other programs if their SDK broadcast is switched on in the aircraft's options file. BA checks this when you pick the aircraft and, if the lines are missing, opens a window titled with the aircraft's name and SDK setup.

Follow the window's instructions with the simulator closed: PMDG rewrites the file when the simulator exits and can drop lines you added while it was running. The window and every step are described in The PMDG SDK Setup Check.

If BA says it could not find the options file at all, that is normal before you have loaded that PMDG aircraft once; PMDG creates the file the first time. Load the aircraft, then follow the steps.

Airport or Runway Not Found: the Navigation Database

BA's airport, runway, taxiway and procedure features all read a navigation database built from your simulator's own scenery. If it is missing or built for the wrong simulator, they fail.

See The Navigation Database for more.

A Taxi Route Will Not Calculate

Tones Play on the Wrong Device, or Not at All

  1. Open Settings and go to the Audio tab.
  2. In Guidance tone output device, choose where you want BA's guidance tones (taxi, takeoff, hand fly, landing guidance and docking). This does not change where your screen reader speaks.
  3. Press Test Tone to hear a tone on the chosen device, and Stop Test to end it. The Status line shows which device is really in use.

If your chosen device is unplugged, the tones move to the Windows default device and come back when you plug it in; see Choosing where the tones play. "No audio device available for guidance tones." means Windows has no working output at all, so every guidance tone is silent.

If a tone is on the right device but too quiet or too loud, each tone has its own volume setting; see the Tone Cheat Sheet.

Updates

Sim Performance

What it is

The Sim Performance window shows the same kind of figures a sighted pilot reads from the simulator's own developer frame-rate display: how smoothly the simulator is running, and how hard it is working your computer. It is useful when you are tuning graphics settings or wondering whether the simulator is struggling.

How to use it

Open it from the File menu, Sim Performance. It opens whether or not the simulator is connected. It is a list with one value per row:

The list updates itself every second, so there is no refresh button. Arrow to the row you care about and stay there: that row is re-read whenever its value changes, while the others stay quiet. Press Escape or the Close button to close it.

The simulator's internal per-thread timings, and its verdict about what is limiting performance, cannot be read from outside the simulator, so they are not shown.

Logs: What to Send When You Ask for Help

Press Windows+R, type %APPDATA%\MSFSBlindAssist\logs and press Enter. Zip that folder and send it with a short description: what you did, what you expected, what happened, and roughly what time. Logs and Getting Help has the full steps.

Tip: Send logs soon after the problem. Logs are rotated as they grow, so an old problem may have been written over.

Frequently Asked Questions

Do I need to see the screen at all? No. Everything BA does is designed for a screen reader and the keyboard. Some aircraft displays can only be read through BA's optional AI display reading, which needs your own API key; see AI Display Reading and Scene Description.

Does BA fly the aircraft for me? No. BA gives you access to the aircraft's own controls and tells you what is happening. The aircraft's autopilot flies when you engage it; BA's tones help you fly by hand when you choose to.

Does BA tell me when a runway is clear? Never. Its runway watch tells you what traffic it can see, as "no traffic seen", because it cannot see everything ATC can. Only a clearance tells you a runway is yours.

Why does BA not announce my button presses? Your screen reader already does. If BA spoke too, you would hear everything twice. BA speaks when you type a value, when something goes wrong, and when something changes on its own.

Can I use BA with MSFS 2020 and MSFS 2024? Yes. Build the navigation database for each simulator you use.

My aircraft is not listed. Can I still use BA? Yes, for the general features: taxi guidance, ground traffic, weather, location, planning, teleport and many readouts. The panels and aircraft-specific windows are only available for the aircraft in the Aircraft menu.

Where do I get help? The MSFS Blind Assist Discord server, linked from the project's home page, is where users and developers talk. Bring your logs.

Hotkey Reference

Press ] for Output mode (reading things out) or [ for Input mode (doing things), then the key. "Output Shift+H" means press ], then Shift+H. If modes are new to you, read Output Mode and Input Mode first.

This appendix is in two parts. Hotkeys on Every Aircraft lists the keys that work the same whatever you fly. Then each aircraft has a short section with only its own keys, the keys inside its own windows, and the general keys that behave differently or do nothing on it. If a key is not in an aircraft's section, it works as described in the general part.

Inside BA, File, then Hotkey List shows the list for the aircraft you have selected, with a search box (see The Main Window).

Hotkeys on Every Aircraft

Modes and BA's main window

These work without a mode.

Output: altitude and vertical speed
Output: speed and heading
Output: autopilot windows

These read what the FCU, MCP or flight control panel shows, with its mode. The exact wording differs by aircraft; see Autopilot Windows.

Output: navigation and distance
Output: fuel, weight and configuration

What each one includes (per tank, centre of gravity) depends on the aircraft; see Readout Hotkeys.

Output: weather
Output: time
Output: where you are
Output: traffic
Output: taxi
Output: flying aids
Output: windows and planning
Output: AI and display reading
Output: ground services and networks
Input: teleport and planning
Input: autopilot windows

Each opens a window where you type a value, with the related mode buttons. The buttons differ by aircraft; see each aircraft section and Autopilot Windows.

Input: aircraft windows
Input: taxi, GSX and SayIntentions
Keys inside shared windows
Hand Fly and Visual Guidance quick keys

While Hand Fly mode or Visual Guidance is on, these single keys work with no mode key at all.

FlyByWire A320neo

Full explanations: FlyByWire A320neo (A32NX).

Output keys

W and Shift+W include the centre of gravity. Shift+D gives top of climb when top of descent is not known yet.

Input keys

The autopilot windows: Ctrl+S has SPD/MACH, Ctrl+H the HDG-V/S / TRK-FPA toggle, Ctrl+A the 100/1000 increment, Ctrl+P AP 1, AP 2, A/THR, APPR, LOC, EXPED, the disconnects and Flight Director status, and Ctrl+B sets both sides from one value.

MCDU window (Input Shift+M)
DCDU window (Input Ctrl+Shift+D)
Other windows
General keys that differ or don't work here

Fenix A320 CEO

Full explanations: Fenix A320 CEO.

Output keys

Each display key opens a live window read from the Fenix. When the Fenix cannot share that display, it gives the AI read instead, which needs an AI provider and Fenix v3.

Input keys

Ctrl+P opens the autopilot window: AP1, AP2, ATHR, APPR, LOC, EXPED and the disconnect buttons for each side. Input Shift+T opens the Fenix's own EFB web page, where Alt+Home goes back to the EFB's home screen.

MCDU window (Input Shift+M)
Fenix windows (Input Ctrl+Shift+F)
General keys that differ or don't work here

FlyByWire A380X

Full explanations: FlyByWire A380X.

Output keys

Q and A read in metres when the FCU's MTRS button is on.

Input keys

The Ctrl+A window adds a metric toggle, and Ctrl+P a Flight Director button.

MCDU / MFD window (Input Shift+M)
RMP window (Input Ctrl+Shift+R)
ECL window (Output Ctrl+Shift+C)
OANS / BTV window (Output Ctrl+Shift+B)
General keys that differ or don't work here

Headwind A330-900neo

Full explanations: Headwind A330-900neo.

The keys are exactly those of the FlyByWire A320neo, including the MCDU, DCDU and flyPad windows. The only difference you will hear is Output B, which reads the simulator's own altimeter on this aircraft.

PMDG 737

Full explanations: PMDG 737 (NG3).

Output keys

F and Shift+F read fuel tank by tank.

In the Engine displays window, Tab moves between the two lists and the controls, the arrow keys read a list, and Escape closes it. The Navigation display and Primary flight display windows work the same way, with one list.

Input keys

The Ctrl+P window is the 737 Autopilot: CMD A, CMD B, CWS A and B, both flight directors, approach, VOR LOC, A/T arm, disengage bar, disconnects and bank limit.

CDU window (Input Shift+M)
General keys that differ or don't work here

PMDG 777

Full explanations: PMDG 777. The keys are those of the PMDG 737 except:

HorizonSim 787-9

Full explanations: HorizonSim 787-9.

Output keys

F and Shift+F read fuel tank by tank; D adds the time en route.

Input keys

The Ctrl+P window is the 787 Autopilot: A/P, A/T, LNAV, VNAV, approach, level change, altitude hold, heading hold, V/S and A/P disconnect. The Ctrl+B window takes the QNH in hectopascals, with a Standard button.

FMC window (Input Shift+M)
EICAS and synoptic windows
General keys that differ or don't work here

iFly 737 MAX8

Full explanations: iFly 737 MAX8.

Output keys

D and Shift+D read the FMC's PROG page; if neither CDU shows it, BA switches the first officer's CDU to it. N includes the NAV mode flag, such as ILS.

Input keys

The Ctrl+P window has CMD A and B, CWS A and B, both flight directors, A/T arm, disengage bar, bank limit and the disconnects. Input Shift+T opens the iFly EFB tablet; F5 reloads it, and a Retry button appears if it cannot be reached.

FMC window (Input Shift+M)
General keys that differ or don't work here

BlueBird 757-200

Full explanations: BlueBird 757-200.

Output keys

BA moves the camera for the AI reads and puts your view back afterwards. The 757 plays its own take-off speed calls, so Takeoff Assist does not call "80 knots" on it; it still calls "100 knots".

F and Shift+F read each tank with a total, L adds the flap angle while the flaps are not at the lever's position, Shift+G adds the lever's position, UP, OFF or DOWN ("Gear up, lever off"), and B reads the three altimeters and the radio minimums ("Altimeter: 1018, 30.05. DH 200"). The trim is spoken in BlueBird's units while it moves ("Trim 5.3"), and the CDU's EXEC light when it comes on and goes out ("EXEC light on", "EXEC light off").

Input keys

Each MCP window, the altimeter window and the nav radios window stay open for the next value; Escape closes them. In an MCP window, Alt and a button's underlined letter presses it: Alt+S HDG SEL, Alt+H HDG HOLD, Alt+L LNAV; Alt+I Speed Intervene, Alt+M IAS/MACH, Alt+S SPD, Alt+T THR, Alt+L FLCH; Alt+H ALT HOLD, Alt+V VNAV, Alt+L FLCH; Alt+V V/S. FLCH is Alt+L in both windows, as Level Change is on the PMDG 737. The 757 has no altitude intervene: for a step climb, set the new altitude on the MCP and enter it as the cruise altitude on the CDU's CRZ page.

Autopilot window (Input Ctrl+P)
CDU window (Input Shift+M)
Display windows (Output Alt+P, Alt+E, Alt+S, Alt+N)
EFB window (Input Shift+T)

With the simulator closed, Shift+T opens the 757 EFB settings window instead: Tab moves through the Status box, the Section list and the section's settings, Enter saves a box, and Escape closes.

Altimeter and minimums window (Input Ctrl+B)
General keys that differ or don't work here

TFDi MD-11

Full explanations: TFDi MD-11.

Output keys

L includes the Dial-A-Flap angle, F and Shift+F read every tank with a total, B reads the captain's altimeter, and Shift+G the gear lever.

Input keys

Ctrl+B sets all three altimeters from one entry. Ctrl+S and Ctrl+V work out from the number you type whether it is knots or Mach, feet per minute or an angle.

Flight Control Panel window (Input Ctrl+P)

Every button has its own Alt+letter, spoken with the button. The ones that are not the first letter:

MCDU window (Input Shift+M)

The MD-11 has no EXEC, DEL or PREV PAGE key, like the real aircraft.

General keys that differ or don't work here