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:
- Panels you can operate. Every switch, knob and selector BA supports for your aircraft appears in its own window as an ordinary Windows control — a list, a button, a text box. You move through them with the arrow keys and Tab, exactly as you would in any accessible program.
- Hotkeys you can press at any time. Global keys read out your altitude, speed, heading, fuel and much more, and other keys open windows, set the autopilot or start guidance. They work while the simulator has the focus, so you do not need to switch windows to use them.
- Automatic announcements and audio guidance. BA watches the aircraft and speaks important changes — a master warning, a flight mode change, a system coming on line — and it can play steering tones that guide you along a taxiway, down a runway centreline or onto a glide path.
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.
- Parts are the top level. Part 1 (this part) gets you set up. Part 2 opens with a walk-through of a whole flight showing how the features fit together, then explains the ideas used everywhere, such as readout hotkeys and what the tones mean. Part 3 is the First Officer, who works your aircraft's flows and checklists with you. Parts 4 to 7 follow a flight in order: planning, the ground, flying, landing, and networks such as VATSIM. Part 8 covers each aircraft. Part 9 explains general flying concepts. The appendices hold a tone cheat sheet, a glossary, troubleshooting and the full hotkey reference for every aircraft.
- On this website each chapter is its own page. The chapter title is heading level 1, sections are level 2 and subsections level 3. The guide contents page lists every part, chapter and section, and each chapter page ends with links to the previous and next chapters.
- The whole guide is also available as one long page, which is the copy that comes with BA: open the Help menu and choose User Guide, and it opens in your web browser, matching the version of BA you have installed. On that page parts are heading level 2, chapters level 3, sections level 4 and subsections level 5, and your browser's find command searches the whole guide at once.
To move by heading in your web browser:
- NVDA: browse mode is on by default in a web browser. Press H to go to the next heading and Shift+H for the previous one. Press 1 to 6 to jump to the next heading at that level. NVDA+F7 opens the Elements List, where you can choose Headings and see the whole outline.
- JAWS: press H and Shift+H to move between headings, or 1 to 6 for a particular level. Insert+F6 lists all headings so you can pick one and press Enter.
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:
- Words BA speaks are shown in quotes and italics, for example "Connected to".
- Names of buttons, check boxes and fields are shown in bold the first time they appear, using exactly the wording on screen.
- Hotkeys are written with their mode. "Output Alt+Y" means: press the right bracket key to enter Output mode, then press Alt+Y. "Input Shift+R" means: press the left bracket key to enter Input mode, then press Shift+R. The section Output Mode and Input Mode explains this properly, and it is worth reading carefully before anything else.
- Some features exist only on some aircraft. When that is the case, the guide says so.
Getting Started
What You Need
- Windows 10 or Windows 11, 64-bit.
- Microsoft Flight Simulator 2020 or Microsoft Flight Simulator 2024. BA works with both, and detects which one is running.
- A screen reader. NVDA or JAWS is recommended. Without one, BA uses Windows speech instead.
- The .NET 10 Desktop Runtime (x64) from Microsoft. BA is built on it. Download it from Microsoft's .NET 10 download page; choose the Desktop Runtime for x64. If it is missing or too old, BA tells you when you start it, in a message box titled "MSFS Blind Assist - Missing Requirements", and closes.
- The MobiFlight WASM module (free), for some aircraft. BA uses it to operate cockpit controls on the FlyByWire A320neo, the FlyByWire A380X, the Headwind A330-900neo, the Fenix A320, the TFDi MD-11 and the BlueBird 757-200. Without it, many controls on those aircraft will not respond, although reading values and hearing announcements still work. On the HorizonSim 787-9 a handful of switches, such as the batteries and generators, also need it. The PMDG and iFly aircraft do not need it. Download it from the MobiFlight website's WASM module page, place it in your simulator's Community folder (the same folder your add-on aircraft live in), and restart the simulator.
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.
- 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.
- 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.
- 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:
- settings.json, your settings.
- The databases folder, holding the navigation databases BA builds.
- The logs folder, holding diagnostic logs (see Logs and Getting Help).
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:
- the navigation database for the simulator you last connected to, which taxi guidance, teleporting, ILS guidance and flight plans all need; or
- the location data used by the nearest-city readout (Output C) and the Location Info window.
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:
- Download location data (or Update location data if some older data is already installed). This starts the download in the background. The window stays open and the button's label changes to show progress: Downloading location data, then Building location data, then Location data ready. Pressing it again while a download runs does nothing; if the download fails or is cancelled, the label returns to Download location data and pressing it retries. While the download runs, the Not now button becomes Close, and the download carries on after you close the window, with its progress spoken.
- Build navigation database. This closes the window and opens the Nav Database window, described in The Navigation Database.
- Not now, or Escape, closes the window without doing anything.
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:
- Lines to add, a read-only box containing the exact lines. For the 737 they are a line reading [SDK], then EnableDataBroadcast=1, EnableCDUBroadcast.0=1 and EnableCDUBroadcast.1=1. The 777 adds EnableCDUBroadcast.2=1 for its centre CDU.
- Files to fix, a list of each options file with a problem, such as "737-800: no [SDK] section".
- Copy lines, which puts the lines on the clipboard and says "Lines copied."
- Open folder, which opens Windows Explorer on the folder of the file selected in the list, with the file already selected so that pressing Enter opens it.
- Close, or Escape.
The steps the window gives are:
- Close Microsoft Flight Simulator first. PMDG rewrites this file when the simulator exits and can drop lines added while it runs.
- For each file in the list, select it, press Open folder, then press Enter on the selected file to open it (usually in Notepad).
- If the file already has an [SDK] section, replace it with the lines; otherwise paste them at the end. Keep only one [SDK] section.
- 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.
The Navigation Database
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
- Once, before you use any of the features above.
- Again after you install, remove or update add-on airport scenery, or update your navigation data, so the database matches what you fly. BA reads your scenery at build time; it does not notice later changes on its own.
- Again if an announcement in this guide or a release note tells you a rebuild picks up a fix.
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:
- A short explanation, including the folder where databases are stored.
- Active database status, for example "Active Database: FS2020 - 41,804 airports - Navigraph data available", or "Active Database: FS2024 (Not Built)".
- Build FS2020 Database and Build FS2024 Database buttons. Focus starts on the FS2020 button.
- Verify Active Database, which re-checks the active database and speaks its status.
- Close, or Escape.
The two simulators are built differently, and this matters:
- For MSFS 2020, close the simulator first. The tool reads the scenery files directly from disk.
- For MSFS 2024, the simulator must be running and loaded to the main menu. The tool asks the running simulator for its scenery data.
To build:
- Close or start the simulator as described above.
- 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.
- 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?"
- 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.
- 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.
Navigraph data
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?"
- Yes - Open Settings (the default) cancels what you were doing and opens the Nav Database window so you can build the right database.
- No - Continue Anyway carries on with the mismatched database. Positions may be wrong, so use this only if you understand the risk.
- Cancel stops what you were doing and changes nothing.
If something goes wrong
- The FS2024 build fails or finds nothing. Make sure MSFS 2024 is fully loaded to its main menu, not still on a loading screen, before you press the button.
- The FS2020 build fails. Make sure MSFS 2020 is completely closed.
- An add-on airport has the wrong gate names or is missing. Rebuild the database after installing the scenery. If the gates are still the simulator's default ones, see Gates, GSX and Docking: some GSX add-ons can affect stand names, and BA's build guards against this.
Connecting to the Simulator
BA connects to the simulator on its own. You do not press a connect button.
- Start the simulator and load a flight. You can do this before or after starting BA.
- While BA is looking, its main window's status line reads Waiting for simulator, and BA tries again every few seconds.
- 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:
- FlyByWire Airbus A320neo
- FlyByWire Airbus A380X
- Headwind Airbus A330-900neo
- Fenix A320 CEO
- PMDG Boeing 737 (the 737-600, -700, -800 and -900)
- PMDG Boeing 777
- HorizonSim Boeing 787-9
- iFly Boeing 737 MAX8
- TFDi Design MD-11
- 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 menu bar, with four menus: File, Aircraft, Extras and Help. Press Alt to reach it.
- The connection status line, which reads Waiting for simulator, Connected to …, or Disconnected from simulator. It is a label, so you do not Tab to it; your screen reader can read it with its read-window or review commands.
- The Sections list (its screen reader name is Aircraft sections). This lists the main areas of the cockpit for your aircraft, such as Overhead, Glareshield, Main Instrument Panel and Pedestal. The exact sections depend on the aircraft.
- The Panels list (named Panel list). This lists the panels inside the section you selected. On the overhead, for example, you might find Electrical, Fuel, APU and Lights.
- The panel controls area. This holds the controls of the panel you selected, each with a label in front of it, and often a Status Display at the bottom.
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:
- Press Ctrl+1, and arrow up or down to the section, for example Overhead.
- Press Tab (or Ctrl+2) to reach the Panels list, and arrow to the panel, for example Lights.
- Press Tab to move into the controls, and keep pressing Tab to reach the control you want.
- 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:
- Combo boxes (drop-down lists). Most switches and selectors are combo boxes, one item per position: for example Off, On; or Off, Auto, On. Arrow up and down to choose a position. The aircraft switch moves as soon as you arrow onto a new position; there is no separate confirm step. Your screen reader reads the new position, and BA does not repeat it.
- Buttons. Momentary push buttons and one-shot actions are buttons. Press Space or Enter to press them. Some buttons show their current state in their name, for example "LNAV: Off", so you can hear the state before you press.
- Text boxes. Controls that take a number, such as a frequency or a value, appear as a text box; your screen reader says "Type a value and press Enter to set". Type the value and press Enter. There is no separate Set button: Tab goes straight to the next control. Decimal values can be typed with either a comma or a full stop, whatever language Windows uses. Do not type thousands separators: a value such as 10,000 or 10.000 is refused rather than guessed at, so type 10000. Where it helps, BA confirms the value it set, because that is something your screen reader cannot tell you.
- Read-only status fields. Some rows are not controls at all but readouts, such as an annunciator, a door state or a gauge value. They are read-only text boxes: Tab to them to hear the current value. You cannot change them.
- Sliders. A few continuous controls, such as some dimmers or levers, are sliders. Use the arrow keys for small steps, and Page Up and Page Down for larger ones.
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.
- Arrow up and down to read each row.
- The list updates itself while you read it. Only the row whose value actually changed is re-read, and your position in the list stays where it is, so you can sit on one row and listen to it change.
- Press F5 at any time to refresh it immediately, or press the Refresh button.
- Press Ctrl+3 from anywhere in the main window to jump straight to it.
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.
- Output mode is for reading things out. You enter it with the right bracket key, ]. BA says "output".
- Input mode is for doing things: opening windows, setting the autopilot, teleporting and so on. You enter it with the left bracket key, [. BA says "input".
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
- Press ] (for Output) or [ (for Input). You hear "output" or "input".
- Press the command key or key combination, for example A, Shift+H or Ctrl+T.
- 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:
- Press the same bracket key again. BA says "cancelled", and your keyboard is back to normal.
- Or, if BA's own window has the focus, press Escape. BA says "cancelled".
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:
- Ctrl+1, Ctrl+2, Ctrl+3 and F5 work only inside BA's main window, as described in The Main Window.
- Some features, such as Hand Fly mode and visual guidance, turn on a small set of instant keys for as long as they are active, so you can read key values with a single press. Those are explained in their chapters, starting with Hand Fly 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
- Open the File menu and choose Hotkey List.
- 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.
- Press Enter in the Search box to jump into the list itself.
- Shift+Tab back to the Show box (named Show Hotkey Mode) to show All hotkeys, only Output hotkeys, or only Input hotkeys.
- 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.
- 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
- Nav Database… opens the window for building and checking navigation databases. See The Navigation Database.
- Settings… opens the Settings window. See The Settings Window.
- FMC Settings appears only for the PMDG aircraft, the Fenix A320 and the HorizonSim 787-9. See FMC Settings.
- Hotkey List opens the Hotkey List, described above.
- Sim Performance opens the Sim Performance window. See Sim Performance.
- Suspend Hotkeys turns the bracket keys off and on again. See Suspending hotkeys.
- Update Application checks for a newer version straight away. See Updates.
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
- User Guide opens this guide in your web browser, all on one page and matching the version of BA you have installed, so it works without an internet connection. If that copy is missing, as it is when you build BA yourself, BA says so and opens the online guide instead. See Finding Your Way Around This Guide.
- Project Website opens msfsblindassist.com, where you can download BA and read the guide online.
- About shows the BA version you are running, the exact build, and the author. Press OK or Escape to close it.
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 window opens on the first tab, Announcements. Press Ctrl+Tab to move to the next tab and Ctrl+Shift+Tab for the previous one, or Tab to the tab list and use the arrow keys.
- Within a tab, use Tab and Shift+Tab to move between options.
- Press OK to save every tab at once. BA applies the changes straight away, without a restart, and says "Settings saved". If something on a tab is not valid, BA switches to that tab, explains the problem in a message box, and puts you on the field to fix; nothing is saved until you do.
- Press Cancel or Escape to close without saving anything.
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:
- A heading, "A new version of MSFS Blind Assist is available!"
- Current version, the one you are running.
- Latest version, the one on offer.
- Release Notes, a formatted document describing what is new for you, with headings you can jump between, real lists, and links that open in your web browser.
- Update Now and Cancel buttons.
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:
- Release builds (recommended), the default. You are offered only full, tested releases.
- Preview builds. You are also offered the preview build, which has the newest changes as soon as they are finished. When you choose it, BA explains the trade-off and asks you to confirm. On the preview channel you are always offered whichever is newer, the preview or the release, so you can never miss a real release.
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:
- Note what you did, what you expected, and what happened instead — including what BA said.
- 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.
- Note the aircraft and the simulator (2020 or 2024), and the airport if it is a ground problem.
- 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.
- 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.
- Install the .NET 10 Desktop Runtime and, if your aircraft needs it, the MobiFlight WASM module. See What You Need.
- Extract BA and run MSFSBlindAssist.exe. See Installing.
- 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.
- Start the simulator and load a flight, parked at a gate, in an aircraft BA supports.
- In BA, open the Aircraft menu and choose that aircraft. You hear "Switched to" and its name.
- Wait for "Connected to" and "Profile and panels active".
- Press ], hear "output", then press A. BA reads your altitude. Try Output H for heading and Output S for airspeed.
- 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.
- Open File, Hotkey List, and search for something you want to do.
- 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:
- A number you typed has been set. When you type a value into a box and press Enter, BA confirms the exact value, because you need to know the aircraft took exactly the number you meant.
- Something went wrong. A value outside the allowed range, a control that could not be reached, a feature that is not available. Errors are always spoken.
- Something changed by itself. A master caution, a flight mode change, the gear coming down, the autopilot dropping out, a taxi instruction, the simulator pausing. These are "background" changes you did not trigger, and they are the heart of what BA announces.
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":
- Screen Reader (NVDA, JAWS, etc.) - Recommended. BA sends its announcements to your screen reader, so they come out in your normal voice, at your normal speed, and on your braille display if you use one. This is the right choice for almost everyone.
- SAPI (Windows Speech) - Fallback. BA speaks with the built-in Windows voice instead. Use this only if you have no screen reader running, or if your screen reader is not working with BA.
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
- Announce nearest city automatically. A combo box with the choices Off, Every 1 minute, Every 2 minutes, Every 5 minutes, Every 10 minutes, Every 15 minutes and Every 20 minutes. When it is on, BA speaks the same sentence as Output C (see Location Info and Nearest City) at that interval while you fly. It is Off by default. It stays silent if you have not downloaded the location data.
- Include seconds in time announcements (Output Z / Shift+Z). When ticked, the local-time and Zulu-time readouts include seconds. Off by default, so you hear hours and minutes only.
- Announce GSX tooltips when Access GSX window is closed. When ticked, GSX's progress messages (boarding, fuelling, pushback and so on) are read aloud even when the Access GSX window is hidden. Off by default. See Gates, GSX and Docking.
- Announce 1,000-foot altitude crossings. On by default. See Altitude Callouts.
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:
- "Sim paused" and "Sim unpaused" when the simulator's Escape menu opens and closes.
- "Active pause on" and "Active pause off" when you toggle active pause.
- "Slew on" and "Slew off" when slew mode is turned on or off.
- "Sim rate 4x", "Sim rate 0.5x" and so on when the simulation rate changes.
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
- A value keeps announcing and is distracting you, for example a clock counter or a light that flickers.
- You want a quieter cockpit on a long cruise.
- You want to check what you have muted before an important flight.
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
- Press Output Ctrl+M. The Monitor Manager opens with the cursor in the Search box.
- 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.
- 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".
- Arrow up and down through the rows. Each row is a checkbox. Checked means BA announces it; unchecked means it is muted.
- Press Space to untick a row and mute it, or tick it again to bring the announcement back.
- 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:
- All lists every announcement.
- Muted lists only the ones you have silenced. Use this to review what you have turned off.
- Unmuted lists only the ones that still speak.
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
- I muted something and it still speaks. Check that you unticked the right row: search for it and set Show to Muted to confirm. Some aircraft announce one event from two places (for example a light and an ECAM memo for the same condition); BA tries to speak it once, but if you still hear it, look for a second row with a similar name.
- I cannot find a row. Try a shorter search, or a different word. Rows use the cockpit's own names, for example "Nav Lights" or "Left Forward Pump".
- I want my 1,000-foot callouts off. These are not in the Monitor Manager. Use the Announcements tab setting described above.
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.
Navigation and distance
| 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:
- Airbus (FlyByWire A320, A330, A380): Shift+1 Green Dot, Shift+2 S speed, Shift+3 F speed, Shift+4 VLS, Shift+5 VS (stall), Shift+6 VFE Next.
- Fenix A320: the same keys, from its PFD's speed tape, with Shift+5 alpha prot, or VSW while the tape draws one.
- PMDG 737, PMDG 777 and iFly 737 MAX: the flap manoeuvring speeds, from flaps up on Shift+1 upward. The exact flap settings differ between types.
- MD-11: Shift+1 slat retraction speed, Shift+2 flap retraction speed.
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
- Output Ctrl+Shift+R reads your last landing rate, and Output Ctrl+Shift+G its peak g-force. See Landing Rate and G-Force.
- Output Shift+T turns trim announcements on and off, on every aircraft. See 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
- 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.
- 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").
- 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.
- 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.
- 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:
- Hand Fly plays one tone that shows the aircraft's attitude. Pitch follows the nose (higher note = more nose-up, the centre note = level). Pan follows the bank: bank right and the tone moves right. To level the wings, roll away from the tone until it is centred.
- Visual Guidance plays two tones: one for the attitude the guidance wants and one for the attitude you have. You match them: roll until the two sit in the same place left to right, and pitch until their notes are the same and the "beating" between them stops.
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:
- Tone type. Every tone offers the same four sounds: Sine (Smoothest), Triangle (Smooth), Sawtooth (Bright) and Sine (Rich). Choose whatever you hear most clearly over engine noise.
- Volume. A slider from 0 to 100 percent. Every guidance tone starts at a gentle 5 percent so that it sits underneath the sound of the aircraft.
- Test Tone. The tabs have a Test Tone button that plays a sample with your current settings, sweeping from one side to the other so you can check both ears. Press it again (it now says Stop Test) to stop early.
- Direction (invert). For taxi guidance and docking: Invert steering tone direction (steer AWAY from the tone), off by default. For takeoff assist and the flare and rollout tones: Steer toward the tone to stay on the centerline, ticked by default. Change these only if "steer away" feels more natural to you; the two are separate, so you can set each your own way.
- Hard pan (speaker-friendly). On stereo speakers it can be hard to tell "slightly left" from "centred". The hard-pan options make the tone jump fully to one speaker or the other instead of drifting gradually: Hard-pan steering tone (full left or full right; speaker-friendly) for taxi and docking, Hard-pan centerline tone (full left or full right; speaker-friendly) for takeoff assist and the rollout, and Hard-pan visual-guidance tones (speaker-friendly) for visual guidance, which snaps once the bank is more than about one degree. All are off by default. Headphone users normally leave them off, because the gradual pan also tells you how far off you are.
- Different sounds for different tones. Visual Guidance's two tones default to different sounds (Triangle for the wanted attitude, Sine for your actual attitude) so they stay distinguishable even when they are exactly matched. If you change one, pick a different sound for the other. The flare's sink-rate tone automatically uses a contrasting sound to the centreline tone for the same reason.
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.
- Open the Settings window and go to the Audio tab.
- In Guidance tone output device, choose a device. Windows default device follows whatever Windows is using.
- 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.
- 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.
- 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
- I hear no tone at all. Remember that silence often means "on profile". Drift deliberately off heading for a moment: the tone should appear. If it does not, check the volume slider for that feature, press Test Tone on its settings tab, and check the Audio tab's Status box.
- The tone is in the wrong ear. Check the direction setting for that feature, and check your headphones are on the right way round. The Test Tone sweep plays left then right.
- I cannot tell small offsets from centred on speakers. Turn on the hard-pan option for that feature.
- Two tones blur together in Visual Guidance. Give the two tones different sounds on the Hand Fly tab.
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
- Alt+D, scene description: on every aircraft, Output Alt+D describes the outside scene: what the simulator window is showing.
- Cockpit displays: on the aircraft whose screens cannot be read as text, Output Alt+P, Alt+N, Alt+E, Alt+S and Alt+I read the PFD, the navigation display, the engine/warning display, the lower or system display, and the standby instruments. Which keys exist depends on the aircraft: the PMDG 737 and 777, iFly 737 MAX, HorizonSim 787, BlueBird 757 and TFDi MD-11 have AI display reads. The Fenix A320 opens live windows of its displays and uses the AI read only when it cannot read a display directly. The FlyByWire aircraft read their displays as text instead, from the Panels list, and need no AI. See your aircraft's chapter for exactly what each key reads.
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:
- "Switch to a cockpit view first." You are in an outside or drone view. BA does nothing until you return to the cockpit.
- "Could not confirm the cockpit view switch; reading what is on screen." BA could not check that the camera moved, often because the simulator is paused or on a menu. It reads whatever is on screen.
- "Could not return to your previous view." BA could not put your view back. It will try again on your next display read.
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
- Set up an AI provider once (see Settings below).
- Press Output and the display key, for example ] then Alt+P. You hear "Capturing PFD..." (the display's name).
- 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".
- Read the result with the arrow keys like any text.
- 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:
- AI Provider. Choose Google Gemini or Anthropic Claude. This is a hard switch: the display reads, scene description and route briefing all use the provider you choose. BA never quietly switches to the other one.
- Gemini API Key and Claude API Key. Paste your key into the box for your provider. The tab has a link to each provider's key page: a free Gemini key is available from Google AI Studio (aistudio.google.com/apikey), and a Claude key from the Anthropic console (console.anthropic.com/settings/keys). Treat your key like a password and never share it.
- Gemini Model and Claude Model. Choose which model to use. Press Refresh models to load the current list from the provider once your key is entered. If BA cannot reach the provider, it offers a short built-in list and says so in the status line below. For Claude, the larger models are the most capable and the smaller ones are cheaper.
- Enable Grounding with Google Search (paid feature). Gemini only. Lets the route briefing look up current information on the web. It needs a billing account with Google. Off by default.
- Enable web search for NOTAM route grounding (extra cost). Claude only. Lets the route briefing search the web while it is being written, billed per search. Off by default.
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
- "AI provider API key not configured. Please go to File menu, Settings, AI tab." No key is entered for the provider you selected. Add one on the AI tab.
- "Microsoft Flight Simulator window not found." The simulator is not running, or BA cannot see its window.
- The provider says the model is unavailable. Some models appear in the list but your account may not be allowed to use them. Choose a different model.
- The provider is busy. BA retries automatically for a short while; if it still fails, try again in a minute.
- The display was cut off or the wrong one was read. On the HorizonSim 787, check you were in a cockpit view that shows the whole display.
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):
- Output C speaks one sentence: the nearest town, the water you are over, and how far the coast or land is.
- Output Shift+L opens the Location Information window, a fuller picture with lists of cities, landmarks, airports, terrain and water around you.
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.
- Open the Settings window and go to the GeoNames tab.
- 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.
- 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:
- Major Cities
- Tourist Landmarks
- Terrain (mountains, hills, valleys, capes, islands)
- Nearby Places
- Cardinal Directions (the nearest towns to the north, east, south and west)
- Airports
- Water Bodies (lakes, bays, gulfs, straits and coves)
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:
- Distance Ranges: Nearby Cities Range, Cardinal Cities Range, Major Cities Range, Landmarks Range (used by all four landmark lists) and Coast Range (how close the sea coast must be, over land, before C mentions it; 50 by default, up to 1,000). Over water the nearest land is always given, whatever the Coast Range.
- Minimum Population for Major Cities: how big a town must be to count as a major city (50,000 by default).
- Distance Units: Miles or Kilometers. This changes the spoken and shown distances.
- Maximum Results Per Category: how many entries each list shows (Nearby Places, Major Cities, Airports, Terrain Features, Water Bodies, Tourist Landmarks).
- Reset to Defaults puts the ranges back.
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
- C says the data is not downloaded. Go to the GeoNames tab and press Download location data.
- The download stalled. BA says "Location data download stalled, no data for 20 seconds." and retries by itself. If it gives up, press the button again: it resumes rather than starting over.
- C says the data will be ready at the next start. Another program (often antivirus) was holding the file. Restart BA.
- Distances are in the wrong unit. Change Distance Units on the GeoNames tab. This is separate from the ground distance unit used by taxi guidance.
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:
- Flows runs each phase's procedure for you, from powering up the aircraft to securing it. The First Officer sets its own switches, checks that each one really moved, and reminds you of the Captain's items.
- Checklists holds the aircraft's normal checklists. A line ticks itself once the aircraft is in that state, and ticking a line yourself has the First Officer do it.
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
- Press Output Shift+C. The first time, the window opens on its tab strip; after that it returns to the control you left.
- Press Ctrl+Tab to switch between the Checklists and Flows tabs, or use the arrow keys on the tab strip.
- 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:
- Available flows: this aircraft's flows, in flight order. On the Fenix A320, for example: Electrical Power Up, Preflight, Before Start, Engine Start, After Start, Taxi, Line-up, After Takeoff, Descent, Approach, Landing, After Landing, Shutdown and Securing.
- Flow steps: the steps of the selected flow. A Captain's item starts with "[CAPTAIN]". During and after a run, each step is marked with a check mark (done), an arrow (skipped) or a cross (failed).
- Current step and Flow status: read-only lines saying what is happening, for example "Step 3: Beacon: ON" and "Running: Before Start".
- The buttons Start Flow, Pause / Resume, Stop Flow and Load SimBrief.
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.
- Power Up switches external power on when ground power is available, and starts the APU when it is not. With neither, it asks you: "No external power and the APU is not running. Connect the GPU on the EFB Ground Services page, or start the APU."
- Preflight ends with eleven of the cockpit's tests, quickest first: the left and right stall warning, the CVR, the takeoff configuration, the wheel well fire, the engine fire and the engine, APU and cargo fire tests, the Captain's and First Officer's oxygen (each held for ten seconds), TCAS and, last, ground proximity. Each step says what to listen for, for example "Engine fire test — listen for the fire bell" or "Ground proximity test — listen for the callouts". Each test is also a checklist line that runs the test again when you tick it, but only parked with the engines stopped; otherwise you hear "Tests left alone: not read on the ground with the engines stopped."
- Before Start turns the electric hydraulic pumps on before it sets the parking brake. Without hydraulic pressure the First Officer leaves the brake alone, in a flow or at a tick: "Parking brake left released: no hydraulic pressure. Turn on the electric hydraulic pumps first." The flow then starts the APU, waits for the IRS to align and reminds you to set the MCP speed, heading and initial altitude and to start ACARS.
- Engine Start starts the right engine, then the left, and knows the engine type from the aircraft. It sets the start selector to GND, waits for the fuel point, sets the fuel control switch (RUN, or RICH on a cold Rolls-Royce, which After Start puts back to RUN), and watches for light-off and for the starter to cut out. If a start it began fails, it says so at once, with what to do, starting "Right engine start aborted:".
- Before Takeoff and Descent ring the cabin: "Cabin call: advise the cabin crew for takeoff" and "Cabin call: landing preparation". Descent also reminds you of the ILS: "Set the ILS frequency and course in the NAV radios window, Input Ctrl+N."
- Final Securing switches the APU off, waits two minutes for it to cool down and then for it to stop, and switches the battery off last. The "APU: OFF" checklist line goes by the APU switch, so it ticks while the APU is still cooling down.
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.
- A line ticks itself once the aircraft is in that state, so as you read down a checklist you hear what is already done.
- Press Space to tick a line yourself. If it is a switch the First Officer can set, it sets it, and BA adds the value it reads, such as the flap setting. If the switch never moves, the line unticks itself and you hear "Unable to complete:" followed by the line.
- If the aircraft's state makes a line unsafe to do, the tick is refused and BA says why. A line that switches the fuel pumps, a hydraulic pump, the IRS or a battery off is done only on the ground with the engines stopped, and a packs-off line only on the ground. Until BA has read the aircraft, it refuses too. For example: "Fuel pumps left on: not read on the ground, or the engines are not read stopped."
- A line the First Officer cannot set, such as a read-back item, only records that you checked it.
- A checklist you finished, by hand or with its flow, stays complete for the rest of the flight, even when later flows move the same switches.
- The Checklist status line below the tree shows the selected line with its live value and whether it is complete, without ticking it.
On the Fenix A320, these lines take their live value from the Fenix itself:
- Before Start Checklist, "Takeoff speeds and thrust: SET": V1, VR, V2 and flex from the MCDU's PERF TAKE OFF page, for example "V1 142, VR 145, V2 149, flex 55", or "not set" until you enter them.
- Line-up Checklist and Landing Checklist, "Cabin: READY": "reported ready" or "not reported". In Fenix v3 the cabin crew reports the cabin ready when it is; your cabin call from the cockpit no longer makes it ready.
- Cockpit Preparation Checklist, "Fuel quantity: CHECKED": the Fenix's own total, which counts any extra center tanks.
- Cockpit Preparation Checklist and Approach Checklist, "Baro reference: SET": "standard" or the QNH, for example "QNH 1013", read from the EFIS's own QNH light, so it stays right after you pull and push the baro knob.
The buttons below the tree:
- Run Related Flow switches to the Flows tab and runs the flow that belongs to the selected checklist.
- Reset Section unticks the selected checklist ("Before Start checklist reset"), and Reset All unticks them all ("All checklists reset").
- Load SimBrief is the same as on the Flows tab.
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:
- "Before Start flow started" when it begins and "Before Start flow complete" when it ends.
- Each step as the First Officer does it, for example "Beacon: ON".
- "Already set:" and the step, when the aircraft is already that way, and "Waiting for:" or "Waiting 30 seconds:" and the step while it waits.
- "Captain action required:" and the item, for something you must do yourself.
- "Skipping:" and the step when a switch did not move, or "Timed out waiting for:" when a wait ran out. The flow carries on with the next step.
- "Before Start flow stopped. Unable to complete:" and the step, when a step the rest of the flow depends on fails.
- "Before Start paused", "Before Start resumed", "Stopping after the current step:" and "Before Start flow cancelled" for your own presses.
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
- "No checklist for this aircraft." This aircraft has no First Officer.
- "A flow is already running. Stop it first." Only one flow runs at a time. Press Stop Flow, or wait for the flow to finish.
- "The last flow is still stopping. Start again when it has stopped." The flow you stopped is finishing a step that cannot be interrupted, such as the weather radar test. Wait for "… flow cancelled".
- "… flow stopped. Unable to complete: Engines stopped" You ran a power-up flow with an engine turning. Choose the flow for this point in the flight. A shutdown or securing flow run in the air stops the same way, on "On the ground". A securing flow run with an engine turning, or a shutdown whose engines take more than two minutes to spin down, stops on "Engines stopped": check the engines are shut down, then run it again.
- "Transition altitude. Set both altimeters to standard." (or "Transition level. Set both altimeters to QNH and set local pressure.") On the FlyByWire A380, BA had not yet worked out whether you are flying MSFS 2020 or MSFS 2024, whose FlyByWire builds use different altimeter controls, so it set nothing. Set the altimeters yourself. The same reason makes an A380 or A32NX flow skip its flight director, baro unit, navigation display or ECAM page step. On the A380X in MSFS 2024 a flight director step is also skipped when one flight director is on and the other off, because the aircraft's single FD button cannot set them both. Set them yourself.
- "Skipping: …" The switch did not move, or the aircraft did not show it in time. Set it yourself from BA's panels and carry on; its checklist line stays unticked until the aircraft shows it.
- "No related flow found for this section" That checklist has no flow; work it by hand.
- "SimBrief username not set. Configure it in Settings." Enter your SimBrief username, as described in SimBrief.
- "Failed to fetch SimBrief data: …" Check your internet connection and your SimBrief username, then press Load SimBrief again.
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)
- Press Input Shift+R. The Runway Teleport window opens with the focus in Airport ICAO Code.
- Type the four-letter code. The Runway List fills, and the status line says, for example, "Found 4 runways for London Heathrow".
- Press Enter to jump to the list, and arrow to the runway you want.
- 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)
- Press Input Shift+G. The Gate & Parking Teleport window opens with the focus in Airport ICAO Code.
- 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".
- 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.
- 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
- "Airport database not found. Configure database from File menu first." Build the navigation database; see The Navigation Database.
- A box says the database does not match the simulator. Your database was built for the other simulator version. Follow the box's advice, or see The Navigation Database.
- "Airport XXXX not found in database" Check the code. Add-on airports appear only after you rebuild the database with them installed.
- The stand you want is missing. Untick Show only fitting stands, set the filter to All, and clear the Search field.
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.
- Open File, then Settings, and move to the SimBrief tab.
- In the SimBrief Username field, type the username you use to log in to www.simbrief.com.
- 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:
- Press Output Shift+E to open the Flight Planning window.
- Press Ctrl+Tab until you reach the SimBrief tab (it is the last tab).
- 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.
- Overview is a tree with six sections: Flight Info, Departure, Destination, Cruise, Fuel Summary and Weight Summary. Arrow to a section and press Right Arrow to open it; its details appear as items underneath. Left Arrow closes it again.
- Nav Log is a tree with one line per waypoint: its name, whether it is on the SID or STAR, the airway, the leg and total distance, the course, the planned altitude and the planned speed. Press Right Arrow on a waypoint to see more: its full name and type, the FIR, a frequency, leg time, elapsed time, the forecast wind with its headwind or tailwind component, the outside temperature and ISA deviation, the minimum off-route altitude (MORA), and the planned fuel figures (fuel on board at that point, leg fuel and total fuel used). The window shows the keys at the top of the tab: "Up/Down: waypoints Right: expand Left: collapse".
- Fuel and Weights are read-only lists with the full fuel breakdown and the weights and payload breakdown. Arrow through them line by line.
- Performance has three lists: Takeoff Performance (V1, rotation speed, V2, flaps, thrust and runway conditions), En Route Performance (climb, cruise and descent profiles and speeds), and Landing Performance (reference speed, flaps, brakes and runway surface). Under the take-off and landing lists are the buttons Show Additional Takeoff Info and Show Additional Landing Info, which add runway distances and weight data to the list and move you to them. Press the button again (it is now called Hide Additional…) to remove them. A button stays dimmed when the plan has no such extra data.
- Weather has one list each for the departure, destination and alternate airport, with the METAR and TAF for each. If the plan has no alternate, its list says "No alternate in this flight plan."
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
- "SimBrief username not configured. Please configure in settings.", or the View tab says "No SimBrief username set. Go to File > Define SimBrief Username." Enter your username on the SimBrief tab of Settings, as above.
- "Invalid SimBrief username or no flight plan found for user" Check the spelling of the username, and make sure you have generated at least one plan on the SimBrief website.
- "Timed out contacting SimBrief" Check your internet connection and try again.
- The plan you just made is not the one loaded. BA always fetches your most recent SimBrief plan. Make sure you generated (not just saved) the new plan on the website, then press Load SimBrief again.
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
- Before the flight, to check the route SimBrief planned and the waypoints of your SID, STAR and approach.
- When ATC or SayIntentions gives you a different runway or procedure, to see what the new one looks like.
- In flight, to see how far away each waypoint is (press F5 to refresh).
- At any time, to look up an airport's frequencies or a runway's length, ILS and lighting.
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:
- Route Viewer — your flight plan, with the Load SimBrief, Refresh Position and Describe Route buttons.
- SID — choose a standard instrument departure.
- STAR — choose a standard terminal arrival route.
- Approach — choose an approach procedure.
- Departure — set the departure airport and runway.
- Arrival — set the arrival airport and runway.
- Airport Lookup — detailed airport and runway information.
- 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:
- Load SimBrief — fetches your latest SimBrief plan and replaces the whole flight plan with it. BA says "SimBrief flight plan loaded". Loading a plan also fetches the online taxiway names for both airports in the background, so taxi guidance has them ready when you get there.
- Refresh Position (F5) — works out the distance and bearing from your aircraft to every waypoint. BA says "Position updated". This needs BA to be connected to the simulator; otherwise it says "Not connected to simulator". You can press F5 anywhere in the window.
- Describe Route — creates the AI route briefing (see The AI Route Briefing). It is dimmed until a SimBrief plan is loaded, and while a briefing is being prepared.
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:
- Dist (NM) and Brg (°) — distance in nautical miles and bearing from your aircraft. These appear after you press Refresh Position.
- Airway — the airway or procedure the waypoint is reached by.
- Type and Fix Type — what kind of waypoint or leg it is.
- Leg Dist — the distance from the previous waypoint.
- Course and T/M — the course of the leg, and whether it is true (T) or magnetic (M).
- Notes, Altitude (restrictions such as "AT OR ABOVE 5000 FT"), Speed and Spd Type (speed limits).
- ARINC, Missed (MISS marks a missed-approach leg), Vert Angle, Time, Turn, RNP, Theta, Rho, Flyover and Alt Fix — detailed procedure data that appears on SIDs, STARs and approaches.
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.
- In SID Airport ICAO, type the departure airport's code.
- 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.
- The SID Procedures list fills with the SIDs for that runway. Choose one.
- 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.
- 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
- In Approach Airport ICAO, type the arrival airport's code.
- 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.
- The Transitions list fills with None first, then the approach's transitions. Choose one or leave None.
- 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.
- In Departure ICAO, type the airport's code.
- 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).
- 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.
- 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."
- 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.
- 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.
- 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.
- Press Output Shift+E. The Flight Planning window opens on the Route Viewer and your SimBrief plan loads: "SimBrief flight plan loaded".
- 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.
- 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".
- 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".
- 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.
- 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".
- Press Ctrl+Tab twice to reach the Arrival tab. Type EHAM, choose runway 18R and press Load Arrival: "Loaded arrival EHAM runway 18R".
- 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.
- 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 lists stay empty after typing the ICAO. Check the code has four letters and is in your navigation database. If you recently switched simulator or have not built the database, see The Navigation Database.
- A message box says "Please select a runway and SID" (or STAR, or approach). One of the lists has nothing selected; arrow into it and choose an item.
- The SID or STAR list is empty for my runway. That runway may have no procedures in your data. Try ALL in the runway list.
- The distance and bearing columns are missing. Press F5 or Refresh Position while connected to the simulator.
- Describe Route is dimmed. Load a SimBrief plan first. The briefing is built from SimBrief's data, so a plan built only from these tabs cannot be described.
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
- You need an AI provider and API key set up on the AI tab of Settings. See AI Display Reading and Scene Description for how to choose a provider and get a key.
- You need a SimBrief plan loaded in the Flight Planning window.
- For the taxi part, you need your navigation database built. If you are using SayIntentions, BA also uses its assigned runways and arrival gate, when SayIntentions has them for this flight.
How to use it
- Open the Flight Planning window (Output Shift+E) and make sure your SimBrief plan is loaded.
- 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...".
- 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:
- Flight overview — origin and destination, distance and flight time, cruise altitude, direction of flight, and the countries or regions you cross.
- 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.
- En route — the cities, mountains, coastlines, borders and other features along the way.
- Arrival and STAR — the same for the destination and your STAR, with its bottom altitude.
- Weather — departure and arrival weather from the METARs in your plan, and any significant weather or SIGMETs along the route.
- 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).
- 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:
- The taxi out runs from where you are parked to your departure runway. If BA is connected and your aircraft is standing at the departure airport, it starts from your actual position; otherwise it picks a representative stand for your aircraft size.
- The taxi in runs from a landing exit you can comfortably make, off your arrival runway, to your stand. If SayIntentions has assigned you an arrival gate, that is the stand used; otherwise a typical stand for your aircraft is chosen and described as typical, not assigned.
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
- "AI provider API key not configured. Please configure it in File menu, Settings, AI tab." Add your key on the AI tab of Settings.
- "No SimBrief flight plan loaded. Please load a flight plan first." Press Load SimBrief first.
- "A route description is already being prepared." Only one briefing runs at a time. Wait for "Route description ready".
- "The flight plan or database changed while the route description was prepared. Press Describe Route again." You loaded a new SimBrief plan, or switched the navigation database, while the briefing was running, so it was thrown away rather than describing the wrong plan. Press Describe Route again.
- "Error generating route description: …" The AI service reported a problem, such as no internet connection, a key that is not valid, or a busy service. Check your key and connection and try again.
- The briefing names a runway different from your SimBrief plan. SayIntentions assigned a different runway for this flight; the briefing says so and names both.
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:
- Use your screen reader's browse mode (NVDA's browse mode, JAWS's virtual cursor). Arrow down to read line by line.
- The page title is a heading. Use your screen reader's quick keys to jump: H for headings, B for buttons, K for links, E or F for edit fields and other form fields.
- Text that is not a control, such as a value or a weather report, is read as plain lines. Long text such as a SimBrief OFP on the PMDG tablet keeps its layout.
Using controls:
- Buttons and links: press Enter or Space. You hear "Activating" and the button's name, and the press goes to the real tablet. A control the tablet has greyed out has ", dimmed" at the end of its name, and pressing it says "Unavailable".
- Edit fields: go into the field (your screen reader switches to focus mode), type the value and press Enter. The value is sent to the tablet when you press Enter or leave the field.
- Drop-down lists, check boxes and sliders: use them as on any web page. The change goes to the tablet as soon as you make it.
- Pop-up messages: when the tablet shows an alert or confirmation, such as a success message after saving, BA reads it out automatically.
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.
- Fenix EFB: opens the Fenix tablet site. Every app is a button you can Tab to, and Alt+Home goes back to the EFB's home screen from anywhere; the details are in the Fenix chapter's EFB section. If the Fenix A320 has not finished loading, the window says so instead, in a message you can reach with Tab: "Fenix EFB is not reachable at http://127.0.0.1:8083. Make sure the Fenix A320 is fully loaded, then press Retry." Press Retry once it has loaded. Escape closes an open menu or pop-up on the page first, then the window.
- iFly 737 EFB: opens the iFly SP1 tablet, with its Performance, Navigraph and SimBrief, Payload and Balance, Ground Services, Doors and other apps. BA says "iFly EFB loaded." when the page is ready. If the iFly EFB is not running yet, a message explains why and a Retry button is focused. Press Escape to close, F5 to reload, and Alt+Home to go back to the EFB's main page.
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:
- Press Input Shift+F. The Track Fix Window opens with the focus in Waypoint Name.
- Type the waypoint's name, for example DET.
- Tab to Tracking Slot and choose Slot 1 to Slot 5.
- 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:
- NAV 1 frequency (MHz) and NAV 2 frequency (MHz), from 108.00 to 117.95.
- NAV 1 course (degrees) and NAV 2 course (degrees), from 0 to 359.
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.
- Alternate line select keys (F1-F6 / F7-F12) — by default, in an FMC window, Ctrl+1 to Ctrl+6 press the left line select keys and Alt+1 to Alt+6 press the right ones. Tick this to use F1 to F6 for the left keys and F7 to F12 for the right keys instead, which frees Ctrl and Alt for other shortcuts. The same choice is used by the FMC, CDU and MCDU windows of the other aircraft too.
- Enhanced distance announcements (PMDG only) — when ticked, Output D and Output Shift+D on the PMDG 777 read the FMC progress page instead of the default readout. Despite the name, it does not change the PMDG 737's readouts. Output D gives distance to destination with the estimated time of arrival in Zulu time and the landing fuel; Output Shift+D gives top of climb, step climb or top of descent in nautical miles with its time. The progress page is read from the right CDU, which must be powered. If the page cannot be read, BA falls back to the default readout. This has no effect on other aircraft.
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.
- The simulator itself. This is always available. Whatever weather MSFS is drawing, live or preset, BA can read the wind, temperature, visibility, cloud and precipitation at your aircraft. When you do not use ActiveSky, this is the main source.
- HiFi ActiveSky, if you own it and switch on BA's ActiveSky integration. ActiveSky is a separate weather program that replaces the simulator's weather. When it is running and enabled in BA, BA reads the wind, precipitation, turbulence and station reports straight from ActiveSky, because under ActiveSky some of the simulator's own weather values become unreliable (precipitation, for example, can stick on "extreme snow").
- The internet. The VATSIM network's public METAR feed gives the written report for any airport. Aviationweather.gov supplies real-world SIGMETs, AIRMETs and pilot reports. Open-Meteo supplies forecast winds at height when ActiveSky is not used. You do not need a VATSIM account for any of this; you only need an internet connection.
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
- The first wind is direction (three digits) at speed in knots, for example "045 at 7", or "calm".
- The second wind comes from your destination airport's latest METAR, read from the VATSIM feed. It can include "gusting" and the speed of the gusts. A variable wind is read as "variable at 3". If the report cannot be found you hear "unavailable".
- If you have not chosen a destination runway, the second part is "no destination". Set one with Input Shift+D. See Choosing a Destination Runway.
With and without ActiveSky
- ActiveSky integration off: the wind here comes from the simulator. That is correct for anyone flying with the simulator's own weather.
- ActiveSky integration on and ActiveSky running: the wind here comes from ActiveSky, so it matches what the Weather Radar shows. While you are on the ground, the surface gust is added ("270 at 12, gusting 20"). In the air, BA does not add the surface gust, because a gust measured at the ground has nothing to do with the wind you are flying through at altitude.
- ActiveSky integration on but ActiveSky not answering: BA tells you before giving the simulator's wind, so you are never misled: "ActiveSky not responding, using simulator wind. 270 at 12, no destination".
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
- Before departure, to check the weather at your departure, destination and alternate airports.
- In cruise, to see how the destination weather is changing.
- To get the altimeter setting and runway-relevant wind before an approach.
How to use it
- Press ], then Shift+M. The METAR Report window opens with focus in the Airport ICAO Code box.
- Type the four-letter code, for example EGLL. Letters are capitalised for you.
- 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.
- Read the report with the arrow keys. Press Shift+Tab to go back to the code box and look up another airport.
- 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
- "Please enter an ICAO code" if you pressed Enter with the box empty.
- "ICAO code must be exactly 4 characters (e.g., KJFK, EGLL, KATL)." if the code is too short.
- "No METAR data found for" followed by the code, if the airport does not publish a report or the code is wrong. Small airfields often have no METAR.
- "Error retrieving METAR data for" followed by the code and the reason, if the internet lookup failed.
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:
- ActiveSky METAR: the report for the same airport as ActiveSky has it. When you fly with ActiveSky this is the weather the simulator is actually showing you, which can differ from the real-world VATSIM report, especially if ActiveSky is in a historical or custom mode.
- Forecast: a list with Now, +1 hour, +2 hours, and so on up to +6 hours. Choosing an offset asks ActiveSky to build a forecast METAR for that time from the airport's report and forecast. The ActiveSky box then updates, and its name tells you which time you are reading, for example "ActiveSky METAR, +2 hours".
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
- Before departure, as a weather briefing.
- In the climb and cruise, to check for turbulence, icing reports, thunderstorm SIGMETs, and to pick a better cruise level from the winds aloft.
- Before descent, to check cloud layers, icing and the surface wind.
- Any time something feels wrong: "Am I in cloud?", "Is it raining?", "Is that turbulence going to get worse?"
How to use it
- Press ], then Shift+R. The Weather Radar window opens and fetches everything at once. Focus starts in the Weather at Current Position list.
- 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.
- Press Tab to move to the next list, Shift+Tab to go back.
- 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.
- Press F5, or Alt+R for Refresh (F5), to fetch fresh data immediately.
- Press Escape, or Alt+C for Close, to close. Focus returns to the simulator.
The controls, in Tab order, are:
- ActiveSky status (only when ActiveSky integration is on)
- Weather at Current Position
- Closest Station Weather (ActiveSky only)
- Vertical Profile (ActiveSky only)
- Route Advisories (ActiveSky only)
- Nearby Advisories
- Winds Aloft
- Decode advisories into plain English checkbox (Alt+D)
- Refresh (F5) button
- Close button
- 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:
- Wind: "Wind: 270° at 12 knots". The wind at your aircraft's position and height, the same as Output I. In cruise this is the wind you are flying through, not the wind at the ground.
- Visibility: "Visibility: 4.5 km (2.8 statute miles)", or "Visibility: 10+ km (6+ statute miles)" when it is good. Both units are given because pilots in the United States think in statute miles and most of the world in kilometres. Under 5 km (about 3 miles) you are near the limits for visual flight; under about 1,500 metres you are in low-visibility territory and should expect an instrument approach.
- Temperature: "Temperature: -12°C". The outside air temperature at the aircraft. At or below about +10°C with visible moisture (cloud or rain), icing is possible; that is when most aircraft need engine anti-ice.
- In cloud: "In cloud: Yes" or "In cloud: No". Whether the aircraft is inside a cloud right now. Useful for anti-ice decisions and for knowing whether you will see the runway yet.
- Precipitation: "Precipitation: None", or for example "Precipitation: Moderate rain (35%)". The type is rain, snow or freezing rain, and the intensity is light, moderate, heavy or extreme. The percentage is the simulator's own intensity figure. Freezing rain is serious: it builds ice quickly on any aircraft.
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:
- SIGMETs and AIRMETs. These are official warnings issued to all pilots. A SIGMET warns of significant weather that affects every aircraft: thunderstorms, severe turbulence, severe icing, volcanic ash, tropical cyclones, dust storms. An AIRMET warns of weather that matters mostly to smaller aircraft: moderate turbulence or icing, low cloud and poor visibility (IFR conditions), mountain obscuration, low-level wind shear.
- PIREPs, pilot reports. Real pilots report the turbulence and icing they actually met, with the height and the aircraft type. A pilot report of moderate turbulence at the level you are about to climb to is one of the most useful things you can know.
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:
- A first line with its type and hazard, for example "[SIGMET] Thunderstorms", followed by a qualifier such as embedded or frequent if one is given.
- "Altitude:" with the heights it covers, if known.
- A line giving the bearing and distance from you to the nearest part of the area, for example "240° / 85 nm", and the time it is valid from and to.
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:
- Wind at altitude: "Wind (at altitude): 280° at 45 knots". The wind at your aircraft, the same figure Output I gives you.
- Turbulence: "Turbulence: moderate". This line only appears when there is turbulence worth reporting. ActiveSky reports turbulence on a scale of 1 to 100 and sits at around 25 even in perfectly calm air, so BA hides that baseline and only shows the line from light upwards, using the words pilots and controllers use: light, moderate, severe or extreme. If there is no Turbulence line, the air is smooth.
- Surface wind: "Surface wind: 250° at 14 knots, gusting 24". The wind at the ground below you. On the ground and on approach this is the wind that matters for takeoff and landing, including the gusts, which you add half of to your approach speed on many aircraft.
- Visibility: "Visibility: 6.0 statute miles (9.7 km)", or "Visibility: 10+ statute miles (16+ km)". ActiveSky reports visibility in statute miles, so here miles come first.
- Temperature at altitude: "Temperature (at altitude): -45°C".
- Surface temperature: "Surface temperature: 12°C". The temperature at the ground below you. This is the figure for the cold temperature calculator and for takeoff performance.
- Temperature and dew point: "Temperature/dew point: 12 / 9°C". Only ActiveSky provides the dew point. When the temperature and dew point are within two or three degrees of each other, expect mist, fog or low cloud, especially as the air cools in the evening.
- Cloud ceiling: "Cloud ceiling: 1,200 ft AGL", the height above the ground of the lowest layer that covers more than half the sky (broken or overcast). This is what decides whether you will see the runway in time. If there is no such layer below 8,000 feet you read "Cloud ceiling: above 8,000 ft AGL or no broken/overcast layer".
- QNH: "QNH: 1013 hPa / 29.91 inHg", the altimeter setting at your position in both units. Set this on your altimeter below the transition level.
- In cloud: "In cloud: Yes" or "No". This still comes from the simulator, because ActiveSky does not report it, and the simulator always knows where its clouds are. If the simulator is not connected you read "In cloud: unknown (sim not connected)".
- Precipitation: "Precipitation: light rain", "heavy snow", "thunderstorm with heavy rain", "freezing drizzle", "showers of rain" and so on, or "None". Under ActiveSky this is read from the nearest station's METAR rather than from the simulator, because the simulator's own precipitation value is unreliable under ActiveSky. The same source is used by the precipitation announcements, so the window and the spoken alerts always agree.
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:
- "Broken, 2,400 to 7,800 feet, moderate icing, rain"
- "Overcast, 14,000 to 22,000 feet, light turbulence"
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:
- "Surface: 250 at 14, gusting 24, 12"
- "10,000 feet: 270 at 38, minus 6"
- "34,000 feet: 280 at 95, minus 49, light turbulence"
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.
- With nothing on your route you read "No advisories on route."
- With the Decode advisories into plain English checkbox unchecked, each advisory is shown as ActiveSky gives it: a header such as "MHTG SIGMET J5 EMBD TS", a "Valid until:" line, and the advisory text in code, with a blank line between advisories. ActiveSky often lists the same advisory several times, once for each leg of the route it touches; BA shows it once.
- With the checkbox checked, each advisory becomes a plain-English summary, for example: "MHTG SIGMET J5: Central American FIR, embedded thunderstorms, observed at 1830Z, tops FL520, moving west at 5 knots, no change expected." then "Valid until 2200Z." The summary names the region, the hazard, whether it was observed or forecast, the heights, its movement and whether it is getting stronger or weaker. The list of latitude and longitude points that draws the area is left out of the summary because it means nothing when read aloud; uncheck the box if you want it. If BA cannot recognise the hazard it shows the advisory as written rather than risk leaving out what it is warning about.
- Where BA can work out where the area is, each advisory ends with a Location line: "Location: 123 nm ahead", "Location: 95 nm behind", "Location: less than one nautical mile ahead", or "Location: Inside" when you are in it. Distances are measured to the nearest edge of the area. Ahead and behind are judged from your heading. Some advisories have no location BA can work out, and then there is simply no Location line.
- If ActiveSky did not answer, the list says "unavailable".
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
- Everything says "Press F5 or Refresh". The first fetch has not finished or failed. Press F5 and check the Status line at the end of the Tab order.
- "Aircraft position unavailable". BA is not connected to the simulator, or you are still in the menus. Load into a flight and press F5.
- The ActiveSky lists are missing. The integration is switched off. Turn on Enable ActiveSky integration on the Weather settings tab.
- The ActiveSky lists say "unavailable" and the status line says "not detected". ActiveSky is not running on this PC, or has not finished starting. Start it, wait until it shows weather, and press F5. BA talks to ActiveSky through the small web service ActiveSky runs on your own PC, so a firewall that blocks local connections can also cause this.
- QNH or temperature showed huge numbers such as 1014999 hPa. This happened with older versions of BA on Windows set to a language that uses a comma for decimals. It is fixed; update BA.
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
- Open the Settings window (see The Settings Window) and go to the Weather tab.
- In the ActiveSky (HiFi) group, check Enable ActiveSky integration (Alt+A).
- 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:
- "Entering cloud" and "Leaving cloud" as you pass into and out of cloud.
- "Precipitation started:" followed by the intensity or type, "Precipitation now" followed by the new description when it changes, and "Precipitation stopped".
- Without ActiveSky, the description is the intensity: light, moderate, heavy or extreme, for example "Precipitation started: moderate". It is spoken again only when it moves to a different intensity band.
- With ActiveSky, it is the full description from the nearest station's METAR, for example "Precipitation started: light rain" or "Precipitation now heavy snow". The same description is never repeated.
- "Visibility low:" followed by the visibility in kilometres when it drops below 1.5 kilometres, and "Visibility improving:" when it rises back above, for example "Visibility low: 0.8 km".
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:
- "Icing conditions, ice accumulating" when ice starts to build up. Turn on your anti-ice (or check it is on) and consider leaving the icing layer by climbing or descending.
- "Icing conditions cleared" when the ice has gone.
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:
- "Entering light turbulence" (or moderate, severe, extreme) when you leave smooth air.
- "Turbulence now moderate" when it gets worse.
- "Turbulence easing to light" when it gets better.
- "Smooth air" when it has gone.
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.
- Approaching: when an advisory ahead of you comes within the en-route advisory distance (100 nautical miles unless you change it): "Route advisory, 95 nautical miles ahead:" followed by a short summary: its name, region, hazard and heights, for example "Route advisory, 95 nautical miles ahead: MHTG SIGMET J5, Central American FIR, embedded thunderstorms, tops FL520." Movement, trend and validity are left out of the spoken version to keep it short; read the Weather Radar's Route Advisories list for those. An advisory that is already behind you is not announced as approaching.
- Already there: if you are already inside an area when BA first sees it: "Route advisory at your position:" followed by its summary.
- Entering: when you fly into the area: "Entering advisory area:" followed by its summary.
- Leaving: when you are clear of it: "Left advisory area:" followed by its name only, to keep it short. BA waits about a minute of being outside before saying this, so brushing the edge of an area does not make it come and go.
- No location known: an advisory BA cannot place on the map is announced once when it first appears: "Route advisory:" followed by its summary.
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
- Nothing about cloud or rain. Check Auto-announce weather state changes is on, and that BA is connected to the simulator.
- No turbulence or "Active sky weather updated" callouts. These need ActiveSky running, Enable ActiveSky integration on, and Auto-announce weather state changes on. Turbulence also needs Announce turbulence changes.
- No route advisory callouts. ActiveSky must have your flight plan loaded, through its SimBrief link or by loading it in ActiveSky. Open the Weather Radar: if Route Advisories says "No advisories on route.", there is simply nothing to announce.
- Too much talking. Turn off the parts you do not need, or set a longer weather announcement interval. You can also use the Monitor Manager to control other announcements; see The Monitor Manager.
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
- Press ], then Ctrl+Shift+T. The Cold Temperature Altitude Correction window opens with focus in the first box.
- 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.
- 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.
- 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.
- 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).
- 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:
- "Published 3000 ft: corrected 3290 ft (add 290 ft)". Fly the corrected altitude.
- "Published 1010 ft: no correction needed (warm), use 1010 ft". When it is not cold enough to matter, the published altitude stands. BA never lowers an altitude on a warm day.
- A line you mistyped is shown as, for example, "3OOO: not a number".
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:
- "Enter a valid field elevation in feet."
- "Field elevation must be between minus 2,000 and 15,000 feet"
- "Enter a valid temperature in degrees Celsius."
- "Temperature must be between minus 90 and plus 60 degrees Celsius"
- "Enter at least one published altitude, one per line."
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
- Make sure you are on the ground.
- Press Output Alt+Y.
- 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:
- A stand or gate. If you are within about 40 metres of a parking spot, BA names it: "Gate A25", or "Parking 12", "Ramp 3", "Hangar 2" if that is how the airport names its spots. Close to a runway, BA only names a stand when you are very close to it, so that a hold line or the runway itself is never reported as a gate.
- A runway. If you are on runway pavement, anywhere along its length, BA names the runway by the end nearer to you: "Runway 27L".
- A taxiway. If you are on a named taxiway: "Taxiway B".
- Near a taxiway. If you are not on any mapped line but there is a named taxiway point within about 60 metres: "Near taxiway K". This often means you are on an apron or a stretch of pavement the airport data does not map.
When nothing matches, you hear "Not on a known taxiway or ramp at" followed by the airport code. Other answers you may hear:
- "In flight." Where Am I only works on the ground.
- "No airport nearby." You are not at an airport in the navigation database.
- "No taxi data available for" and the airport code. The navigation database has no taxiway map for this airport.
- "Airport database not available." BA has no navigation database loaded. See The Navigation Database.
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
- On the ground, press Output Alt+L.
- 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.
- Where Am I. The same line Output Alt+Y gives.
- 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.
- 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:
- "No surroundings data for" and the airport code. BA could not find any buildings or places for this airport.
- "Nothing within 600 metres." There is data, but nothing close enough to mention.
- "Surroundings lookup failed." Something went wrong. Try again in a moment.
- "In flight." Look Around only works on the ground.
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
- On the ground, press Output Ctrl+Shift+L.
- 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.
- 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.
- 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.
- 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:
- "COM 1 standby 121.9" or "COM 1 active 121.9": the frequency is set.
- "Could not tune COM 1 standby to 121.705. It reads 121.7.": the radio set something different, usually because it uses a different channel spacing.
- "COM 1 did not report back after tuning 121.9.": BA sent the frequency but could not read the radio back.
- "Not connected to the simulator.": BA is not connected.
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:
- each building is called at most once every five minutes, and BA says at most one passing callout every ten seconds;
- callouts are spoken only while you are taxiing, between about 2 and 40 knots;
- they wait their turn behind taxi guidance, and never interrupt it;
- they are never spoken on a runway, during takeoff, during the landing rollout, or while docking at a gate.
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:
- Same as taxi (default): use the taxi setting.
- Off: no ground speed callouts while takeoff assist is active.
- Every 5 knots or Every 10 knots: a different step just for the takeoff roll.
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:
- "Off the pavement, on grass." Your wheels have left the paved surface. The last word tells you what you are on now: "grass", "an unpaved surface", "water", or "snow or ice".
- "Back on pavement." You are back on a paved surface.
- "Now on grass." (or another surface) The surface changed again while you were already off the pavement.
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:
- names for taxiways the navigation database leaves unnamed;
- alternative names for stands, so a gate a controller calls "A24" can be matched to the stand your scenery calls "A 24A";
- airport buildings such as terminals, concourses, hangars, the tower and fuel.
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:
- "Taxiway names refreshed for KJFK: 12 added."
- "Taxiway names refreshed for KJFK. No new names found."
- "Online taxi data is switched off. Nothing refreshed."
- "No airport nearby."
- "Aircraft position unavailable."
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
- Where Am I says "Not on a known taxiway or ramp". You may be on an apron or a piece of pavement the airport data does not map. Try Look Around (Output Alt+L), which can still tell you which apron you are on and what is around you.
- A taxiway is named in the clearance but BA never says it. The navigation database may not name it. Make sure online names are switched on, then press Refresh Taxiway Names on the Taxi Guidance tab.
- Look Around says "No surroundings data". The airport has no buildings in the navigation database, OpenStreetMap or your scenery. At add-on airports, check that Read installed scenery for airport buildings (offline) is on and look at the Scenery index status box.
- No passing callouts. They are off by default, and have the limits listed in Buildings you pass.
- Tuning from the Surroundings window says "Could not tune". The frequency in the list does not match a channel your radio can select. The message tells you what the radio reads now, so you can adjust it with the aircraft's own radio controls.
- "In flight." All of these features work only on the ground.
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.
- A steering tone for the fine steering, second by second: tone in your left ear, steer left; in your right ear, steer right; quiet, you are pointing the right way.
- Spoken instructions for the planning: turns coming up, the taxiway you have joined, runways you must stop before, the distance to your stand, and when you are lined up.
Follow the tone, and listen for the words.
Here is how the pieces fit together on a typical departure:
- 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.
- 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.
- Guidance starts straight away. You release the parking brake, taxi, and follow the tone and the callouts.
- At each runway hold line BA tells you to stop. When ATC clears you across or onto the runway, you press Continue (Input Y).
- 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 navigation database. Without one, the planner says "Airport database not available. Configure database in settings."
- A connection to the simulator, with your aircraft on the ground at the airport. BA starts the route from wherever you are standing.
A few things make the experience better.
- Online taxiway names (on by default) fill in names your scenery leaves blank and add the names of painted holding points such as "A2", which the named holding point features need. See Online names.
- Rebuilding your database after a scenery change, or BA will still be using the old airport's taxiways.
- Knowing where you are. Output Alt+Y (Where Am I) is a good first check before you plan a route.
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:
- Runway — taxi to a runway for departure.
- Gate / Parking — taxi to a stand, gate or parking spot.
- Progressive Taxi — taxi one leg at a time, ending at a hold short or a point ATC named, with no final destination yet.
- Deice Area — taxi to a remote de-icing pad (these come from GSX airport profiles).
- Place — taxi to a named place such as an FBO, hangar, fuel island, terminal or cargo area.
Each one is explained in Choosing Your Destination.
Gate search
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.
- For runways, each item reads like "Runway 27L". Closed runways are left out. A runway whose full length can only be reached by taxiing along it first reads "Runway 28 (backtrack required)"; see Full-length departure (requires backtrack).
- For stands, each item names the stand, its type and its equipment, for example "Gate A 25 - Gate Medium (Jetway)". The stands nearest to you by taxi distance come first, so a stand just across a runway, close as it looks, is listed behind the ones you can reach without going all the way round. If the stand is also known by another name online, the item ends with something like ", also 25 (online)". A stand the taxiway network does not reach is still listed, with "(no taxi route)" on the end, so you know it exists; BA will tell you it cannot route there if you choose it.
- For places, each item names the place, its kind and the stand it ends at.
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.
- Choose a taxiway for "via A, hold short of taxiway B". Guidance stops where your route first meets that taxiway, with "Stop. Hold short of taxiway B. Press continue when cleared."
- Choose a holding point for "via L, hold short of L2". Guidance stops at that point, with "Stop. Hold short of holding point L2. Press continue when cleared." The holding points come from online data, so they need the online names setting switched on and the airport's data loaded.
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:
- "Note: this route starts at holding point L2. No stop will be called there." The route begins at the point itself, so you are at it or just short of it, and there is nothing left to count down. You can also hear it after "Route changed", when a new route is worked out close to the point. Stop there yourself until you are cleared.
- "Note: holding point A1 lies beyond the Runway 16 hold short point, so no stop is called there." The point is past the line where guidance already stops you before your runway.
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
- Open the planner with Input Shift+Y.
- Check the airport.
- Choose the destination type and the destination: the runway or stand ATC gave you.
- Tick any runway option ATC gave you: intersection, named holding point, low visibility, or backtrack.
- Set First taxiway to the first taxiway ATC said.
- 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.
- Press Add Taxiway and choose the next taxiway. Repeat until you have entered them all.
- 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:
- Try the online names setting, if it is off. It fills in names your scenery leaves blank.
- Check you have the right airport, and that your database was built after you installed this scenery.
- Some default sceneries have fewer taxiways than the real airport. You may need to pick the nearest equivalent, or use (None - calculate shortest path) and let BA find the way.
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."
- Destination type: Runway. Destination: Runway 27L.
- First taxiway: A.
- 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.
- 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.
- Destination: Runway 09.
- First taxiway: A.
- Add Taxiway, Taxiway 2: C.
- Add Taxiway, Taxiway 3: A. It is in the list, because only the taxiway immediately above, C, is left out.
- 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:
- First taxiway N, and on that row set Hold short of runway to 15R.
- Add Taxiway. Because the row above holds short, N is offered again. Choose N, and set its Hold short of runway to 22L.
- 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."
- Destination: Runway 27L. Tick Intersection departure and choose B3 in the list that appears.
- First taxiway A, Taxiway 2 B3.
- 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."
- 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.
- Open the planner with Input Shift+Y. The airport is filled in.
- Destination type: Gate / Parking. In Gate search, type B12, then choose the stand in Destination.
- First taxiway K, Taxiway 2 L.
- 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.
- 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.
- 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."
- 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.
- Press Calculate Route.
When you reach the end of the leg, the tone stops and you hear one of:
- "Hold short of runway 09. Set a new route when cleared."
- "Hold short of taxiway D. Set a new route when cleared."
- "Across runway 09. Hold position. Set a new route when cleared."
- "Hold at VIKAS. Set a new route when cleared."
- "Route ended. Hold position. Set a new route when cleared."
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:
- Takes your aircraft's current position.
- Builds a route that follows your taxiways in order.
- 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.
- Speaks a summary and writes it into the Last route summary box.
- Starts guidance.
Reading the route summary
A summary has the form "Route to (destination) via (taxiways). (distance), (runways and holds)." For example:
- "Route to Runway 27L via A, B. 1450 metres, crossing runway 22R."
- "Route to Gate B 12 - Gate Heavy (Jetway) via K, L. 2.3 kilometres, crossing runways 09L and 09R."
- "Route to Runway 04R via C. First taxi onto C. 800 metres."
What each part means:
- via ... lists the taxiways in the order you will use them.
- then ... after your taxiways names the ones BA added to reach the destination. You hear it when the taxiways you entered stop short of it: enter only L for Runway 16 and you may hear "Route to Runway 16 via L, then W, EX23, E, EX33, D. 2.0 kilometres." Everything before "then" is what you entered; everything after it is BA's own choice of route from there. If ATC gave you the rest of the route, add those taxiways and calculate again.
- First taxi onto C or First taxi via ... to reach C means your first cleared taxiway is some way from you, and BA has added the bit of apron or link taxiway that gets you onto it.
- The distance is the whole route. Short distances are in metres or feet, depending on your setting; long ones switch to kilometres, or nautical miles if you use feet.
- crossing runway X and entering runway X name every runway the route crosses or goes onto, other than your own departure runway at the end. A runway crossed twice says "twice". Both ends of one runway are named together, such as "10L/28R".
- N hold short points counts the other stops you asked for, such as a taxiway hold short.
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:
- "No airport loaded. Enter an ICAO code first."
- "Please select a destination."
- "No taxi route to Gate C 9. This stand can't be reached by the taxi network."
- "No taxi route to Gate C 9. It isn't connected to the taxiway network you're on."
- "No taxi route from here. You aren't on the connected taxiway network, and the way onto it crosses runway 13." BA refuses to steer you across a runway on ground its data does not map.
- "Gate list updated from GSX. Please choose the destination again." GSX finished loading and the stand list changed. Choose your stand again and recalculate.
- "No taxi path data available for this airport.", "Could not find a nearby taxiway node." or "Could not calculate a route to the destination." Usually missing or broken taxiway data in the scenery.
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:
- "Taxiway A. Steering guidance active." You are already on your first taxiway.
- "Steering guidance active. Join taxiway A in 60 metres." You are on a stand or apron, and the first named taxiway is that far ahead.
- "Steering guidance active." The route has no named taxiways.
- "Stop. Hold short of runway 22R. Press continue when cleared." You are already standing at a runway hold line that is the route's first stop. The tone stays silent until you press Continue.
Straight after that, BA may add:
- Your intersection or holding point, for example "Intersection B3 departure, runway 27L. About 2400 metres of runway ahead."
- Any warning about unmapped ground at the start, or a route that does not reach the runway.
- A turn cue, when the route starts behind you or at a sharp angle. This is common after a pushback, when you are facing the wrong way. You may hear "Taxiway A is behind you. Turn left to come around.", "Make a U-turn to the right.", "Sharp turn left onto taxiway K." or "Sharp turn right."
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.
- It stays on until you are within half a degree of the runway heading, and comes back if you drift more than one degree.
- It reaches full pan at 15 degrees instead of 30.
- If you are to the side of the centreline, it does not just point you along the runway; it points you back towards the centreline at an angle (up to 30 degrees), easing off as you get closer, so you arrive on the line already pointing the right way.
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:
- 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."
- 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:
- "Slow for turn." above about 10 knots approaching a turn.
- "Slow for sharp turn." above about 8 knots approaching a turn of 60 degrees or more.
- "Taxi speed, 32 knots." above 30 knots on a straight taxiway.
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:
- Output Y tells you your taxiway, your next turn and the distance to go, for example "Taxiway A, right onto taxiway B in 150 metres, 1200 metres to Runway 27L." At a hold it reminds you what you are holding for.
- Output Ctrl+Y repeats the last instruction exactly, if another sound drowned it out. If nothing has been said yet you hear "No taxi instruction yet.", and with no guidance running, "No taxi guidance active."
- Output Alt+Y tells you where you are on the airport. See Where Am I.
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:
- before every runway your route crosses or enters,
- at the departure runway itself,
- after any taxiway row where you ticked Hold short, and
- at any runway you chose in a Hold short of runway list.
The countdown
As you approach a hold short, BA counts you down in three steps, starting earlier the faster you are going:
- "Hold short runway 22R in 120 metres."
- "Hold short runway 22R in 60 metres. Slow down."
- "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:
- At the line: "Stop. Hold short of runway 09 and runway 01. Press continue when cleared for runway 09."
- When cleared for 09, press Continue. You hear "Runway 09 cleared. Still holding. Press continue when cleared for runway 01." Stay where you are.
- 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:
- 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."
- 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.
- 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.
- "Crossing runway 22R at B." A reminder that the hold line just ahead is part of your route, a runway crossing you have planned.
- "Passing the runway 09L at F hold line." The route passes a runway hold line but does not then go onto the runway, for example a line set back to protect an ILS beside your taxiway. You are not crossing a runway here.
- "Warning: approaching runway 36L at M8, off route." You are heading towards a runway hold line that is not on your route, for example because you turned the wrong way or missed a turn. Stop and check where you are with Output Alt+Y. This only speaks for a hold line actually ahead of you, on your heading or on the taxiway you are turning onto, not for lines beside a parallel taxiway you are correctly following. It repeats for the same line no more than every ten seconds.
Lining Up on the Runway
At the departure runway, guidance takes you from the hold line onto the centreline.
- 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."
- 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."
- 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.
- 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
- "Off route. Unable to recalculate." BA could not find a route from where you are. Stop, check your position with Output Alt+Y, and plan a new route in the planner.
- "Off route. Could not follow clearance. recalculated route too long. Continuing on original route." or "... recalculated route heads backwards ..." The only new route BA could find would take you far out of your way, or send you back the way you came, so it kept your original route. Get back onto it, or plan a new one. The middle part may instead give a technical reason from the route builder.
- "Off route. Unable to recalculate. The way to Gate C 9 crosses runway 13." and similar. The only way to your destination from where you are crosses a runway over ground the airport data does not map, so BA will not steer you there.
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:
- "5 metres. Continue ahead for docking." or "Docking guidance ahead. Continue forward."
- "Align with Gate B 12, heading 270. Then continue ahead for docking guidance."
- "Aligned with Gate B 12. Continue ahead. Docking guidance will take over."
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.
- Steering tone type, Volume (default 5 percent), Test Tone, Invert steering tone direction (steer AWAY from the tone) and Hard-pan steering tone (full left or full right; speaker-friendly) — the tone settings described in Settings that change the tones.
- Announce crossing taxiways (e.g., "Crossing taxiway Link 53") — on by default. Untick for quieter taxiing.
- Announce ground speed every: and During takeoff assist, announce ground speed every: — see Ground speed.
- Use feet for distances (default: metres) — every taxi distance in feet instead of metres. This covers turns, hold short countdowns, stands, runway exits and the status readouts.
- Show ground traffic distances in metres (default: feet) — a separate setting for the ground traffic callouts only. See Ground Traffic.
- Auto-select arrival gate in GSX on route calculation — see Gates, GSX and Docking.
- Docking guidance settings — see Docking Guidance.
- Refresh Taxiway Names, Online taxiway, gate and airport building names (OpenStreetMap + X-Plane) and Read installed scenery for airport buildings (offline) — where BA gets names from. See Knowing Where You Are.
- Announce airport buildings as you taxi past them and Tell me when I leave the paved surface — optional extra callouts while taxiing, such as "Passing Concourse B, on the left." and "Off the pavement, on grass." See Callouts While You Taxi and The Off-the-Pavement Alerts.
- SayIntentions import starts taxi guidance immediately — see SayIntentions Taxi Import.
Two related settings live elsewhere:
- Auto-activate Takeoff Assist on lineup, on the Hand Fly tab, on by default.
- The sound device your guidance tones play on, on the Audio tab.
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:
- The takeoff roll. While takeoff assist is active, proximity, route and queue callouts are silent. Your hands are on the rudder and the thrust levers, and you could not act on them anyway. The runway watch keeps running while you line up and wait, and only goes quiet once your takeoff roll reaches 30 knots.
- The landing rollout. While you are still rolling down the runway after landing, traffic callouts wait, so they never talk over the exit and runway-end callouts. This ends the moment you come to a stop, so if ATC holds you on the runway you still hear about the traffic around you.
- A fast landing exit. While you turn off the runway on a landing exit at 30 knots or more, only "Stop" and the runway watch are spoken. "Slow down" and the other callouts wait until you are below 30 knots. If they are still true then, you hear them.
- In the air. The monitor is a ground feature. In the air, use TCAS instead; see TCAS Traffic.
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:
- "Delta A320"
- "Lufthansa 747"
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:
- "stopped"
- "same direction": moving the way you are pointing
- "opposite direction": moving the other way, off to one side
- "head-on": coming toward you
- "crossing left to right" or "crossing right to left"
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
- Only traffic in front of you can make you slow down or stop. "Slow down" and "Stop" are given only for aircraft within about 120 degrees either side of your nose. An aircraft behind you gets at most an awareness callout. If you then turn to face a very close aircraft, you do hear "Stop".
- Traffic moving away is not a threat. If an aircraft is pulling away from you, for example the one ahead moving off in the queue, BA does not tell you to stop for it. If it stops again while still close, or you start closing on it, you hear "Stop" then. Whatever the speeds say, BA always warns you once the gap is down to about 200 feet.
- No nagging. Each zone is announced when you enter it, not again and again. If you back off and then close in again, BA speaks again only for a more serious zone, or once 15 seconds have passed. There is one exception: after a "Stop", if you creep another 50 feet or so closer, you hear "Stop" again.
- Parked aircraft beside your route. When taxi guidance has a route, BA knows where you are actually going. An aircraft parked beside your route, which you will pass rather than hit, does not draw "Slow down". It can still draw "Stop" if you get within about 250 feet of it. "Slow down" and "Stop" are kept for traffic on or near your route, traffic genuinely close, and moving traffic on a collision course.
- One aircraft at a time in a line. When several aircraft are lined up ahead of you on your route, you hear about the first one, the one you would reach first, rather than every one behind it. The queue callout tells you how many there are. A "Stop" is never held back, though, whichever aircraft it is for.
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:
- "stopped": it is sitting on your route. Expect to stop behind it, or to be given another way round.
- "same direction": it is going the same way as you. Keep your distance.
- "coming toward you": it is heading toward you along your route. Slow down, be ready to stop, and check with ATC.
- "crossing": it is crossing your route ahead.
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.
- "Number 3 in the departure queue." There are two aircraft ahead of you in the line.
- "First in the departure queue." You have moved up to the front. You only hear this after you have been further back.
- "... More traffic holding further ahead." Added when there are more aircraft beyond the end of your line.
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:
- it only comes after "ahead is moving", and only when that aircraft moved off along your route;
- you must be stopped, on your route, with taxi guidance running, and not on a runway;
- it is never given while anything else is within about 250 feet ahead of you, and it waits while the departing aircraft is still that close;
- it is given at most three times, 20 seconds apart, and stops as soon as you start moving.
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:
- hold short of a runway with taxi guidance, including a Progressive Taxi hold at a runway;
- cross a runway;
- backtrack along a runway;
- line up on a runway with taxi guidance;
- wait on the runway with takeoff assist active, until your takeoff roll reaches 30 knots;
- are on a runway's pavement for any other reason, including stopped on it after landing.
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:
- "Runway 27L: no traffic seen on the runway or on final."
- "Runway 27L: no traffic seen on the runway. Delta A320 on final runway 27L, 4.5 miles."
- "Runway 27L: Delta A320 on the runway, rolling, same direction as you, ahead, 3000 feet. No traffic seen on final."
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:
- "Delta A320 on runway 27L, taxiing, coming toward you, ahead and to the left, 1200 feet." An aircraft has appeared on the runway. Its movement is "stopped", "taxiing" or "rolling" (30 knots or more), with its direction where BA can tell: "coming toward you", "opposite direction", "same direction as you", "moving left to right" or "moving right to left".
- "Delta A320 on final runway 27L, 6.2 miles." An aircraft is on final approach to the runway.
- "Delta A320 short final runway 27L, 1.8 miles." An aircraft on final is now within 2 miles. Expect it to land very soon.
- "Delta A320 landing runway 27L." An aircraft is over the runway, landing. This includes an aircraft already in the flare.
- "Runway 27L: no traffic seen on the runway now." The aircraft that was on the runway has gone. If there is still traffic on final, you hear "Runway 27L: no traffic seen on the runway now. Traffic still on final."
Each aircraft is announced once. One that disappears for a moment and comes back is not announced again.
What to do
- Holding short. Listen to the status and keep it in mind when ATC clears you. If BA reports an aircraft on short final or landing, and you have been cleared to cross or line up, stop and query the clearance with ATC before you move.
- On the runway. If you hear of an aircraft landing, or on short final, while you are on the runway, tell ATC and follow their instructions. If you are crossing, the quickest way off the runway is usually straight ahead.
- Waiting for takeoff. An aircraft reported on the runway ahead of you means the runway is occupied. Do not start your takeoff roll until you are cleared.
Interrupting or waiting
How runway news is delivered depends on where you are:
- On the runway (crossing, backtracking, lining up, waiting for takeoff, or stopped on it), a new aircraft on the runway, an aircraft on short final or landing, and a first status that reports traffic on the runway or on short final all interrupt whatever is being said. This is urgent.
- At a hold, and while turning off the runway after landing, runway news waits its turn. It never cuts off a taxi or exit instruction.
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:
- your place in the queue, for example "Number 3 in the departure queue.", if you are stopped or slow in one;
- the status of the runway you are watching, in the same words as the runway watch's first status.
Other answers:
- "No ground traffic nearby."
- "Ground traffic monitor not active in flight."
- "Ground traffic monitor not connected to the simulator."
What Interrupts and What Waits
Taxiing is busy, and taxi guidance has a lot to say. To keep the important things audible:
- Only three kinds of callout interrupt what is being said: "Stop", "Slow down", and runway news while you are on the runway.
- A "Stop" is never cut off by a "Slow down" or by a second "Stop" a second later. A newer warning only cuts in straight away if it is more urgent, and otherwise is spoken a moment later.
- Everything else (awareness, on your route, converging, the queue and runway news at a hold) waits its turn behind other speech. At most one of these alerts is spoken every three seconds.
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:
- Show ground traffic distances in metres (default: feet): off by default, so traffic distances are in feet, the usual aviation convention. Switch it on to hear them in metres, for example "Slow down, Delta A320 ahead, 120 metres."
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
- I hear no traffic callouts at all. The automatic callouts only run while taxi guidance is running. Start a route in the taxi planner. Check with Output Alt+G that BA can see traffic at all.
- An aircraft I know is there is never mentioned. BA can only see what the simulator shows. Some AI traffic and some online pilots are not shown, or are only shown close by. This is one of the reasons BA never calls a runway clear.
- No callouts during the takeoff roll or landing rollout, no "Slow down" for an aircraft parked beside my route, or only the first aircraft in a line is mentioned. All deliberate; see When Ground Traffic Speaks and How the zones behave.
- The runway watch says "no traffic seen" but ATC holds me. ATC knows about traffic BA cannot see, or has other reasons. Always follow ATC.
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:
- The stand's name — here "A 12". BA uses one naming rule everywhere, so the taxi planner, the gate teleport list, Where Am I and the SayIntentions gate check all call a stand by the same name.
- The stand type after the dash — for example Gate Small, Gate Medium, Gate Heavy, Ramp GA or Ramp Cargo.
- The terminal, only when two stands at the same airport would otherwise sound identical. At a big airport such as New York JFK, "Gate 2" exists at more than one terminal, and the terminal name is what tells them apart. It comes right after the type so you hear it early.
- (Jetway) if the stand has a jet bridge.
- The parking guidance system in square brackets, when the scenery or GSX says which one is installed: SafeDock, APIS, AGNIS, Marshaller and so on.
- Online names, at the end, when the real-world name differs from your scenery's. For example "B 6 - Gate Medium, also B04 (online)" means your scenery calls it B 6 but real-world charts and ATC call it B04. These come from OpenStreetMap and the X-Plane Scenery Gateway; your scenery's own name always stays first.
- (no taxi route) at the very end means the stand exists but BA cannot find a taxiway that reaches it. It stays in the list so you know it is there, but you cannot be guided to it.
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:
- GSX status — a read-only line showing whether BA is connected to GSX.
- Menu options — the current GSX menu, one option per line.
- Active services — a list that appears only when two or more GSX services are running at once (see below).
- Tooltip — GSX's latest message.
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.
Menus that update by themselves
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:
- "GSX's Remote API is not reachable. This needs GSX 4.0.8 or newer." — GSX is not running, or it is older than 4.0.8.
- "Lost the connection to GSX's Remote API. Reconnecting." — GSX restarted; BA reconnects on its own. GSX restarts itself routinely, so give it a moment.
- "Not connected to the simulator, so GSX is not being monitored." — BA is not connected to MSFS.
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
- Open the Access GSX window with Input Alt+G.
- Press F5 to open the GSX menu.
- Press C. The GSX Settings window opens.
- 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.
- 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.
- 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
- Services starting and finishing, for every GSX service. The start names the handling company when GSX has one, for example "Refuel in progress by United Ground Express." or "Deboard in progress by OneJet.". When a service ends you hear it named followed by "complete". When a finished service becomes requestable again, nothing is said — the invoice tells you it is done.
- Passengers and bags, at milestones rather than for every passenger: "pax 0 of 155.", "pax 1 of 155.", then every ten passengers, and "bags 40 percent." every ten percent. A changed passenger total is always announced.
- Fuel, at most once every 30 seconds while fuel is flowing: "fuel 2221 kg loaded, aircraft 5252 kg."
- The bus, once per phase — approaching, on the way, in position, leaving. The countdown in GSX's text ("ETA 15 secs") is not read every second.
- The ground crew and vehicles. GSX narrates what each vehicle is doing — the front loader raising its belt, the rear stairs in position, the trains on their way, the operator walking to the fuel pump, the boarding platform going down, and every "waiting for your action" prompt. This works for pushback, refuelling, boarding and deboarding. Only what has actually changed is spoken, so moving one vehicle does not read the whole ramp out again.
- GSX's own banners when no service is running — the follow-me car, the marshaller and the positioning messages — whenever their wording changes.
- Ground connection timers. GSX bills for metered connections such as the jet bridge, ground power and stairs. When one starts you hear its name followed by "timer running", for example "Jetway operations timer running." Every 15 minutes you get a reminder with the time so far and the amount, for example "... still running, 30 minutes, amount 75.50.", and when it stops, "... timer stopped, 1 hour 6 minutes, amount 116.97." Anything under a minute is read as "under a minute".
- Invoices, once each: "Invoice available from" the handling company, followed by the total, for example "Invoice available from OneJet. Total 1761.42." If GSX has not published an amount yet, the invoice is announced without one rather than with a made-up figure.
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
- "GSX prepared Gate A 12." — success. GSX is set up at the stand you picked.
- "Careful: you selected" one stand "but GSX prepared" another — at large airports several stands can share a name, and GSX resolved to a different one. Check which stand you really mean, and if necessary pick it from the GSX menu yourself.
- "GSX is already set up at" the stand — nothing needed doing. If it is a different stand from the one you picked, the sentence starts with "Careful:" instead.
- "GSX warns" the stand "may be too small for this aircraft." — GSX prepared it, but its profile thinks your aircraft is too big.
- "GSX released the previous stand's services." — GSX had services set up at another stand; it let them go and prepared yours.
- "GSX could not find" the stand ", so no stand was prepared." or "GSX could not prepare this stand." — nothing was prepared. Choose the stand from the GSX menu in the Access GSX window instead.
- "The requested stand is occupied by another aircraft. GSX did not select it." — BA never forces GSX onto an occupied stand, because that would put you nose-to-nose with an aircraft you cannot see. Pick another stand.
- "GSX found more than one matching stand", followed by up to a few names — choose a more specific stand.
- "Automatic gate selection needs GSX 4.0.8 or newer. This GSX build does not offer it, so select the stand in the GSX menu yourself." — said once per taxi planner window, not on every route.
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:
- A steering tone — the same stereo tone taxi guidance uses — keeping you on the stand's centre line.
- A proximity beep, like a car's parking sensor, that speeds up as the stop gets closer and becomes a solid tone when you are on the stop.
- A few short spoken calls: the distance at fixed milestones, your speed in knots, and a clear closing phrase.
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
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.
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.
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.
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.
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.
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:
- You rolled past the stop (by more than about a metre): "Stop. You have passed the stop position."
- You are too far to one side of the stand line to make the stop: "Stop. Too far left of the gate centerline. Back up and try again." (or right).
- You reached the stop, but crooked — more than 7 degrees off the gate's heading: for example "Stop. Nose 18 degrees right of the gate heading. Back up and try again."
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:
- Stop and set the parking brake.
- 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.
- 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:
- "Docking. 15 metres to stop. Slight left, 5 degrees. Square with the gate."
- "Docking. 5 metres to stop. Centered. Nose 9 degrees left of the gate heading."
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.
- Docking guidance (auto-engage at the gate) — on by default. Untick to turn docking off entirely; taxi guidance then simply ends at the parking spot as it did before.
- Docking beep sound — the wave type of the proximity beep. The default is sine.
- Docking beep volume — a slider from 0 to 100 percent, with a Test button beside it to hear the beep at the chosen sound and volume.
- Announce ground speed every knot while docking — on by default. Untick if you find the speed calls too chatty.
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
- Docking never engaged. It needs you within its engage distance, roughly lined up with the stand, and below 15 knots. If you were still far off the stand line when you got close, docking waits and taxi guidance keeps steering you through the turn. Keep following the taxi tone and roll forward slowly. If you stop at the parking spot and hear taxi guidance's own arrival calls, docking was not able to engage at this stand.
- GSX says the aircraft is not parked, or offers to reposition it. Your park was outside what GSX accepts. If BA said "Back up and try again", follow the retry steps above.
- The stop seems to be in the wrong place at a stand without GSX. Without GSX, the target is the scenery's parking spot centre, not a jet bridge stop position. This is a limit of the scenery data.
- Something felt wrong and you want to report it. BA writes every docking attempt to a log file called docking.log. Include it in your report; see Logs and Getting Help.
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:
- Taxi to the runway with Taxi Guidance. When you line up, Takeoff Assist switches itself on.
- Roll down the runway following the Takeoff Assist tone, listening to the speed and V-speed calls.
- At liftoff BA hands you over to Hand Fly mode, which gives you a tone for pitch and bank.
- Engage the autopilot when you are ready, using the autopilot windows to set speed, heading, altitude and vertical speed.
- 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:
- If you teleported to a runway with Input Shift+R (see Teleporting to a Runway or Gate), it uses that runway.
- If taxi guidance just lined you up, it uses the runway taxi guidance took you to.
- 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.
- 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:
- "Takeoff assist active, runway 27L at EGLL" means BA found the real runway. The tone follows its painted centreline.
- "Takeoff assist active, no runway selected, extending centerline from current position, heading 272" means BA could not identify a runway. It will keep you on a straight line from where you are, so make sure you are lined up and centred before you press Ctrl+T.
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
- 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.
- Listen for the heading warning. If there is none, you are aligned.
- Advance the thrust levers and start the roll.
- Steer with the rudder toward the tone (see below). When the tone is silent, or centred, you are tracking the centreline.
- Listen for "80 knots", "100 knots" and the V-speed calls.
- Rotate. Takeoff Assist calls your pitch every time it changes by a degree: "+3", "+7", "+12".
- 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
- Centreline position, as the distance from the centreline changes by about 10 feet, at most twice a second. The number is in steps of 10 feet and the word is the side you are on: "2 left" means you are about 20 feet left of the centreline, so steer right. "center" means you are within 25 feet of it. You can mute these and keep just the tone.
- Pitch, whenever it changes by one degree, at most twice a second: "level", "+5", "+14", or "-1" for nose down.
- Speeds: "80 knots" and "100 knots". On the BlueBird 757-200, which plays its own "80 knots", only "100 knots" (see BlueBird 757-200). The V-speed calls come from the aircraft itself or from BA's own V-speed callouts, whether or not Takeoff Assist is on (see Takeoff Speed Callouts).
- Ground speed, if you have turned it on (see Settings below), for example "60 knots.".
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:
- "Airborne, hand fly." Takeoff Assist is off and Hand Fly mode is now on.
- "Airborne." You had already switched Hand Fly on yourself before takeoff, so only Takeoff Assist was turned off.
- "Airborne, hand fly, quick keys failed." Hand Fly is on, but its single-letter readout keys could not be set up (see If something goes wrong under Hand Fly).
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):
- Takeoff Assist Tone: the sound of the tone. Choose from Sine (Smoothest), Triangle (Smooth), Sawtooth (Bright) or Sine (Rich).
- Takeoff Assist Volume: 0 to 100 percent. The default is 5 percent.
- Mute centerline deviation announcements: keeps the tone and pitch calls but drops the "2 left" and "center" speech. Off by default.
- Steer toward the tone to stay on the centerline: on by default. Untick it to reverse the panning, so you steer away from the tone instead.
- Hard-pan centerline tone (full left or full right; speaker-friendly): the tone jumps fully to one side instead of moving gradually. Useful on speakers, where a slightly off-centre tone is hard to tell from a centred one. Off by default.
- Play steering tone: when the tone sounds. Always plays it all the time (centred when on track). At 1 degree error (the default) up to At 5 degrees error keep it silent until the correction needed reaches that size.
- Legacy takeoff assist mode (heading-based, no tone): see above. Off by default.
- Enable takeoff assistant call outs: the 80 knots and 100 knots calls. On by default.
- Auto-activate Takeoff Assist on lineup: on by default. Takeoff Assist switches on when taxi guidance lines you up on your departure runway. This happens once per taxi route: if you switch Takeoff Assist off after it came on, it stays off until your next taxi route.
- Auto-activate Hand Fly on takeoff (deactivates Takeoff Assist): on by default. This is the liftoff handover described above.
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
- You heard "no runway selected" when you were on a real runway. BA could not match your position to a runway in its navigation database. Check that the database matches your simulator (see The Navigation Database). The tone still works, along a straight line from where you pressed Ctrl+T, so only press it once you are centred and aligned.
- Takeoff Assist did not come on at lineup. It only switches itself on when taxi guidance was guiding you to that runway and you came to a steady lineup on it, and only once per route. Press Output Ctrl+T.
- The tone keeps swinging from side to side. You are over-correcting. Use smaller rudder inputs and give the aircraft a moment to respond.
- You hear nothing at all. With the default setting the tone is silent while you are on track, which is the goal. To confirm it is working, set Play steering tone to Always for a while. Also check that Legacy takeoff assist mode is not ticked, and the Takeoff Assist Volume.
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:
- They arm only on the ground, below 40 knots, with V1 and VR entered. So a landing can never fire them, and after a rejected takeoff they re-arm for the next attempt.
- Each is called once per takeoff roll.
- If two come due at the same moment, for example where V1 and VR are the same speed, you hear them together as one phrase: "V1, Rotate".
- On the MD-11, "N1 70 percent" is called once when the first engine reaches 70 percent N1, where the autothrottle takes over.
- Each call can be muted in the Monitor Manager (Output Ctrl+M) with its speed's row (V1, VR, V2). See The Monitor Manager.
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
- Press the key, for example Input Ctrl+A. The window opens with the cursor in the value box.
- 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.
- BA confirms the value it set. On the FlyByWire Airbuses, for example, the speed window says "FCU speed 250, selected".
- Tab on to the other buttons if you need them, such as Altitude Pull (selected).
- 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:
- Push hands that value to the flight management computer. This is called managed: the aircraft flies the speed, route or altitude profile from your flight plan.
- Pull makes the aircraft fly the number in the window. This is called selected.
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
- Changes that happen without you — a mode change, a capture, the autopilot dropping out — are announced automatically through the flight mode announcements on the aircraft that have them.
- On every aircraft except the MD-11, turning a real knob, on your hardware or in the virtual cockpit, speaks the new value too, so you do not need to read the window after each turn. On the FlyByWire Airbuses, values the aircraft shows as dashes are not spoken.
All of these can be muted individually in the Monitor Manager (Output Ctrl+M).
If something goes wrong
- The value is set but the aircraft does not follow it. On an Airbus the window is probably still managed; press Pull (selected). On a Boeing check that the right mode is engaged, for example HDG SEL for a heading.
- The vertical speed you set does nothing. On most aircraft the vertical speed only takes effect once V/S mode is engaged; use the pull or engage button in the vertical speed window.
- Aircraft-specific behaviour is described in Airbus Aircraft and Boeing Aircraft and the MD-11.
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:
- Its pitch shows your aircraft's pitch. Wings-level, nose-level flight is the middle note. Nose up raises the note; nose down lowers it. The note keeps rising all the way to 20 degrees nose up, so it stays useful through the whole initial climb, and keeps falling down to 10 degrees nose down. The nose-down side changes faster per degree than the nose-up side, because you rarely need large nose-down attitudes.
- Its position between your ears shows your bank. Right wing down moves the tone to your right ear; left wing down moves it to your left. It reaches fully one side at 10 degrees of bank. Centred means wings level.
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:
- Pitch, whenever it changes by a degree, at most twice a second: "level", "+8", "-2". This is exactly the same style as Takeoff Assist, so nothing changes in your ears at liftoff.
- Bank, whenever it changes by a degree, at most twice a second: "left 15", "right 5", "wings level".
- Heading (on by default), once a second when it has changed: just the number, "275".
- Vertical speed (off by default), once a second when it has changed: "+1850", "-700".
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
- Take off with Takeoff Assist. At liftoff you hear "Airborne, hand fly." and the tone starts. Or press Output Ctrl+H.
- Hold your takeoff pitch by keeping the note steady at the right height. Listen to the pitch calls to confirm the number.
- 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.
- Press the quick keys for anything else: S for speed, A for altitude, V for climb rate.
- When the autopilot is engaged, press Output Ctrl+H to turn Hand Fly off.
Settings
On the Hand Fly tab of the Settings window:
- Hand flying feedback type: Audio Tones Only, Screen Reader Announcements Only, or Both Tones and Announcements (the default).
- Hand fly tone type: Sine (Smoothest), Triangle (Smooth), Sawtooth (Bright) or Sine (Rich).
- Volume: 0 to 100 percent, default 5 percent. The Test Tone button plays a sample with your settings so you can hear the note move; press it again to stop. The sample sweeps only part of the nose-up range, so it does not play the very highest note.
- Monitor Heading (announce heading changes at 1-second intervals): on by default.
- Monitor Vertical Speed (announce VS changes at 1-second intervals): off by default.
- Auto-activate Hand Fly on takeoff (deactivates Takeoff Assist): on by default.
The same tab holds the Visual Guidance and Takeoff Assist tone settings; those are covered in their own sections.
If something goes wrong
- "Hand fly mode active, quick keys failed." (or "Airborne, hand fly, quick keys failed." at liftoff). Another program on your computer already uses one of the single-letter keys as its own global hotkey, so BA could not take it. Hand Fly still works, and you can still read everything with output mode (for example Output S for speed). Close the other program, or turn Hand Fly off and on again, which retries the keys.
- No tone, only speech. Check that the feedback type is not Screen Reader Announcements Only, and check the volume. If Visual Guidance is on, the Hand Fly tone is deliberately silent.
- Too much speech. Choose Audio Tones Only, or untick Monitor Heading.
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:
- "Speed brake down" — the lever is down, or short of the Armed detent.
- "Speed brake armed" — only at the Armed detent itself.
- "Speed brake flight", "Speed brake 50 percent", "Speed brake fully deployed" — at those detents.
- "Speed brake 35 percent" — wherever the lever rests between detents, for example with a hardware lever.
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:
- PMDG 737, iFly 737 MAX 8 and BlueBird 757-200: "Trim 5.3".
- PMDG 777: "Trim 5.25 units".
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:
- Airborne Traffic, for example "Airborne Traffic — 4 aircraft".
- On Ground Traffic, for the aircraft on the ground. When a parked aircraft is at a known gate or stand, its line includes "at" and the gate or stand name, which is handy for finding a friend at the airport.
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
- In the TCAS Traffic window, arrow to the aircraft.
- Press the Applications key (or Shift+F10) to open the context menu.
- Choose Add to track list. You hear, for example, "UAL 123 added to track list."
- 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:
- For an advisory that asks you to change your climb or descent: "TCAS: Climb. Fly vertical speed plus 1500 to plus 2000 feet per minute."
- For an advisory that asks you not to change something: "TCAS: Do not descend." or "TCAS: Do not climb more than 1000 feet per minute.", sometimes with "Maintain plus 500 feet per minute".
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
- The lists are empty. There may be no traffic near you. Check that AI or multiplayer traffic is turned on in the simulator, or that you are connected to your network.
- Callsigns are missing. Some AI traffic has no callsign; those aircraft are listed by type, or as "unknown" with a number.
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
- Press Input Shift+D. The Select Destination Runway window opens with the cursor in the Airport ICAO Code box.
- 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".
- Press Enter. The cursor moves to the Available Runways list and the first runway is selected.
- 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).
- 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.
- 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
- "Airport database not found. Configure database from File menu first." You have not built the navigation database yet. See The Navigation Database.
- BA warns that the database does not match your simulator. You built the database for MSFS 2020 but are flying MSFS 2024, or the other way round. Select the right database first.
- "No runways found for ..." The airport exists in the database but has no runway records. Try updating your navigation data.
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:
- The glideslope part is only given within 25 nautical miles of the runway.
- "Warning: ILS signal range is 18 nautical miles." at the start of the report means you are farther out than the ILS is published to reach. The numbers are still calculated, but your aircraft's own ILS receiver may not have a signal yet.
- "Approaching from opposite direction. Fly heading 093 to extend outbound." You are on the wrong side of the airport. Fly that heading to get out onto the approach side, then turn back.
- "No ILS available for runway 27L at EGLL." The database has no ILS for that runway. Use Visual Guidance or Output Ctrl+D instead.
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:
- The guidance tone (BA calls it the desired tone) is where the aircraft should be. Its pitch, high or low, is the pitch attitude the aircraft should have. Its position from left to right is the bank angle the aircraft should have.
- The current tone (the current-attitude tone) is where the aircraft is. Its pitch is your actual pitch attitude and its position left to right is your actual bank angle.
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
- Hand-flying a visual approach, or any approach where you want to fly the final yourself.
- Practising approaches.
- Backing up an autopilot approach, to hear whether the aircraft is doing what you expect.
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
- Set a destination runway (Input Shift+D).
- Fly toward the runway. Visual Guidance can start from a long way out; it will lead you onto the extended centreline.
- Press Output Ctrl+V. BA says "Visual guidance active, runway 27L" and both tones start.
- Match the tones as described above. Listen for the phase callouts (below), which tell you which part of the approach you are in.
- 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:
- "Intercepting final, 1.8 miles to final": you are more than about a third of a mile to one side of the extended centreline. The guidance is turning you to join it. The distance is how far you are from the centreline, not from the runway.
- "Established on centerline": you are on the extended centreline but not yet on the glide path.
- "On vertical profile": you are on the centreline and within about 100 feet of the glide path. This is where you want to be.
- "Extending, turn to heading 093": you are more than 500 feet up and on the wrong side of the runway for this approach. Fly the heading given to fly out onto the approach side. While you extend, BA gives progress every ten seconds, such as "2.5 miles behind threshold", and "Approaching threshold" when you are close to it.
- "Flare": your wheels are about 30 feet above the runway (40 feet on the Headwind A330 and the PMDG 777, 35 feet on the MD-11). The guidance tone now asks for the flare pitch. Raise the nose smoothly to match.
- "Touchdown": the wheels are a few feet from the runway.
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):
- Visual Guidance Tone: the sound of the guidance (desired) tone. Default: triangle.
- Visual Guidance Volume: its volume.
- Current-attitude tone: the sound of the current tone. Default: sine. Choose a different sound from the guidance tone, or the two become hard to tell apart when matched.
- Current-attitude Volume: its volume. Turning it down makes the guidance tone stand out more. Do not turn it off; you need both.
- Hard-pan visual-guidance tones (speaker-friendly): when ticked, both tones jump fully left or fully right once the bank is more than about one degree, instead of moving smoothly. Use it on speakers, where "a little to the left" is hard to hear. On headphones you will usually leave it off.
If something goes wrong
- The tones are always fully to one side during the turn onto final. Normal. The guidance is asking for more bank than the tone can show. Follow the spoken bank callouts until you are close to the centreline.
- The pitch tone feels jumpy. Make small, smooth pitch changes and give the aircraft a second to respond. Chasing the tone with large inputs makes it worse.
- You hear three tones. Visual Guidance mutes Hand Fly's tone automatically; if you hear a third tone, it is probably another BA tone such as taxi or takeoff assist that is still running. Switch it off.
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, which you switch on with the Manual landing assist (adds flare tones) checkbox when you choose your destination runway. They guide you from 50 feet down to touchdown.
- The rollout centerline tone, which is on by default for every landing with a destination runway or a planned landing exit, including autolands. It guides you from touchdown down the runway.
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.
- A high tone means you are sinking too fast. Pull back: raise the nose to slow the descent.
- A low tone means you are floating: not coming down fast enough. Relax the back pressure and let the aircraft settle.
- Silence means you are on the profile. A well-flown flare is a quiet one.
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:
- With a landing exit planned, the tone stays with you until exit guidance takes over to steer you off the runway, or until you stop. BA's exit guidance and the centreline tone take turns; they never play together. Near your exit, the exit guidance's own tone steers you into the turn.
- Without a landing exit, the tone ends when you slow below about 40 knots or when you are clear of the runway.
What you will hear
- "Flare guidance": the flare tones have started, at 50 feet.
- "Rollout guidance": the rollout centreline tone has started after touchdown. With a landing exit planned, the touchdown sentence about your exit (see the Landing Exit Planner below) normally takes its place.
- "Rollout guidance complete": the rollout tone has finished.
- "Flare guidance, runway 27R, not 27L." or "Rollout guidance, runway 27R, not 27L.": you are landing on a different runway from the one you chose (a parallel, or the other end). The tones switch to the runway you are really on.
- "Go around detected. Flare assist rearmed.": you climbed back above 100 feet during the flare. The tones stop and are ready again for your next approach. BA always speaks here, because in this feature silence means "on profile" and must never be mistaken for the assist giving up.
- "Flare sink rate cue unavailable": the vertical tone could not play, usually because your audio device disappeared. Fly the flare without it.
- "Manual landing assist off" or "Rollout centerline tone off": the tones have been disarmed, for example because you switched navigation database. Set your destination again.
- "Manual landing assist armed for EGLL runway 27L": the flare tones were brought back by another change, such as a landing exit plan for the same airport.
How they behave
- Engaging. The flare tones start only if you are armed, have come down from above 80 feet, are now at or below 50 feet, are descending, and are within 3 miles of the runway.
- Bounces. If you bounce back into the air (above about 5 feet), the vertical tone comes back to talk you through the second touchdown. The lateral tone never stops.
- Circuits and touch-and-goes. The assist stays armed after a landing, so every approach to the same runway gets the tones without opening the window again.
- With Visual Guidance on. While Visual Guidance is running, the flare tones stay silent, because Visual Guidance has its own flare cue. The rollout tone still starts after touchdown, once Visual Guidance has switched itself off.
- Hand Fly. Hand Fly's tone is muted while the flare or rollout tones are playing.
- Taxi guidance. When taxi guidance takes over after landing, the rollout tone stops at once, without talking over the taxi instructions.
- Light aircraft. The rollout-only tone (without the flare checkbox) starts only if you touch down at 50 knots or more, so a very slow touchdown gets no rollout tone.
Settings
- Manual landing assist (adds flare tones): the checkbox in the Select Destination Runway window. Unticked by default, and chosen fresh each time you set a destination.
- Rollout centerline tone when a destination runway or landing exit is set: on the Hand Fly tab of Settings. Ticked by default.
- The rollout tone, and the lateral flare tone, use the Takeoff Assist tone settings on the same tab: Takeoff Assist Tone:, Takeoff Assist Volume:, Steer toward the tone to stay on the centerline, and Hard-pan centerline tone (full left or full right; speaker-friendly). The vertical flare tone uses a contrasting sound automatically.
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
- Press Input Shift+X. The Landing Exit Planner window opens.
- 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…".
- 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."
- 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."
- 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.
- 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."
- 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°)"
- The name: the taxiway you will turn onto. "(unnamed)" means the database has no name for it.
- The distance from the landing threshold, in metres or feet depending on your setting.
- The type:
- High-speed: a rapid exit taxiway that leaves the runway at a shallow angle (50 degrees or less). You can turn off at speed.
- Normal: an ordinary exit at roughly a right angle. You must be at taxi speed to take it.
- End: an exit at or near the far end of the runway that turns back sharply (more than 110 degrees). You will need to slow right down, and it often means a sharp turn back.
- The side: left or right, as you face the landing direction.
- The angle between the exit and the runway, in degrees.
- "(sharp turn back)" at the end means the exit's path turns back hard soon after it leaves the runway, so you must be at walking pace by the turn. BA pre-selects an exit without this mark when there is one.
- "(backtrack required)" at the end means the exit is a turn pad at the runway end: you roll to the end, turn around and backtrack along the runway to a taxiway. BA guides that backtrack for you.
- "— WARNING: no taxiway mapped clear of the runway" at the end means your database has nothing past the junction. BA could guide you to the turn but not off the runway. Choose another exit if you can.
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.
- 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".
- 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.
- 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.
- "Approaching high-speed exit taxiway B5, 500 metres." You keep braking normally.
- "Taxiway B5, 300 metres." This extra callout is only given for high-speed exits.
- "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.
- "Turn right now, taxiway B5." The steering tone swings right. You turn with the tone and let it guide you along the exit.
- 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
- Guidance starts by itself when BA sees a real landing: the aircraft was in the air and is now on the ground at 40 knots or more. Taxiing onto the ground or teleporting does not count.
- If you land on a different runway from the one you planned (the parallel, or the other end), BA tells you at touchdown and guides you to a suitable exit on the runway you are actually on, for example: "Touchdown on runway 27R, not 27L. Exit taxiway A6 in 900 metres."
- If BA cannot work out which runway you landed on, it says "Touchdown. Runway not identified. No exit guidance this landing." Your plan is kept for the next landing.
- If you go around or do a touch-and-go after guidance has started, and are still in the air five seconds later, BA says "Exit guidance off, plan kept." and your plan is ready again for the next touchdown.
- Switching simulator or rebuilding the navigation database clears a pending plan and says so, because the old runway positions may no longer match.
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
- "Touchdown. exit taxiway B7 in 1200 metres." (or "high-speed exit", or "runway-end exit"): guidance has started; this is your exit and how far away it is. Keep the centreline.
- "Touchdown on runway 27R, not 27L. ...": you are not on the runway you planned for. BA has picked an exit on this runway. If that touchdown sentence also carries "Slow down." or "Turn left now.", it has folded in callouts that came due while it was speaking; act on them.
- "Touchdown on runway 27R, not 27L. No usable exit.": there is no usable exit on the runway you landed on. BA goes straight to the runway-end countdown.
- "Touchdown. Runway not identified. No exit guidance this landing.": BA could not work out which runway you are on, for example after a bounce, a touch-and-go or a landing beside the runway. You get no exit guidance on this landing, but your plan is kept for the next one. Taxi off the runway yourself, then use Where Am I (Output Alt+Y) and the taxi planner.
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
- "Approaching exit taxiway B7, 500 metres." (1,500 feet): your first warning.
- "Taxiway B5, 300 metres." (900 feet): high-speed exits only, a second warning, about where a sighted pilot would see the first exit lights.
- "Taxiway B7, 150 metres." (500 feet): get ready to turn. If it ends with "Slow down.", you are too fast to make this exit: above about 60 knots for a shallow exit, or above about 30 knots for a right-angle exit or an end exit. Brake.
- "Left turn ahead, taxiway B7." or "Right turn ahead, taxiway B7.": on an ordinary right-angle exit, an early warning that the turn is coming. It comes sooner the faster you are, so you have time to slow down; it does not mean turn yet.
- "Turn left now, taxiway B7." or "Turn right now, taxiway B7.": turn now. The steering tone swings to the exit; follow it. For a very shallow exit (under 20 degrees) you hear "Gentle left now" or "Gentle right now" instead: make a small steering input, not a full turn.
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:
- "LAHSO hold point, runway 27, in 600 metres."
- "LAHSO hold point in 300 metres. Slow down."
- "LAHSO hold point in 150 metres. Stop before runway 27."
- "Warning: past the LAHSO hold point for runway 27.": you have rolled past it. Stop and tell ATC.
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:
- "Exit H is behind you. Keeping taxiway G."
- "Taxiway H is past the LAHSO hold point for runway 27. Keeping taxiway G."
- "That exit list is for runway 09. Rolling out on runway 27. Keeping taxiway G.": the planner was showing the other end of your runway, whose exits are measured from the other threshold. Choose the runway you are on and pick again.
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
- "Too fast for taxiway B7. Continue to taxiway B9, 500 metres.": at the turn point you were too fast to take B7. Do not turn. BA has switched to the next exit you can reach and restarted the countdown. The sentence may end with "Slow down.".
- "Taxiway B7, too fast to turn. Slow down.": you are too fast for the exit and there is no other exit ahead. Brake. Do not try the turn at that speed.
- "Missed taxiway B7. Retargeting taxiway B9, 500 metres ahead.": you rolled past the exit. BA is now guiding you to the next one ahead. It never sends you to an exit behind you, and never back across the runway you just landed on. If you had started to turn, the sentence includes "Straighten.": straighten up along the runway first.
- "Taking earlier exit, taxiway B5, 300 metres ahead.": you slowed down sooner than expected and there is a reachable exit before the one you planned. BA has switched to it. If you prefer the planned exit, you will need to stop guidance and taxi there yourself.
- "Missed taxiway B7. No reachable exit remaining." or "Too fast for taxiway B7. No reachable exit remaining.": there is no exit ahead that BA can route you to. The runway-end countdown starts.
- "Missed last exit on runway 27L.": you passed the last exit. The runway-end countdown starts.
- "Continue rolling to taxiway B7, 400 metres ahead.": you slowed or stopped well short of your exit. Keep rolling to it at taxi speed.
- "Left the runway short of taxiway B7. Now following taxiway B5.": you turned off at an earlier taxiway than planned. That is fine: guidance follows you onto the taxiway you actually took.
- "Off pavement.": your wheels have left the runway and taxiway surface. Steer back onto the pavement and slow down.
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:
- "Off the runway at Taxiway B7. Stop and hold position. Open the taxi planner to set a route to your gate.": a normal, successful exit. Stop, contact ground, and plan your taxi with Input Shift+Y.
- "Taxiway data ends at Taxiway B7. You may still be on the runway — continue ahead until clear, then open the taxi planner to set a route to your gate.": your database maps nothing beyond this junction, so BA cannot be sure you are clear. Do not stop here: keep going straight ahead slowly until you are sure you are off the runway.
- "You have passed the Taxiway B7 vacate point. Exit guidance ended. Stop and hold position, then open the taxi planner to set a route to your gate.": you are off the runway but went a different way from the exit route. Stop and plan a route from where you are.
- "You have left the runway short of Taxiway B7. Exit guidance ended. Stop and hold position, then open the taxi planner to set a route to your gate.": you left the runway before your exit and BA could not match where you went.
- "Exit guidance ended: no usable route from here. Stop and hold position, then open the taxi planner to set a route to your gate.": you are off the runway but BA cannot route from here.
- "Exit reached. Route unavailable. Taxi to taxiway B7 and use the taxi planner.": BA could not build the route off the exit. Turn off at the exit yourself and plan with the taxi planner.
The runway-end countdown
When there is no exit left ahead, BA counts you down to the end of the runway instead:
- "Runway end in 500 metres." (1,500 feet)
- "Runway end in 150 metres. Slow down." (500 feet; "Slow down" only if you are faster than about 30 knots)
- "Runway end in 30 metres. Stop." (100 feet): stop now.
- "Stopped on runway 27L. Runway end in 900 metres.": said once if you stop part-way down the runway, for example when ATC holds you. After that BA stays quiet until you move.
The countdown ends according to what you do next:
- If you turn off onto a taxiway: "Runway vacated. No route set — use the taxi planner for a route to your stand."
- If you reach the end and turn around: "End of runway 27L. Turn around, heading 093. Backtracking." The tone steers you back along the runway on that magnetic heading.
- If you turn around part-way down the runway: "Backtracking on runway 27L, heading 093."
While backtracking:
- "Taxiway H ahead on the left. Vacate runway.": the taxiway BA found for you to leave the runway is coming up, about 200 metres ahead, on the side named. The tone now swings toward it; follow it off the runway. Without a name or a clear side you hear just "Taxiway ahead. Vacate runway."
- "Runway vacated. No route set — use the taxi planner for a route to your stand.": you are off, clear of every runway. The tone stops, and if you ask for taxi status you will hear that no route is loaded. That is expected.
- "Backtracking on the runway. No taxiway connection found — use the taxi planner to set a route.": BA cannot find a taxiway to leave by. Ask ATC and plan with the taxi planner.
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
- Ground traffic callouts wait while you are rolling down the runway; see When Ground Traffic Speaks.
- To stop exit guidance at any time, press Input Ctrl+Y (Stop Taxi Guidance).
Landing Rate and G-Force
After every landing, two Output keys tell you how firm it was. They work on every aircraft.
- Output Ctrl+Shift+R: the touchdown vertical speed, for example "Landing rate 142 feet per minute."
- Output Ctrl+Shift+G: the peak vertical g-force during the touchdown, for example "Landing g-force 1.24 g."
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:
- hear the last thing the controller said again, whenever you like;
- look up your assigned arrival gate, the runways in use and the altimeter setting;
- turn a spoken taxi clearance into a ready-made route in the taxi planner, without typing the taxiways in by hand.
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:
- Cabin and crew chatter. SayIntentions mixes cabin announcements and crew intercom into the same stream as ATC. BA filters these out, so pressing Ctrl+S during taxi gives you the ground controller, not the purser. A real ATC instruction that happens to contain a cabin-sounding word, such as "Hold position, passenger aircraft crossing left to right", is still recognised as ATC.
- Your own transmissions. Your readback is usually the newest thing on the frequency the moment you press the key, so BA never reads your own words back to you.
What you might hear instead of a transmission:
- "No ATC transmission yet. Only your own calls so far." — you have spoken on the frequency, but the controller has not replied yet. There is no need to keep pressing.
- "SayIntentions flight.json not found. Start an active SayIntentions flight." — SayIntentions is not connected to a flight.
- "No SayIntentions transmission found. Check SayIntentions is connected to this flight." — the flight is there but nothing has been said yet.
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:
- 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.
- Press Tab to move from one section to the next.
- Use the Up and Down arrows to move within a section. Typing a letter jumps to the next item starting with that letter.
- Press Escape to close the window and go back to the simulator.
The sections, each shown only when there is something in it:
- Flight — the current airport, origin, destination, aircraft type, callsign and filed route. While you are in the cruise, SayIntentions often reports the en-route control centre instead of an airport. BA labels that line Controlling facility rather than calling it an airport.
- Gate and runway — your assigned arrival gate, the departure runway, and the runway you are cleared to land on (or the arrival runway).
- Airport sections — one for each airport, headed with the airport's code, for example "EDDF airport". Each lists the landing runways, departing runways, preferred runway, runway flow and the altimeter.
Some details worth knowing:
- The gate is always your arrival gate. SayIntentions does not assign departure gates, so the gate line always means the stand you will park at, at your destination. Until SayIntentions assigns one, you see "Assigned arrival gate: none assigned yet".
- At your destination, BA checks where you are parked. If you are within about 100 metres of a stand, an extra line tells you whether it is your assigned gate, for example "Aircraft appears near assigned gate A24." or "Aircraft appears near B 12, not assigned gate A24." This catches a wrong arrival position.
- The departure runway disappears once you are airborne, and again at your destination, because by then it is old ground information.
- The airport you need comes first. On the ground at your departure airport, its section leads. Everywhere else, including in the air, your destination leads.
- The altimeter is given in both units, for example "Altimeter: 30.12 inches (1020 hPa)", so you never have to convert in your head.
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
- Request taxi from SayIntentions and listen to the clearance as normal. Read it back if the controller expects you to.
- Press Input Ctrl+Shift+Y. You hear "Reading SayIntentions taxi clearance."
- 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.
- Listen to the spoken summary. It ends with "Review the fields, then press Calculate Route to start guidance."
- Check the planner's fields against what you heard: the destination, the taxiway list, and the hold-shorts.
- 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
- The destination — the runway or gate the controller cleared you to. A runway you are told to hold short of, or to cross, is never taken as your destination.
- The taxiways — the cleared taxiways, in the order given. A taxiway used twice in one clearance, for example either side of a runway crossing, gets a row each time.
- The hold-shorts — each hold-short is tied to the taxiway it comes after in the clearance, so the stop is placed at the right crossing.
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.
- When the track agrees with the clearance (every cleared taxiway is on it, in the order you were given them), BA takes the taxiway list from the track. This catches legs that are hard to pick out of speech. For example, a controller saying "North" for a taxiway called N. You hear "Route from SayIntentions ground track."
- When the two disagree, the clearance wins. You hear "SayIntentions ground track differs from the clearance. Using the clearance." What you heard on the frequency is what gets built.
- When there is no clearance at all (you pressed before asking for taxi, or the radio calls could not be read), BA uses the track because it is the only thing available, and warns you: "Route from SayIntentions ground track. No cleared taxiways to check it against, so this is SayIntentions' own plan, not ATC's." Treat that route as a suggestion, not a clearance.
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:
- "SayIntentions route to Gate A9." — the lead, naming the destination that was set.
- "SayIntentions route. Destination Gate A9 not set. Check the destination field." — BA could not set the destination. Pick it yourself in the planner.
- "SayIntentions assigned South Terminal Gate A24, which this scenery lists under another name." — the stand is here, but this scenery spells it differently. BA found it anyway.
- "SayIntentions assigned Gate B06, which this airport does not have. This is the nearest stand to the assigned position." — no stand here matches that name, so BA chose the stand nearest the position SayIntentions published. Check it is the one you want.
- "Route from SayIntentions ground track." or "SayIntentions ground track differs from the clearance. Using the clearance." — where the taxiway list came from, as described above.
- "No cleared taxiways to check it against, so this is SayIntentions' own plan, not ATC's." — no clearance was found to check the track against.
- "No taxi clearance on the SayIntentions frequency yet." or "SayIntentions comms history timed out." — why no clearance was found. Usually you have not requested taxi yet.
- "Could not apply K." — a cleared taxiway that is not in the route, either because this airport does not have it or because the planner could not use it. The rest of the route is still built. On a route from the clearance, every missing taxiway is named, because each one is a word you heard. On a route from the ground track, only the first three are named and the rest are counted, for example "Could not apply F, G, R and 1 more."
- "12 of 40 ground track points were off the taxiways, so the route may be incomplete." — much of the published track did not match this airport's taxiways. Check the route carefully.
- "Could not set hold short of runway 22." — a hold-short BA could not place. Treat it as still in force: guidance will not stop you there, so you must stop yourself.
- "Via A, B, C." — the route that was built. A long route from the ground track is shortened in speech, for example "Via R7, E7, E6 and 9 more." The whole list is always in the planner's route summary box.
- "Hold short of runway 15R after N." — a hold-short that was set, one line for each.
- "Review the fields, then press Calculate Route to start guidance." — or "Guidance started." if you have turned on auto-start (see Settings below).
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."
- You read back the clearance.
- You press Input Ctrl+Shift+Y. You hear "Reading SayIntentions taxi clearance."
- 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."
- 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.
- 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:
- SayIntentions import starts taxi guidance immediately — off by default. When ticked, the import calculates the route and starts guidance straight away, and the summary ends with "Guidance started." Leave it off while you are learning, so you always get the chance to review the route first.
If something goes wrong
- "SayIntentions flight.json not found." SayIntentions only writes its flight file while you are connected to a flight. Start or reconnect your SayIntentions flight.
- The import says there is no taxi clearance. You may have pressed before asking for taxi, or the controller's last message was something else. BA looks back through recent calls for the newest taxi clearance, so a later "hold position" or traffic advisory does not hide it.
- A taxiway you heard is missing. Listen for the "Could not apply" line. Add the taxiway by hand in the planner if the airport has it under another name.
- The destination is wrong or missing. Set it yourself in the planner's destination field before pressing Calculate Route.
- Something still seems wrong. BA keeps a record of every import in the file sayintentions.log, in your logs folder (see Logs and Getting Help). It shows what BA read, which source it used and what it could not apply. Your SayIntentions key is never written to the log.
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:
- The METAR window (Output Shift+M) fetches its reports from VATSIM's weather service. See Weather.
- The wind readout uses a VATSIM METAR for the destination wind.
- When network traffic is shown in the simulator, the TCAS window and ground traffic callouts look up its aircraft type and route from VATSIM's live data, so you hear a real type instead of a placeholder. See TCAS Traffic and Ground Traffic.
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
- Install vPilot if you have not already.
- In BA, open Settings from the File menu and go to the VATSIM tab (the third tab, after Weather).
- Tick Announce VATSIM events from vPilot.
- 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.
- Press OK. BA installs its plug-in into vPilot and tells you what happened as part of the "Settings saved" confirmation.
- 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:
- "VATSIM announcements are turned off." — the main checkbox is unticked.
- "vPilot was not found. Install vPilot, then re-open these settings."
- "The plugin is not installed. Press OK to install it."
- "An older plugin is installed. Press OK to update it."
- "The plugin is installed and up to date."
- "vPilot is connected." — everything is working.
- "vPilot is not connected. Start vPilot, or restart vPilot if you have just installed the plugin."
- "Announcements are muted for this session. Press ] then Alt+V to unmute."
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.
- "VATSIM announcements muted" / "VATSIM announcements unmuted".
- "VATSIM announcements are turned off in Settings." — the main checkbox is off, so there is nothing to mute.
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:
- Its vPilot plug-in is removed automatically when BA installs its own, so you never hear the same event twice. You hear once: "Removed the old vPilot to TTS plugin. MSFS Blind Assist now handles VATSIM announcements."
- The old tray program itself is not removed. Uninstall it yourself once you have switched.
- Its settings are not copied across. BA's defaults already match what it did (every event on, not muted).
If something goes wrong
- You hear "vPilot plugin installed. Restart vPilot to load it." That is normal after the first install. Close and reopen vPilot.
- You hear "vPilot is running with an older plugin. Close vPilot and re-open Settings to update it." (or, at start-up, "...Close vPilot and restart MSFS Blind Assist to update it."). vPilot is holding the old plug-in open. Close vPilot, then do what the message says.
- You hear "The vPilot plugin could not be installed. See the log for details." Something stopped the copy, such as folder permissions. Send your logs when asking for help (see Logs and Getting Help); the plug-in keeps its own log, vpilot-plugin.log, in the same folder.
- Nothing is spoken. Open the VATSIM tab and read the status box. Check you have not muted announcements with Alt+V, and that the event you expected is ticked.
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
- To know who else is flying near you, on Volanta or on VATSIM, IVAO, PilotEdge or APOC.
- To find out where your friends are and what they are doing.
- To check which air traffic control is online at an airport before or during a network flight.
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:
- Distance — 10, 25, 50, 100 (the default), 200, 500 or 1,000 nautical miles, then a warning item, then All pilots across Volanta. That last choice lists about 3,000 aircraft, which is a lot to arrow through.
- Show — All aircraft, Airborne only or On the ground only.
- Sources — checkboxes for Volanta users, VATSIM, IVAO, PilotEdge, APOC and Other networks.
- Search — type a callsign, flight number, user name, aircraft type, registration or airport. A search covers every distance, whatever the Distance box says.
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:
- Go to the Connection tab and press Log in to Volanta.
- Volanta's own login page opens in a window of its own. Log in there.
- 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
- The tab you are on updates by itself every 5 seconds. If the line you are on changes, it is read again.
- While you are in a list, its order holds still, so the Down arrow always reaches the next aircraft. New aircraft join at the end.
- Press F5, or the Re-sort now button, to re-sort at once. BA reads the tab's status line, for example how many aircraft are shown.
- If Volanta's data stops arriving, a line at the top of the list says why. The last aircraft received stay below it.
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
- The lists stay empty. Check the status line at the top of the list and the Connection tab; they say whether the map is loading, unable to start, or not receiving anything. Check your internet connection.
- You hear "Volanta's login page cannot open: the web map is not running. The status above says why." Read the Connection tab's status for the reason.
- Your own flight shows as traffic. Log in to Volanta; once logged in, BA recognises your flight and leaves it out.
- Positions look a little old. Volanta's positions can be a minute or more out of date. BA moves airborne traffic forward along its heading and speed for up to three minutes to make up for this, but treat distances as approximate. This is not a collision-avoidance tool; for traffic near you in the air, use TCAS Traffic.
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:
- BA does not switch profiles by itself: choose the aircraft from the Aircraft menu before you fly (see Choosing Your Aircraft).
- They all need the free MobiFlight WASM module to operate switches and knobs (see What You Need).
- The FCU windows work as described in Autopilot Windows; this chapter covers the Airbus details.
- On the A32NX, the Headwind A330 and the Fenix, the MCDU line select keys are Ctrl+1 to Ctrl+6 (left) and Alt+1 to Alt+6 (right), or F1 to F12 with the alternate setting in FMC Settings. The A380's MFD has no line select keys; you arrow to a line and press Enter instead (see its section).
- Output Ctrl+M opens the aircraft's Monitor Manager.
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:
- The FlyByWire A32NX, installed with the FlyByWire Installer.
- The MobiFlight WASM module in your Community folder.
- A screen reader.
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:
- ELEC: batteries 1 and 2, external power (and whether it is available), generators 1 and 2, APU generator, bus tie, AC essential feed, IDG disconnects, commercial and galley power, and the emergency generator controls.
- ADIRS: the three IR mode selectors (Off, Nav, Att), and the IR and ADR pushbuttons.
- APU: APU master switch, APU start, and the auto-extinguish test and reset.
- Oxygen: crew supply, passenger masks, the passenger oxygen light and the timer reset.
- Fire: guards and handles for both engines and the APU, the fire tests, and the agent discharge buttons.
- Hydraulics: engine and electric pumps with their fault lights, the PTU, the blue pump override, leak measurement valves and the RAT manual deploy.
- Fuel: the mode selector, the six tank pumps and the crossfeed.
- Air Conditioning: cockpit, forward cabin and aft cabin temperatures (type a value in degrees Celsius, 18 to 30), and hot air.
- Bleed: APU bleed, engine bleeds, cross bleed, pack flow, packs 1 and 2 and ram air.
- Pressurization: mode, manual cabin vertical speed, ditching and landing elevation.
- Ventilation, Anti Ice (wing, both engines, probe and window heat), Wipers, Signs (seat belts, no smoking, emergency exit lights).
- Interior Lighting (annunciator lights, dome, and flood and integral brightness levels from 0 to 100) and Exterior Lighting (nose, landing, strobe, beacon, wing, nav and logo, runway turn-off, plus "all landing lights on" and "all off").
- Calls, GPWS, Flight Control Computers (ELACs, SECs, FACs and rudder trim), Cockpit (cockpit door, door video, armrests, third occupant seat), Evacuation, Cargo Smoke, Recorder and Misc, and Engine Start (the FADEC ground power switches).
Glareshield holds:
- FCU: heading, speed, altitude and vertical speed values with their push and pull knobs, LOC, APPR, Expedite, autopilots 1 and 2, autothrust, the red AP disconnect, SPD/MACH and the TRK/FPA toggle.
- EFIS Captain and EFIS First Officer: ND mode and range, navaid selectors, the ILS button, the flight director, the altimeter (value, inHg/hPa unit, push and pull for QNH and standard), and the map filters (constraints, waypoints, VOR/DME, NDB, airports).
- Warnings: the master warning and master caution acknowledge buttons for both sides.
Instrument holds the main instrument panel:
- Gear, Autobrake (DIS, LO, MED, MAX, plus the brake fan), ISIS, Source Switching and Clock (chronometer start and stop, reset, and elapsed time).
- PFD, ND, ISIS, System Display and Status, which are mostly read-only status displays. This is where you read the flight instruments; see "Special windows" below.
Pedestal holds:
- Flight Controls (spoilers armed status, speed brake handle, flaps), Speed Brake (a combo, arm and disarm, retract, full, and a fine control), Parking Brake, Engines (engine mode selector and both engine masters), and Thrust Levers (set all levers, or each lever, to a detent).
- ECAM Control Panel: every page key (ENG, APU, BLEED, COND, ELEC, HYD, FUEL, PRESS, DOOR, BRAKES, FLT CTL), ALL, STS, RCL, T.O. CONF, EMER CANC and both CLR keys.
- Weather Radar, Transponder (mode, ATC system, altitude reporting, squawk, ident, TCAS mode and display, and the ATC message acknowledge) and RMP.
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:
- Up and Down arrow read the screen line by line. Labels and values keep their left, centre and right positions, so on a braille display the right-hand values line up in one column.
- Green text (usually the active choice, or a value the FMS has accepted) is marked with a star in front of the value, so "*10.2/0213" means that value is shown in green.
- PageUp and PageDown scroll (the flight plan, and runway lists on the departure and arrival pages). Left and Right arrow move between pages of a multi-page form such as PERF when the display list has focus. Alt+Left and Alt+Right do the same from anywhere in the window, and Alt+Up and Alt+Down scroll.
To type into the scratchpad:
- Press Alt+S to jump to the scratchpad input field.
- Type your entry, for example a waypoint name or a cruise level.
- Press Enter. BA sends it to the MCDU scratchpad.
- 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:
- Dashboard: your flight, weather, and SimBrief import (set your SimBrief username in the flyPad Settings first; see SimBrief).
- Ground: Services (doors, jet bridge, stairs, GPU, baggage, catering, fuel truck), Fuel and Payload. Each door tile carries the door's real name and says whether it is active. Wheel chocks and safety cones read as status lines, "placed" or "not placed". They are information only: the aircraft places them itself.
- Payload and Fuel: BA rebuilds these pages as readable lines and fields. Each payload field tells you the current and maximum values and the unit, and the refuel target is offered both as a slider and as a number field.
- Settings: each setting reads its name followed by its choices, with the selected one marked. The "US Units" setting switches BA's own weight readouts (gross weight and fuel) between pounds and kilograms, so what you hear matches the aircraft.
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:
- In the flyPad Settings, choose an ACARS provider: Hoppie, SayIntentions or BeyondATC.
- 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:
- Read the message to the end. PageDown moves to the next page of a long message, PageUp goes back.
- Press the answer key, for example Alt+2 for WILCO. The keys change to CANCEL and SEND.
- Press Alt+2 again to send.
- 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:
- Flight mode annunciator changes: vertical, lateral and autothrust modes. An armed altitude that carries an FMS constraint is announced as "Altitude constraint armed", so you can tell it from an ordinary armed altitude without reading the PFD.
- ECAM warnings, cautions and memos, and master warning and master caution.
- "Mode reversion, check FMA", when the flight guidance has reverted to another mode by itself, and "Altitude discrepancy between sides" when the captain's and first officer's altitudes disagree (the CHECK ALT flag a sighted pilot sees on the PFD).
- Altimeter changes, approach minimums, flaps and gear.
- TCAS traffic and resolution advisories, including what to fly; see TCAS Traffic.
- COM frequency changes, and "Transmitting on VHF 1" when you start transmitting.
- Flight phase changes, such as "Entering Climb phase".
- Door states, and aircraft preset loading progress ("Aircraft preset loading complete").
- "V1", "Rotate" and "V2" on the take-off roll, from the MCDU PERF TAKE OFF page; see Takeoff Speed Callouts. Speeds the FMS has cleared are read as "not set".
Every one of these can be muted in the Monitor Manager (Output Ctrl+M).
Things to know
- Wing anti-ice, the evacuation horn and other one-way controls behave like the real ones. For example, the evacuation horn shut-off silences the horn ("Evacuation horn silenced") and is not something you switch back on.
- RTO autobrake may refuse to arm right after a flight. That is the aircraft's own logic, not a fault; it arms normally on a fresh start.
- Weight units follow the flyPad's "US Units" setting; you hear "Weight units kilograms" or "Weight units pounds".
- There is no metric altitude on the A320. The real A320 has no MTRS button, so BA does not offer one.
- The A32NX is updated often. FlyByWire's development builds sometimes rename things underneath. If a readout suddenly says "not available" after an aircraft update, update BA too and report it if it persists.
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:
- Fenix v3, loaded and running in the simulator. Older Fenix versions (2.x) are no longer supported, so update the Fenix if you have not. The MCDU, the EFB and the Fenix windows all talk to the Fenix's own data service, which only runs while the aircraft is loaded.
- The MobiFlight WASM module in your Community folder. BA works the switches through it, and turns, pushes and pulls the FCU and baro knobs through it too.
- For the AI reads, which BA uses when it cannot read a display directly (see Special windows): an AI provider set up with your own API key. See AI Display Reading and Scene Description.
- For current navigation data: either your Navigraph account connected in the Fenix's own EFB, on the Settings app's Connections page (see EFB below), or a navigation data file you import yourself on the MCDU's DATA, A/C STATUS page.
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:
- Electrical: batteries, generators, APU generator, external power, APU master and start, bus tie, AC essential feed, IDGs, galley, commercial, and the emergency generator controls and covers.
- ADIRS: the three IR mode selectors and the ADR pushbuttons. On the GNADIRS panel it adds the data and system display selectors and the full keypad (keys 0 to 9, Clear and Enter), so you can enter a position; on the plain ADIRS panel it adds the IR pushbuttons instead.
- Air Conditioning and Pressurization: bleeds, packs, hot air, ram air, ditching, pressurization mode and manual vertical speed, ventilation, cross bleed, pack flow (Econ Flow, Off or On, on the A321), the three zone temperatures, and on aircraft with aft cargo heat, Aft Cargo Hot Air and Aft Cargo Temperature (0.0 to 1.0, like the zone temperatures).
- Fire, Hydraulic, Fuel (six tank pumps, crossfeed, mode selector, and ACT Pump, Off or On, on aircraft with extra center tanks), Anti-Ice, Signs, Exterior Lights, Interior Lights, Voice Recorder, Oxygen (including mask tests), Evacuation, Calls (with Calls Mid and Calls Exit on the A321), Wipers (including rain repellent), Cargo Smoke, GPWS, Flight Control Computers (ELAC 1 and 2, SEC 1 to 3, FAC 1 and 2), Engine (manual start, and on IAE engines the N1 mode switches) and Maintenance (FADEC ground power, ELT, APU auto-extinguish test and reset, and more).
Pedestal:
- Engines (engine mode and both masters), Weather Radar, and ECAM: TO CONFIG, every page key, ALL, STS, both CLR keys, RCL, EMER CANC and the ECAM brightness controls.
- Flight Controls: parking brake, speed brake, rudder trim (left, right and reset), pitch trim (type the trim in degrees as the MCDU shows it, for example 0.3 for UP 0.3 or -0.8 for DN 0.8, and press Enter; BA answers "Pitch trim set to up 0.3"), the flap lever, the thrust levers (left, right or both) and the A/THR and AP disconnect buttons for both sides.
- ATC TCAS: TCAS and transponder modes, altitude reporting, traffic display, ident and the squawk code.
- Radio Management Panel (RMP): COM 1, 2 and 3 standby frequency and transfer, and every RMP's power and mode buttons (VHF, HF, NAV, VOR, ILS, GLS, ADF, BFO and AM).
- Audio Control Panel (ACP): the captain's volume knobs, transmit keys, reception switches (VHF 1 to 3, HF 1 and 2, interphone, cabin, VOR 1 and 2, marker and others), RESET, VOICE and the INT/RAD switch.
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:
- On the A321: Econ Flow instead of Pack Flow, and Calls Mid and Calls Exit.
- With extra center tanks: ACT Pump, whose upper and lower lights are announced.
- With IAE engines: the N1 mode switches, whose lights are announced ("Engine N1 Mode 1 Lower: On"). CFM engines have no N1 mode switches.
- On the GNADIRS panel: the ADIRS keypad and the data and system display selectors. On the plain ADIRS panel: the IR pushbuttons.
- With the digital ISIS: the ISIS controls. With the round standby gauges: the standby attitude cage. With aft cargo heat: Aft Cargo Hot Air and Aft Cargo Temperature.
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.
- Getting around: Alt+Home goes back to the EFB's home screen from anywhere, even from a text box. In an app, the "App switcher" button opens the list of apps.
- Takeoff and Landing: each result reads its label right before its value, for example "V1" and then "142"; a result not worked out yet says "not computed". Landing's two wind figures each follow what their arrow shows: "Crosswind from the left" or "Crosswind from the right", and "Headwind" or "Tailwind". Landing's runway condition is one Tab stop where the arrow keys choose the code, and each system's page of faults has a "Back" button, with the faults as check boxes.
- Failures: a failure says ", failed" or ", armed", and a chapter with an active failure says ", has failures".
- Settings: every on/off option is a switch named by its setting. Each "More options" button opens its menu with the focus inside it, read right after the button; Escape or the "Close menu" button closes it. Your Navigraph account, one way for Fenix v3 to get current navigation data, is connected on the Connections page; the other is importing a navigation data file on the MCDU's DATA, A/C STATUS page.
- Quick settings has a "Close quick settings" button. Its "Cycle sim rate" button says the rate it is on after its name, for example "NORMAL", and "AP REQUIRED" while the autopilot is off; the Fenix only lets you change the rate with the autopilot on, and until then Tab skips the button, so find it in browse mode.
- Escape first closes an open menu, drop-down list or the Panel States pop-up; the next Escape closes the window.
- The MCDU and FAP pages cannot be read with a screen reader. If you open one, BA takes you back to the home screen and tells you where to go instead: "The EFB's MCDU can't be read with a screen reader. Use the MCDU window instead: input mode, then Shift+M." or "The EFB's FAP can't be read with a screen reader. Use the Fenix windows list instead: input mode, then Control+Shift+F."
- Charts: the map is pictures only; it is announced as "Moving map".
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."
- Ctrl+1 and Ctrl+2 are the left keys, Alt+1 and Alt+2 the right ones (or F1, F2, F7 and F8 with the alternate setting in FMC Settings). A key with no label says "No action on that key." A held key presses only once.
- Page Down and Page Up scroll within a message; Ctrl+Page Down and Ctrl+Page Up go to the next and previous message. Ctrl+P prints.
- The Bright and Dim buttons after the list step the brightness and say the new level, for example "Brightness 60 percent".
- To answer, press the answer's key twice: once for WILCO and again for SEND. BA reads back the status and each new info line ("WILCO", "SENDING", "RECEIVD BY ATC"). CLOSE clears the message.
- A departure clearance needs your callsign in FLT NBR on the MCDU's INIT page. It comes back on the DCDU as two messages, a status and the clearance, so step to the clearance with Ctrl+Page Down.
With the window open or not, BA calls each new message ("DCDU:
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:
- Status: cabin ready, cabin lights, boarding music, doors, slides, cargo doors, temperatures, water and waste, and cautions. The Cabin ready check box reports the cabin ready (while the FAP does not offer it yet, you hear "Cabin ready is not available yet."), and the Cabin lights list sets Bright, Dim 1, Dim 2 or Off.
- Audio: boarding music on or off, its channel and volume (Volume up, Volume down); the prerecorded announcements, with Play now, Add to memo, Remove from memo, Clear memo, Play next, Play all and Stop; and the FAP loudspeaker volume, in 5 percent steps.
- Doors: each door with its slide and pressure messages. Select a door or cargo door, and the button after the list opens or closes it, for example "Open door 1 left". Doors work on the ground only, as in the Fenix EFB; above 100 feet you hear "Doors can only be opened or closed on the ground." A line with no door control, such as an overwing slide, has no button.
- Temperature: the forward and aft zones, with Forward warmer, Forward cooler, Aft warmer, Aft cooler and Reset to the cockpit temperatures.
- Water: water, the preselect (Preselect up, Preselect down), waste, service panels, lavatories and cautions.
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".
- Search: type part of a name and press Enter. BA says how many failures match and moves to the first.
- Show: All failures, Armed, Failed, or Armed or failed.
- Fail now (Alt+N), Arm (Alt+A, or Enter on a failure) and Clear (Alt+C) each ask Yes or No before anything changes, with No as the default. BA then says what the Fenix reports, for example "CPC 1 failed." Arm asks for its condition first, in a dialog that takes Above IAS, Above altitude AMSL, Below altitude AMSL, After event (None, V1, Take-off or Landing) and a number of seconds; it needs at least one ("Enter at least one condition.").
- Refresh (F5) reads the failures again.
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.
- Ctrl+F: the search box. Type at least 3 characters and press Enter; the results appear in the tree with how many there are.
- Ctrl+P: open the procedure the Fenix pinned for the latest ECAM alert. Press it again for the next pinned document.
- Ctrl+D: pin or unpin the selected or open document. The pin shows in the cockpit EFB too. BA reads it back, "Pinned:" or "Unpinned:" and the name, which can take a few seconds because the Fenix shows the change late.
- F6 moves between the document, the list and the search box, and Shift+F6 goes back. F5 reloads the list.
- Escape hides the window and keeps the open document for next time.
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".
- Enter on any option reads its details, which the details box (Tab) also shows: for an option in the first group its note first ("Effect on MSFS Blind Assist: …"), then the Fenix's own description of the option, its choices, where its value comes from (the Fenix default, your livery, this simulator session or your own permanent setting), and whether the EFB lets you change it.
- F2 changes an on/off or choice option for this simulator session, until you change aircraft or livery, as the EFB's own switch does: choose the new value in the dialog. The five options that reshape the cockpit (Standby Instruments, ISIS, ADIRS, ACP and DCDU) then ask Yes or No before anything changes.
- Shift+F2 makes an option your permanent setting, for every flight and livery: choose the value in the dialog.
- Ctrl+F2 resets your change to the Fenix default.
- Shift+F2 (after you choose the value) and Ctrl+F2 always ask Yes or No before anything changes, with No as the default.
- F5 reads the options again, for example "Refreshed, no changes."
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".
- ENG: fuel used, oil, vibrations, and the start values during a start.
- ELEC: batteries, generators and transformers, and which buses are powered.
- HYD: the three systems' pressures, pumps and valves, and the PTU.
- FUEL: each tank, the pumps and valves, the fuel on board and the tank temperatures. The rows follow your aircraft: an A321 has no outer tanks, and extra center tanks have their own rows.
- STATUS: the STATUS text, with its colors.
- APU: the APU generator, AVAIL, its bleed pressure and valve, N and EGT.
- BLEED: pack temperatures and flow valves, the cross bleed and APU valves, and each engine's bleed pressure, temperature and valves.
- PRESS: landing elevation, ΔP, cabin V/S and altitude, the outflow valve and the vents.
- COND: each zone's temperature, duct temperature and trim valve ("24 °C, duct 38 °C, trim valve 34 % hot"), and hot air.
- CRUISE: the page the SD shows by itself in cruise: fuel used, oil and vibrations, then the cabin's pressure and temperatures.
- DOOR: oxygen, then every door nose to tail for your aircraft, with its slide ("Door 1 left: closed, SLIDE armed").
- WHEEL: the gear and gear doors, steering, anti skid and brakes, auto brake, then each wheel by number ("wheel 2: brake 204 °C, tire 205 PSI").
- F/CTL: spoilers by number from inboard ("SPD BRK left, 1 to 5: 0°, 25°, 25°, 25°, 0°"), ailerons and elevators up or down, the flight control computers, pitch trim and rudder.
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:
- Top left: ground speed and true airspeed ("GS 456 TAS 448"), the wind ("wind 213 / 37") and the green wind arrow ("wind arrow pointing 75° right").
- Top center: the tuned ILS, and the heading under the lubber line with the track diamond ("heading 318 under the lubber line, track diamond 4° right").
- Top right: the next waypoint, its bearing, distance and time ("VAKSU 318; 84 NM; 17:29"), or "PPOS" with no flight plan. ROSE LS and ROSE VOR show the radio block here instead ("ILS2 110.15; CRS 186°; ICIZ").
- Center and right side, ROSE LS: the course pointer, the localizer bar ("localizer bar 0.4 dots right") and the glideslope ("glideslope diamond 1.3 dots above").
- Center, ROSE VOR: the course pointer, and the deviation bar in dots with TO or FROM ("deviation bar 1.9 dots right, FROM").
- Map, the route (ARC, ROSE NAV and PLAN): the route line, then in route order the last waypoint passed, the TO waypoint ("ALPHA, white diamond, 10.0 NM ahead") and every later one ("green diamond"). A white or colored ring around a waypoint is its altitude constraint, and with CSTR on the row adds the constraint as printed ("TROYS, green diamond in a magenta ring, 30.0 NM ahead; + 3500"). The runways, the top of climb and descent and other markers, and any hold, come where they lie along the route. Where the line leaves the display you hear "route goes off the top edge, toward PADGT", and at a gap in the route "route line ends at PADGT" and "route line starts again at SMTTH".
- Map, a temporary flight plan: "temporary flight plan, yellow dashed line" and its waypoints.
- Map, the missed approach: "missed approach line, cyan solid line" and its waypoints, listed once the ND draws it, as the approach nears.
- Map, what needs no flight plan: the heading bug, the track line, the cross-track error ("cross-track error 4.7L, left of the aircraft"), the range rings, FIX INFO, and the bearing pointers ("VOR 1 single-line pointer, at 205 on the compass").
- Map, navaids and airports: with VOR.D, NDB, ARPT or WPT selected, each one nearest first ("LGC, magenta circle with a cross, 45.2 NM, 103° left"). They are magenta, and a tuned navaid is cyan.
- Map, traffic: "other traffic, hollow diamond", "proximate traffic, filled diamond" and "traffic advisory, amber filled circle", each with where it is, its altitude relative to you in hundreds of feet and its trend ("3.0 NM, 90° left, +01, climbing"). At ranges 10 and 20 the TCAS ring is listed too.
- Bottom corners: the radios on the EFIS's selectors ("Bottom left: VOR1; CVG; 8.4 NM; single-line arrow"), a failed one in red ("Bottom right: VOR2, red"), and at the bottom right TERR, the weather radar's mode or WXR OFF.
- Messages, last: the ND's own messages, for example "Message: MODE CHANGE", and what its two boxes show ("TA ONLY").
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:
- "Cabin ready", once, when the cabin crew reports the cabin ready. In Fenix v3 the virtual purser reports it; your cabin call from the cockpit no longer makes the cabin ready.
- A passenger or cargo door opening or closing, for example "Door 1 left open" or "Forward cargo door closed". A door you open or close in the Cabin window is said only once, by the window.
- "Slides armed" or "Slides disarmed", when the passenger doors' slides are all armed or all disarmed.
- "Cabin caution:" and the caution, when one appears on the flight attendant panel.
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
- Panel buttons are pressed and released, like a real finger press. The aircraft's light shows the result. You do not need to "un-press" anything. Bus Tie, Service Interphone Override, Avionics Compartment Light, the weather radar's GCS, ACP PA Transmit, Calls Mechanic, All, Forward, Aft, Mid and Exit, the clock's Chronometer and Date buttons, ISIS Baro Push and Pedestal Video are buttons you press once, like the real ones. One with a light shows its state on its label and the light announces the change; one without a light says, for example, "Calls Mechanic pressed".
- ADR, IR and Bus Tie read the right way round. Their light is the OFF legend, so the button reads "ADR 1: On" while ADR 1 works and "ADR 1: Off" once you switch it off (Bus Tie reads "Auto" or "Off"), and the light announces the same words, for example "ADR 1: Off" or "Electrical Bus Tie: Off". Their Monitor Manager rows are named "ADR 1" to "ADR 3" and "IR 1" to "IR 3".
- ISIS Baro Push says it was pressed; the ISIS window's altitude row shows the baro setting it left.
- The Fenix does not model MLS reception, so there is no MLS switch on the audio panel.
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:
- The FlyByWire A380X, installed with the FlyByWire Installer. BA follows FlyByWire's Development build. FlyByWire changes things underneath from time to time, and an older copy of the aircraft may not report every readout correctly, so keep the aircraft updated.
- The MobiFlight WASM module in your Community folder.
- The displays powered (battery on, or a powered preset) so there is something to read.
- For the full airport map and Brake-To-Vacate features: a Navigraph subscription, logged in inside the flyPad.
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:
- EFIS: each side has LS, V/V, constraints, airport and traffic switches, ND mode and range, navaid 1 and 2, the weather or terrain overlay, the airport map range, and one ND Filter control offering Off, Waypoints, VOR/DME and NDB. These are alternatives on the A380: choosing one replaces the last. Once one is chosen, the aircraft has no way to go back to showing none, so picking "Off" tells you so rather than appearing to work.
- Flight directors: on the A380 both flight directors are one pushbutton, as on the real aircraft. One press switches both.
- Interior Lighting has the main panel flood and side console dimmers as sliders, the storm light, lighting presets, and cabin brightness from 0 to 100 percent.
- RMP in the Pedestal is a quick read-only glance at the three radio panels. To tune radios, use the RMP window described below.
- Audio Control Panel lets you check and switch which VHF radios you are listening to and transmitting on, and set their volume.
- Aircraft presets (Cold and Dark, Powered, Pushback, Taxi, Takeoff) are loaded from the flyPad's Presets page. BA announces the progress, ending with "Aircraft preset loading complete".
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:
- The Altitude window has a Metric (MTRS) button, which reads "Metric (MTRS) — now OFF (press for metres)" or "now ON (press for feet)". With metric altitude on, the value you type is in metres (30 to 14,935).
- The Autopilot panel has an FD button for both flight directors, and no EXPED button, because the A380 FCU has none.
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:
- button: press Enter to activate it. Flight plan waypoints and discontinuities are buttons too; Enter opens their menu.
- edit: a field you can type into. An empty one reads "blank".
- combo box: a dropdown, which also says whether it is collapsed or expanded and what is selected. Press Enter to open it; its choices then appear right underneath as "option" lines.
- option: a choice in an open menu. Arrow to it and press Enter.
- dimmed: the aircraft is not accepting that control right now. This is usually correct aircraft behaviour, not a fault.
To enter a value:
- Arrow to the field.
- Type the value. It goes into the scratchpad (Alt+S also jumps there).
- 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:
- The Go to MFD page combo at the top reaches every page: the ACTIVE pages (F-PLN, PERF, FUEL & LOAD, WIND, INIT), POSITION, SEC INDEX and the secondary flight plans, DATA, ATC COM and SURV. Arrow to a page and it opens once your selection settles.
- The Alt page buttons: Alt+I INIT, Alt+F F-PLN, Alt+E PERF, Alt+L FUEL & LOAD, Alt+R RAD NAV, Alt+P SEC FPL, Alt+D DIR, Alt+A ATC COM, Alt+V SURV.
- Ctrl+Up and Ctrl+Down (or PageUp and PageDown) step to the previous or next page and, on the flight plan, scroll it. You hear "Previous page" or "Next page".
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:
- Press Alt+V for the VHF page.
- 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".
- Type the frequency without a decimal point. It completes itself: 118500 or just 1185 both give 118.500. Backspace deletes a digit.
- Press Enter. The frequency goes into standby and BA reads it back, for example "VHF standby 1, 118.500".
- 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:
- Press Alt+T for the transponder page.
- Type the four digits (0 to 7). It sets on the fourth digit and reads back, for example "Squawk 2222".
- 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.
- Up and Down arrow move the real checklist cursor and read each line, including whether it is checked.
- Enter opens the highlighted checklist from the menu, or ticks the highlighted item.
- Backspace goes back to the menu.
- The Abnormal procedures button lists active ECAM procedures.
- F5 refreshes and Escape 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:
- Map and BTV: choose the BTV runway and press Arm runway, then choose the BTV exit and press Arm exit. Clear BTV removes the selection. The exit list only offers exits valid for the armed runway, closest first, each with its distance down the runway. The status box below reads back the runway and landing distance available, the exit and its distance, the predicted dry, wet and live stopping distances (worked out on approach, not on the ground), runway occupancy and turnaround times, and any runway-ahead caution. If the aircraft rejects an exit, BA tells you.
- Airport: type an ICAO code in Airport code and press Display airport, or use the Origin, Destination and Alternate buttons. You hear "Loading airport" and the code.
- Status: whether the airport database is loaded, and the AIRAC cycle.
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:
- Arm a runway and an exit in this window, choosing an exit beyond the predicted wet stopping distance.
- 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:
- Ctrl+0 reads the approach capability as LAND 2, LAND 3 single or LAND 3 dual.
- With metric altitude (MTRS) on, Q, A, Shift+A and the altitude panel fields all speak metres, and the altitude callouts come every 300 metres and say the unit, for example "3000 meters". The standby ISIS always stays in feet.
- Ctrl+E switches the E/WD callouts on and off, and the choice is remembered.
The A380 announces everything the A32NX does, and also:
- Thrust lever detents as the levers reach them, for example "All thrust levers" followed by the detent.
- The full warning stream from the E/WD: failure titles and their action lines in the order a crew reads them, memos, and the small status reminders at the bottom of the display (status, advisory, failure pending).
- Overhead pushbutton fault lights.
- Approach capability changes.
- "Altitude constraint armed" or "Cruise altitude armed". On the A380 the PFD marks a constraint only by a colour change, so this callout is the only way to hear it.
- Runway overrun protection: "Runway too short" and "If wet, runway too short" on approach, "Max braking", "Set max reverse" and "Keep max reverse" on the rollout, and "Runway ahead" when taxiing towards a runway.
- During a BTV rollout, the BTV state and a countdown such as "500 meters to exit" and "300 meters runway remaining".
- "V1", "Rotate" and "V2" from the speeds entered on the PERF page.
- Speed protection, minimums set or cleared, and weight unit changes.
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
- The A380 is a development build. FlyByWire marks some features as unfinished, for example parts of ATC COM, FLS approaches and the second ISIS. If something reads as an error page or does nothing, it is often the aircraft, not BA.
- Wing anti-ice works, but the "Wing Anti-Ice Flowing" readout may still say there is no flow. FlyByWire has not yet modelled the A380's wing anti-ice air supply.
- Surroundings window frequencies: on the A380, pressing Enter on a frequency in the Surroundings window does not tune it. It reminds you to tune COM 1 with the RMP window instead.
- The A380 always keeps a destination runway. To change the arrival, choose a different runway or approach; you cannot remove it entirely.
- TCAS resolution advisories are inhibited on the ground and close to it. Hearing only traffic advisories while taxiing is correct.
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
- DCDU: Input Ctrl+Shift+D, exactly as on the A32NX, including the two-step answer and the need for a datalink connection.
- E/WD: Output Alt+E.
- PFD, ND, ISIS and System Display from the Instrument section panels.
- First Officer: Output Shift+C, with the A330's flows and checklists.
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:
- Altimeter (Output B): BA reads the simulator's own altimeter on the A330, because the FlyByWire baro values do not reach BA on this aircraft. You hear for example "Altimeter: 1013, 29.91", with the unit the FCU is set to read first, or "Altimeter standard". Knob changes in the cockpit are announced the same way. If nothing has been read yet you hear "Altimeter not available".
- Characteristic speeds (Shift+1 to Shift+6): the A330 still publishes its speeds the older way, and BA reads them from there, so VFE and VS keep working on this aircraft.
- Distance to destination (Output D): the A330 keeps this in an older place, and BA looks there too.
Things to know
- The Ctrl+B altimeter window sets both sides as on the A32NX. Its own change is not announced twice.
- Visual guidance and taxi guidance use widebody settings on the A330: a heavier, faster approach profile and a slightly earlier turn cue when taxiing, to suit the longer aircraft.
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:
- Overhead: Electrical, ADIRU, Hydraulics, Fuel, Engines, Anti-Ice, Air Systems, Lights, Signs, Oxygen, Wipers, Flight Controls, Flight Recorder.
- Forward Panel: Landing Gear, Autobrake, GPWS, Instruments.
- Pedestal: Control Stand, Transponder/TCAS, Fire Protection, Cargo Fire, Radio, Calls, Flight Deck Door, Boris Audio Works.
- Glareshield: MCP, Warnings, EFIS Captain, EFIS First Officer, Display Select.
- Interior: Cockpit Furniture, Cabin Bins, Cabin Items, Galley.
A few panels deserve a word:
- Electrical has the engine generators as On and Off buttons, like the APU generators, followed by the Generator 1 and 2 Off Bus lights and the APU Gen Off Bus light, so you can check whether each generator has actually taken its bus.
- Engines puts each engine's fuel lever straight after its start switch: Start 1, Fuel 1, Start 2, Fuel 2.
- Air Systems includes the pressurisation readouts (cabin altitude, differential pressure, cabin climb rate, duct pressures) and fields for the flight and landing altitudes.
- Control Stand has the Speed Brake combo (Down, Armed, 50 percent, Flight detent, Fully deployed), the stabiliser trim cutout switches, and TO/GA and autothrottle disconnect buttons.
- Transponder/TCAS has a Squawk Code field: type the four digits and press Enter.
- Radio shows COM 1 and COM 2 active frequencies, a standby field for each and a swap button.
- Calls has the microphone selectors, the Captain and First Officer VHF 1 to 3 receiver buttons (each says whether that receiver is on — useful for listening to a second radio, such as COM 2 on SayIntentions), the service interphone, and the ATTEND and GRD CALL buttons, which BA confirms with "Attend call" and "Ground call".
- Instruments has the N1 SET selector, a Manual N1 button and the Speed Reference selector, then Fuel Flow Used and Fuel Flow Reset buttons and the MFD ENG and MFD SYS buttons. The fuel flow switch springs back by itself on the real aircraft, so it is two buttons: Fuel Flow Used shows the fuel used on the engine displays for 10 seconds, Fuel Flow Reset sets it to zero, and BA reads the line back a moment after the press, for example "FUEL USED: 1.23, 1.20" (in thousands of pounds). MFD ENG and MFD SYS choose the lower display's page, and BA reads back what it now shows, for example "Lower display: SYS page". Manual N1 sets the N1 reference by value when N1 SET is on 1, 2 or BOTH: type a number from 0 to 105 and press Enter, and BA turns the knob for you (a big change takes a few seconds) and reads back the result, for example "N1 reference 95.5", or each engine's value when they differ. With N1 SET on AUTO it says "Set N1 SET to 1, 2 or BOTH first".
- EFIS Captain and EFIS First Officer each have a Captain Minimums (feet) (or First Officer) field next to the baro/radio selector. The Captain's turns the knob from the value the PFD shows and reads back what it then shows, "Minimums: BARO 300"; it needs the PFD reader. The First Officer's still works the old way and can land on a different value from the one you typed.
- Boris Audio Works holds the controls of that sound pack, if you use it: Headphone Simulation, Hydraulic Pump Model (Vickers 1 or Vickers 2) and Passenger Chatter.
- The Interior section is for fun and immersion: sliding windows, sun visors, window shades, headrests, rudder pedals, jumpseat, armrests, storage cubbies, all 38 overhead bins (plus Open All and Close All), window blinds, cabin and galley lights, curtains, lavatory doors, and the galley taps, coffee makers and airstair panel. Many of these make their sound back in the cabin, so you may hear nothing from the cockpit — BA's announcement is your confirmation.
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:
- Input Ctrl+H opens MCP Heading (0 to 359), with Heading Select and LNAV buttons that show Engaged or Off.
- Input Ctrl+S opens MCP Speed (knots 100 to 399, or Mach M0.40 to M0.95), with a Speed Intervene button. Speed Intervene only shows a state while VNAV is engaged, because that is the only time it means anything.
- Input Ctrl+A opens MCP Altitude (0 to 50000 in 100-foot steps), with Altitude Intervene, Altitude Hold, VNAV and Level Change buttons.
- Input Ctrl+V opens MCP Vertical Speed (-9000 to +9000 feet per minute), with an Engage V/S button. The value box only accepts a number once V/S is engaged — until then it says "Engage mode first to enter a value" — because the real MCP window is closed until the mode is on. The 737 has no flight path angle mode.
- Input Ctrl+B opens the Altimeter window. Type either hectopascals (900 to 1060) or inches (26.50 to 31.30); BA works out which from the number, so "1013" and "29.92" both work. It also has a Standard button.
- Input Ctrl+N sets the NAV radios: NAV 1 and NAV 2 frequency (108.00 to 117.95) and course, pre-filled with the current values. Press Enter in any of the four boxes to apply all four and close the window; Cancel or Escape closes it without changing anything.
- Input Ctrl+P opens the 737 Autopilot window: CMD A (Alt+A), CMD B (Alt+B), CWS A, CWS B, F/D Captain, F/D First Officer, Approach (Alt+P), VOR LOC (Alt+O), A/T Arm, Disengage Bar, A/P Disconnect, A/T Disconnect and a Bank Limit list (Alt+L). Each button shows its live state.
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 display is a list: Up and Down arrow read it line by line. When the page changes, BA reads the new page title.
- Page Up and Page Down (or Alt+Up and Alt+Down) are the previous and next page keys.
- Line select keys: Ctrl+1 to Ctrl+6 are the left keys, Alt+1 to Alt+6 the right keys.
- Alt+S jumps to the Scratchpad box. Type your entry and press Enter; BA types it into the CDU one key at a time. Alt+Home returns you to the display.
- Backspace on the display is CLR when the scratchpad has text and DEL when it is empty. When the scratchpad empties, BA says "Cleared". Any new scratchpad message from the FMC is read aloud.
- Page keys: Alt+I Init Ref, Alt+R RTE, Alt+A Dep/Arr, Alt+F Fix, Alt+G Legs, Alt+H Hold, Alt+P Prog, Alt+M Menu, Alt+B CLB, Alt+Z CRZ, Alt+D DES, Alt+N N1 Limit, Alt+E Execute (or Ctrl+Enter), Alt+C CLR/DEL. There is no VNAV key on the 737 window. Every key is also a button in the window.
- Where a page offers a choice between options shown with arrows, the selected one is marked with an "X".
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:
- After you press Calculate on the Performance page, the results read as lines such as "V1: 155 kt".
- The Ground Operations app is opened from the tablet's home screen. Its live values — turn time, time remaining, fuel uplift — are read as named lines, and the turnaround progress as "Turnaround: 45%".
- Alert cards, such as the confirmation after Save Preferences, are spoken as soon as they appear; the OK button stays a normal button.
- Unit toggles on the Preferences page appear as two-choice lists showing the current unit.
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:
- 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.
- MFD ENG and 4. MFD SYS: choose the lower display's page; BA reads back what it shows.
- 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.
- Fuel Flow Used and 7. Fuel Flow Reset, as in the Instruments panel.
- N1 SET: 2, 1, AUTO or BOTH.
- 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:
- MAP, the one you fly with: the aircraft near the bottom of the screen, pointing up, with the route, its waypoints and the map ahead, under a compass arc. The top of the map is the aircraft's track, the way it is actually moving over the ground, printed as TRK at the top; in a crosswind the nose points a few degrees off it. The map turns to the heading instead, and prints HDG, if the IRS is in a degraded mode or the 737 is set up to show MAP heading-up.
- PLN (plan): north up, centred on a waypoint you choose with the STEP key on the CDU's LEGS page, for checking a route before you fly it.
- APP and VOR: the approach pictures, for flying an ILS (APP) or a VOR radial (VOR). There is no route; instead a course pointer lies across the compass, and a deviation bar in the pointer's middle slides left or right across a scale of dots to show how far you are off the localizer or radial. The tuned ILS or VOR is at the top right, and APP adds a glideslope scale on the right. They are described after the map lines below.
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:
- "Captain ND: MAP, range 20": the mode and the range knob. With CTR pressed, ", centred"; in PLN, ", centred on" and the waypoint. If no display is showing the Captain's ND (the display selectors moved it), the list says only "Captain ND: not on any display", and with the displays off, "Captain ND: off".
- "Top left: GS 0, TAS ---, wind ---°/---": ground speed, true airspeed and the wind. The ND shows dashes for the airspeed and the wind until the aircraft is moving fast enough to work them out. In flight the wind reads like "wind 351°/14, from 88° left": 351 degrees at 14 knots, and the ND's wind arrow showing it coming from 88 degrees left of the top of the map.
- "Top centre: TRK 079 MAG": the direction the top of the map points, magnetic. In PLN the ND prints an N with an arrow pointing up there instead, "Top centre: N↑": north is up. The other three compass letters sit at the left and right edges of the screen, level with the centre waypoint, and at the bottom, and the list has each in its place: "Left side: W" after the map buttons, "Right side: E" after the map lines, "Bottom centre: S" just before the messages.
- "Top right: EMPAD, 1533.3Z, 6.8 NM": the active waypoint, the one the aircraft is flying to, with its arrival time in hours, minutes and tenths of a minute UTC, and the distance to go along the route. With no route, "------Z, --- NM".
- "Left side: STA, ARPT": which map buttons are on, as the ND prints them. With WXR on, the radar's tilt follows as the ND prints it, "tilt +2A": the antenna's tilt in degrees up (+) or down (−), with A for automatic tilt or M for manual; then "VAR" while the radar's gain is not at its calibrated setting. With TERR on, the ND prints the highest and lowest terrain elevation in the picture under the label, in hundreds of feet, each in the colour of its terrain band, while PMDG's terrain peaks mode (GPWS_TerrPeaksMode, on by default) is set: "Left side: TERR, highest 045 (amber), lowest 012 (green)". While it shows them, it shows no radar tilt.
- Lines starting with "Map:": what is drawn on the map, each with its distance and how many degrees left or right of the top of the map it is, for example "Map: EMPAD, 8.1 NM, 103° left". In PLN the place is the distance and compass point from the centre waypoint instead: "Map: PT753, 5.0 NM north-west of EMPAD". Only what the real map shows at this range is listed: turn the range knob or press CTR and the list changes as the picture does. In MAP the map reaches past the sides of the aircraft and a little behind it, down to the bottom of the screen, so a waypoint just behind your wing can be on it.
- "Right side: VDEV 250, above the path": in a VNAV descent, how far the aircraft is above or below the descent path, in feet. The ND draws a pointer on a scale on the right: at the top when you are below the path, at the bottom when you are above it, with the number beside it. Within 30 feet the ND prints no number, and the list says "VDEV, on the path". When the FMC's vertical path data has failed, the ND draws the amber letters VTK in a box in the scale's place instead, and the list has "Right side: VTK (amber, boxed)"; BA says "ND message: VTK". When the ND shows RNP and ANP at the bottom, it also prints the vertical RNP and ANP in feet beside the scale, and the line ends ", vertical RNP 400, ANP 154" (dashes while the FMC has no value).
- "Bottom: RNP 1.00, ANP 0.05": the navigation accuracy required and the accuracy the FMC has, in nautical miles.
- "Below the aircraft: XTK 9.7 R": in MAP, with the RNP display on, the number printed under the aircraft symbol: how far the aircraft is off the route, in nautical miles, R when it is right of the route and L when left (XTK, cross-track error, is BA's word; the ND prints the number alone). At the two closest ranges it has two decimals, and on the route it reads 0.0.
- "Bottom left: FMC L": in MAP and PLN, the FMC the map's route comes from, as the ND prints it (FMC L or FMC R).
- "Bottom left: VOR 1, CAG, DME 23.4" and "Bottom right": what the VOR/ADF switches show in the bottom corners: the station's identifier and its DME distance. A failed receiver shows only its label, in amber inside a box: "Bottom left: VOR 1 (amber, boxed), DME (amber, boxed)".
- "Message: TCAS OFF" for each message the ND shows, or "Messages: none". In MAP, "Message: MAP" is the amber MAP flag the ND shows when it has no position to draw the route from: before the IRS is aligned, or while the FMC has no position. The top right then shows dashes, and the list has no route, no map buttons on the left side and no navaids, fixes or airports.
What the map lines name:
- "half-range ring 10": the number printed on the dashed ring halfway to the edge of the compass arc. It is half the range you selected: at range 20 it says 10.
- "track line, straight ahead, marks at 5, 10 and 15 NM": the line from the aircraft up toward the compass arc along the track, with three short marks across it at a quarter, half and three quarters of the way to the arc. When WXR, TERR or TFC is on, the ND draws range arcs instead of the marks (PMDG's ND_RangeArcs option, on by default), but keeps the marks with CTR pressed. When the map is heading-up, the line leans off the top by the drift: "track line, 4° right".
- "range rings 5 and 10": in PLN, the two circles round the centre and the numbers printed on each, above and below the centre. The outer circle is half the range you selected from the centre, the inner one a quarter: at range 20 they say 5 and 10.
- "…, at the edge" at the end of a line: the edge of the map cuts that symbol, but part of it, or of its name or text, still shows. This goes for route waypoints, the route's markers, tuned VORs, navaids, fixes, airports, traffic, and your aircraft in PLN.
- "aircraft, 7.5 NM south-east of PADGT": in PLN centred on a waypoint, where the ND draws your aircraft, when it is on the map or at its edge.
- The route's waypoints in flying order, with, when DATA is on, each one's altitude constraint and arrival time after a semicolon: "Map: PT753, 23.0 NM, 20° right; FL240B, 1537Z". An altitude ending in A is "at or above", B "at or below". With DATA off, the ND still prints the active waypoint's altitude constraint, without the time, while PMDG's option for it (ND_ActWptData, on by default) is set, and the list does the same: "Map: HRMBE, 19.6 NM, ahead; FL210B, 16000A".
- "hold at HRMBE, inbound 270°, right turns, legs 4.0 NM": a hold you entered on the CDU, right after its fix's line, while the fix is on the map. The ND draws the holding pattern there. The inbound course, the turns and the legs are what the HOLD page shows: the leg distance when one is set, otherwise the leg time, "1.0 minute legs".
- "route goes off the left edge, toward PT753": where the route line leaves the map, and the waypoint the line is heading for. Where the route has a discontinuity, the ND draws no line across the gap, so nothing is said there.
- The route's markers: T/C top of climb, T/D top of descent, S/C step climb, DECEL where the aircraft starts slowing down, E/D end of descent.
- The departure and arrival airports; close up, the departure runway, drawn as its outline, with a dashed extended centreline 14.2 NM beyond each end. Its line says which way the centreline runs on the screen and, while you are beside it, how far you are from it: "Map: runway 08R, 0.5 NM, 122° right; centreline 14.2 NM each way, running 5° right of the top, you are 1.2 NM left of it". When the route has a runway for an airport, the ND draws the route's symbol at that runway, so with ARPT on the airport has two lines: the route's at the runway, "runway 08R" or "airport KATL, runway 08R", and the ARPT circle at the airport itself, "airport KATL".
- "heading bug": the MCP heading, a small mark on the compass arc, while it is on the screen.
- "dashed line to the heading bug, 30° right": the dashed line the ND draws from the aircraft to the heading bug, also when the bug itself is off the screen. With PMDG's PFD/ND display option (Glass_PFD_ND, on by default), while LNAV or VOR/LOC is engaged, the line shows only for 10 seconds after you change the MCP heading. It is not drawn in APP or VOR when centred.
- "altitude arc, 11.6 NM ahead": the green arc showing where the aircraft will reach the MCP altitude at its present climb or descent.
- "trend vector, straight ahead, 6.3 NM in 90 seconds": in MAP, above 80 knots, the dashed line the ND draws ahead of the aircraft to show where it will be at its present ground speed: one 30-second piece at ranges 5 and 10, two at 20, three above. In a turn the line curves, and the list says which way, how far the aircraft will have turned by the end of it and the radius of the turn: "trend vector, curving right through 180° in 90 seconds, 2.0 NM radius".
- A VOR you tuned (while its receiver has power), with the course line drawn from it, and the circles and radials you set on the CDU's FIX page. After you press ABEAM on the FIX page, the ND draws a line from the fix to the abeam point on the route, and the fix's line ends "; abeam line to the route at 8.2 NM, 10° left": where that point is. PMDG does not add the point to the route; pressing ABEAM again copies it to the scratchpad.
- "VOR 1 pointer, 34° left": a bearing pointer. With a VOR/ADF switch on VOR or ADF, the ND draws a long pointer across the compass, its head pointing at that station, and the list says where the head points. Pointer 1 is a single line and pointer 2 a double one. A VOR pointer is drawn only while that VOR is tuned and PMDG has its bearing, an ADF pointer while the ADF is receiving a station. The pointers are drawn in APP and VOR too, but not in PLN.
- With POS on: "VOR 1 line toward CAS, R-090, 30° right", a line from the aircraft toward each tuned VOR while the top centre shows its heading or track number, with the radial the ND prints on it ("V1" or "V2" instead on the inboard display's map page); "ADF 2 line, A2, 20° right", a line toward each ADF station received; and "IRS position, 0.2 NM, 30° left" and "GPS position, 0.1 NM, ahead", where the IRS and the GPS each place the aircraft, drawn as a star and a circle. The VOR and ADF lines show regardless of the VOR/ADF switches.
- With STA, WPT or ARPT on: navaids ("VOR/DME CAG", "VOR"; PMDG's ND draws no NDBs or ILS stations), fixes and airports, each kind nearest first. One the edge of the map cuts, with part of its symbol or name still showing, ends in "at the edge": "Map: fix ZMANN, 37.0 NM, 41° left, at the edge". The ND draws a limited number of each; when there are more, it shows EXCESS DATA. It counts the ones the edge hides too, and so does the list.
- With TFC on, in MAP, centred or not: traffic, nearest first, as the ND draws it: "traffic advisory, 6.2 NM, 30° right, +12 climbing". The number is the traffic's height above you (+) or below you (−) in hundreds of feet, the word after it its arrow (climbing or descending). The ND draws other traffic as a hollow diamond, proximate traffic as a filled one, a traffic advisory as an amber circle and a resolution advisory as a red square; the list names them other traffic, proximate traffic, traffic advisory and resolution advisory. Traffic the map's edge cuts ends in "at the edge", as for fixes. A traffic or resolution advisory beyond nine tenths of the range, or too far off the screen for the ND to draw, gives "Message: OFFSCALE". During the TCAS self-test ("Message: TCAS TEST"), once the test pattern appears, the ND draws four test symbols at fixed places instead of the real traffic, one of each kind: two ahead at 3.6 NM and two beside the aircraft at 2.0 NM. The list reads them like any other traffic, for example "other traffic, 3.6 NM, 34° left, +10".
- "TCAS ring, 3 NM": with TFC on, or during the TCAS self-test, at range 80 and below, the ND draws a ring of twelve dots 3 NM round the aircraft, so you can judge how close the traffic is. It is not drawn while the four test symbols show. The list gives it before the traffic.
What the list leaves out. Three pictures on the ND are not described, only whether they are on:
- The weather radar picture (WXR): rain and storms ahead as coloured areas, from green for light rain to red for heavy rain, and magenta for turbulence.
- The terrain picture (TERR): the ground around and ahead of you as coloured areas, by how high it is compared with your aircraft, from green well below you to red at or above your altitude.
- The vertical situation display (the VSD, the CTR button's third press): a side view of the flight ahead along your track, across the bottom of the ND, with your aircraft, the ground under your path, the path you are descending on and an altitude scale.
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:
- "Top right: ILS 1, IATL, CRS 268, DME 12.3": the receiver the picture shows (ILS 1 or ILS 2 in APP, VOR 1 or VOR 2 in VOR), the station's identifier, the selected course and the DME distance. In APP the identifier is shown only for an ILS frequency or an approach from the FMC; with a VOR tuned the ND prints "------" there. In VOR it is the other way round, and a VOR whose identifier has not come in yet shows its frequency, "VOR 1, 113.20". With no DME distance, "DME ---"; a failed DME shows its label in amber in a box, "DME 1 (amber, boxed)". When the ND takes the approach from the FMC instead of the radio, the label is "FMC L".
- "Centre: track line, 4° right, marks at 5, 10 and 15 NM": the track line as in MAP, leaning off the nose by the drift. Centred on the inboard display's map page, the ND draws a small track pointer on the compass instead: "Centre: track pointer, 4° right".
- "Centre: course pointer 268, ahead": the Captain's selected course, and where the pointer's arrowhead points: "ahead", or how many degrees left or right of the top of the screen, "course pointer 081, 2° right". On the localizer in a crosswind, the pointer sits off the top by the angle the aircraft is crabbing.
- "Centre: deviation bar 0.6 dots left": where the localizer or radial is, measured in the dots of the scale across the pointer. The scale has two dots on each side of the centre. A bar left of centre means the localizer is to your left, so you fly left to centre it. In the middle it reads "deviation bar centred", and at the end of its travel, just past the second dot, "deviation bar at full scale, left". While the receiver has nothing usable, the ND draws no bar and the list has no bar line. The line ends in how the bar is drawn: "filled" in APP while the bar is inside the scale, "outlined" in VOR, and in APP once it reaches the last dot.
- "Centre: heading bug, 30° right": the MCP heading, the small mark on the compass, as in MAP, and when not centred "Centre: dashed line to the heading bug, 30° right".
- "Centre: VOR 2 pointer, 34° left": the bearing pointers, as in MAP.
- "Right side: glideslope pointer 1.2 dots below", in APP only: the glideslope scale on the right of the screen, two dots above and two below its centre, and the pointer showing where the glideslope is. A pointer below centre means the glideslope is below you: you are high. It also reads "glideslope pointer centred" and "glideslope pointer at full scale, below". When the ND draws the scale but no pointer, the line is "Right side: glideslope scale, no pointer". A failed glideslope shows the letters G/S in amber in a box instead, "Right side: G/S (amber, boxed)", and BA says "ND message: G/S".
- "Centre: TO" or "Centre: FROM", in VOR only: whether the course you set takes you to the VOR or away from it, printed below and right of the aircraft symbol.
- With TFC on, and not centred, the traffic and the TCAS ring as in MAP: "Centre: TCAS ring, 3 NM", "Centre: traffic advisory, 6.2 NM, 30° right, +12 climbing".
- Two kinds of messages belong to these modes, listed and spoken like the others. "Message: LOC 1" in APP means the localizer receiver has failed, and "Message: VOR 1" in VOR the VOR receiver. "Message: EFIS MODE/NAV FREQ DISAGREE" means the mode does not suit what is tuned: APP with a VOR frequency, or VOR with an ILS frequency.
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:
- Mode: APP, VOR, MAP or PLAN, as on the EFIS panel.
- 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.
- 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".
- 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).
- 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:
- "A/T: MCP SPD", "Roll: VOR/LOC", "Pitch: G/S", "AFDS: CMD": the four columns of the flight mode annunciator. A part with nothing showing reads none, and a mode BA has no word for reads unrecognised. An armed mode follows the active one: "Roll: HDG SEL, armed LNAV". Texts the PFD draws beside the columns have lines of their own: "AUTOPILOT", "CWS P", "CWS R". While BA cannot read the FMA, the four columns are one line saying why: "FMA reader waiting for PMDG SDK data" until PMDG's SDK data arrives (see Before you fly), "FMA reader starting" for the moment it takes BA to find the FMA, or the "FMA announcements stopped" or "unavailable" line with its reason, with the last FMA BA read after "Last known" when its reading stopped matching the aircraft.
- "Above the speed tape: selected speed 150": the MCP speed, or the selected Mach, ".78". V1 shows here too when the V1 bug is off the visible part of the tape, "Above the speed tape: V1 152".
- "Speed tape: 160 knots, trend arrow to 154": the box, and the trend arrow, which points to where the speed is heading.
- The speed tape's bugs, highest first: "15 bug, 157, 3 below" is the flap bug for flaps 15, and "UP bug" the one for flaps up; "selected speed bug" is the MCP speed; "V1 bug", "VR bug"; "REF bug" is the landing reference speed, VREF; "VREF plus 20 bug", "V2 plus 15 bug", "80 knot bug" (100 with PMDG's option) and "speed reference bug" (the one you set with the speed reference selector on BUG) are the white bugs PMDG draws without a label.
- The speed tape's bands: "red and black band from 200 up, 40 above" is the maximum speed, "red and black band from 115 down, 45 below" the stick shaker speed, and "amber bar from 128 down, 32 below" the minimum manoeuvring speed. Stay between them.
- "Below the speed tape: GS 152": the ground speed, or the Mach number once it is above .40, "Mach .445". With the speed reference selector on V1, VR, WT or VREF, what it sets: "V1 152", "WT 147850" (the gross weight, in the aircraft's weight unit), "VREF 142". The landing flaps and VREF from the FMC read "REF 15/142".
- "Attitude: pitch 2.5° up, wings level": the nose's angle above the horizon (down below it), to the nearest half degree, and the bank in whole degrees, "bank 10° left".
- "Attitude: slip indicator, centred": the small mark under the bank scale that shows whether the aircraft is slipping sideways. "slightly left" while PMDG draws it hollow, "left" once it fills in.
- "Attitude: flight director pitch bar, 0.5° above" and "flight director roll bar, centred": the flight director's two bars show which way to steer, and you fly toward them. A pitch bar above means raise the nose; a roll bar "10° right" means bank 10 degrees further right. "at the right edge" is as far as the bar goes. With PMDG's single-cue option the PFD draws one chevron instead, which BA does not read: "flight director, single cue, not read".
- "Attitude: flight path vector, 2.5° below, 1° left", with FPV on: where the aircraft is actually going, compared with where the nose points.
- "Attitude: pitch limit indicator, 11° above": how much more you can raise the nose before the stick shaker, shown at low speed.
- "Attitude: approach info, ICVG/177, DME 4.8": the tuned ILS, its course and the DME distance ("DME, no distance" while there is none), then "approach mode, ILS", or LNAV/VNAV and the like on other approaches. "Attitude: marker beacon, OM" while the outer, middle (MM) or inner (IM) marker is received.
- "Attitude: glideslope pointer, 0.1 dots below" and "localizer pointer, 0.2 dots left": the ILS pointers, in tenths of a dot, as on the ND. A glideslope pointer below means the glideslope is below you: you are high. A localizer pointer left means the localizer is to your left: fly left. "centred" is on it, "at the right edge" full scale.
- "Attitude: radio altitude 1480": the height above the ground, below 2,500 feet. "Attitude: minimums, BARO 1100" or "RADIO 200": the minimums you set.
- In some phases more lines appear: "Attitude: rising runway, 60% risen, 40% left" on the localizer below 2,500 feet, the runway symbol that rises toward the aircraft from 200 feet (0%) to touchdown (100%) and slides sideways with the localizer; "angle of attack 4.2, limit 16.5" with PMDG's angle of attack option; "TCAS zone, from 3° above, upward" during a resolution advisory, the pitch to keep out of; and in LNAV and VNAV the navigation performance scales, "lateral performance scale, RNP 0.30, ANP 0.12" in nautical miles and "vertical performance scale, RNP 400 feet, ANP 148 feet", with their pointers.
- "Above the altitude tape: selected altitude 3000": the MCP altitude.
- "Altitude tape: 2380 feet": the box, as PMDG prints it. Then its bugs: "selected altitude bug, at the top edge", and "minimums bug, 1100, 420 below" once you are within 500 feet of the minimums. Before landing, the landing altitude from the FMC: "hatched band from 650 down, 1730 below", and the "lower landing bar from 650 to 1150" and "upper landing bar from 1150 to 1650", the 500 feet above it.
- "Below the altitude tape: 30.01 IN.": the altimeter setting, "1013 HPA" in hectopascals, or "STD, preselect 1014 HPA" with STD set and a value waiting.
- With MTRS on, the altitudes add metres: "Altitude tape: 2380 feet, 725 metres".
- "Vertical speed: 750 down": the climb or descent rate in feet per minute, as printed from 400; below that, the needle: "needle, 200 up", "needle level". In V/S mode, "selected bug, 1000 down".
- "Heading: 177 MAG" (TRU when true), then "selected heading 180, 3° right", the MCP heading, and "track 175, 2° left", where the aircraft is actually going over the ground.
- "Message: NO VSPD": each message the PFD shows, last. PMDG draws them in different places: NO VSPD (takeoff speeds not set), INVALID ENTRY (a speed reference value the selector cannot set now: VREF on the ground, V1 or VR in the air), SEL SPD, SPD LIM, DSPLY SOURCE and CDS FAULT with the speed tape; PITCH and ROLL in the attitude (the two sides disagree); LDG ALT (no landing altitude), DISPLAYS CONTROL PANEL, INSTR SWITCH (an instrument transfer switch, such as IRS Source on the Display Select panel, is off NORMAL) and ALT DISAGREE with the altitude tape.
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:
- 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.
- 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".
- 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".
- Baro units: IN or HPA.
- Altimeter: type the setting and press Enter, as in the Ctrl+B dialog: "Altimeter: 1013, 29.91".
- 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.
- Speed reference: SET, AUTO, V1, VR, WT, VREF or BUG, the speed reference selector.
- 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):
- Output Shift+1 to Shift+6 read the flap manoeuvring speeds for your current weight — flaps up, 1, 5, 10, 15 and 25 — for example "Flaps 5 maneuver speed 190 knots, calculated". They come from tables measured on the -700 and -800 FMCs; the -600 and -900 borrow those tables, so on those two treat them as estimates.
- Output F / Shift+F read fuel per tank; the other Readout Hotkeys work as usual. Output Ctrl+M opens the PMDG Monitor Manager.
- Output Alt+N opens the Navigation display window and Output Ctrl+W reads the active waypoint as the ND shows it, "EMPAD, 1533.3Z, 6.8 NM".
- Output Alt+P opens the Primary flight display window, whose list starts with the whole flight mode annunciator (FMA).
What BA announces by itself:
- MCP value changes, autopilot mode lights (AP, A/T, LNAV, VNAV, LVL CHG, HDG SEL, VS, ALT HOLD, VOR/LOC, APP) and the MCP switches and knobs. Everything BA says by itself about the MCP starts with "MCP:", for example "MCP: speed 250 knots", "MCP: Level Change: engaged", "MCP: VOR/LOC: armed", "MCP: Flight Director Captain: On", "MCP: Bank Limit: 25" and "MCP: Course Captain: 223". The output mode readouts (Shift+H and so on) keep their own wording.
- The flight mode annunciator. Every change at the top of the PFD, starting with "FMA:" and then in Boeing's wording: A/T: N1, Roll: VOR/LOC, Roll armed: VOR/LOC, Pitch: G/S, AFDS: SINGLE CH. Changes that happen together come as one sentence, such as "FMA: Roll: VOR/LOC, Pitch: G/S, AFDS: SINGLE CH", so you hear localizer and glideslope capture as they happen. An armed mode that becomes active is said once, as the active mode, and a part that goes blank is said as none, for example "FMA: Pitch armed: none". A mode BA has no word for is said as unrecognised, for example "FMA: Roll: unrecognised" when TO/GA is pressed for a go-around, so a change is never silent. The MCP lights in the item above are still announced, starting with "MCP:". You hear both, and neither cuts the other off; the FMA often comes first, because BA learns of an FMA change a moment before PMDG reports the MCP light. BA reads the FMA only while PMDG's SDK data is arriving (see Before you fly). To silence it, mute Flight Mode Annunciator in Ctrl+M: that silences the FMA announcements and BA's own FMA messages in the next three items, while the Primary flight display window still lists the FMA.
- If BA cannot read the FMA, it says "FMA announcements unavailable" and the reason, once, and the FMA line of the Primary flight display window then gives the same reason. When the reason is that it cannot find the FMA in the aircraft's memory, or that what it finds does not match the aircraft, BA keeps looking for two minutes before it says so, then keeps trying every 30 seconds, for example through a long loading screen, and says "FMA announcements resumed" if it finds the FMA. Any other reason is said as soon as BA knows it, for example "no access to the simulator"; BA then does not try again until you load a new flight or select the 737 again. If BA cannot load its display files, you hear one line for all four displays instead, described below.
- If BA loses the FMA during a flight for more than a few seconds, it says "FMA announcements stopped" and the reason, and keeps trying. When it reads the FMA again you hear "FMA announcements resumed", followed by any mode change you missed, for example "FMA announcements resumed, Roll: VOR/LOC, Pitch: G/S". A change during a shorter gap is announced as usual once BA reads the FMA again. The one exception is "FMA announcements stopped: unexpected values": BA then waits until you load a new flight or select the 737 again.
- The engine displays. What appears on and goes from the two engine displays, in their own words, starting with the display it is on: "Upper DU alert: engine 1 START VALVE OPEN", "Upper DU alert gone: engine 1 LOW OIL PRESSURE", "Upper DU alert: fuel CONFIG", "Upper DU alert: tank 1 fuel LOW", "Lower DU alert: engine 2 X-BLD START", "Upper DU alert: NO AUTOLAND". Gauge colours: "Upper DU: engine 1 EGT amber", then red or normal; vibration above its limit is high. The thrust mode: "Upper DU: thrust mode CLB". Things that change together come as one line, and nothing interrupts anything else. When ENG PRI has moved the engine page down, the lines start with "Lower DU". BA says nothing while the displays are dark, and nothing for the first few seconds after they come on, so powering up is quiet. Each kind has its own row in Ctrl+M: Engine display alerts (which also silences BA's own "Engine display announcements stopped", "unavailable" and "resumed" messages, which work like the FMA's above), Engine gauge colors and Thrust mode.
- The navigation display. Its messages as they appear and go, "ND message: TCAS OFF", "ND message gone: TCAS OFF", and the active waypoint when it changes, "ND: PT753, 23.0 NM" ("ND: no active waypoint" when the route ends or is deleted); see the Navigation display window. Nothing interrupts anything else, and it is quiet while the displays are dark and for the first few seconds after they come on. Mute ND messages in Ctrl+M to silence all of it, BA's own "ND announcements stopped", "unavailable" and "resumed" messages included.
- The primary flight display. Its messages as they appear and go, "PFD message: ALT DISAGREE", "PFD message gone: ALT DISAGREE", including the flags that replace an instrument, "PFD message: SPD"; WINDSHEAR and PULL UP are left to the aircraft's own callouts. See the Primary flight display window. It 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 it, BA's own "PFD announcements stopped", "unavailable" and "resumed" messages included.
- When BA cannot load its display files. BA reads the FMA, the engine displays, the ND and the PFD through files made for each version of PMDG's 737. If it cannot load them, for example after a PMDG update, until a BA update brings the files for the new version, you hear one line for all four, soon after the 737 loads: "PMDG display files could not be loaded; the display keys fall back to AI reading." Alt+E, Alt+N and Alt+P then describe the displays with AI. You hear the line once each time you select the 737 or start BA, and not again when you load a new flight. Muting one of the four rows in Ctrl+M (Flight Mode Annunciator, Engine display alerts, ND messages, PFD messages) leaves the line to the others; it is silent only with all four muted.
- In MSFS 2020. BA reads the FMA, the engine displays, the ND and the PFD in MSFS 2020 as well, from files made for PMDG's MSFS 2020 version of the 737.
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. |
- If you load a new flight after BA said "FMA announcements stopped", or "unavailable" because it could not find the FMA, you hear "FMA announcements resumed" when BA reads the new flight's FMA. The new flight's modes are not read out as changes; the Primary flight display window (Output Alt+P) lists them.
- "MCP: overspeed" or "MCP: underspeed" when the MCP speed window starts flashing because the selected speed is beyond a limit, and "MCP: powered" or "MCP: unpowered" when the MCP gains or loses power.
- The pressurisation panel's flight and landing altitudes when they change, for example "Flight altitude 35000 feet".
- Master Warning and Master Caution, the fire warnings ("Fire warning Captain"), and each caution group of the six-pack recall ("Hydraulics caution", "Fuel caution" and so on). Annunciator lights are announced both on and off.
- FMC V-speeds as they are entered: "V1 142 knots", "VR 145 knots", "V2 150 knots", and "Cruise altitude 35000 feet".
- Stabiliser trim in units ("Trim 5.3") and the speed brake where the lever comes to rest; see Trim and Speed brake.
- Flap position changes, gear, the APU starting and stopping, IRS alignment, altimeter changes, the 1,000-foot altitude crossings, COM frequency changes ("COM1 standby 121.500") and squawk changes ("Squawk 1200").
Things to know
- Right after loading, before PMDG's first data arrives, a switch may say "Switch not ready, please try again in a moment." and some readouts show "--". Wait a few seconds.
- The fire handles cannot be pulled unless there is a fire warning for that engine or the APU. PMDG locks them, just as the real aircraft does, so a press without a fire does nothing.
- A speed brake lever resting just short of Armed is not armed, and BA says "Speed brake down" — check you have it fully in the detent.
- The 737 ignores the simulator's own speed brake key binding; use the Control Stand combo or a hardware lever.
- Seats themselves do not move on the PMDG 737; only the headrests, armrests and jumpseat do.
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:
- Overhead: Electrical, ADIRU, Hydraulic, Fuel, Engines, Bleed Air, Air Conditioning, Pressurization, Anti-Ice, Fire, Lights, Signs, Oxygen, Wipers, Panel Lighting.
- Overhead Maintenance: Flight Controls, Backup Systems, EEC/APU Maintenance.
- Glareshield: EFIS Captain, EFIS First Officer, MCP, Display Select Panel.
- Forward Panel: Landing Gear, Brakes, GPWS, Instruments.
- Pedestal: Control Stand, Transponder/TCAS, Evacuation, Warning, Engine Fire, Radio, Calls, Boris Audio Works.
- Cockpit: Captain Seat, First Officer Seat, Windows and Shades, Doors and Tables.
- Displays: System Display.
Things that help when you are finding your way:
- Overhead controls are named by position, not number, so a warning tells you which side it means: "Left Forward Pump", not "Forward Pump 1". The hydraulic Center system's pumps read Center 1 and Center 2, because they are not a left and right pair.
- The Brakes panel's autobrake selector has eight positions: RTO, OFF, DISARM, 1, 2, 3, 4 and MAX AUTO. (Unlike the 737, the 777 has a DISARM detent.)
- The Control Stand has the Speed Brake combo: Down, Armed, 50 percent and Up (full).
- On the Air Conditioning panel, the flight deck and cabin temperature knobs are stepped lists. The four cargo temperature knobs only work on the 777F, and the cabin knob does nothing on the freighter, so BA hides the knobs that do not apply to your variant.
- The Cockpit section has the armrests, sun visors, shoulder heaters, worktables, window shades, cockpit and crew-rest doors, the cockpit curtain and the sliding windows. Choosing Open on a sliding window unlocks the handle and moves the clipboard aside for you first. The seats themselves cannot be adjusted on the PMDG 777.
- Boris Audio Works holds the sound pack's controls, including its Hydraulic Pump Model.
Autopilot: the MCP windows
All in input mode:
- Input Ctrl+H opens MCP Heading (0 to 359), with Intervene, Mode (HDG or TRK), LNAV and Heading Hold.
- Input Ctrl+S opens MCP Speed (knots 100 to 399, or Mach M0.00 to M0.99), with Intervene and Mode (IAS or Mach).
- Input Ctrl+A opens MCP Altitude (0 to 45000), with Intervene, VNAV, Level Change and Altitude Hold.
- Input Ctrl+V opens MCP Vertical Speed, which takes vertical speed (-8000 to 6000 feet per minute) or flight path angle (-9.9 to 9.9 degrees) depending on the Mode button (V/S or FPA). The Engage button turns the mode on; the value box only works once it is engaged.
- Input Ctrl+P opens the 777 Autopilot window: AP Left (Alt+A), AP Right (Alt+R), F/D Left and Right, A/T Arm Left and Right, Approach (Alt+P), LOC (Alt+O), A/T, Disengage Bar, A/P Disconnect, A/T Disconnect and Bank Limit (Alt+L).
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.
- Open the Displays section (Ctrl+1) and the System Display panel (Ctrl+2).
- Choose a page in the System Display Page list: Engine, Status, Electrical, Hydraulics, Fuel, Air, Doors, Gear or Flight Controls.
- 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:
- Engine: N1, N2, EGT, fuel flow, oil pressure, temperature and quantity, vibration and fuel used, for each engine.
- Status: gross weight, centre of gravity, total and outside air temperature, whether the IRS is aligned, and the APU.
- Electrical: main bus, battery and generator voltages.
- Hydraulics: left, center and right system pressures and reservoir levels, and system integrity.
- Fuel: total fuel and the left, center and right tanks.
- Air: cabin altitude, cabin climb rate, differential pressure and duct pressures.
- Doors: every entry door, the cargo doors and the access doors — open, closed, closed and armed, opening or closing.
- Gear: each gear leg and the brake accumulator pressure.
- Flight Controls: aileron, elevator and rudder, the trims (elevator trim in units), flap angle and spoilers.
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
- Output Shift+1 to Shift+5 read the flap manoeuvring speeds for flaps up, 1, 5, 15 and 20 at your current weight. They come from each variant's own FMC tables; between the weights measured they are estimates.
- Output Alt+P, Alt+N, Alt+E, Alt+S, Alt+I describe the PFD, navigation display, upper EICAS, lower display and standby by AI vision, moving the camera for you as on the 737. Alt+S names which page the lower display shows first. (Oil pressure, oil quantity and vibration are also on the Engine page of the System Display, with no AI needed.)
- Output Ctrl+M opens the PMDG Monitor Manager.
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
- The SDK setup must include the center CDU line, or the Center CDU stays blank.
- Before the first data arrives, readouts show "--" rather than zeros, so you will never hear "every door open" just because the data has not loaded yet.
- The speed brake lever takes about ten seconds to travel from end to end. BA waits until it stops and announces once.
- The landing altitude knob on the pressurisation panel is deliberately not offered: the aircraft does not report what it is set to.
- Fire handles, as on the 737, only move when there is a fire.
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
- Overhead: Electrical, IRS, Hydraulics, Fuel, Bleed Air, Air Conditioning, Pressurization, Cooling, Anti-Ice, Signs, Flight Controls, Engines, Fire Protection, Cargo Fire.
- Glareshield: EFIS, MCP, HUD, FMC Status, Annunciators, Warnings, Fire.
- Pedestal: Radio, Transponder, Landing, Lighting, Options.
- Ground Services: Doors, Services.
- Flight Data: VNAV, LNAV and Progress, Glidepath, Engine Data, Flight Control Inputs, Timers, Other Data.
Some highlights:
- IRS has the two IRS knobs and the air data source switches, and its status display shows the alignment state and IRS Time To Align (min).
- EFIS shows the barometric setting in both units, for example "1013 hPa (29.92 inHg)".
- Warnings has the Master Caution and Master Warning reset buttons, each labelled with whether that warning is on.
- Transponder has the mode, a squawk field and an Ident button.
- Landing has the parking brake, autobrake (Off, RTO, 1, 2, 3, 4 and MAX), anti-skid, flap handle and gear handle.
- Options has the SATCOM, V-Bar and EFB power switches; Doors has every door, both cargo doors and the flight deck door power; Services has the refuel door and the GPU.
- The Flight Data panels are read-only status displays — VNAV and LNAV data, glidepath, engine data, timers and more. Press Ctrl+3 on any of them to read the values.
Autopilot: the MCP windows
All in input mode:
- Input Ctrl+H opens MCP Heading, with LNAV, Heading Hold and HDG / TRK.
- Input Ctrl+S opens MCP Speed (knots 100 to 399, or Mach 0.40 to 0.99), with Mode (IAS or Mach), FLCH and Speed INTV (shows Manual or FMC).
- Input Ctrl+A opens MCP Altitude (0 to 45000 feet), with VNAV, Level Change, Altitude Hold and Alt INTV.
- Input Ctrl+V opens MCP Vertical Speed, taking vertical speed (-6000 to 6000 feet per minute) or flight path angle (-9.9 to 9.9 degrees), with Engage V/S, V/S FPA (the mode) and Approach, which shows GS Active, LOC Active, Armed or Off. In V/S mode, a tiny number such as -2.5 is refused with "V/S must be 0 or at least 50 fpm; for an angle, switch the mode to FPA".
- Input Ctrl+B opens the Altimeter window. Type the QNH in hectopascals (900 to 1100); a Standard (STD) button sets 29.92.
- Input Ctrl+P opens the 787 Autopilot window: A/P, Autothrottle, LNAV, VNAV, Approach, Level Change, ALT Hold, HDG Hold, V/S and A/P Disconnect. A/P Disconnect always disconnects, unlike the A/P button, which toggles. BA announces "Approach armed" and "Approach disengaged".
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:
- Ctrl+Enter for EXEC (Alt+E also works).
- Backspace is CLR when there is text and DEL when the scratchpad is empty; Ctrl+Backspace clears the whole scratchpad at once.
- Page keys: 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+N NAV/RAD.
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:
- Output Alt+E opens the 787 EICAS window: each engine's N1, EGT, N2, oil pressure and oil temperature, total fuel, gross weight and TAT, then every active warning, caution and advisory. Arrow through it; it updates live; Escape closes it. BA does not read out each alert as it appears, but Master Caution and Master Warning are announced the moment something posts, so you know to press Alt+E.
- Output Alt+S opens the 787 System Synoptic Display window, a live text version of the lower display's system pages (hydraulics, electrics, fuel, air, APU, oxygen and status messages). F5 refreshes it; Escape closes it.
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
- Output D reads the distance to destination with the estimated time en route; Shift+D the distance to top of descent, or "Top of descent not available" if the FMS has not computed one.
- Output Ctrl+M opens the 787 Monitor Manager, listing everything the 787 announces by itself.
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
- IRS alignment takes real time. After you turn the IRS knobs on, BA says "IRS aligning" and the IRS panel shows the minutes left; when it finishes you hear "IRS aligned". Plan for several minutes on the ground before you can fly.
- Some switches seem to "snap back" only because the engines are running: a running engine keeps its generator and bleed on, and refuelling will not connect. That is correct aircraft behaviour.
- The Light Master, forward cooling and HUD auto-brightness switches are automatic on this aircraft; BA reports their real state.
- If engine or hydraulic readouts look dead, check you are not in a failure state, such as running out of fuel. The 787 shows failures faithfully.
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
- You do not need MobiFlight or any other add-on. Everything goes through the iFly plugin that runs with the aircraft.
- The aircraft must be loaded in the simulator before the panels, MCP windows and FMC window have any data. If BA cannot see it, you hear "iFly 737 not detected."; if the plugin stops answering, "iFly plugin not responding."
- The EFB is served by iFly's own EFB program. It must be running, and it uses port 8084 unless you have changed it in your iFly installation (if so, the port in BA's settings file must match).
How the panels are organised
- Overhead: Electrical, Fuel, Hydraulics, Air Systems, Pressurization, Anti-Ice, Engines and APU, Exterior Lights, Interior Lights, Signs, Oxygen, Flight Controls, IRS, Flight Recorder and Warning.
- Glareshield: MCP, EFIS Captain, EFIS First Officer, Warnings.
- Forward Panel: Landing Gear, Autobrake, Display Select, GPWS.
- Pedestal: Radios, Audio Control, Transponder, Fire Protection, Cargo Fire, Trim, Control Stand, Door Lock.
- FMS: FMS Data.
Highlights:
- The MCP panel carries every mode button — CMD A and B, CWS A and B, both flight directors, autothrottle arm, TOGA, the disconnects, the disengage bar, SPD INTV and ALT INTV — each reading Engaged or Off, plus fields for the courses, heading, altitude and vertical speed.
- Radios shows active and standby for all three radio tuning panels, with Set Standby Frequency fields (type, for example, 121.950) and Transfer buttons. It also has both NAV panels (type a VOR or ILS frequency, or a five-digit GLS channel) and both ADF panels (190.0 to 1750.0 kHz, tuned live; ADF has no transfer button). Every frequency is read back as the aircraft actually accepted it.
- Audio Control has one group per unit — Captain, First Officer and Overhead — with a microphone selector for each radio source and a receiver switch and volume (0 Min to 6 Max) for each source you can listen to.
- Transponder has a Set Squawk Code field and an Ident button.
- Control Stand has the Speed Brake lever: Down, Armed, Flight detent and Fully deployed.
- Fuel includes the refuelling panel's valves.
- FMS Data shows what the FMC has computed: V1, VR, V2, VREF, takeoff and landing flaps, cruise altitude, transition altitude and level, and the full flap speed schedule.
- Door lights are not on a panel; they announce when they come on or go off.
Autopilot: the MCP windows
All in input mode:
- Input Ctrl+S sets the MCP speed: type knots (250) or Mach (M0.78 or .78). Buttons: Speed Intervene, IAS/Mach changeover, N1 mode, Speed mode.
- Input Ctrl+H sets the heading. Buttons: Heading Select, LNAV, VOR LOC, Approach, Bank Limit.
- Input Ctrl+A sets the altitude. Buttons: Altitude Hold, Altitude Intervene, VNAV, Level Change.
- Input Ctrl+V sets vertical speed (-7900 to 6000). Buttons: VS mode, Altitude Hold.
- Input Ctrl+B sets the altimeter for both altimeters, with Standard (STD) and Units (inches or hectopascals) buttons.
- Input Ctrl+N sets the NAV radios: NAV 1 and NAV 2 frequency and course, pre-filled. BA keys each frequency on the NAV panel, transfers it to active and sets the MCP courses. Read them back with Output N, for example "NAV 1 active 110.90 ILS".
- Input Ctrl+P opens the 737 Autopilot window, with live-state buttons for CMD A, CMD B, CWS A, CWS B, F/D Captain, F/D First Officer, A/T Arm, the Disengage Bar and Bank Limit, plus A/P Disconnect and A/T Disconnect.
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).
- Arrow keys read the screen. Type in the Scratchpad box (Alt+S) and press Enter to send; the entry is read back once you stop typing.
- Ctrl+1 to 6 and Alt+1 to 6 are the line select keys, or F1 to F12 with the alternate setting in FMC Settings, which applies here too.
- Page keys: Alt+I INIT REF, Alt+R RTE, Alt+A or Alt+D DEP ARR, Alt+T ATC, Alt+V VNAV, Alt+F FIX, Alt+G or Alt+L LEGS, Alt+H HOLD, Alt+O FMC COMM, Alt+P PROG, Alt+M MENU, Alt+N N1 LIMIT. Page Up and Page Down are PREV and NEXT PAGE.
- Alt+E or Ctrl+Enter is EXEC. Alt+C (or Backspace on the display) is CLR when there is text and DEL when it is empty; Delete or Alt+X is DEL. Alt+Home goes to the display; Escape closes.
- The EXEC light and the message light announce by themselves: "EXEC light on", "FMC message".
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
- Output D / Shift+D read the distance to destination and to top of descent from the FMC PROG page, with time estimates. If neither CDU is showing PROG, BA switches the First Officer's CDU to it (and leaves it there); the Captain's CDU is never touched.
- Output Shift+1 to Shift+6 read the flap manoeuvring speeds (up, 1, 5, 10, 15, 25). The iFly does not publish its speed-tape flap bugs, so BA calculates these from your gross weight using Boeing's schedule; expect them within a few knots of the drawn bugs.
- Output Alt+P, Alt+N, Alt+I, Alt+E describe the PFD, navigation display, standby and the engine and alert display by AI vision, moving the camera for you.
- Output Shift+C opens the iFly 737 MAX8 First Officer, with its flows and normal-procedures checklists.
- Output Ctrl+M opens the iFly 737 Monitor Manager.
What BA says by itself:
- On the takeoff roll, "V1", "Rotate" and "V2" as you reach the FMC speeds (the iFly plays no callouts of its own); see Takeoff Speed Callouts. Muting V1, VR or V2 in Ctrl+M silences both its entry announcement and its roll callout.
- V-speeds as they are entered in the FMC: "V1 142 knots".
- Stabiliser trim in units ("Trim 5.3") and the speed brake where it comes to rest, as on the PMDG 737.
- Annunciators when they come on, and off once they have stayed off for two seconds. The A/P and A/T disengage lights include their colour. Nothing is announced while the master lights test is held.
- The parking brake, COM and squawk changes, and engine bowed-rotor motoring during start.
Things to know
- The squawk code, radio frequencies and MCP windows read back what the aircraft actually accepted; a different value from the one you typed means the aircraft changed it.
- Guarded switches (stabiliser trim cutouts, nose wheel steering, GPWS inhibits, flight spoilers) are pushed through their guard for you.
- The navigation display range is a pair of increase and decrease buttons, matching the real knob.
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:
- BBS Nest, BlueBird's companion app. Without it the cockpit takes every switch, but no system responds. About a second after BA connects, after you switch to this profile or after you load a flight, BA checks for it. If it is missing you hear "BBS Nest is not running. The 757's systems will not respond until it runs and the flight is reloaded." Start BBS Nest, then reload the flight.
- The MobiFlight WASM module (see Installing). BA sets every switch by replaying the cockpit's own click through it. Without it, readouts still work, but each control you try says it is unavailable, and a short while after connecting you may hear "MobiFlight calculator path unavailable. Some cockpit controls may not respond." Install or reinstall the module and restart 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:
- Overhead: Electrical, APU, IRS, CVR, Emergency lights and passenger oxygen, Window heat, Pressurization, Hydraulics, Fuel, Passenger signs, Exterior lights, Air conditioning and bleed, SELCAL and cabin call, Electronic engine control (RR), Yaw dampers, Panel lighting, Ram air turbine and engine limiters, Anti-ice, Wipers, Equipment cooling, Indicator lights and door lock.
- Glareshield: MCP, VOR/DME, Master warning and caution.
- Forward panel: Brakes; Caution, config and G/S inhibit; Landing gear; Captain foot and shoulder heat; Captain instrument source selectors; Heading reference; Thrust mode select; Alternate flaps; Ground proximity overrides; First officer instrument source selectors; First officer foot and shoulder heat; Yokes; Captain autoland status; Standby instruments; Captain DDRMI; Captain chronometer; First officer autoland status; First officer DDRMI; First officer chronometer.
- Pedestal: Control stand, Engines, TCAS and transponder, COM radios, Radio tuning panel 1, Audio panel 1, Radio tuning panel 2, Radio tuning panel 3, Audio panel 2, ILS tuning, Fire protection, Stabilizer trim, Rudder and aileron trim, EICAS control, Captain EFIS, First officer EFIS, CDU brightness, Weather radar.
- Other: P61 panel, Oxygen, Flight deck door, Forward attendant panel, Windows and sun visors, Seats and stowage.
- Status: one panel to read rather than operate. Press Ctrl+3 to read the APU state, Master Warning and Master Caution, the left and right AC bus power sources, the APU speed, the cabin altitude, the chocks ("In place" or "Removed"), the flaps (the lever's position and the flap angle), the gear, the speedbrake, the parking brake and the two lines of the autoland status annunciator.
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:
- Electrical starts with the Battery (its guard first), EXT PWR and STBY Power. Its status display (Ctrl+3) shows whether external power is on and available, and whether ground power is connected.
- Engines on the Pedestal is where you start and stop the engines: Ignition, then for each engine its start selector (GND, AUTO, OFF, CONT, FLT) and its fuel control switch. Its status display shows N1, N2, EGT, fuel flow and EPR for each engine and the two start valves, so you start an engine without leaving the panel: press Ctrl+3 to jump to the values, which update live while you read them. While you are on a switch they pause; F5 or Ctrl+3 brings them up to date.
- Control stand has the Parking Brake, the Flap Lever (UP, 1, 5, 15, 20, 25, 30), the Speedbrake Armed, Speedbrake Down and Speedbrake Up buttons, TO/GA and A/T Disconnect. About a second and a half after a speedbrake button you hear where the lever is, for example "Speedbrake armed".
- Landing gear has the Gear Lever with its three positions, UP, OFF and DOWN. OFF is the position you select after the gear is up.
- Pressurization starts with a Landing Altitude box: type the destination's elevation in feet and press Enter. BA reads back what the panel took, rounded to 10 feet, for example "Landing altitude 1030 feet". The 757 has no cruise altitude selector here: the FMC's cruise level is on the CDU. With Mode Select on MAN, the Climb Cabin 1 s and Descend Cabin 1 s buttons hold the manual switch for a second and say the outflow valve, for example "Outflow valve 87 percent open"; in another mode they say "Set the pressurization mode to MAN first".
- TCAS and transponder starts with TCAS Mode and has a Squawk Code box right after it: type the four digits and press Enter. About a second and a half later BA reads the transponder back and says "Squawk 4743"; if the transponder holds another code it says so. An empty box says "Type a four-digit squawk first.", and letters or a digit 8 or 9 say "Squawk must be four digits, each 0 to 7."
- COM radios has, for each of COM1, COM2 and COM3, a standby frequency box and a transfer button. COM1 is the aircraft's VHF L, COM2 VHF C and COM3 VHF R. Type a frequency such as 121.5 and press Enter, and BA reads it back: "COM1 standby 121.500". The transfer button says both: "COM1 active 121.500, standby 124.850". The status display lists all six frequencies.
- MCP on the Glareshield starts with the two flight directors and A/T Arm, then the mode and CMD buttons, the Bank Limit selector and the Autopilot Disengage Bar. Its status display lists the light of every mode and CMD button ("CMD L: On"). Set its four values with the MCP windows.
- Stabilizer trim and Rudder and aileron trim hold the spring-loaded trim switches as buttons, such as Left Rudder Trim 1 s or Nose Up Stab Trim 1 s. Each press holds the switch for one second, releases it and says the result: "Rudder trim 0.9 units right", "Aileron trim centered". The stabilizer trim is spoken by the usual trim callout while it moves.
- Fire protection lists each fire handle before its tests: an Unlock button, the handle (In or Pulled) and its Rotation (Left, Center, Right) for engine 1, engine 2 and the APU. Picking Pulled pulls the handle. As in the cockpit, a handle pulls only while its fire light is on or it has been unlocked, and with the rotation at Center; otherwise the list goes back to In. Without a fire warning, press the handle's Unlock button first. The handle locks again a second and a half later, so move to the handle and pick Pulled straight away.
- The cockpit tests are buttons that BA holds for as long as the cockpit needs; listen for the aircraft's own sound while one is held. The P61 panel's tests, such as Takeoff Config Test 3 s or Ground Proximity Test 3 s, are held for three seconds and then say, for example, "Takeoff config test done". The tests on the other panels, such as Engine Fire Test on Fire protection or TCAS Test on TCAS and transponder, are held the same way and say "
pressed" . Lamp Test, on Indicator lights and door lock, switches on and off with each press and says "Lamp test on" or "Lamp test off". - Captain EFIS, First officer EFIS, EICAS control and CDU brightness hold the brightness of the displays (Minimum, Half, Full).
- Windows and sun visors and Seats and stowage, in the Other section, are for comfort and immersion: both side windows, the sun visors and their positions, the four window shades, both seats forward or aft, the armrests and headrests, the jumpseats, the chart holders, the floor box and the stowage doors.
How the controls behave:
- Each control is named as on the aircraft, and a switch, knob or selector is a list of its positions. Arrow to the position you want. BA waits a moment after you stop on a row and sets only that one, so arrowing through a list does not step the switch through every position on the way.
- A list moves back if the aircraft did not take the change. About a second and a half after a write, BA reads the control again, and the list shows where the switch really is. A switch behind a closed guard, or one the aircraft refuses, therefore jumps back to its real position, and your screen reader reads it.
- Guards are their own rows. A guarded switch, such as the Battery or Altn Gear, has a guard row beside it (Closed or Open): open the guard, then use the switch. For three switches BA works the guard for you: Emergency Lights and the two Stab Trim Cutout switches. Pick the position you want and BA opens the guard first, and closes it again when you pick ARMED or NORMAL. If the switch did not follow you hear, for example, "Emergency Lights did not move".
- Buttons say "pressed", or what they did. A button with no state of its own is pressed, held for as long as the aircraft needs and released, and you then hear "
pressed" . An MCP mode or CMD button instead says its light about a second and a half later, for example "CMD R on" or "LNAV off", EXT PWR says "EXT PWR on" or "EXT PWR off", and a speedbrake button says the lever. - A control BA cannot write says so. You hear "
unavailable" and nothing is sent. This happens when the MobiFlight module is missing, or when BA cannot read where the control is now.
Autopilot: the MCP windows
All in input mode:
- Input Ctrl+H opens MCP Heading (0 to 360; 360 is north), with HDG SEL (Alt+S), HDG HOLD (Alt+H) and LNAV (Alt+L) buttons.
- Input Ctrl+S opens MCP Speed (100 to 399 knots, or Mach 0.40 to 0.86), with Speed Intervene (Alt+I), IAS/MACH (Alt+M), SPD (Alt+S), THR (Alt+T) and FLCH (Alt+L) buttons.
- Input Ctrl+A opens MCP Altitude (100 to 49000 feet, rounded to 100), with ALT HOLD (Alt+H), VNAV (Alt+V) and FLCH (Alt+L) buttons.
- Input Ctrl+V opens MCP Vertical Speed (minus 8000 to 6000 feet per minute, rounded to 100), with a V/S button (Alt+V).
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:
- Altimeter box: type inches (29.92) or hectopascals (1013) and press Enter. All three altimeters are set together. They take a few seconds to follow; BA then reads them back, for example "Altimeter: 1018, 30.05" or "Altimeter standard". If they still differ, each is read: "Altimeter 1: …, Altimeter 2: …, Altimeter 3: …". Typing 29.92 or 1013 sets standard, the same as the Standard button.
- Standard, 29.92 button: sets all three to standard.
- Radio minimums box: type the decision height in feet (0 to 2500; it moves in steps of 10) and press Enter. BA steps the minimums and reads back what the ADI shows, for example "DH 200".
- Status box: read-only, with the values when the window opens and the last result.
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:
- Status box, where the window opens. BA reads the radios and speaks them once: the VORs, the ILS course and frequency, and the ILS of the FMC's runway for reference, for example "FMC runway ILS KATL 09L, 110.50, IHZK, front course 095". It names the airport because, on the ground, the FMC shows the departure runway's ILS.
- ILS course box (Alt+I): type the course, 0 to 360, and press Enter. You hear, for example, "ILS course 095".
- ILS frequency box (Alt+F): type the frequency, 108.10 to 111.95, and press Enter. BA turns the panel's knobs for you, one click at a time, then says what the panel shows: "ILS 110.50 set", or "ILS already 110.50". If the panel ends on another frequency you hear both, "ILS shows 110.55, not 110.50"; press Enter again.
- ILS park button (Alt+P): parks the ILS panel, as after landing: "ILS parked".
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.
- The display is a list. Up and Down arrow read it line by line, as on the other Boeings: "Title:" and the page title first; then, for each of the six line select keys, the small label line and the line itself, starting with its number ("3:" is line 3); and "Scratchpad:" last. A screen with nothing on it says so, for example "Captain CDU screen blank".
- Line select keys: Ctrl+1 to Ctrl+6 are the left keys, Alt+1 to Alt+6 the right keys. If Alternate line select keys is ticked, they are F1 to F6 and F7 to F12. That setting is in File, FMC Settings, which the 757's File menu does not show, so change it while another aircraft is selected.
- Page keys: Alt+I INIT REF, Alt+R RTE, Alt+D DEP ARR, Alt+T ATC, 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.
- Page Up and Page Down (or Alt+Up and Alt+Down) are PREV and NEXT page. Ctrl+Enter or Alt+E is EXEC.
- Alt+S jumps to the Scratchpad box. Type your entry and press Enter; BA sends it to the CDU one key at a time. Alt+Home returns you to the display.
- Backspace is CLR and Delete is DEL, on the display or in an empty scratchpad box. CLR deletes one character or clears a message. Alt+C clears the whole scratchpad. Typing "-" presses the +/- key once and "+" presses it twice.
- Every key is also a button in the window. Escape closes the window.
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:
- 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.
- Press Alt+R for RTE, then REQUEST SEND (Ctrl+3). Within about 15 seconds the page says "ROUTE 1 UPLINK READY".
- 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:
- A question from BlueBird, when one is waiting, with its answer buttons.
- The tablet page itself, with its sections as headings and every value with its label.
- 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.
- A Sections heading: the side menu of the app you are in. The one you are on ends in "(current page)".
- 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:
- Buttons, tiles and tabs are buttons, named in the tablet's words; one with a label reads the label first, for example "Left FWD: Open". The current tab ends in "(current)".
- Switches are check boxes.
- A setting with two choices, such as Nosewheel steering (Realistic or Rudder), is a list of the two. The tablet's own drop-downs are lists too. As on the panels, arrowing through a list chooses only the entry you stop on.
- Sliders are a list of their steps, or a slider from 0 to 100.
- Text boxes are edit boxes. Type, then press Enter: BA types it on the tablet's own keyboard and reads the box back, for example "Airport: KATL". Leaving a box without Enter changes nothing on the tablet, and you hear "
not changed" . - A value box, such as the fuel quantity, is a button. Pressing it opens BlueBird's entry dialog as a question at the top of the page: type in its edit box, press Enter, then press the dialog's own button to confirm.
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 "
A few things can be in the way, and BA then presses nothing and says why: "
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:
- Set your SimBrief ID once (see BlueBird's settings, or the Settings app's AIRAC data page on the tablet).
- On the Navigation app's ACARS dashboard, press Fetch SIMBRIEF OFP. If BlueBird asks about the weight units, answer it.
- 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:
- "Fueling complete. Fuel 16340 pounds: left 8170, right 8170, center 0."
- "Boarding complete. Passengers 21090 pounds. Cargo 3990 pounds: forward 3990, aft 0." When the plan has more passengers than the 757 has seats, you also hear that they were capped and the rest of the payload goes in the holds.
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.
- Sign in to Navigraph, a button BA adds to the page while you are signed out: BA reads the sign-in code letter by letter ("Navigraph code …. The sign-in page opens in your browser in a moment.") and a few seconds later opens Navigraph's sign-in page in your browser, only ever a navigraph.com address. The code stays on the page as "Navigraph code: …". If BlueBird has no code ready you hear "No Navigraph sign-in code is waiting yet. Try again in a minute."
- Latest cycle: Update is BlueBird's own button for installing the newest cycle. After you press it BA watches the installed cycle and says "Nav data cycle 2611 installed. Reload the flight to use it.", or "The update did not finish. Try again after reloading the flight." Reload before you fly: BlueBird looks for a new cycle only when a flight loads, and the aircraft misbehaves on newly installed data until you reload.
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:
- A check box, a list or a slider is saved as soon as you change it.
- A box is saved when you press Enter, and you hear "
saved" . Leaving it without Enter puts the stored value back: "not saved" . - If something cannot be saved you hear "Couldn't save
:" and the reason.
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
- "The BlueBird tablet could not be read: aircraft memory not found. Is the 757 loaded? Press F5 to try again.": the aircraft is not loaded yet, or BA is not connected. The window keeps trying by itself.
- "The BlueBird tablet could not be read: BlueBird file not recognised. This copy of MSFS Blind Assist cannot read this version of the 757; check for an update.": BA reads the tablet through files made for each version of BlueBird's 757. After a BlueBird update, wait for the BA update that brings the new files.
- "The tablet cannot be reached, so nothing was tapped.": the same, at a press.
- Presses do nothing on the aircraft: check that BBS Nest is running.
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:
- "Left: airspeed 250". The tape starts at 30, so below 30 knots, as when you are parked, it reads "Left: airspeed 30".
- "Left: target speed 200": the MCP speed. While VNAV controls the speed, the target is the FMC's and the list leaves it out.
- "Left: V1 135" and "Left: VR 140", your takeoff speeds from the FMC, on the ground and until two minutes after lift-off, while they are on the visible part of the tape (within about 40 knots of your airspeed; V1 is also listed while it is printed above the tape). Before you have set the takeoff speeds, the ADI shows "Left: V1 INOP".
- "Left: flap maneuvering speed 161": the maneuvering speed for the flaps you have set, from 10 seconds after lift-off and below 20,000 feet, while it is on the visible part of the tape. For flaps up to 20 it is the number Output Shift+1 to Shift+5 give once PERF INIT is done, and at flaps 25 and 30 it is VREF 25 or VREF 30 (see Aircraft-specific hotkeys and callouts).
- "Left: Mach .780" once you reach Mach .40, and "Left: ground speed 250".
In the center, the attitude:
- "Center: pitch 2.5 up, bank 10 left", or "Center: level, wings level".
- "Center: flight director, pitch bar 7.4 above, roll bar 3 right": where the flight director bars sit, in degrees, while the Captain's F/D is on. A bar above, or to one side, is where the flight director wants you to go; centered means you are on it.
- "Center: TCAS, keep the pitch above 5.0 up" (or below) during a TCAS resolution advisory.
- "Center: rising runway, 0.3 dots right" on an ILS approach close to the localizer, in LOC or ROLLOUT, below 2,500 feet. The runway symbol takes the place of the localizer pointer and slides sideways as the pointer would, so this line gives the localizer deviation, and the bottom line then reads "Bottom: localizer scale, expanded".
On the right and at the bottom, the approach:
- "Right: glideslope, pointer 0.5 dots up": the glideslope is above you, so fly up. It also reads centered and at full scale, up (or down).
- "Right: ALT", while you descend between 2,500 and 500 feet radio altitude.
- "Right: DH 200": the radio minimums you set (Input Ctrl+B).
- "Right: radio altitude 150", below 2,500 feet; above that there is no line. On the ground it can read a few feet below zero, such as "-6".
- "Bottom: localizer, pointer 1.2 dots right": the localizer is to your right, so fly right. It also reads centered and at full scale, right (or left), and adds ", expanded scale" once you are close to the centerline and the scale expands.
- With a frequency set and no signal, the scale without its pointer: "Right: glideslope scale, no pointer", "Bottom: localizer scale, no pointer".
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:
- "EPR: 1.03, 1.03", "N1: 19.9, 19.9", "EGT: 358, 360". A color shows only when it is not normal, after its engine's value, as in "EGT: 800 amber, 360", and a reading the display leaves empty is blank.
- While they show: "TAI: L, R" (engine anti-ice), "REV: L green, R green" (reversers), the N1 and EGT maximums ("EGT max: 870, blank") and the in-flight start block.
- "Thrust reference: TO", or CLB, CRZ, "D-TO 1, +25c" and so on, then the reference EPR while it shows, and "TAT: +11c".
- The messages in the display's order, each with its level: "Warning: L ENGINE FIRE", "Caution: L ENG SHUTDOWN", "Advisory: PARKING BRAKE", "Communication: CABIN ALERT", or "Messages: none". Then "PAGE 2" and "RECALL" while the display shows those words.
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".
- The engine page: "N2: 81, 82" (and N3 on a Rolls-Royce), "FF: 3.6, 3.6" (fuel flow in thousands, in BlueBird's weight unit), "OIL PRESS: 91, 91", then OIL TEMP, OIL QTY and VIB the same way. A line that reads only "STATUS" is the display's cue that status messages are waiting.
- The STATUS page: "HYD QTY: L 0.98, C 0.97, R 1.00", the hydraulic pressures, the APU's EGT, RPM and oil quantity, the oxygen pressure, the flight control positions in words ("RUD: centered", "AIL left: 30 % down", "ELEV: 10 % up"), the fuel flow, each status message on a line of its own, and "BRAKE TEMP:" with the eight wheels.
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:
- "EHSI: MAP, range 160": the mode and range, with ", centered" after CTR.
- "Top: TRK 079 M" or "Top: HDG 119 M": where the top of the map points.
- "Top left: 37.5 NM" and "Top right: 1521.4z": the distance to the active waypoint and the time you reach it.
- With TERR on: "Top right: terrain 031 red, 004 amber", the highest and lowest terrain figures the display prints. The terrain picture itself is not described: "Map: terrain shown, not read".
- TCAS's words at the sides, such as "Left side: TFC", "Left side: TA ONLY" or "Right side: TRAFFIC, amber".
- Lines starting with "Map:": everything drawn on the map, from the top of the screen down, each with its distance and how many degrees left or right of the top of the map it is: "Map: KOLM, active, 37.5 NM, 86° right". In PLAN the place is the distance and compass point from the centered waypoint instead: "13.4 NM north-east of KOLM". Only what the screen shows at this range is listed.
- "Right side: VNAV path deviation 120 ft above the path", in a VNAV descent.
- "Bearing pointer 1: VOR L, SEA, 74° right", the wind ("Bottom left: wind 70 kt from 30° left"), the heading bug ("Heading bug: 147, 28° right"), and the display's messages, "Message: EXCESS DATA" or "Messages: none".
The map lines name:
- The route's waypoints, the active one marked active, and with DATA on each one's altitude constraint and time: "Map: KOLM, active, 37.5 NM, 86° right, 2300A, 1518Z" (A is at or above, B at or below). A route that is not active yet reads "Map, inactive route:", and a change waiting for EXEC "Map, modification:".
- The VNAV points T/C, T/D and E/D, and "deceleration starts" and "deceleration ends". A step climb is not read from the EHSI; Output Shift+D reads it from the CDU's PROGRESS page.
- The departure and arrival airports and runways: "Map: runway 16L, 2.0 NM, 15° left".
- With the map options on: navaids ("Map: VORTAC SEA, tuned, 0.5 NM, 173° left"), airports and waypoints.
- What you set on the CDU's FIX page: "Map: fix TCM, circle 15 NM", "Map: fix TCM, radial 300".
- "Map: altitude range arc, 13.9 NM, ahead": where the aircraft will reach the MCP altitude.
- With TFC on, the traffic: "Map: proximate traffic, 3.8 NM, 11° left, +10 climbing", with traffic, proximate traffic, traffic advisory and resolution advisory as its four kinds, and the traffic's relative altitude as the display prints it.
- A tuned VOR's course line: "Map: VOR L course 187 through SEA".
In VOR and ILS, the list has the approach picture instead of the map:
- "EHSI: VOR, range 160" (or ILS), the heading at the top, and "Top left: DME 12.3".
- "Center: course pointer 187, 68° right": the course you set, and where its pointer points.
- "Center: deviation 0.5 dots right": where the deviation bar sits on its scale of dots. It also reads "deviation centered" and "deviation at full scale, right".
- In ILS, "Right side: glideslope 1.2 dots below": where the glideslope pointer sits on its scale.
- In VOR, "Bottom right: TO" or "FROM". In ILS, the frequency at the bottom right, and "Bottom left: ILS".
- The bearing pointers, the wind and the heading bug, as in 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):
- Output L reads the flap lever, for example "Flaps 5". When the flaps are not at the lever's position yet, it adds where they are: "Flaps 5, moving, 3 degrees", or "Flaps 1, surfaces at 0 degrees" when they stay there (no hydraulic pressure).
- Output Shift+G reads the gear, then the lever's position, UP, OFF or DOWN: "Gear up, lever off" in cruise, "Gear down, lever down" on the ground. Listen for a disagreement. "Gear down, lever off" means the gear has not retracted: the simulator's gear key steps the 757's lever one position each press (DOWN, UP, OFF, then DOWN again), so a second press before the gear starts up leaves it at OFF with the gear hanging. Put the lever where you want it with the Gear Lever on the Landing gear panel.
- Output Shift+1 to Shift+5 read the flap maneuver speeds for flaps up, 1, 5, 15 and 20, and Output Shift+6 the landing reference speeds, VREF 30 and VREF 25. Once the CDU's PERF INIT page has the fuel and the zero fuel weight, they are the FMC's own speeds, the ones its APPROACH REF page shows: "Flaps 5 maneuver speed 161 knots", "VREF 30 121 knots, VREF 25 123 knots". Before that, or while BA cannot read the FMC's speeds from the aircraft, they are calculated from your gross weight with BlueBird's own VREF figures, and each ends in calculated: "Flaps 5 maneuver speed 164 knots, calculated", "VREF 30 124 knots, VREF 25 126 knots, calculated". The calculated speeds cover gross weights from 140,000 to 250,000 pounds; outside that you hear "Flap speeds unavailable." So if you still hear calculated after PERF INIT, the speeds are BA's own working, not the FMC's.
- Output D reads the distance and time to the destination, "568 miles to destination KMIA, ETA 03:32 Zulu", and Output Shift+D the next point of the vertical path: "Top of climb in 56 miles, 02:18 Zulu", "Top of descent in …" or "Step climb in …". Both are read from the First Officer's CDU, which they leave on page 1 of PROGRESS. If that CDU does not answer you hear "The first officer's CDU did not answer."
- Output B reads the three altimeters and the radio minimums, as described above, and Output N the nav radios, as described under Radios.
- Output F reads the fuel in pounds, the total and each tank: "Fuel 25480 pounds: left 12740, right 12740, center 0". Output Shift+F says the same in kilograms.
- Output W reads the gross weight in pounds, Output Shift+W in kilograms.
- Output Ctrl+W reads the active waypoint from the EHSI, and Output Shift+H, Shift+S, Shift+A and Shift+V the MCP, as described above.
What BA announces by itself:
- The flight mode annunciations. Every change, starting with "FMA:" and then in the ADI's own words: "FMA: Roll: LOC, Pitch: G/S", "FMA: A/T: SPD", "FMA: Roll armed: LOC". Changes that happen together come as one sentence, so you hear localizer and glideslope capture as they happen. An armed mode that becomes active is said once, as the active mode, and a part that goes blank is said as none, for example "FMA: A/T: none". The whole annunciator is in the Ctrl+P window and at the top of the ADI window.
- The ADI's flags, as they appear and go: "ADI flag: ATT", "ADI flag gone: G/S", and the same for SPD, LOC and RA. Nothing else on the ADI is spoken by itself; the ADI window lists the rest.
- EICAS messages, as they appear and go, by level: "EICAS warning: L ENGINE FIRE", "EICAS caution: L ENG SHUTDOWN", advisories and communication messages as "EICAS: R PACK OFF", and "EICAS gone: L ENG OVHT". Messages that change together come as one line. The advisory FMC MESSAGE is not spoken, because the CDU's own message is (see The CDU); the Upper EICAS window still lists it.
- The thrust reference when it changes, "Thrust reference: CLB", and an engine gauge that changes color: "EICAS: L EGT red", then "EICAS: L EGT normal".
- The lower EICAS: its page when it changes, "Lower EICAS: STATUS page", and, while the STATUS page shows, status messages as they come and go: "Status: L EICAS CMPTR", "Status gone: WARN ELEX".
- The EHSI: the active waypoint when it changes, "EHSI: KOLM, 37 NM", and its messages and flags as they appear and go ("EHSI message: TA ONLY", "EHSI flag: LOC, G/S").
- The MCP. Its lights when they change, for example "CMD R on" or "VNAV off"; the heading, speed or Mach, altitude and vertical speed once the knob has stopped for a second and a half, for example "MCP heading 090" or "MCP altitude 12000"; "A/T armed" and "A/T disarmed"; "Autopilot disconnect" and "Autothrottle disconnect". A value you set from BA's own windows is not said twice.
- The flaps ("Flaps 15"), the gear ("Gear in transit", then "Gear down" or "Gear up"), the speedbrake ("Speedbrake armed", "Speedbrake up 50 percent", "Speedbrake down") and the parking brake ("Parking brake set", "Parking brake released"). They work whether you move the control from BA, from the simulator's own keys or from your hardware.
- The trim, while it moves, about once a second, in the units BlueBird's trim indicator shows, for example "Trim 5.3", as on the 737s. The simulator's trim keys move it. Output Shift+T turns these announcements off and on; see Trim.
- The CDU's EXEC light: "EXEC light on" when a change, such as an activated route, waits for EXEC, and "EXEC light off" once you execute it.
- Radios and transponder: COM frequencies, the squawk ("Squawk 4743"), the TCAS mode ("TCAS TA/RA") and the Captain's altimeter setting once the knob stops.
- Power and ground services: "External power available", "EXT PWR on", "Ground power connected", and the aft stairs, fuel truck, catering and cargo service.
- Other cockpit events: the autoland status ("LAND 3", "NO AUTOLAND"), "Altitude alert", "Configuration warning", each IRS as it finishes aligning ("IRS L aligned"), the engine start valves closing ("Left start valve closed"), and the doors ("Door L1 open", "Forward cargo door closed").
- The annunciator lights, as they come on and go out, for example "Left bus off light on".
- Any switch moved by something other than your own pick in BA: a preset, BlueBird's own automation, the mouse or a hardware panel. You hear the switch and its new position, for example "Battery On". When many move at once, as when a cockpit preset loads, you hear one line instead: "Panel state changed: 34 switches".
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
- BBS Nest must be running before the flight loads, or the aircraft's systems do not respond to what BA sets.
- BA reads one version of the aircraft at a time. The display windows, the flight mode annunciations and the tablet are read through files made for each version of BlueBird's 757. After a BlueBird update they may stop until BA is updated; see When BA cannot read a display. The panels, the MCP windows and the CDU do not depend on those files.
- Thrust. The simulator's throttle keys, a game controller or a hardware throttle move BlueBird's thrust levers. For takeoff with the autothrottle, check that the A/T is armed (Input Ctrl+P: "A/T Arm: On"). Lined up, with the brakes held, press THR: from the MCP panel or the speed window (Input Ctrl+S) you hear "THR on" about a second and a half later, and in the Ctrl+P window its caption reads "THR: On". Release the brakes only then. If you hear "THR off" or "THR did not engage", keep the brakes held and check A/T Arm.
- Set the takeoff trim with the trim keys. The simulator's trim keys move BlueBird's stabilizer trim, and BA says the setting while it moves ("Trim 5.3"). Trim to the TRIM figure on the CDU's TAKEOFF REF page before takeoff.
- The speedbrake lever is worked with the Armed, Down and Up buttons on the Control stand panel, or the simulator's own keys.
- The ILS has its own panel. Set its frequency and course in the Ctrl+N window before the approach, and park it after landing.
- The CDU is read from the aircraft. It needs the aircraft powered; until then the window says it is waiting.
- Output N, D and Shift+D and the Ctrl+N window use the First Officer's CDU and change the page it shows. Do your own work on the Captain's.
- Reload the flight after a nav data update. The aircraft misbehaves until you do, and BlueBird looks for a new cycle only when a flight loads.
- The Hotkey Reference lists which general keys do nothing on the 757.
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
- Install the MobiFlight WASM module. Every control on the MD-11 goes through it; without it, readouts still work but nothing you press reaches the aircraft. If BA cannot get through, about a minute after the aircraft is selected it says "MobiFlight calculator path unavailable. Some cockpit controls may not respond.", and any control you then try says it is unavailable, for example "Heading push unavailable".
- The MCDUs need no setup: TFDi publishes their screens as text specifically so tools like BA can read them.
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:
- Overhead: Electrical, IRS, Fuel, Hydraulic, Air, Cabin Pressurization, Anti-Ice, Engines and Ignition, Flight Controls, Lights and Signs, Cockpit Lights, Windshield Wipers, Miscellaneous.
- Aft Overhead: Cargo Fire, Engine Fire, APU, Evacuation, GPWS.
- Glareshield: Flight Control Panel, EFIS Captain, EFIS First Officer, Warnings Captain, Warnings First Officer.
- Instrument Panel: Source Input Captain, Source Input First Officer, Landing Gear, Brakes and Antiskid, Standby Instruments, Captain Side, First Officer Side, Yokes.
- Pedestal: Radios, Throttle Quadrant, Flaps, Speedbrake, Trim, System Display Control Panel, Transponder, Weather Radar, Audio Panel Captain, First Officer and Observer, Cockpit Door, Emergency Controls.
- Ground and Exterior: Doors, Cabin, Aircraft Options, EFB.
- Circuit Breakers: Upper, Lower, Left Aft and Overhead.
- Read-outs: V-Speeds, Minimums and Altimeters, Autoflight Status, Engines, APU Status, Fuel Quantity.
How the panels behave:
- Controls speak their state. A button reads what its lights show, for example "Battery: On" or "Pack 1: Off", and "unpowered" when the annunciators have no power. Tab moves only between the controls you can operate.
- Indicator lights are in each panel's status display. Press Ctrl+3 and arrow through rows such as "AC Bus 1: Off" or "External Power AVAIL light: On". They update live, and F5 refreshes.
- Guard covers are listed immediately before the control they cover.
- The Read-outs section is where the numbers a sighted pilot would read off the screens live: V1, VR and V2 with the slat and flap retraction speeds, the minimums and all three altimeters, the autopilot and autothrottle state and the four flight control panel windows, N1 for all three engines ("Engine 1 N1: 25.4 percent"), the APU, and fuel per tank ("Tank 1: 12000 pounds"), including the auxiliary and tail tanks. Fuel rows are in the weight unit set on the EFB's Options page, as the overhead shows them; until the aircraft has reported that unit, a row shows just the number, and while the aircraft is still loading its fuel the rows say "not available".
- Radios (first in the Pedestal) lists the active and standby frequency of COM 1, 2 and 3, a COM 1 Standby field (type 124.9 or 124.900 and press Enter) and a COM 1 Transfer button, and the same for COM 2 and 3. After Enter you hear "COM 1 standby 124.900"; after Transfer, "COM 1 active 124.900"; if the aircraft refuses, "COM 1 standby did not change, still 121.500". Further down the same panel are the aircraft's own radio control panel knobs and buttons for the captain, first officer and observer, unchanged.
- Transponder starts with the Squawk code row and a Squawk field: type four digits and press Enter. BA presses the aircraft's own keypad and reads back what the transponder actually shows — "Squawk 1200", or "Squawk entry did not take, the transponder reads 5473".
- EFIS Captain and EFIS First Officer each have a Minimums field: type feet and press Enter. The aircraft applies a typed value to the baro minimums. If the minimums mode switch beside it is on Radio, you are told so: "Captain baro minimums set to 500 feet. Minimums mode is Radio, showing 200 feet". These panels also have Captain Altimeter STD and First Officer Altimeter STD buttons, and the Standby Instruments panel has Standby Altimeter STD.
- Speedbrake has two rows. Spoilers is the lever's travel (Retracted, 1/3 extended, 2/3 extended, Fully extended). Ground spoilers is its pull (Not armed, Armed, or Extended once they have deployed by themselves on landing). Choose Armed to arm them for landing — the lever must be retracted first, and you are told if it is not.
- Flaps holds the flap and slat handle and the Dial-A-Flap thumbwheel (see the flaps section below).
- System Display Control Panel has the cue buttons that choose which page the system display shows.
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:
- NAV and FMS Speed read engaged or not engaged. BA works this out from the panel's own windows: the heading window shows dashes while NAV flies the aircraft, and the speed window while FMS speed does.
- The mode selects read their current mode: "IAS / Mach: Mach", "Heading / Track: Heading", "VS / FPA: V/S", "Altitude Unit: feet".
- PROF, Approach/Land, Go Around, the knob Push and Pull buttons, the vertical speed wheel and the autothrust disconnects have no state to show and read as plain buttons.
- Each button has its own Alt+letter, which your screen reader speaks with the button. Two are not the first letter: Approach/Land is Alt+O (Alt+P is PROF) and Wheel up is Alt+W (Alt+U is Altitude Unit; Wheel down is Alt+D).
- Shift+Tab from the Autoflight button reaches a live status list: "Speed: Mach 0.82", "Heading: dashed, NAV engaged", "Altitude: 36000 feet", "Vertical speed: dashed, not engaged", "Autopilot: AP 1", "Autothrottle: on".
- The bank angle limiter and the Dial-A-Flap take-off angle are at the bottom of the window.
The value windows, all in input mode, take typed values — no knob-winding:
- Input Ctrl+H sets the heading. Buttons in order: Push, Pull, NAV, then Track / Heading.
- Input Ctrl+S sets the speed. Type knots (250) or a Mach number (0.82); BA works out which from the number and sets the unit for you. Buttons: Push, Pull, FMS Speed, IAS / Mach.
- Input Ctrl+A sets the altitude, always in feet. Buttons: PROF, Push, Pull. (The window's own feet or metres unit is the Altitude Unit Select row on the Flight Control Panel panel.)
- Input Ctrl+V sets the vertical speed: type feet per minute (-1500) or a flight path angle (-3). It also has the wheel.
- Input Ctrl+B sets all three altimeters — captain, first officer and standby — from one entry. Type hPa (1013) or inHg (29.92); each altimeter is set in whichever unit its own display uses. The Standard button sets standard pressure on all three. A moment later BA reads back the captain's ("Altimeter: 1020, 30.12" or "Altimeter standard"), and then tells you only about one that did not take: "Standby altimeter not set, reads 1012, 29.88".
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.)
- Ctrl+Shift+L, Ctrl+Shift+C and Ctrl+Shift+R switch to the Left, Center and Right MCDU; the MCDU unit list does the same.
- Alt+Home jumps to the screen; arrow keys read it line by line. Lines are numbered to match the keys: the line that reads "3:" is the one Ctrl+3 acts on.
- Alt+S jumps to the scratchpad box. Type and press Enter; BA types it into the aircraft one key at a time.
- Line select keys: Ctrl+1 to 6 left, Alt+1 to 6 right (or F1 to F6 and F7 to F12 with the alternate layout).
- Pages: Alt+I Init, Alt+E Perf, Alt+F Fpln, Alt+Shift+F Sec Fpln, Alt+P Prog, Alt+R Ref, Alt+N Nav Rad, Alt+X Fix, Alt+D Dir Intc, Alt+T To Appr, Alt+O Eng Out, Alt+M Menu.
- Backspace or Alt+C is Clr, which deletes one character, as the real key does. Delete clears the whole scratchpad in one keystroke and then says "Scratchpad cleared" — BA presses Clr for you until it is empty.
- Page Up and Page Down (or Alt+Up and Alt+Down) slew up and down; Right Arrow on the screen, or Alt+Right anywhere, is the next page.
- The MCDU's four lights are spoken when they come on. MSG is the important one: the FMS has put a message in the scratchpad for you. FAIL, DSPY and OFST are reported too.
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:
- Section tabs read with the current one marked, such as "General (selected)".
- Groups of choice buttons read as one list, such as "Weight Units: Imperial".
- Stepper fields (with up and down arrows on the tablet) read as one list with every option, so you can pick a runway directly.
- Values read as lines such as "Block Fuel: 77347 lbs" or "V1: 155".
- Service tiles read with their state, such as "GPU: Connect", and the State page's tiles say which state is the default.
- Messages that pop up at the bottom of the tablet are spoken straight away.
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:
- Flap Up / Slat Retracted — clean.
- Flap 0 / Slat Extended — slats out, flaps still at zero.
- Dial-A-Flap — the take-off detent; the angle comes from the thumbwheel.
- Flap 28 — mainly the go-around setting. There is a gate at 28, so a go-around from 35 or 50 retracts to 28 first.
- Flap 35 — a normal landing setting.
- Flap 50 — maximum landing flaps.
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:
- Alt+P — the captain's PFD, flight mode annunciator first. This is the way to hear PROF, LAND ARMED, ALT HOLD and the other modes.
- Alt+N — the captain's navigation display.
- Alt+E — the EAD, the engine and alert display (this aircraft's EICAS): engine gauges, thrust limit, flap and slat, and every alert with its colour.
- Alt+S — the SD, the system display, whatever page it is showing. For another page, press its cue button first (Pedestal section, System Display Control Panel).
- Alt+I — the standby instrument. It is small in its view, so it reads best on a high-resolution display.
- Alt+D — describes the outside scene.
Aircraft-specific hotkeys and callouts
- Output Shift+1 reads the slat retraction speed (VSR) and Shift+2 the flap retraction speed (VFR). V1, VR and V2 have no key; read them in Read-outs, V-Speeds.
- Output F / Shift+F read fuel tank by tank with a total, including the auxiliary and tail tanks, F in pounds and Shift+F in kilograms whichever weight unit the EFB is set to (until the aircraft has reported that unit you hear "Fuel quantity unavailable, the aircraft has not reported its weight unit", and for about 20 seconds after a flight loads, while the aircraft sets its fuel, "Fuel quantity unavailable"); B the captain's altimeter, "Altimeter: 1013, 29.92"; Shift+G the gear lever.
- Input Shift+1 and Ctrl+1 push and pull the heading knob, Shift+2 and Ctrl+2 the altitude knob, and Shift+3 and Ctrl+3 the speed knob.
- Output Ctrl+M opens the monitor manager.
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
- Press confirmations. On most aircraft BA stays quiet when you press a button, because your screen reader has already spoken it. The MD-11 is the one exception. Nothing the aircraft shows confirms a panel press, so after you press a button BA waits a moment for the lights to settle and then says the result once, for example "External Power: On". A press that does nothing — a generator with the engines off, say — reads back the unchanged state, so you know it was inert.
- When a control will not move. If you pick a combo value and the control cannot get there, you hear "... did not move. It may be guarded, unpowered, or inhibited." BA works each control step by step and checks the aircraft after each step, rather than assuming it arrived.
- There are a lot of lights. The MD-11 announces over 500 indicator lights as they change. With no readable displays, those lights are this aircraft's instrument panel — but it is a lot of talking. Use The Monitor Manager (Output Ctrl+M) to silence the ones you do not want; searching "fuel" finds every fuel lamp, and every announcement, including each take-off callout, has its own row.
- Lights going out are quieter than lights coming on. A light coming on is spoken at once. A light going out waits a moment, and is dropped entirely if the aircraft has lost power, so shutting down does not read the whole panel to you.
- Tests are held for you. Every test button on the MD-11 is hold-to-test, so BA holds it for three seconds and announces the lights as they come on. The exception is the annunciator light test, which stays a short tap — held, it would light every annunciator at once. The fire test is one button for the whole aircraft, labelled Engine and APU Fire Test: it lights all three engine FIRE lights, the APU FIRE light and the master warning.
- Minimums and radio. A typed minimums value always goes to the baro minimums. If the mode switch is on Radio, the display keeps showing the radio value until you switch it to Baro.
- The FMA is on the PFD only. For PROF, approach and land modes, use Output Alt+P.
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.
- Preflight. The aircraft is parked at a stand (a gate or a remote parking spot). You power it up, program the flight computer with the route, load fuel and passengers, work out takeoff speeds and settings, and get your route clearance from ATC.
- Pushback and engine start. A tug pushes the aircraft backwards off the stand, because airliners cannot reverse on their own. Engines are usually started during or just after the push.
- Taxi out. You drive along the taxiways to the departure runway, following the route ATC gives you, and stop at the holding point before the runway.
- Takeoff. Cleared onto the runway, you line up on the centreline, set takeoff thrust, and accelerate. At the decision speed V1 you are committed to go; at VR you rotate (raise the nose); V2 is the safe climb speed if an engine fails.
- Climb. Gear up, flaps retracted in stages as speed builds, then a long climb to cruising altitude, usually with the autopilot on from a few hundred or a few thousand feet.
- Cruise. Level flight along the planned route. This is the quiet part: monitoring fuel, weather and position, and preparing for the arrival.
- Descent. Starting at the top of descent, a point the flight computer calculates, you descend towards the destination, often on a published arrival procedure (a STAR).
- Approach. The final part of the descent, lined up with the landing runway, with gear down and flaps set for landing. This might be an ILS, an RNAV approach or a visual approach.
- Landing. Crossing the runway threshold at about 50 feet, flaring just above the ground, touching down, and slowing down on the runway with reverse thrust and brakes.
- Taxi in. Leaving the runway at an exit taxiway, then taxiing to your arrival stand, where you park, set the parking brake and shut down.
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:
- Taxi: ground speed every so often (BA can announce it automatically, see the Taxi Guidance settings), Output Y for taxi status, and Output Alt+G for nearby ground traffic.
- Takeoff and initial climb: let the tones and callouts work; check Output S (airspeed) and Output V (vertical speed) once you are climbing.
- Climb: every minute or two, altitude (Output A), airspeed (Output S) and vertical speed (Output V). Check the autopilot targets with the FCU or MCP readouts (Output Shift+H, Shift+S, Shift+A, Shift+V) after every change you make.
- Cruise: every few minutes, altitude and speed; now and then fuel (Output F), wind (Output I), and distance to destination (Output D). Check the fuel against your plan once an hour or so.
- Descent: every minute, altitude, speed and vertical speed, plus distance to the runway (Output Ctrl+D) once you have chosen one.
- Approach: much more often — every 15 to 30 seconds — altitude above the ground (Output Q), airspeed and vertical speed. Gear (Output Shift+G) and flaps (Output L) before you are established.
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.
- Flight director. Commands shown to the pilot: "pitch up a little, bank left". You can follow them by hand.
- Autopilot. Flies the aircraft to follow those same commands. Most airliners have two or three autopilots, but you normally use one, except for autoland where more may be engaged.
- Autothrust or autothrottle. Controls engine thrust to hold a speed or a thrust setting.
- Flight management system (FMS). The computer that holds your route, performance data and speeds. You talk to it through the MCDU or CDU.
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:
- Selected: you dial a number on the glareshield panel and the aircraft follows that number. "Fly heading 270." "Hold 250 knots." "Climb at 1,500 feet per minute."
- Managed (Airbus) or FMS-driven (Boeing, called LNAV and VNAV): the aircraft follows the flight plan and speeds in the FMS. You do not touch the heading knob; the aircraft turns at each waypoint by itself.
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:
- Thrust: what the autothrust is doing, for example SPEED, MACH, THR CLB or THR IDLE.
- Vertical: for example CLB, OP CLB, ALT, ALT CST, DES, V/S, G/S.
- Lateral: for example NAV, HDG, LOC, RWY.
- Approach capability: for example CAT 3 DUAL, or blank.
- Engagement: which autopilot, flight directors and autothrust are on, for example AP1, 1FD2, A/THR.
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.
- ILS (Instrument Landing System). Two radio beams from the runway: the localizer (LOC) gives left and right guidance along the centreline, and the glideslope (G/S or GS) gives a descent path, usually 3 degrees. The autopilot can capture both and fly the aircraft down to a few hundred feet, or all the way to touchdown in an autoland if the aircraft and the runway are certified for it. Output Ctrl+I gives you an ILS report once you have chosen your destination runway.
- RNAV or RNP approach. Uses GPS and the FMS instead of radio beams. The lateral path comes from the flight plan; on most airliners the vertical path is built by the FMS too. The FMA modes have different names (for example FINAL APP on an Airbus), but the idea is the same.
- Visual approach. You fly to the runway by looking at it. For a blind pilot in the simulator, BA's Visual Guidance and the destination runway readouts take the place of looking out of the window.
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:
- On the correct lateral and vertical path, needing only small corrections.
- In the landing configuration: gear down, landing flaps set.
- At the approach speed, not slower, and not more than a few knots faster.
- Descending at a normal rate, usually no more than about 1,000 feet per minute.
- Thrust set to match, not at idle.
- Landing checklist complete.
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:
- ATIS — a recorded broadcast of the weather, the runways in use and the altimeter setting. Each version has a letter, "information Alpha", "information Bravo", and you tell the controller which one you have.
- Clearance Delivery — gives you your route clearance before you start.
- Ground — pushback and taxi.
- Tower — takeoff and landing, and anything on the runways.
- Departure, Approach and Centre — the radar controllers who look after you in the air.
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:
- Runway instructions: hold short, cross, line up, cleared for takeoff, cleared to land.
- Altitudes, headings and speeds you are assigned.
- Frequencies, squawk (transponder) codes and the altimeter setting.
- Taxi routes, if the controller gives you one.
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.
- "Taxi to holding point runway 27L via A, B" — follow taxiway A, then B, to the holding point for runway 27L. In the United States you will hear "taxi to runway 27L via A, B" instead.
- "Hold short of runway 27R" — stop before the runway's hold short line and do not enter it. You must read this back.
- "Cross runway 27R" — you may cross that runway. You must read this back too. Never cross a runway without hearing this.
- "Hold position" — stop where you are.
- "Give way to the Airbus coming from your left" — let that aircraft pass first.
- "Follow the 737 ahead" — taxi behind that aircraft.
- "Line up and wait runway 27L" (in some countries "line up runway 27L") — enter the runway and line up on the centreline, but do not take off yet.
- "Cleared for takeoff runway 27L" — you may take off. This is the only phrase that means that.
- "Expedite" — please be quick.
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.
- Never enter or cross a runway without a clearance. BA stops you at every runway hold short with "Stop. Hold short of" and the runway, and waits for you to press continue (Input Y). Press it only when ATC has actually cleared you.
- Read back every runway instruction. Hold short, cross, line up, takeoff and landing clearances, every time.
- Know where you are. Output Alt+Y tells you at any moment whether you are on a taxiway, a stand or a runway. Use it whenever you are unsure, and especially before you move after a stop.
- Take warnings seriously. If BA says "Warning: approaching runway" and that you are off route, stop and check your position and your clearance.
- "No traffic seen" is not "clear". At a hold, BA's runway watch tells you what traffic it can see on the runway and on final. It never says a runway is clear, because it cannot see everything ATC can. The controller's clearance is what lets you go.
- After landing, get off the runway. Do not stop on the runway unless told to. Use the Landing Exit Planner so you know which exit you are aiming for, and stop to tidy up only once you are clear of the runway.
- When in doubt, stop and ask. "Hold position" is always safe, and saying "confirm cleared to cross runway 27R" costs you five seconds.
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:
- Your aircraft's own documentation. Most add-on aircraft come with a tutorial flight, a pilot's operating handbook or flight crew operating manual, and a quick reference. They are written for sighted users, but the procedures and explanations are what you need.
- The developers' online documentation. FlyByWire, PMDG, Fenix and others publish manuals and guides on their websites; many are plain text pages that work well with a screen reader.
- Flight simulation communities. Forums, Discord servers and user groups for your simulator, your aircraft and your network. The MSFS Blind Assist Discord server (linked from the project's home page) is the place to ask other blind pilots how they do things.
- Network training. Online networks such as VATSIM run free pilot training and publish guides to phraseology and procedures, which teach you how to talk to ATC with confidence.
- Aviation theory books and courses. Private pilot ground school material explains weather, navigation, aerodynamics and radio procedure from the beginning. Many are available as audiobooks or accessible ebooks.
- Podcasts and videos. Many airline pilots talk through real flights, procedures and incidents. Look for ones that describe what they are doing rather than only showing it.
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:
- Pan (which ear the tone is in) almost always means "steer this way". By default you steer towards the tone. Each family of tones has its own setting to reverse that, listed below.
- Pitch (how high or low the tone is) is used for up and down: attitude in Hand Fly and Visual Guidance, sink rate in the flare.
- Silence in a guidance tone means you are on profile. It never means the feature has stopped: when guidance ends or gives up, BA says so in words.
- Hard pan options, found next to each tone's other settings, make the tone jump fully to one ear instead of panning part-way. They help on speakers, where a slight pan is hard to tell from the centre.
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:
- Taxi Guidance 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). These apply to taxiing, runway lineup and the docking steering tone. The docking beep has its own Docking beep sound and Docking beep volume.
- Hand Fly tab, Takeoff Assist: Takeoff Assist Tone, Takeoff Assist Volume, Steer toward the tone to stay on the centerline (untick it to steer away from the tone), Hard-pan centerline tone (full left or full right; speaker-friendly) and Play steering tone. These also apply to the rollout centreline tone and the flare's lateral tone.
- Hand Fly tab, Hand Fly: Hand flying feedback type (tones, announcements or both), Hand fly tone type and Volume.
- Hand Fly tab, Visual Guidance: Visual Guidance Tone, Visual Guidance Volume, Current-attitude tone, Current-attitude Volume and Hard-pan visual-guidance tones (speaker-friendly).
- Audio tab: the output device, with a Test Tone button that plays a tone on the chosen device.
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
- ActiveSky — a third-party weather add-on for MSFS. BA can read richer weather from it if you turn on Enable ActiveSky integration on the Weather tab. See ActiveSky.
- AGL (above ground level) — height above the ground directly below you. Output Q reads it. Compare MSL.
- Airbus — the European aircraft maker. Its airliners in BA include the A320, A330 and A380.
- AIRMET — a weather warning for lighter aircraft about hazards such as moderate turbulence or icing. Compare SIGMET.
- Apron — the paved area where aircraft park, load and refuel. Also called the ramp.
- ATC (air traffic control) — the controllers who give you clearances on the ground and in the air.
- ATIS — a recorded broadcast of an airport's weather, runways in use and altimeter setting, identified by a letter such as "information Bravo".
- Autopilot (AP) — the system that flies the aircraft by itself, following the modes you select.
- Autothrust (A/THR) or autothrottle (A/T) — the system that controls engine thrust to hold a speed or thrust setting. Airbus says autothrust, Boeing says autothrottle.
- Backtrack — taxiing along a runway in the opposite direction to the one you will take off or have landed in, usually to reach the start of a runway with no taxiway at its end, or to leave one. In the taxi planner, tick Full-length departure (requires backtrack) when a runway needs one.
- Boeing — the American aircraft maker. Its airliners in BA include the 737, 777 and 787.
- CDU (Control Display Unit) — Boeing's name for the keyboard and screen you use to program the flight computer. See MCDU.
- Centreline — the painted line along the middle of a runway or taxiway.
- Clearance — permission from ATC to do something specific, such as taxi, cross a runway, take off or land.
- Destination runway — in BA, the runway you choose with Input Shift+D. It feeds distance readouts, Visual Guidance, the landing assist and exit planning. See Choosing a Destination Runway.
- Docking — the final few metres of parking at a gate, where you stop exactly on the stop mark. See Docking Guidance.
- ECAM — Airbus's warning and system display system. The upper part is the E/WD (engine and warning display), the lower part the SD (system display).
- EFB (Electronic Flight Bag) — a tablet in the cockpit used for performance calculations, loading, ground services and charts. BA's own flight planning window is opened with Output Shift+E; each aircraft's tablet is covered in Aircraft EFBs.
- EICAS — Boeing's equivalent of ECAM: the engine indications and crew alerts display.
- Exit (runway exit) — a taxiway you leave the runway by after landing. A high-speed exit leaves at a shallow angle so you can turn off fast. See The Landing Exit Planner.
- FCU (Flight Control Unit) — the Airbus autopilot panel on the glareshield, with knobs you push (managed) or pull (selected). Compare MCP.
- Flare — raising the nose just before touchdown to slow the descent for a gentle landing.
- Flight director (FD) — commands shown to the pilot telling them how to pitch and bank to follow the active modes.
- Flight level (FL) — altitude on the standard altimeter setting, in hundreds of feet: FL350 is about 35,000 feet.
- FMA (Flight Mode Annunciator) — the strip at the top of the primary flight display showing which autopilot, flight director and thrust modes are active or armed. See General Flying Concepts.
- FMC, FMS, FMGC — the flight management computer that stores your route and performance data. Boeing calls it the FMC; Airbus's version is part of the FMGC. You program it through the CDU or MCDU.
- Glideslope (GS or G/S) — the part of an ILS that gives you a descent path to the runway, usually 3 degrees.
- Go-around — abandoning an approach and climbing away, to try again or divert.
- GSX (GSX Pro) — a third-party add-on that provides ground services such as pushback, jetways, catering and boarding. BA has an accessible window for it. See Gates, GSX and Docking.
- Hard pan — a BA option that sends a steering tone fully to one ear instead of panning part-way.
- Hold short — an instruction to stop before a line, usually a runway's holding point, and not go past it until cleared.
- Holding point — the marked place where you stop before entering a runway. Some are named, such as "holding point A1".
- IAS (indicated airspeed) — the airspeed the instruments show; what the aircraft "feels". Output S reads it.
- ILS (Instrument Landing System) — radio guidance to a runway: a localizer for left and right, and a glideslope for up and down.
- Input mode — BA's hotkey mode for commands that change something or open a window. Press the left bracket key to enter it. See Output Mode and Input Mode.
- Intersection departure — taking off from a point partway down the runway instead of the very start, which leaves less runway ahead.
- Lineup — positioning the aircraft on the runway centreline, pointing down the runway, ready for takeoff.
- LNAV and VNAV — Boeing's modes for following the FMC route laterally (LNAV) and vertically (VNAV).
- LOC (localizer) — the part of an ILS that guides you left and right onto the runway centreline.
- Managed mode — Airbus term for letting the flight computer control speed, route or altitude profile. Compare selected mode.
- Mach — speed as a fraction of the speed of sound, used at high altitude: Mach 0.78.
- MCDU (Multipurpose Control and Display Unit) — Airbus's keyboard and screen for programming the flight computer. Input Shift+M opens it on most Airbus aircraft. The A380 replaces it with the MFD.
- MCP (Mode Control Panel) — the Boeing autopilot panel on the glareshield, with a button for each mode. Compare FCU.
- METAR — a routine weather report for an airport, issued about every half hour or hour. Output Shift+M opens the METAR report.
- MobiFlight WASM module — a free add-on you put in your MSFS Community folder. BA needs it to operate controls on several aircraft, including the FlyByWire and Fenix Airbuses.
- Monitor Manager — BA's window for silencing individual automatic announcements, opened with Output Ctrl+M. See The Monitor Manager.
- MSL (mean sea level) — height above the sea, which is what the altimeter shows when set to QNH. Output A reads it. Compare AGL.
- NOTAM — a notice about a temporary change at an airport or along a route, such as a closed taxiway.
- Output mode — BA's hotkey mode for readouts and windows that only tell you something. Press the right bracket key to enter it. See Output Mode and Input Mode.
- Pan — moving a sound between your left and right ears. BA's steering tones use pan to tell you which way to turn.
- PFD and ND — the primary flight display (attitude, speed, altitude, FMA) and the navigation display (route, map, weather).
- Pushback — being pushed backwards off a stand by a tug before taxiing.
- QNH — the local altimeter setting that makes the altimeter read height above sea level. Given in hectopascals (1013) or inches of mercury (29.92). Output B reads your setting.
- RA (resolution advisory) — a TCAS instruction to climb, descend or hold your vertical speed to avoid a collision. You must follow it. BA announces RAs on aircraft that provide them. Compare TA.
- Readback — repeating a clearance back to ATC so they can confirm you heard it correctly.
- RNAV or RNP — navigation by GPS and the flight computer rather than by radio beacons. An RNAV approach is flown this way.
- Rotate (VR) — the speed at which you raise the nose on the takeoff roll.
- Runway incursion — an aircraft, vehicle or person on a runway where they should not be. Hold short instructions exist to prevent them.
- SayIntentions — an AI-driven air traffic control service for flight simulators. BA can read its transmissions and build a taxi route from its clearances. See SayIntentions.
- Selected mode — Airbus term for flying a value you dialled on the FCU. Compare managed mode.
- SID — a published departure procedure from a runway to the start of your route.
- SIGMET — a warning of significant weather hazardous to all aircraft, such as severe turbulence, severe icing or thunderstorms.
- SimBrief — a free online flight planner. BA can load your SimBrief plan and brief it to you. See SimBrief.
- Squawk — the four-digit code you set in your transponder so ATC can identify you on radar. Output X reads it.
- Stable approach — an approach that is on path, at the right speed, configured for landing and at a normal descent rate by a set height.
- Stand — a parking position for an aircraft, either at a gate with a jet bridge or out on the apron.
- STAR — a published arrival procedure from the end of your route to the start of the approach.
- TA (traffic advisory) — a TCAS alert that traffic is close. No avoiding action is required, but look out for it. Compare RA.
- TAS (true airspeed) — your actual speed through the air, which is higher than IAS at altitude. Output T reads it.
- Taxi — moving the aircraft on the ground under its own power.
- TCAS — the traffic collision avoidance system, which warns of nearby aircraft and gives resolution advisories. See TCAS Traffic.
- Threshold — the start of the usable landing part of a runway. A displaced threshold is set back from the end of the pavement.
- Top of descent (TOD) — the point where the flight computer plans to start your descent. Output Shift+D reads the distance and time to it on many aircraft.
- Transition altitude and level — the heights at which you change between the local QNH and the standard altimeter setting.
- Transponder — the radio that answers ATC radar with your squawk code and altitude.
- V1, VR and V2 — takeoff speeds. V1 is the decision speed: after it, you continue the takeoff even with an engine failure. VR is rotation speed. V2 is the safe climb speed with an engine out.
- VATSIM — a free online network where real people act as air traffic controllers. BA can announce its activity through vPilot. See VATSIM.
- Vertical speed (V/S) — how fast you are climbing or descending, in feet per minute. Output V reads it.
- Visual Guidance — BA's two-tone guidance for flying a final approach by hand. See Visual Guidance.
- Vref — the reference landing speed for your weight and flap setting. Approach speed is usually Vref plus a few knots.
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
- Check the announcement method on the Announcements tab of Settings (see Announcement Settings). If it says "No screen reader detected", check that NVDA or JAWS is actually running.
- Speech in an unexpected voice. Hearing the Windows voice usually means BA could not reach your screen reader for that message.
- BA does not repeat your own key presses, and many controls work with no sound at all. Silence after you change a control does not mean it failed; read the control or panel row again after a second or two.
- You may have muted the announcement. Open the Monitor Manager (Output Ctrl+M) and check that the item you expect is not switched off.
- VATSIM announcements specifically: press Output Alt+V in case you muted them for the flight, and check the VATSIM tab of Settings. After BA installs its vPilot plugin, you must restart vPilot once.
Hotkeys Do Nothing
- Enter a mode first, and the right one. Almost every hotkey works only after ] (Output, "output") or [ (Input, "input"), and the same key can do different things in each mode: Output Shift+D reads top of descent, Input Shift+D opens the destination runway window. See Output Mode and Input Mode and the Hotkey Reference.
- Check your aircraft. Hotkeys differ between aircraft.
- Hotkeys may be suspended from the File menu. If BA says "Warning: failed to re-register hotkeys. Another application may be using the bracket keys.", close the other program, or a second copy of BA, and try again.
- Hand Fly and Visual Guidance take over single letters (A, S, H, V, Q, D, B, P and F). Turn the mode off (Output Ctrl+H or Ctrl+V) before typing in another program.
- "Not connected to simulator." BA is not connected yet. See the next section.
- Keyboard layout. If your bracket keys never turn a mode on, try the two keys to the right of P, or ask for help on the Discord.
BA Will Not Connect, or Uses the Wrong Aircraft
- "Waiting for simulator." BA's status line shows this until the simulator is running. Load into a flight; BA connects on its own, says "Initializing, please wait", then "Connected to" followed by the aircraft's title.
- BA uses the profile you chose, not the one it guesses. After connecting, BA says which profile is active, for example "FlyByWire Airbus A320neo Profile and panels active". If that is not your aircraft, choose the right one from the Aircraft menu. BA remembers your choice for next time.
- Your aircraft is not in the Aircraft menu. Only the aircraft listed there have panels and aircraft-specific features. The general features — taxi guidance, weather, location, teleport and so on — still work with other aircraft, but the panels will not match.
- iFly 737 MAX8: "iFly 737 not detected." or *"iFly plugin not responding."* BA talks to the iFly through the iFly's own SDK connection, which only exists while the aircraft is loaded and the simulator is running and not paused. Load the aircraft, unpause, and try again. See Boeing Aircraft and the MD-11.
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.
- Build it, for the right simulator. Open File, then Nav Database, and press Build FS2020 Database or Build FS2024 Database (close MSFS 2020 first; have MSFS 2024 at its main menu).
- "Database Mismatch Warning". Choose Yes - Open Settings to switch, rather than No - Continue Anyway: the wrong database can give you wrong runway positions.
- Rebuild after scenery or navigation data changes, so BA sees the same airport layout as the simulator.
- Messages such as *"Airport KJFK not found in database"* in the taxi planner, teleport or destination runway windows usually mean the database is missing or out of date.
See The Navigation Database for more.
A Taxi Route Will Not Calculate
- Load the airport. The taxi planner needs the airport's taxi network. If the status says "No taxi data for" the airport, the database has no taxiways for it, often because the scenery or database is out of date.
- Be at the airport and connected. Calculate Route uses your aircraft's live position. "Could not find your position on the taxi network." means BA could not place you on a taxiway or stand: check you are at the right airport and on the pavement.
- Check your clearance entry. In Progressive Taxi, a message such as "Could not find taxiway B from A. Check your entry." means the taxiways you entered do not join up the way you entered them. Check the order and spelling against what ATC said. Some sceneries name taxiways differently from the charts; the planner's lists show the names this airport actually uses.
- "Could not calculate a route to the destination." There is no connected path. The destination may be on a part of the taxi network that the scenery has left disconnected. Try another destination nearby, or a different entry point.
- Warnings in the route summary — for example that the route does not reach the runway, or that there is no hold short point for a runway — are BA being honest about a problem in the airport data. Read them before you move. Everything Taxi Guidance Says explains each one.
- A runway or stand looks wrong. Your scenery's data may differ from the real airport. See Taxi Guidance.
Tones Play on the Wrong Device, or Not at All
- Open Settings and go to the Audio tab.
- 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.
- 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
- Checking for updates, preview builds and going back to a release are described in Updates.
- If an update ever leaves you stuck, you can download the release zip from the project's releases page, close BA, and extract it over your BA folder.
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:
- Simulator, which simulator is running, or Simulator: not running.
- Frame rate, in frames per second, and Frame time, in milliseconds. While the simulator is paused or still loading it says Frame rate: no frames received, sim paused or still loading.
- Simulation rate, for example 1x, 4x or paused.
- Simulator CPU, as a percentage of all cores.
- Simulator memory and System memory.
- GPU load, Simulator video memory and GPU memory in use, where Windows can measure them.
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 mode. Press ] again to cancel.
- [ — Input mode. Press [ again to cancel.
- Escape — Cancel the active mode, when BA's window has the focus.
- Ctrl+1 — Move to the Sections list.
- Ctrl+2 — Move to the Panels list.
- Ctrl+3 — Move to the current panel's status display (it refreshes if it is empty).
- F5 — Refresh the current panel's status display without leaving the control you are on.
Output: altitude and vertical speed
- Output A — Altitude above sea level.
- Output Q — Altitude above the ground.
- Output V — Vertical speed.
- Output Ctrl+Shift+R — Last landing rate, in feet per minute.
- Output Ctrl+Shift+G — Peak g-force of the last landing.
Output: speed and heading
- Output S — Indicated airspeed.
- Output T — True airspeed.
- Output G — Ground speed.
- Output M — Mach number.
- Output H — Magnetic heading.
- Output U — True 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 Shift+H — Selected heading (or track).
- Output Shift+S — Selected speed or Mach, or that the FMS is managing it.
- Output Shift+A — Selected altitude.
- Output Shift+V — Selected vertical speed or flight path angle.
Output: navigation and distance
- Output N — NAV 1 and NAV 2: frequency, ident, localiser, glideslope and DME.
- Output D — Distance to destination, from the aircraft's FMS. Not on: MD-11.
- Output Shift+D — Distance and time to top of descent. Not on: MD-11.
- Output 1 to Output 5 — Read tracked waypoint slots 1 to 5 (see Tracking Waypoints).
- Output Ctrl+D — Distance to your selected destination runway.
- Output Ctrl+I — ILS guidance report for the destination runway.
Output: fuel, weight and configuration
What each one includes (per tank, centre of gravity) depends on the aircraft; see Readout Hotkeys.
- Output F — Fuel on board, in pounds.
- Output Shift+F — Fuel on board, in kilograms.
- Output W — Gross weight, in pounds.
- 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 "Altimeter standard".
- Output X — Transponder squawk code.
- Output Shift+T — Turn trim announcements on or off (every aircraft announces trim).
Output: weather
- Output I — Wind (see Weather).
- Output O — Outside air temperature in Celsius.
- Output Shift+R — Open the Weather Radar.
- Output Shift+M — Open the METAR report window.
- Output Ctrl+Shift+T — Open the cold temperature altitude correction calculator.
Output: time
- Output Z — Local time at the aircraft, with the time zone name.
- Output Shift+Z — Zulu (UTC) time.
Output: where you are
- Output C — Nearest city, or the water you are over.
- Output Shift+L — Open the Location Info window (see Location Info and Nearest City).
- Output Alt+Y — Where Am I: the taxiway, stand or runway you are on.
- Output Alt+L — Look Around: where you are, the apron or concourse, and the nearest buildings.
- Output Ctrl+Shift+L — Open the Surroundings window.
Output: traffic
- Output R — Announce the TCAS traffic you are tracking (see TCAS Traffic).
- Output Ctrl+R — Open the TCAS traffic window.
- Output Alt+G — Nearest ground traffic, up to three aircraft with direction and distance (see Ground Traffic). While you taxi, alerts also come by themselves at 600, 400 and 250 feet.
Output: taxi
- Output Y — Taxi status: current taxiway, next turn, distance to go (see Taxi Guidance).
- Output Ctrl+Y — Repeat the last taxi instruction.
Output: flying aids
- Output Ctrl+H — Turn Hand Fly Mode on or off.
- Output Ctrl+V — Turn Visual Guidance on or off. It needs a destination runway, but not Hand Fly mode.
- Output Ctrl+T — Turn Takeoff Assist on or off.
Output: windows and planning
- Output Shift+E — Open the Flight Planning window: route viewer, procedures and airport lookup.
- Output Shift+B — Open the SimBrief briefing.
- Output Shift+C — Open this aircraft's First Officer: its flows and checklists. Not on: HorizonSim 787 (you hear "No checklist for this aircraft.").
- Output Ctrl+M — Open this aircraft's Monitor Manager, to mute any automatic announcement.
Output: AI and display reading
- Output Alt+D — Describe the outside scene (needs an AI provider; see AI Display Reading).
- Output Alt+P, Alt+N, Alt+E, Alt+S, Alt+I — Read cockpit displays. What each does, and whether it exists, depends on the aircraft; see the aircraft sections below.
Output: ground services and networks
- Output Ctrl+G — Read the latest GSX message without opening the Access GSX window (see Gates, GSX and Docking).
- Output Ctrl+S — Read the last SayIntentions transmission.
- Output Ctrl+Shift+S — Open the SayIntentions flight information window.
- Output Alt+V — Mute or unmute VATSIM announcements.
- Output Shift+O — Open the Volanta window.
Input: teleport and planning
- Input Shift+R — Teleport to a runway (see Teleporting).
- Input Shift+G — Teleport to a gate.
- Input Shift+D — Choose a destination runway.
- Input Shift+F — Open the waypoint tracking window.
- Input Shift+X — Open the Landing Exit Planner.
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 Ctrl+H — Heading window.
- Input Ctrl+S — Speed window.
- Input Ctrl+A — Altitude window.
- Input Ctrl+V — Vertical speed window.
- Input Ctrl+P — Autopilot panel window, with live-state buttons.
- Input Ctrl+B — Altimeter window. Not on: PMDG 777. The BlueBird 757 has its own Altimeter and minimums window.
Input: aircraft windows
- Input Shift+M — Open this aircraft's MCDU, CDU or FMC window.
- Input Shift+T — Open this aircraft's EFB (see Aircraft EFBs). Not on: HorizonSim 787.
Input: taxi, GSX and SayIntentions
- Input Shift+Y — Open the Taxi Planner.
- Input Y — Continue past the hold-short point you are holding at.
- Input Ctrl+Y — Stop taxi guidance.
- Input Alt+G — Open the Access GSX window.
- Input Ctrl+Shift+Y — Build a taxi route from the last SayIntentions taxi clearance.
Keys inside shared windows
- Surroundings window, Frequencies list: Enter tunes the frequency into COM 1 standby, Shift+Enter straight into COM 1 active. Not on the A380, which tunes through its RMP window.
- Access GSX window: F5 opens the GSX menu, 1 to 9, 0 and A to E choose a menu option, C opens GSX Settings, Escape hides the window.
- SayIntentions flight information window: arrow keys read line by line, Escape closes.
- Every MCDU, CDU and FMC window except the A380's MFD: Ctrl+1 to Ctrl+6 are the left line select keys and Alt+1 to Alt+6 the right ones. With Alternate line select keys ticked in File, FMC Settings, they become F1 to F6 and F7 to F12. Alt+S jumps to the scratchpad box, Enter sends what you typed, and Alt+Home returns to the screen. The A380's MFD window has no line select keys; see its section.
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.
- 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 the destination runway.
- F — Target vertical speed and how high or low you are (Visual Guidance only; otherwise you hear "Visual guidance not active").
FlyByWire A320neo
Full explanations: FlyByWire A320neo (A32NX).
Output keys
- Output Shift+1 — Green Dot speed.
- Output Shift+2 — S speed.
- Output Shift+3 — F speed.
- Output Shift+4 — VLS.
- Output Shift+5 — VS (stall speed).
- Output Shift+6 — VFE Next.
- Output Ctrl+W — Active waypoint on the ND: name, distance and bearing.
- Output Ctrl+0 — Approach capability (CAT rating).
- Output Ctrl+E — Turn the automatic E/WD callouts on or off.
- Output Alt+E — Open the E/WD window: engines, memos and warnings.
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
- Input Shift+A — Autopilot 1 on or off.
- Input Ctrl+O — Autopilot 2 on or off.
- Input Shift+P — Approach mode.
- Input Ctrl+J — Autothrust.
- Input Ctrl+L — Localiser.
- Input Shift+1 to Shift+4 — Push the heading, altitude, speed and vertical speed knobs.
- Input Ctrl+1 to Ctrl+4 — Pull the heading, altitude, speed and vertical speed knobs.
- Input Ctrl+Shift+D — Open the DCDU (datalink) window.
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)
- Up, Down — Read the screen line by line.
- Page Up, Page Down — Scroll (flight plan, runway lists).
- Left, Right — Previous or next page of a multi-page form, when the screen has focus.
- Alt+Left, Alt+Right — Previous or next page, from anywhere in the window.
- Alt+Up, Alt+Down — Scroll.
- Backspace — Clear the scratchpad.
- Alt+I INIT, Alt+D DIR, Alt+P PROG, Alt+F F-PLN, Alt+E PERF, Alt+R RAD NAV, Alt+Shift+F SEC F-PLN, Alt+U FUEL PRED, Alt+K ATC COM, Alt+M MCDU MENU, Alt+A AIRPORT, Alt+T DATA, Alt+O OVFLY, Alt+C CLR.
DCDU window (Input Ctrl+Shift+D)
- Ctrl+1, Ctrl+2 — Left soft keys 1 and 2 (F1, F2 with alternate keys).
- Alt+1, Alt+2 — Right soft keys 1 and 2 (F7, F8 with alternate keys). Answering takes two presses: the first arms the answer, the second sends.
- Page Up, Page Down — Scroll within the message.
- Ctrl+Page Up, Ctrl+Page Down — Older or newer message.
- F5 — Refresh. Escape — Close.
Other windows
- E/WD window (Output Alt+E): arrow keys read it, F5 refreshes, Escape closes.
- flyPad EFB (Input Shift+T): your screen reader's browse mode works as on a web page; F5 refreshes.
General keys that differ or don't work here
- Output Alt+P, Alt+N, Alt+S, Alt+I do nothing. Read the PFD, ND, ISIS and System Display from their panels in the Instrument section.
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.
- Output Alt+P — The captain's PFD window. The AI read looks at the first officer's PFD.
- Output Alt+N — The captain's navigation display window, with its EFIS controls.
- Output Alt+E — The E/WD window, with T.O CONFIG, CLR, RCL and EMER CANC after the list.
- Output Alt+S — The SD window: the System Display's page, its values, STATUS and the bottom line, with the ECAM page keys after the list.
- Output Alt+I — The ISIS window, with the ISIS panel's buttons and baro knob after the list. With the three round standby gauges, always the AI read.
- Output Shift+1 to Shift+6 — Green dot, S, F, VLS, alpha prot or VSW, and VFE next, from the PFD's speed tape.
- Output Ctrl+W — The next waypoint: name, bearing, distance and time.
- Output D, Output Shift+D — Distance and time to the destination and to the top of descent, worked out from the Fenix's flight plan.
Input keys
- Input Shift+1 to Shift+4 — Push the heading, altitude, speed and vertical speed knobs.
- Input Ctrl+1 to Ctrl+4 — Pull the heading, altitude, speed and vertical speed knobs.
- Input Ctrl+Shift+D — Open the DCDU window.
- Input Ctrl+Shift+F — Open the Fenix windows list: Engines, Cabin, Failures, Fenix documents, Fenix options, PFD, ND, E/WD, SD, ISIS and DCDU. On any other aircraft you hear "This aircraft has no extra windows."
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)
- Up, Down — Read the screen line by line.
- Left, Right — Switch page sections (for example INIT A and INIT B).
- Alt+Left, Alt+Right — Previous or next section, from anywhere.
- Page Up, Page Down, Alt+Up, Alt+Down — Scroll.
- Backspace — Clear the scratchpad.
- Ctrl+Shift+L, Ctrl+Shift+R — Left (captain's) or right (first officer's) MCDU.
- Alt+I INIT, Alt+D DIR, Alt+P PROG, Alt+F F-PLN, Alt+E PERF, Alt+R RAD NAV, Alt+Shift+F SEC F-PLN, Alt+U FUEL PRED, Alt+K ATC COM, Alt+M MCDU MENU, Alt+A AIRPORT, Alt+T DATA, Alt+O OVFLY.
Fenix windows (Input Ctrl+Shift+F)
- The list: Enter opens the selected window, Escape closes the list.
- Engines: arrow keys read the values, F5 reads them again, Escape closes.
- Cabin: Ctrl+Tab moves between the Status, Audio, Doors, Temperature and Water tabs, Escape closes.
- Failures: Enter in the search box searches; Alt+N Fail now, Alt+A (or Enter on a failure) Arm, Alt+C Clear, each after a Yes or No; F5 refreshes, Escape closes.
- Fenix documents: Enter opens a document, Ctrl+F the search box, Ctrl+P the pinned ECAM procedure, Ctrl+D pins or unpins, F6 and Shift+F6 move between the document, the list and the search box, F5 reloads, Escape hides the window.
- Fenix options: Enter speaks the selected option's details; F2 changes an on/off or choice option for this simulator session, Shift+F2 makes an option permanent, Ctrl+F2 resets your change to the Fenix default; F5 reads the options again, Escape closes.
- PFD, ND, E/WD, SD and ISIS: arrow keys read the rows, which update every second; Tab reaches the controls after the list; F5 refreshes without a word, Escape closes.
- DCDU: arrow keys read the rows; Ctrl+1, Ctrl+2 the left keys and Alt+1, Alt+2 the right ones (or F1, F2, F7, F8 with the alternate setting); Page Down, Page Up scroll the message; Ctrl+Page Down, Ctrl+Page Up the next and previous message; Ctrl+P prints; Bright and Dim buttons after the list; F5 refreshes, Escape closes.
General keys that differ or don't work here
- Output Ctrl+0, Ctrl+E do nothing.
- Input Shift+A, Ctrl+O, Shift+P, Ctrl+J, Ctrl+L do nothing; use the Ctrl+P window.
FlyByWire A380X
Full explanations: FlyByWire A380X.
Output keys
- Output Shift+1 to Shift+6 — Green Dot, S, F, VLS, VS and VFE Next speeds.
- Output Ctrl+W — Active waypoint on the ND.
- Output Ctrl+0 — Approach capability: LAND 2, LAND 3 single or LAND 3 dual.
- Output Ctrl+E — Turn the automatic E/WD callouts on or off.
- Output Alt+E — Open the E/WD window.
- Output Ctrl+Shift+B — Open the Airport Map and Brake-To-Vacate (OANS) window.
- Output Ctrl+Shift+C — Open the live Electronic Checklist (ECL).
Q and A read in metres when the FCU's MTRS button is on.
Input keys
- Input Shift+A, Ctrl+O, Shift+P, Ctrl+J, Ctrl+L — Autopilot 1, autopilot 2, approach, autothrust and localiser, as on the A32NX.
- Input Shift+1 to Shift+4 and Ctrl+1 to Ctrl+4 — Push and pull the heading, altitude, speed and vertical speed knobs.
- Input Ctrl+Shift+R — Open the Radio Management Panel (RMP) window.
The Ctrl+A window adds a metric toggle, and Ctrl+P a Flight Director button.
MCDU / MFD window (Input Shift+M)
- Up, Down — Move through the lines.
- Enter — Activate the line (send the scratchpad, or open a list).
- Backspace or Alt+C — CLR.
- Delete — Clear the selected field.
- Ctrl+Up or Page Up — Previous page. Ctrl+Down or Page Down — Next page (and scrolls the F-PLN).
- F5 — Refresh.
- Alt+S — Jump to the scratchpad.
- Alt+I INIT, Alt+F F-PLN, Alt+E PERF, Alt+L FUEL & LOAD, Alt+R RAD NAV, Alt+P SEC FPL, Alt+D DIR, Alt+A ATC COM, Alt+V SURV.
- Alt+N — Switch BA's weight readouts between kilograms and pounds.
RMP window (Input Ctrl+Shift+R)
- Alt+V — VHF page. Alt+T — Transponder page. Alt+Home — Back to the screen.
- Ctrl+1 to Ctrl+3 — Select radio 1 to 3 (F1 to F3 with alternate keys).
- Alt+1 to Alt+3 — Swap that radio's active and standby (F7 to F9 with alternate keys).
- Type a frequency without the decimal and press Enter to load it into standby; Backspace deletes a digit; Alt+C clears a stuck entry.
- On the transponder page, type four digits to set the squawk; Alt+I sends IDENT.
ECL window (Output Ctrl+Shift+C)
- Up, Down — Move through the checklist.
- Enter — Open the checklist, or tick the item.
- Backspace — Back to the menu. F5 — Refresh.
OANS / BTV window (Output Ctrl+Shift+B)
- Arrow keys read the controls, Enter activates a button or opens a list, F5 refreshes, Escape closes.
General keys that differ or don't work here
- Output Alt+P, Alt+N, Alt+S, Alt+I do nothing; read the displays from the panels.
- Input Ctrl+Shift+D (DCDU) is not on the A380.
- In the Surroundings window, Enter and Shift+Enter do not tune COM 1; use the RMP window.
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
- Output Shift+1 to Shift+6 — Flap manoeuvring speeds for flaps up, 1, 5, 10, 15 and 25, at your current weight.
- Output Alt+P — Open the Primary flight display window: the Captain's PFD, read from the aircraft, as a list part by part (the FMA, the speed tape, the attitude, the altitude tape, vertical speed, heading, then the messages), with MINS mode, Minimums, MINS RST, Baro units, Altimeter, STD, FPV, MTRS, Flight director and the speed reference. No AI key needed; if BA cannot read the PFD it reads the PFD with AI instead, and if the classic EFIS display is selected it says so first.
- Output Alt+N — Open the Navigation display window: the Captain's ND, read from the aircraft, as a list from the top of the screen to the bottom, with Mode, Range, CTR, the map buttons and VOR/ADF 1 and 2. No AI key needed; if BA cannot read the ND it reads the ND with AI instead.
- Output Ctrl+W — The active waypoint as the ND shows it: name, arrival time and distance to go.
- Output Alt+E — Open the Engine displays window: the upper and lower engine displays, read from the aircraft, with MFD ENG, MFD SYS, Lower DU, Fuel Flow, N1 SET and the manual N1. No AI key needed; if BA cannot read the displays it reads the upper display with AI instead.
- Output Alt+S — Read the lower display unit (AI), whatever it is set to show.
- Output Alt+I — Read the standby instrument (AI).
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
- Input Ctrl+N — Set the NAV radios: NAV 1 and NAV 2 frequency and course.
- Input Shift+T — Captain's EFB tablet.
- Input Ctrl+Shift+T — First officer's EFB tablet.
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)
- Up, Down — Read the screen line by line.
- Page Up, Page Down, or Alt+Up, Alt+Down — Previous or next CDU page.
- Backspace — CLR when the scratchpad has text, DEL when it is empty.
- Alt+I Init Ref, Alt+R RTE, Alt+A Dep/Arr, Alt+F Fix, Alt+G Legs, Alt+H Hold, Alt+P Prog, Alt+M Menu, Alt+B CLB, Alt+Z CRZ, Alt+D DES, Alt+N N1 Limit, Alt+E or Ctrl+Enter Execute, Alt+C CLR/DEL.
General keys that differ or don't work here
- Output Ctrl+0, Ctrl+E do nothing.
- Input Shift+A, Ctrl+O, Shift+P, Ctrl+J, Ctrl+L and the Shift/Ctrl+number knob keys do nothing; use the Ctrl+P window and the MCP windows.
PMDG 777
Full explanations: PMDG 777. The keys are those of the PMDG 737 except:
- Output Shift+1 to Shift+5 — Flap manoeuvring speeds for flaps up, 1, 5, 15 and 20. There is no Shift+6.
- Output Alt+E reads the upper EICAS, and Alt+S the lower display, whatever page it shows.
- Output Alt+N reads the navigation display with AI; there is no Navigation display window, and Output Ctrl+W does nothing.
- Output Shift+V reads vertical speed or flight path angle; the Ctrl+V window has V/S and FPA modes.
- With Enhanced distance announcements on in FMC Settings, Output D and Shift+D read the CDU's PROG page. This works on the 777 only, not the 737.
- Input Ctrl+B and Input Ctrl+N do nothing on the 777.
- The Ctrl+P window is the 777 Autopilot: AP left and right, both flight directors, both A/T arms, approach, LOC, A/T, disengage bar, disconnects and bank limit.
- The CDU window can also show the centre CDU. Its page keys differ: Alt+D is Dep/Arr, Alt+A Altn, Alt+V VNAV, Alt+O FMC Comm and Alt+N Nav Rad, and there are no CLB, CRZ, DES or N1 Limit keys (no Alt+B or Alt+Z).
HorizonSim 787-9
Full explanations: HorizonSim 787-9.
Output keys
- Output Alt+E — Open the EICAS window: engines and every active alert. No AI key needed.
- Output Alt+S — Open the System Synoptic Display window. No AI key needed.
- Output Alt+P, Alt+N, Alt+I — Read the PFD, navigation display and standby instrument by AI. Put those displays on screen in a cockpit view first; BA does not move the camera on this aircraft.
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)
- Up, Down — Read the screen line by line.
- Page Up, Page Down, or Alt+Up, Alt+Down — Previous or next page.
- Ctrl+Enter or Alt+E — EXEC.
- Backspace or Alt+C — CLR when there is text, DEL when the scratchpad is empty.
- Ctrl+Backspace — Clear the whole scratchpad.
- 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+N NAV/RAD.
EICAS and synoptic windows
- Arrow keys read them; F5 refreshes the synoptic; Escape closes.
General keys that differ or don't work here
- Output Shift+1 to Shift+6, Ctrl+W, Ctrl+0, Ctrl+E do nothing.
- Input Shift+T says "787 EFB not available."
- Input Shift+A, Ctrl+O, Shift+P, Ctrl+J, Ctrl+L and the Shift/Ctrl+number knob keys do nothing; use the Ctrl+P window.
iFly 737 MAX8
Full explanations: iFly 737 MAX8.
Output keys
- Output Shift+1 to Shift+6 — Flap manoeuvring speeds for flaps up, 1, 5, 10, 15 and 25, calculated from your weight.
- Output Alt+P, Alt+N, Alt+I — Read the PFD, navigation display and standby (AI).
- Output Alt+E — Read the engine display and crew alerts (AI).
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
- Input Ctrl+N — Set the NAV radios: NAV 1 and NAV 2 frequency and course.
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)
- Arrow keys read the screen. The CDU Unit list switches between left and right.
- Page Up, Page Down — PREV and NEXT PAGE.
- Alt+E or Ctrl+Enter — EXEC.
- Alt+C, or Backspace on the screen — CLR when there is text, DEL when empty.
- Delete or Alt+X — DEL.
- Escape — Close.
- Alt+I INIT REF, Alt+R RTE, Alt+A or Alt+D DEP ARR, Alt+T ATC, Alt+V VNAV, Alt+F FIX, Alt+G or Alt+L LEGS, Alt+H HOLD, Alt+O FMC COMM, Alt+P PROG, Alt+M MENU, Alt+N N1 LIMIT.
General keys that differ or don't work here
- Output Alt+S, Ctrl+W, Ctrl+0, Ctrl+E do nothing.
- Input Shift+A, Ctrl+O, Shift+P, Ctrl+J, Ctrl+L and the Shift/Ctrl+number knob keys do nothing; use the Ctrl+P window and the MCP windows.
BlueBird 757-200
Full explanations: BlueBird 757-200.
Output keys
- Output Shift+H, Shift+S, Shift+A, Shift+V — Read the MCP's own heading, speed or Mach, altitude and vertical speed, each followed by the MCP mode buttons that are lit.
- Output Shift+1 to Shift+5 — Flap maneuver speeds for flaps up, 1, 5, 15 and 20: the FMC's own once PERF INIT is done, calculated from your current weight before (they then end in calculated).
- Output Shift+6 — VREF 30 and VREF 25, the FMC's own or calculated in the same way.
- Output D — Distance and time to the destination, from the First Officer's CDU PROGRESS page.
- Output Shift+D — Distance and time to the top of climb, the top of descent or a step climb, from the same page.
- Output N — The nav radios: VOR L and VOR R, the ILS course and the ILS frequency.
- Output Alt+E — Open the Upper EICAS window: engine indications, thrust reference and every message, with Cancel, Recall and Max Ind. No AI key needed; if BA cannot read the display it reads it with AI instead.
- Output Alt+S — Open the Lower EICAS window: the page it shows and its values, with Engine and Status buttons. AI read when BA cannot read it.
- Output Alt+N — Open the EHSI window: the Captain's map display as a list, with Mode, Range, CTR, TFC and the map options. AI read when BA cannot read it.
- Output Ctrl+W — The active waypoint as the EHSI shows it: name, distance and time.
- Output Alt+P — Open the ADI window: the flight mode annunciator, then the Captain's ADI as a list (the speed tape, the attitude and flight director, the glideslope, the radio altitude and minimums, the localizer), with its flags spoken as they appear and go. AI read when BA cannot read it.
- Output Shift+C — Open the 757's First Officer.
- Output Ctrl+M — Open the 757 Monitor Manager.
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
- Input Ctrl+H — MCP Heading window (0 to 360), with HDG SEL, HDG HOLD and LNAV buttons.
- Input Ctrl+S — MCP Speed window (100 to 399 knots, or Mach 0.40 to 0.86), with Speed Intervene, IAS/MACH, SPD, THR and FLCH buttons.
- Input Ctrl+A — MCP Altitude window (100 to 49000, rounded to 100 feet), with ALT HOLD, VNAV and FLCH buttons.
- Input Ctrl+V — MCP Vertical Speed window (minus 8000 to 6000, rounded to 100), with a V/S button.
- Input Ctrl+B — Altimeter and minimums window: the three altimeters (inches or hectopascals), a Standard button, and the radio minimums in feet.
- Input Ctrl+N — 757 Nav Radios window: the ILS course, the ILS frequency and an ILS park button.
- Input Ctrl+P — 757 Autopilot window: the flight mode annunciator as a list, then CMD L, C and R, A/T Arm, both F/D switches, the mode buttons, Speed Intervene, A/T Disconnect and A/P Disconnect, each with its key.
- Input Shift+M — Open the CDU window.
- Input Shift+T — Open the EFB window: BlueBird's tablet, or BlueBird's settings when the simulator is closed.
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)
- Alt+L CMD L, Alt+C CMD C, Alt+R CMD R, Alt+A A/T Arm, Alt+F Captain F/D, Alt+O F/O F/D.
- Alt+T THR, Alt+S SPD, Alt+N LNAV, Alt+V VNAV, Alt+H FLCH, Alt+D HDG HOLD, Alt+E ALT HOLD, Alt+Y V/S, Alt+G LOC, Alt+P APP.
- Alt+I Speed Intervene, Alt+X A/T Disconnect, Alt+B A/P Disconnect (the Captain's yoke button; press it again to silence the warning).
- Escape — Close.
Nav radios window (Input Ctrl+N)
- Alt+I, then Enter in the ILS course box — Set the ILS course (0 to 360).
- Alt+F, then Enter in the ILS frequency box — Set the ILS frequency (108.10 to 111.95).
- Alt+P — ILS park.
- Escape — Close.
CDU window (Input Shift+M)
- Up, Down — Read the screen line by line.
- Ctrl+Tab — Switch between the Captain's and the First Officer's CDU. Ctrl+Shift+L — The Captain's. Ctrl+Shift+R — The First Officer's.
- Ctrl+1 to Ctrl+6 — Left line select keys. Alt+1 to Alt+6 — Right line select keys.
- Page Up, Page Down, or Alt+Up, Alt+Down — PREV and NEXT page.
- Ctrl+Enter or Alt+E — EXEC.
- Alt+S — Scratchpad box; Enter sends it. Alt+Home — Back to the display.
- Backspace — CLR. Delete — DEL. Both work on the display or in an empty scratchpad box. Alt+C — Clear the whole scratchpad.
- Escape — Close.
- Alt+I INIT REF, Alt+R RTE, Alt+D DEP ARR, Alt+T ATC, 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.
Display windows (Output Alt+P, Alt+E, Alt+S, Alt+N)
- Up, Down — Read the display line by line. Tab — Move to the controls after the list.
- ADI: the list only, no controls.
- Upper EICAS: Alt+C Cancel, Alt+R Recall, Alt+M Max Ind.
- Lower EICAS: the Engine and Status buttons, reached with Tab.
- EHSI: Alt+M Mode, Alt+R Range, Alt+C CTR, Alt+T TFC, Alt+W WXR, Alt+E TERR, Alt+N NAV AID, Alt+A APRT, Alt+D DATA, Alt+P WPT.
- Escape — Close.
EFB window (Input Shift+T)
- Your screen reader's browse mode works as on a web page: headings, buttons, check boxes, lists and edit boxes.
- Enter or Space on a button — Press it on the tablet.
- Enter in an edit box — Type it on the tablet. Leaving the box without Enter changes nothing.
- F5 — Read the tablet again.
- Alt+F4 — Close.
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)
- Enter in the Altimeter box — Set all three altimeters (29.92 or 1013).
- Standard, 29.92 — Set all three to standard.
- Enter in the Radio minimums box — Set the decision height (feet, 0 to 2500).
- Escape — Close.
General keys that differ or don't work here
- Output Ctrl+0, Ctrl+E do nothing.
- Input Shift+A, Ctrl+O, Shift+P, Ctrl+J, Ctrl+L, the Shift/Ctrl+number knob keys and Input Ctrl+Shift+T do nothing. The engage buttons are in the Ctrl+P window and on the Glareshield section's MCP panel; the four MCP values are set in the Ctrl+H, Ctrl+S, Ctrl+A and Ctrl+V windows.
TFDi MD-11
Full explanations: TFDi MD-11.
Output keys
- Output Shift+1 — Slat retraction speed.
- Output Shift+2 — Flap retraction speed.
- Output Alt+P — Read the captain's PFD, flight mode annunciator first (AI).
- Output Alt+N — Read the captain's navigation display (AI).
- Output Alt+E — Read the engine and alert display, the EAD (AI).
- Output Alt+S — Read the system display, whatever page it shows (AI).
- Output Alt+I — Read the standby instrument (AI).
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
- Input Shift+1, Ctrl+1 — Push or pull the heading knob.
- Input Shift+2, Ctrl+2 — Push or pull the altitude knob.
- Input Shift+3, Ctrl+3 — Push or pull the speed knob.
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:
- Alt+O — Approach/Land.
- Alt+P — PROF.
- Alt+U — Altitude Unit.
- Alt+W — Wheel up. Alt+D — Wheel down.
- Shift+Tab from the Autoflight button — the live status list.
MCDU window (Input Shift+M)
- Ctrl+Shift+L, Ctrl+Shift+C, Ctrl+Shift+R — Left, centre or right MCDU.
- Backspace or Alt+C — Clr, one character.
- Delete — Clear the whole scratchpad.
- Page Up, Alt+Up — Slew up. Page Down, Alt+Down — Slew down.
- Right (on the screen) or Alt+Right — Next page.
- Alt+I Init, Alt+E Perf, Alt+F Fpln, Alt+Shift+F Sec Fpln, Alt+P Prog, Alt+R Ref, Alt+N Nav Rad, Alt+X Fix, Alt+D Dir Intc, Alt+T To Appr, Alt+O Eng Out, Alt+M Menu.
The MD-11 has no EXEC, DEL or PREV PAGE key, like the real aircraft.
General keys that differ or don't work here
- Output D, Shift+D, Shift+3 to Shift+6, Ctrl+W, Ctrl+0, Ctrl+E do nothing. V1, VR and V2 are in the Read-outs section.
- Input Shift+4 and Ctrl+4 do nothing (the vertical speed wheel is in the Ctrl+P and Ctrl+V windows).
- Input Shift+A, Ctrl+O, Shift+P, Ctrl+J, Ctrl+L do nothing; use the Ctrl+P window.