MSFS Blind Assist

Boeing Aircraft and the MD-11

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

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

This chapter covers the PMDG 737 (NG3 family), the PMDG 777, the HorizonSim 787-9, the iFly 737 MAX8, the BlueBird 757-200 and the TFDi Design MD-11, describing only what differs on each. The complete key list for every aircraft is in the Hotkey Reference, and the shared autopilot window behaviour is in Autopilot Windows. All but the HorizonSim 787-9 have a First Officer on Output Shift+C.

PMDG 737 (NG3)

BA supports the whole PMDG 737 NG3 family — the 737-600, -700, -800 and -900 — with one set of panels. The panels, the autopilot windows, both CDUs and the EFB all work on every variant.

Before you fly

The PMDG 737 talks to BA through PMDG’s SDK data broadcast, which PMDG ships switched off; until it is on, the CDU window and most cockpit readouts stay empty. It is set once per variant, in that variant’s 737_Options.ini. BA checks every installed variant for you and opens the PMDG 737 SDK setup window when lines are missing; see The PMDG SDK Setup Check. The PMDG 737 does not need the MobiFlight WASM module.

How the panels are organised

Press Ctrl+1 for the Sections list and Ctrl+2 for the Panels list. The 737 has five sections:

A few panels deserve a word:

The MCP panel holds the engage buttons — the flight directors, autothrottle arm, bank limit, disengage bar, CMD A and B, CWS A and B, Approach and VOR LOC. The heading, speed, altitude and vertical speed values are not typed on the panel; you set them with the autopilot windows below.

Autopilot: the MCP windows

All in input mode:

Type a value and press Enter to set it. The windows stay open afterwards, so you can enter several values in a row. When the MCP value changes, BA reads it back, for example “MCP: heading 270” or “MCP: altitude 12000 feet”.

In the heading, speed, altitude and vertical speed windows, a button press that works is confirmed three ways: your screen reader reads the button’s new label, and you hear the MCP light, such as “MCP: Level Change: engaged”, and the mode change on the FMA, such as “FMA: Pitch: MCP SPD”. BA adds nothing, so none of them is cut off. If a press changes nothing, BA reads the button back about 3 seconds later, for example “Level Change Off”. Altitude Intervene, and Speed Intervene outside VNAV, show no state, so pressing one is confirmed straight away, for example “Altitude Intervene pressed”.

To read the MCP without opening anything, use output mode: Shift+H says, for example, “Heading 270, HDG SEL”; Shift+S says the speed with ”, LVL CHG” when level change is on, or “Speed managed by FMC” when the window is blank; Shift+A adds VNAV, LVL CHG or ALT HOLD; Shift+V says “VS -1500 feet per minute, engaged” or “Vertical Speed window blank”.

The CDU

Press Input Shift+M to open the PMDG 737 CDU window. The 737 has two CDUs; the CDU selector at the top switches between Left (Captain) and Right (First Officer).

The status line says CDU Connected, CDU Not Powered or CDU Not Connected. If it never connects, check the SDK setup above.

FMC Settings offers alternate line select keys (F1 to F12). Its enhanced PROG-page distance announcements apply to the 777 only, not the 737.

The EFB

Input Shift+T opens the Captain’s tablet and Input Ctrl+Shift+T the First Officer’s. The window is titled PMDG 737 EFB and works like the other EFB windows described in Aircraft EFBs. You get the whole tablet: Dashboard, Preferences, Navdata, Performance, Ground Ops, Weights and Balance and Manuals. Nothing needs installing in your Community folder, and no simulator restart is needed.

Some useful details:

Special windows and readouts

The Engine displays window

Output Alt+E opens Engine displays: the two engine display units in the middle of the panel, read straight from the aircraft, no AI needed. Press Tab to move through:

  1. Upper display and 2. Lower display: two lists that follow the real displays. The first line names what the display shows, for example “Upper display: primary engine page” or “Lower display: SYS page”; a page BA does not read is only named, such as “navigation display”, “blank” or “off”. The lines after it are the page’s rows, in the display’s order and wording, both engines on one line, engine 1 first: “N1: 21.0, 21.0”, “EGT: 466, 466”, “FF: 0.67, 0.67”, “Alerts: engine 1 LOW OIL PRESSURE”, “FUEL LB: 1: 8.63, CTR: 7.81, 2: 8.63, TOTAL: 25.1” on the upper display, and N2, fuel flow, oil pressure, temperature and quantity and vibration on the lower. Fuel and fuel flow are in thousands, as printed, in KG if PMDG is set to kilograms. A colour shows only when it is not normal, after its engine’s value, as in “EGT: 960 red, 466”, and so do messages such as REV, TAI, ENG FAIL, X-BLD START and LO. A reading the display leaves empty is blank. The lists update every second without losing your place.
  2. MFD ENG and 4. MFD SYS: choose the lower display’s page; BA reads back what it shows.
  3. Lower DU Captain: ENG PRI, NORM or ND, as on the panel. The displays follow PMDG’s logic: on ND the engine pages share the upper display (“compact engine page”); back on NORM the lower display stays blank until you press MFD ENG, sometimes twice.
  4. Fuel Flow Used and 7. Fuel Flow Reset, as in the Instruments panel.
  5. N1 SET: 2, 1, AUTO or BOTH.
  6. Manual N1: type the N1 reference and press Enter, as with the Instruments panel’s Manual N1 button. Tab skips it while N1 SET is on AUTO.

Escape closes the window. On ground power the displays stay blank for about half a minute while they start, as in the real aircraft, and the lists say so. If BA cannot read the displays, Alt+E reads the upper display with AI instead, without saying anything first; while BA is still finding them, the window opens and says “Engine displays starting”.

The Navigation display window

The navigation display (ND) is the Captain’s second screen, beside the PFD: a moving map of the route ahead, with the aircraft’s speeds and the wind in the top corners, the next waypoint at the top right, and whatever the map buttons add: navaids, fixes, airports, traffic. Output Alt+N opens Navigation display, read straight from the aircraft, no AI needed. It shows what the Captain’s ND shows right now, so it is also a way to learn what the ND looks like and what each knob and button does to it.

The four modes. The mode knob on the EFIS control panel turns the ND into one of four pictures:

The list. The first item in the window, Captain ND, lists the screen from top to bottom, each line starting with where it sits, in the ND’s own words. On the ground before departure it might read:

What the map lines name:

What the list leaves out. Three pictures on the ND are not described, only whether they are on:

In APP and VOR. These two pictures are heading-up: the top of the screen is where the nose points, so the top centre prints the heading, “Top centre: HDG 268 MAG”, and every “left” or “right” below is measured from the nose. The header, the top left, the bottom corners and the messages read as in MAP. In place of the map, the list has the approach picture, and what is drawn across the compass starts with “Centre:”. With an ILS tuned in APP it might read:

If a PMDG update changes how the ND draws these pictures and BA no longer recognises them, the list says “ILS data: not read: PMDG file not recognised” in APP, or “VOR data: not read: PMDG file not recognised” in VOR, between the top centre line and the bottom corners. MAP and PLN still work. In the same way, if BA no longer recognises the bearing pointers and POS, the list says “Pointers and POS: not read: PMDG file not recognised” wherever the ND would draw them.

The list updates every second without losing your place, and speaks only when you move through it.

The controls. Press Tab after the list to reach them:

  1. Mode: APP, VOR, MAP or PLAN, as on the EFIS panel.
  2. Range: 5 to 640 nautical miles. In MAP that is the distance to the compass arc ahead; centred, the arc around the aircraft covers half of it.
  3. CTR: changes the map in three presses: centred (the aircraft in the middle, the full compass rose around it), then centred with the vertical situation display (VSD) at the bottom, then back to normal. The button shows which: “CTR: normal”, “CTR: centred”, “CTR: VSD on”.
  4. TFC, WXR, STA, WPT, ARPT, DATA, POS, TERR: the map buttons, each showing on or off. TFC shows traffic, WXR the weather radar picture, STA navaids, WPT fixes (up to range 40), ARPT airports, DATA each waypoint’s constraint and time, POS the lines toward the VORs and ADFs and the IRS and GPS positions, TERR the terrain picture. The window does not describe the weather or terrain pictures, only that they are on (see “What the list leaves out” above).
  5. VOR/ADF 1 and VOR/ADF 2: VOR, OFF or ADF, the bottom corners’ switches.

When you press a button, its label changes to the new state as the aircraft reports it, and your screen reader reads it, for example “STA: on”. If the press does not take, the label stays as it was, and after 3 seconds BA says the state that stayed, for example “STA off”, so a press is never silent. The EFIS control panel in the panels is unchanged; CTR and the map buttons are in this window. Escape closes it.

Output Ctrl+W says the active waypoint as the ND’s top right shows it, “EMPAD, 1533.3Z, 6.8 NM”, or “No active waypoint”, even when no display is showing the ND.

If BA cannot read the ND, Alt+N describes it with AI instead, without saying anything first; while BA is still finding it, the window opens and says “Navigation display starting”.

The Primary flight display window

The primary flight display (PFD) is the Captain’s main flight instrument, the screen in front of the Captain. It shows how the aircraft is flying right now: the speed on a tape down the left side, the attitude in the middle (how far the nose is above or below the horizon, and how far the wings are banked), the altitude on a tape down the right side with the vertical speed beside it, the heading along the bottom, and the flight mode annunciator (FMA) across the top. Output Alt+P opens Primary flight display, read straight from the aircraft, no AI needed.

How the PFD shows numbers. The speed and the altitude are each a ruler that slides up and down behind a fixed box. The box in the middle prints the current value; the ruler above the box holds higher values, below it lower ones. Marks on the ruler, called bugs, show values that matter, such as the speed you selected on the MCP, V1 or a flap speed. A bug sits on the ruler at its value, so as the aircraft speeds up the ruler slides down and the bug slides toward the box. Coloured stretches of the ruler, bands and bars, mark speeds or altitudes to stay away from. Only part of each ruler is visible at a time. The list says where each bug or band is compared with the box: “selected speed bug, 150, 10 below” is 10 knots below the current speed, and “at the current speed” means it is level with the box. A bug whose value is off the visible part is not drawn, except a few that PMDG parks at the end of the ruler, which the list gives as “at the top edge” or “at the bottom edge”. The heading scale along the bottom works the same way, sideways: “3° right” of the heading. The ruler’s own numbers are never listed.

The list. The first item in the window, Captain PFD, lists the screen part by part, each line after the FMA starting with the part it is in, in the PFD’s own words. On final approach on an ILS with the autopilot on, flaps 15 and about 1,500 feet above the ground, it might read:

When an instrument fails, or has no data yet, PMDG removes it and draws an amber flag in its place, and the list puts the flag there too: “Speed tape: SPD flag”, “Attitude: ATT flag” (before the IRS is aligned), “Altitude tape: ALT flag”, “Vertical speed: VERT flag”, “Heading: HDG flag”, and FPV, F/D, RA, LOC, G/S and DME in the attitude. “Attitude: PULL UP” and “Attitude: WINDSHEAR” are listed where PMDG draws them.

Some states replace the whole list with one line: “Captain PFD: off” while the displays are dark, “Captain PFD: not on any display” when the display selectors have moved it off every screen, “Captain PFD: classic EFIS display, not read” if the Captain’s screen switches to PMDG’s classic EFIS look, “Primary flight display starting” while BA finds it, and “Primary flight display stopped” and the reason when it cannot read it for a moment. The list updates every second without losing your place, and speaks only when you move through it.

What the list leaves out: the ruler’s numbers, where the single-cue flight director points, the angle of attack dial’s arc, the heading marks along the horizon, and the FMC’s runway line in the approach info.

The controls. Press Tab after the list to reach them, all on the Captain’s side:

  1. MINS mode: RADIO or BARO, as on the EFIS panel. PMDG moves the First Officer’s selector with it, so you may hear the First Officer’s line as well.
  2. Minimums: type the minimums in feet and press Enter. BA turns the knob and says what the PFD then shows, “Minimums: BARO 300”, with ”, not shown” when the minimums display is off. The EFIS Captain panel’s Captain Minimums field does the same. Both need this reader: without it they say “Minimums need the PFD reader”.
  3. MINS RST: on the 737 this button turns the minimums display on or off; with no minimums set it sets BARO 200 or RADIO 50. BA says what the PFD then shows, “Minimums: BARO 200” or “Minimums: off”.
  4. Baro units: IN or HPA.
  5. Altimeter: type the setting and press Enter, as in the Ctrl+B dialog: “Altimeter: 1013, 29.91”.
  6. STD, FPV, MTRS and Flight director (the Captain’s FD switch): each shows on or off as the aircraft reports it, and your screen reader reads the new state when you press it. If the press does not take, the label stays as it was, and after 3 seconds BA says the state that stayed, for example “FPV off”. STD also gets the altimeter callout, and waits with “Still setting altimeter, please wait.” while the altimeter knob is turning.
  7. Speed reference: SET, AUTO, V1, VR, WT, VREF or BUG, the speed reference selector.
  8. Speed reference value: with the selector on V1, VR, WT, VREF or BUG, type the value and press Enter. BA turns the knob until the PFD shows it and says it, “V1 140”. Tab skips the field on SET and AUTO.

Escape closes the window, and a speed reference value still turning stops.

What BA says by itself. Each message as it appears and goes, “PFD message: ALT DISAGREE”, “PFD message gone: ALT DISAGREE”, including the flags that replace an instrument, “PFD message: SPD”. WINDSHEAR and PULL UP are not spoken, since the aircraft calls them out. Nothing interrupts anything else, and BA is quiet while the displays are dark, while the Captain’s PFD is on no screen, and for the first ten seconds after the displays light up. Mute PFD messages in Ctrl+M to silence all of it, BA’s own “PFD announcements stopped”, “unavailable” and “resumed” messages included.

If BA cannot read the PFD, Alt+P describes it with AI instead, without saying anything first. With PMDG’s classic EFIS look on the Captain’s screen, it says “Classic EFIS is selected, falling back to AI reading”, then uses AI. While BA is still finding the PFD, the window opens and says “Primary flight display starting”.

With an AI provider set up, the other output mode keys describe the displays, moving the camera for you as described in AI Display Reading: Alt+S the lower display unit, and Alt+I the standby (ISFD); Alt+P, Alt+N and Alt+E use AI only when BA cannot read those displays itself. Alt+S names which page the lower display is showing first, since it can show engine data or a navigation display.

Aircraft-specific hotkeys and callouts

Highlights (the full list is in the Hotkey Reference):

What BA announces by itself:

Some engine messages come from three different places in the cockpit, and you hear each of them, for example during an engine start or on landing:

| What you hear | Where it comes from | | — | — | | “Upper DU alert: engine 1 START VALVE OPEN” | The message printed on the upper engine display, as the crew sees it. | | “Engine 1 REVERSER: on” | The amber light on the overhead engine panel. | | “Engine 1 Start Valve: Open” | The valve’s real position from PMDG’s data; no cockpit light shows it. |

Things to know

PMDG 777

BA supports the PMDG 777 variants — the 777-200ER, 777-200LR, 777F freighter and 777-300ER — with one set of panels, three CDUs, the EFB, an MCP set of windows and a System Display that reads the synoptic pages as text.

Before you fly

The 777 needs the same one-time SDK setup as the 737, in each variant’s 777_Options.ini, plus the extra EnableCDUBroadcast.2=1 line for its centre CDU. BA checks for you and opens the PMDG 777 SDK setup window; see The PMDG SDK Setup Check. The 777 does not need the MobiFlight WASM module.

How the panels are organised

The 777 has seven sections:

Things that help when you are finding your way:

Autopilot: the MCP windows

All in input mode:

The output mode readouts work as on the 737: Shift+H, Shift+S, Shift+A and Shift+V, including the HDG/TRK mode and the VS/FPA state. Turning a hardware MCP knob also speaks the new value.

The CDU

Input Shift+M opens the PMDG 777 CDU window. The CDU selector offers Left (Captain), Center and Right (First Officer). Everything else works as on the 737 CDU. The 777’s page keys are Alt+I Init Ref, Alt+R RTE, Alt+D Dep/Arr, Alt+A Altn, Alt+V VNAV, Alt+F Fix, Alt+G Legs, Alt+H Hold, Alt+O FMC Comm, Alt+P Prog, Alt+M Menu, Alt+N Nav Rad, Alt+E Execute and Alt+C CLR/DEL. The alternate line select keys and enhanced distance announcements in File, FMC Settings apply here too.

The EFB

Input Shift+T opens the Captain’s tablet and Input Ctrl+Shift+T the First Officer’s, in a window titled PMDG 777 EFB. The 777 tablet is the same application as the 737’s, so everything said in The EFB for the 737 applies: Dashboard, Preferences, Navdata, Performance, Ground Ops, Weights and Balance and Manuals, all readable and usable.

The System Display

The real 777 has synoptic pages on its lower display. BA gives you the same pages as text, read live, with no AI needed.

  1. Open the Displays section (Ctrl+1) and the System Display panel (Ctrl+2).
  2. Choose a page in the System Display Page list: Engine, Status, Electrical, Hydraulics, Fuel, Air, Doors, Gear or Flight Controls.
  3. Press Ctrl+3 to move to the status display and arrow through the lines. They refresh by themselves while you read.

What each page shows:

Weights and fuel are given in both pounds and kilograms, for example “85000 pounds (38555 kg)”. Some things simply are not available from the aircraft, so they are not on these pages: oxygen, water, brake temperatures, tyre pressures, APU details, generator loads and the EICAS message text.

Aircraft-specific hotkeys and callouts

The automatic announcements are the same family as the 737’s: MCP values and modes (with FLCH, HDG HOLD, VS/FPA and LOC), Master Warning and Caution, annunciators on and off, V-speeds as entered, speed brake at rest, flaps, APU, IRS, altimeter, COM and squawk changes. Stabiliser trim is spoken in units, matching the FMC and the control stand indicator, to the nearest quarter unit: “Trim 5.25 units”.

Things to know

HorizonSim 787-9

BA supports the HorizonSim 787-9 in both MSFS 2020 and MSFS 2024. It reads the FMC and the alerting system straight from the aircraft’s own displays.

Before you fly

No Community folder bridge and no SDK file are needed. Older versions of BA installed a bridge package for the 787; BA now removes it automatically if it finds it.

Install the free MobiFlight WASM module all the same (see Installing). The FMC, the EICAS and most controls work without it, but a number of switches are worked through it: the batteries, the engine and APU generators, the avionics master, probe heat, antiskid, the logo and wing lights, the bleed air and hydraulic pump switches, and the altitude intervention (Alt INTV) button. Without the module those do nothing, and on the 787 BA does not warn you, so if one of them never moves, check MobiFlight first.

The FMC window needs the aircraft’s displays powered, and the CDU showing on one of the multi-function displays (it appears on the third MFD by default).

How the panels are organised

Some highlights:

Autopilot: the MCP windows

All in input mode:

Turning an MCP knob on your own hardware speaks the new selected value, so you get the same confirmation whether you use BA’s windows or a physical panel.

The FMC

Input Shift+M opens the 787-9 FMC window. It works like the PMDG CDU windows: Up and Down arrow read the lines, Page Up and Page Down change pages, Ctrl+1 to 6 and Alt+1 to 6 are the line select keys (or F1 to F12 with the alternate keys from File, FMC Settings), Alt+S goes to the scratchpad and Enter sends, and Alt+Home goes back to the display.

The 787 adds:

The status line tells you what is wrong if the screen is empty: “FMC not connected — load the HorizonSim 787 and power its displays.” or “FMC connected — show the CDU on an MFD screen (it renders on MFD 3 by default).”

The EFB

There is no EFB support on the 787. Its tablet’s input fields cannot be filled in from outside the simulator, so it could not be made usable. Input Shift+T says “787 EFB not available.” Use The Flight Planning Window (Shift+E) and SimBrief for planning instead.

Special windows: EICAS and the synoptic display

The 787 does not need an AI key to read its main engine and alert display:

With an AI provider, Output Alt+P, Alt+N and Alt+I describe the PFD, navigation display and standby instrument. On the 787 BA does not move the camera for you, so first set the simulator to a cockpit view where those displays are on screen.

Aircraft-specific hotkeys and callouts

Automatic announcements include Master Caution and Warning, autopilot modes, hydraulics, anti-ice, the IRS (“IRS Left On”, “IRS aligning”, “IRS aligned”), selected MCP values, and the usual altimeter, COM and squawk changes. Some one-off events have their own short callouts: “TOGA Active”, “Autopilot Disconnected”, “Glideslope active” when the approach captures the glideslope, “Fuel Balance Fault”, and “Fire Bottle 1 discharged” (or 2) and “Cargo Fire Discharged” after a fire bottle is fired.

Things to know

iFly 737 MAX8

BA connects to the iFly 737 MAX8 through iFly’s own official SDK, which comes with the aircraft. It reads the aircraft directly and sends commands through the iFly plugin.

Before you fly

How the panels are organised

Highlights:

Autopilot: the MCP windows

All in input mode:

Output Shift+S reads blank when the FMC owns the speed.

The FMC

Input Shift+M opens the iFly 737 FMC window, laid out like the PMDG 737 CDU. The CDU Unit list switches between Left (Captain) and Right (First Officer).

The EFB

Input Shift+T opens the iFly SP1 tablet, titled iFly 737 EFB, in a built-in browser. It loads by itself — there is no address or Connect button — and says “iFly EFB loaded.” The tablet’s own pages are proper web pages, so your screen reader reads them normally: Performance, Navigraph and SimBrief, Payload and Balance, Ground Services (including pushback), Doors, Failures, Cabin Voice and Settings. F5 reloads.

Fuel and payload on the iFly are set from the EFB’s Payload and Balance page.

If the tablet cannot be reached — the simulator is not running, the aircraft is still loading or the iFly EFB program has not started — the window shows a message explaining why and puts focus on a Retry button. Press it once the EFB is ready.

Aircraft-specific hotkeys and callouts

What BA says by itself:

Things to know

BlueBird 757-200

BA supports the BlueBird Simulations 757-200, with either engine type, with one set of panels that follows the real cockpit, MCP value windows and an autopilot window, an altimeter and minimums window, a nav radios window, both CDUs read as text, BlueBird’s tablet read aloud and operated like a web page, windows that read the ADI, the upper EICAS, the lower EICAS and the EHSI straight from the aircraft, spoken flight mode annunciations, ADI flags and EICAS messages, and a First Officer. Read Things to know before your first flight.

Before you fly

The 757 needs two things running besides the simulator:

The aircraft always loads cold and dark, wherever you start. Bring it up from the panels, let the First Officer run its Power Up flow, or load one of BlueBird’s cockpit presets on the tablet (the Aircraft app’s Cockpit presets page in the EFB window). With BlueBird’s Initial chocks in place setting on, the wheel chocks are on at every load: remove them on the tablet’s Ground services page before you taxi. The Status panel’s Chocks row says where they are.

BlueBird’s own settings, such as your SimBrief ID, rudder or tiller steering and the callouts, can be changed with the simulator closed: see BlueBird’s settings.

How the panels are organized

Press Ctrl+1 for the Sections list and Ctrl+2 for the Panels list. Every regular switch, knob and button of the cockpit is on a panel, named as on the aircraft and grouped as in the real cockpit. In each section the panels follow the preflight flow, and inside a panel the controls you use most come first. The 757 has six sections:

The aircraft comes with Pratt & Whitney or Rolls-Royce engines, and BA shows only what your aircraft has. It tells the two apart by the letters PW or RR in the aircraft’s title. The Engines panel lists the fuel control switches of your engine type, and the Electronic engine control (RR) panel is there only on a Rolls-Royce. A livery whose title names neither gets both sets.

A few panels deserve a word:

How the controls behave:

Autopilot: the MCP windows

All in input mode:

Type a value and press Enter. Each window stays open for the next value, and Escape closes it. About a second later BA reads the value back from the MCP: “Heading 090”, “Speed 250”, “Altitude 12000” or “Vertical speed minus 1500”. You hear what the MCP took, not what you typed, so a different number means the aircraft did not accept yours. BA sets a speed by turning the MCP’s speed knob for you, which takes a few seconds; it checks the result and corrects it before it speaks.

Mach. In the speed window, type a Mach number as 0.78, .78 or M.78. If the MCP is showing knots, BA presses IAS/MACH for you first, then sets the Mach and reads it back: “Mach 0.78”. A speed in knots typed while the MCP shows Mach changes it back the same way. When the aircraft does not change over, as on the ground, you hear “IAS/MACH changeover is not available now”.

When VNAV has the speed. While VNAV controls the speed the MCP’s speed window is blank, and the box in the speed window takes no value. The Speed Intervene button shows which it is: “Speed Intervene: Window blank” or “Speed Intervene: Window open”. Press it to open the window, then type your speed.

The buttons are the MCP’s own, and each one with a light shows it, for example “LNAV: On”; HDG SEL and IAS/MACH have no light and show none. Pressing one is the same as pressing it on the MCP panel: about a second and a half later you hear its light, for example “LNAV on”, or at once “HDG SEL pressed”. Alt and the button’s underlined letter presses it from anywhere in the window.

The 757 has no altitude intervene: the MCP panel’s ALT SEL Push button does nothing in BlueBird’s aircraft. For a step climb, set the new altitude on the MCP and enter it as the cruise altitude on the CDU’s CRZ page.

Output Shift+H, Shift+S, Shift+A and Shift+V read the same four values without opening a window, followed by the MCP mode buttons that are lit: “Heading 090, LNAV”, “Speed 250, SPD”, “Altitude 12000, ALT HOLD”. These are the button lights, so an armed mode whose button is lit is named too, and heading select, which has no light, names nothing. In Mach mode Shift+S says “MCP Mach 0.78”, and with the window blank “MCP speed window blank. Speed Intervene opens it.” They read the MCP’s own values, never the simulator’s autopilot values, which disagree with BlueBird’s MCP.

Input Ctrl+P opens the 757 Autopilot window. It starts on a list, Flight mode annunciator, with the four parts of the FMA as the ADI shows them: “A/T: SPD”, “Roll: LNAV, armed LOC”, “Pitch: VNAV PTH, armed G/S”, “AFDS: CMD”. A part with nothing showing reads none. The same four lines start the ADI window (Output Alt+P). Tab from the list to the buttons, or press a button’s key from anywhere in the window; your screen reader says each button’s key when you land on it. The buttons and their keys, in order:

Button Key
CMD L Alt+L
CMD C Alt+C
CMD R Alt+R
A/T Arm Alt+A
Captain F/D Alt+F
F/O F/D Alt+O
THR Alt+T
SPD Alt+S
LNAV Alt+N
VNAV Alt+V
FLCH Alt+H
HDG HOLD Alt+D
ALT HOLD Alt+E
V/S Alt+Y
LOC Alt+G
APP Alt+P
Speed Intervene Alt+I
A/T Disconnect Alt+X
A/P Disconnect Alt+B

Each button shows its state, for example “CMD L: On” or “A/T Arm: Off”. The mode and CMD buttons show their light, and A/T Arm shows whether the autothrottle is armed, as the aircraft holds it. A press is the cockpit’s own click, and the button then shows the new state. If the aircraft does not take the press, you hear so about a second and a half later, for example “CMD L did not engage” or “LNAV did not disengage”; for A/T Arm it is “A/T Arm did not arm” or “A/T Arm did not disarm”. Speed Intervene, A/T Disconnect and A/P Disconnect say “… pressed”. A/P Disconnect is the button on the Captain’s yoke: it disconnects the autopilot, and a second press silences the warning. The MCP’s disengage bar is on the MCP panel only. Escape closes the window.

What BA says by itself about the autopilot is listed under Aircraft-specific hotkeys and callouts.

Altimeters and minimums

Input Ctrl+B opens the Altimeter and minimums window:

Escape closes the window. Output B reads the same: “Altimeter: 1018, 30.05. DH 200”. When the Captain’s altimeter is changed from anywhere else, BA says the new setting once the knob stops.

Radios

The COM radios are on the Pedestal’s COM radios panel, described under How the panels are organized. Every change of a COM frequency is spoken, for example “COM1 active 124.850”.

The VORs are normally tuned by the FMC. To tune a station yourself, with its course, use the NAV RADIO page in the CDU window (Alt+N), as on the aircraft.

The ILS is a small panel of its own on the pedestal, with a frequency and a front course. Input Ctrl+N opens the 757 Nav Radios window to set it:

Enter applies only the box you are in. The window stays open, and Escape closes it. If BA cannot read the ILS panel’s frequency, it goes by its own count of the clicks it has sent and says so, for example “ILS 110.50 set by count: the ILS display could not be read.”

Output N reads the radios without opening a window, for example “VOR L 116.90 auto, GSU. VOR R 113.90 remote, course 095. ILS course 095. ILS 110.50.”, or “ILS parked.” at the end. A VOR’s course is said only when that VOR is not tuned automatically.

To read the VORs and the FMC’s runway ILS, the Ctrl+N window and Output N look them up on the First Officer’s CDU and leave it on its NAV RADIO page. The Captain’s CDU is never touched.

The CDU

Press Input Shift+M to open the BlueBird 757 CDU window. It shows both CDUs, read as text straight from the aircraft, starting on the Captain’s; the window’s title names the side. Ctrl+Tab switches to the other CDU, Ctrl+Shift+L picks the Captain’s and Ctrl+Shift+R the First Officer’s, and each says which one you are on: “Captain CDU” or “First officer CDU”. The two are independent, as on the aircraft. The First Officer’s CDU shows once its screen changes, so if its list says it is waiting, press a page key such as Alt+R.

What you hear. A new page says its title, for example “ACT RTE 1 LEGS 1/2”, and puts you on line 1. When only the title changes, as when an entry turns ACT into MOD, the new title is said and you stay on your line. After you type an entry, BA reads the scratchpad back once the keys have gone in, so you hear what the CDU took, for example “KATL”. If the CDU missed a key you hear what it shows instead: “Scratchpad shows KAT” or “Scratchpad is empty”. A scratchpad that empties says “Cleared”, and any message the FMC puts in the scratchpad is read aloud. Typed entries go in at about two to three characters a second, other keys a little over half a second apart, and holding a key down presses it once. If the link to the aircraft drops while keys are still going in, the rest are not sent and you hear “CDU connection lost, keys not sent”.

CDU messages while the window is closed. With the window closed, BA speaks each new message in the Captain’s scratchpad, starting with “CDU:”, for example “CDU: TAKEOFF DATA UPLINK”. The Speak CDU messages when closed check box at the end of the window turns this off, and so does the CDU Messages While Closed row in Ctrl+M; they are the same setting. This works from the moment you select the 757: you do not have to open the CDU window first.

The status box says “Waiting for the 757’s CDU. Is the aircraft powered?” until the CDU has a screen.

A SimBrief flight and route come in through the CDU’s ACARS pages. First set your SimBrief ID (see BlueBird’s settings) and fetch the flight on the tablet (see Fuel, payload and boarding). Then, in the CDU window:

  1. Press Alt+M for MENU, then ACARS (the left 2 key, Ctrl+2), OPERATIONS (the right 2 key, Alt+2), PREFLIGHT (Ctrl+1), INIT FLT (Ctrl+1) and INIT (the right 6 key, Alt+6). The page shows “VHF IN PROG”, then the flight’s origin and destination.
  2. Press Alt+R for RTE, then REQUEST SEND (Ctrl+3). Within about 15 seconds the page says “ROUTE 1 UPLINK READY”.
  3. Press LOAD (Ctrl+4), ACTIVATE (Alt+6) and EXEC (Ctrl+Enter). The page title then says “ACT RTE 1”.

Read each page’s numbered lines before you press a key: the line that reads “2:” on the left is the one Ctrl+2 presses, and on the right the one Alt+2 presses. Without a SimBrief ID, ACARS INIT does nothing.

The EFB

Input Shift+T opens the 757 EFB window: BlueBird’s tablet itself, read aloud. It is a page you read with your screen reader’s browse mode, like a web page, with headings, buttons, check boxes, lists and edit boxes, and everything a sighted pilot can press on the tablet you can press here. BA reads the tablet straight from the aircraft and taps it for you. (In output mode, Shift+T toggles trim announcements instead.)

With the simulator closed, Shift+T opens BlueBird’s settings instead.

Reading the tablet

The page’s main heading names the tablet page you are on, for example “BlueBird tablet: Aircraft, Fuel”, and BA says each new page as it arrives: “BlueBird tablet page: Aircraft, Fuel”. Below the heading, in this order:

  1. A question from BlueBird, when one is waiting, with its answer buttons.
  2. The tablet page itself, with its sections as headings and every value with its label.
  3. A Status bar heading: the tablet’s top bar, with the time, the departure countdown and the boarding button, and under it a Notifications heading with BlueBird’s notifications, newest first.
  4. A Sections heading: the side menu of the app you are in. The one you are on ends in “(current page)”.
  5. A Home button, last on every page but the home screen.

The tablet’s home screen has five apps: Aircraft (Cockpit presets, Fuel, Weight & balance, Ground services, Cabin & doors, Maintenance, Failures), Navigation (ACARS dashboard, Operating FP, Weather & NOTAM, Charts, Map, PERF calc), Systems, Checklist and Settings (General, Aircraft, Livery options, Callouts, Cabin audio, AIRAC data). Press an app on the home screen, then a section under Sections.

The page updates by itself while the window is open and keeps your place. F5 reads the tablet again. Alt+F4 closes the window; Escape is left to your screen reader.

Pressing, choosing and typing

Each kind of control on the tablet becomes the control your screen reader knows:

When a control is further down the tablet’s page, BA scrolls the tablet to it before it taps; there is nothing for you to scroll.

After a press you hear what changed. A button whose words change says its new words. A press that changed nothing says *“: no change on the tablet."*, and a switch that did not follow says *" did not change."* A press that takes you to another page is confirmed by the new page's name. If the tablet ends up somewhere else you hear *"The tablet did not show . Try again, or press F5 to read the tablet again."*

A few things can be in the way, and BA then presses nothing and says why: *“ is under a BlueBird notification, not pressed."* (a notification covers the top right corner of the tablet for about ten seconds; try again), *" is under the tablet's keyboard, not pressed."*, *" could not be brought into view, not pressed."* or *" is no longer on the tablet."*

Notifications and questions. While the window is open, BA speaks each new notification from BlueBird as it arrives, for example “GPU connected.”, and each question once when it appears, such as whether to switch the weight units after a SimBrief fetch, or whether to defuel. Answer a question with its buttons at the top of the page. While a question is waiting, the rest of the page is shown as plain text and cannot be pressed.

The colors theme on the Settings app’s General page is a line of text, not a choice: it says that other color schemes than the default are not supported.

Fuel, payload and boarding

You fuel and board with BlueBird’s own buttons, and BA tells you when each is complete:

  1. Set your SimBrief ID once (see BlueBird’s settings, or the Settings app’s AIRAC data page on the tablet).
  2. On the Navigation app’s ACARS dashboard, press Fetch SIMBRIEF OFP. If BlueBird asks about the weight units, answer it.
  3. With BlueBird’s Automatic boarding setting on, BA starts listening for both the fueling and the boarding at the fetch. Otherwise press Import from SIMBRIEF on the Aircraft app’s Fuel page, and Start boarding in the Status bar.

BlueBird then fuels and boards at its own pace; with its realistic load rate, boarding can take half an hour or more. You can close the window and carry on: BA checks the tanks and holds every 15 seconds and tells you once each, in the aircraft’s weight units and rounded to 10, for example:

BA takes the target weights from your latest SimBrief plan. If it cannot read a 757 plan, you hear “The SimBrief plan could not be read, so the app won’t say when fueling and boarding are complete.”, after the reason when BA knows it: for example “No SimBrief ID is set in the 757’s EFB settings.”, “Your latest SimBrief plan is for A320, not a 757-200. Create a B752 plan, then try again.”, “The plan’s fuel is more than the tanks hold.” or “SimBrief could not be reached. Check your internet connection and try again.” If nothing has moved after three minutes you hear “BlueBird has not started loading. Is BBS Nest running? Check the fuel with F and the weight with W.”, or the same about the fueling or the boarding alone. If one has not finished after an hour, you hear, for example, “Boarding has not finished after an hour. Check the weight with W.” Loading another flight stops the checking.

On the Ground services page you call BlueBird’s ground power and ground services and set or remove the chocks. Ground power, the aft stairs, the fuel truck, catering and the cargo service are also spoken when they change, whether or not the window is open: “Ground power connected”, “Catering called”, “Fuel truck removed”.

Navigraph and nav data

The Settings app’s AIRAC data page has your SimBrief ID, the Navigraph sign-in and the installed nav data cycle.

Warning: BlueBird shows the Update button and a Remove button in the same place, and the button’s name tells you which one it is. Read it before you press: “Latest cycle: Remove” removes the nav data you have installed. If that happens you hear “BlueBird removed the installed nav data.”, or, when an update was due, “BlueBird removed the installed nav data instead of updating it. With an active Navigraph subscription, reload the flight and update again.”

BlueBird’s settings, with the simulator closed

BlueBird reads its settings when the aircraft loads. With no simulator running, Input Shift+T (with the 757 selected in BA) opens the 757 EFB settings window, which changes them in BlueBird’s own settings file, ready for the next load. With the simulator running, use the tablet’s Settings app instead.

The window opens on a Status box that says whether the settings can be changed, for example “The simulator is closed. Changes are saved to BlueBird’s settings at once and take effect when the 757 next loads.” Then comes a Section list: General, Aircraft, AIRAC data, ACARS, Failures, Livery options, Callouts and Cabin audio. Tab on from it through the chosen section’s settings:

Settings worth knowing: in AIRAC data, SimBrief ID number, which BlueBird’s SimBrief fetch and the CDU’s ACARS need; in Aircraft, Nosewheel steering (Rudder lets you steer on the ground with the rudder pedals, Realistic uses the tiller), Parking brake mode, IRS alignment time, Boarding & load rate, Automatic boarding, Automatic GPU/jetway and Initial chocks in place; in Livery options, Units (Imperial or Metric) and EHSI up reference (HDG or TRK); in Callouts, each of BlueBird’s own callouts. Livery options, Callouts and Cabin audio are kept per aircraft registration, and a Registrations box at the top of those sections says which ones your change applies to.

In General, EFB colors theme is a note that other color schemes than the default are not supported. If the file holds another theme, a Set to Dark blue button beside the note sets it back.

Escape closes the window. If you start the simulator while it is open, you hear “Simulator started: BlueBird’s settings are read-only.”

If the tablet cannot be read

Special windows: the ADI, EICAS and the EHSI

BA reads four of the 757’s displays straight from the aircraft, with no AI: the Captain’s ADI, the upper EICAS, the lower EICAS and the Captain’s EHSI. Each opens as a window with a list you arrow through, followed by the display’s own controls, if it has any; press Tab to reach them. The lists update every second without losing your place and speak only when you move through them. Escape closes a window.

The ADI window

Output Alt+P opens ADI, with the list Captain ADI. It starts with the flight mode annunciator, the same four lines as the 757 Autopilot window: “A/T: SPD”, “Roll: LNAV, armed LOC”, “Pitch: VNAV PTH, armed G/S”, “AFDS: CMD”. Then comes the rest of the ADI, each line starting with where it sits on the display: Left is the speed tape, Center the attitude, Right the glideslope scale and the radio altitude, Bottom the localizer scale. A line is there only while the ADI shows its item, so the list grows and shrinks with the flight.

On the left, the speed tape:

In the center, the attitude:

On the right and at the bottom, the approach:

Flags. When an instrument fails or has no data, the ADI draws an amber flag in its place, and the list puts the flag there instead of the value: “Left: SPD flag” (the whole speed tape), “Center: ATT flag”, “Right: G/S flag”, “Right: RA flag” and “Bottom: LOC flag”. While the IRS aligns the center reads “Center: no attitude”: no horizon and no flag until the alignment is complete.

What you hear by itself. Only the flags, as they appear and go: “ADI flag: ATT”, “ADI flag gone: ATT”, and the same for SPD, LOC, G/S and RA. Speeds, attitude, needles, radio altitude and minimums are in the list only and never spoken: the 757 makes its own 80 knots, V1, rotate, minimums and altitude calls. To silence the flags, untick ADI messages in the 757 Monitor Manager (Output Ctrl+M); the window still lists them.

What the list leaves out: the FMC’s target speed while VNAV controls the speed, the speed limit bands, the speed trend arrow, the pitch limit indicator, and the amber flashing of the minimums and of the localizer and glideslope scales close to the ground. The AUTOLAND STATUS annunciator beside the ADI is not in the list either: BA speaks it as it changes, and the Status panel shows it.

The window has no controls. While the ADI is off it reads “ADI display not powered”. If BA cannot read the flight mode annunciator, the first line says why, and the rest of the ADI follows.

If you hear an AI description instead. When BA cannot read the ADI from the aircraft, Alt+P describes it with AI, without saying anything first; this needs an AI provider (see AI Display Reading). The flight mode annunciations are still in the Ctrl+P window whenever BA can read them. See When BA cannot read a display for why this happens and what to do.

The Upper EICAS window

Output Alt+E opens Upper EICAS. The list follows the display, left engine first:

After the list come three buttons of the EICAS control panel: Cancel (Alt+C), Recall (Alt+R) and Max Ind (Alt+M). Each says “… pressed”, and Cancel and Recall are then confirmed by what the display did: “EICAS: 3 messages cancelled”, “EICAS recall: L ENG SHUTDOWN, PARKING BRAKE” or “EICAS recall: no cancelled messages”.

The Lower EICAS window

Output Alt+S opens Lower EICAS. The first line says which page the display shows: “Page: engine”, “Page: STATUS” or “Page: engine off”; a blank display reads “Lower EICAS: blank”.

After the list, the Engine and Status buttons press the EICAS control panel’s ENGINE and STATUS keys. BA confirms a press by the page change: “Lower EICAS: STATUS page”.

The EHSI window

The EHSI is the Captain’s map display. Output Alt+N opens EHSI, with the list Captain EHSI. What it holds depends on the mode.

In MAP and PLAN, from the top of the screen down:

The map lines name:

In VOR and ILS, the list has the approach picture instead of the map:

What the list leaves out: the weather radar picture and the terrain picture.

The controls. After the list, each with its key: Mode (Alt+M: VOR, APP, MAP or PLAN; APP is the ILS picture), Range (Alt+R, 10 to 320 NM), CTR (Alt+C), TFC (Alt+T), and the map options as check boxes: WXR (Alt+W), TERR (Alt+E), NAV AID (Alt+N), APRT (Alt+A), DATA (Alt+D) and WPT (Alt+P). They are the Captain’s EFIS controls, and they show the cockpit’s real state.

Output Ctrl+W says the active waypoint as the EHSI’s top corners show it, “KOLM, 37.5 NM, 1521.4z”, or “No active waypoint”, whether or not the window is open. In VOR or ILS mode it says, for example, “KOLM, EHSI in ILS mode”. For the first ten seconds after the displays power up it says “EHSI waypoint unavailable: starting”.

When BA cannot read a display

BA reads the displays, the flight mode annunciations and the tablet through files made for each version of BlueBird’s 757. If it cannot load them, for example after a BlueBird update, you hear once: “BlueBird display files could not be loaded; the display keys fall back to AI reading.” Alt+P, Alt+E, Alt+S and Alt+N then describe the display with AI instead, until a BA update brings the files for the new version.

While a reader is still finding its display, its window opens and says so, for example “EHSI reader starting”; with the display dark it says “EHSI display not powered”. If a reader loses its display during a flight you hear, for example, “EICAS announcements stopped: aircraft memory not found”, and “EICAS announcements resumed” when it is back, followed by anything that changed meanwhile. While a reader is stopped or unavailable, its key gives the AI description instead of the window. BA keeps looking for a display it lost, so wait for “resumed”; after “announcements stopped: unexpected values”, reload the flight to start that reader again.

The standby instruments have no read on the 757, so Output Alt+I does nothing here: what they show is on keys of their own. Output S gives the airspeed, Output A the altitude, Output B all three altimeter settings, the standby’s included, and the attitude is in the ADI window (Output Alt+P). Alt+P, Alt+E, Alt+S and Alt+N fall back to an AI read (it needs an AI provider; see AI Display Reading); Alt+P’s describes the attitude, the flight mode annunciations and the AUTOLAND STATUS annunciator. BA moves the simulator’s camera to the display and puts your own view back afterwards; from an outside or drone view you hear “Switch to a cockpit view first.”

The First Officer

Output Shift+C opens the 757’s First Officer, with BlueBird’s Normal Checklist and twelve flows: Power Up, Preflight, Before Start, Engine Start, After Start, Before Takeoff, After Takeoff, Descent, Before Landing, After Landing, Shutdown and Final Securing. What is particular to the 757, from the cockpit tests in the Preflight flow to the engine start on each engine type, is described in The BlueBird 757.

Aircraft-specific hotkeys and callouts

Readouts, in output mode (the complete key list is in the Hotkey Reference):

What BA announces by itself:

The 757 does not say “glideslope alive”: listen for “FMA: Pitch: G/S” instead.

Output Ctrl+M opens the 757 Monitor Manager, where you untick anything you do not want to hear. Besides a row for each announcement above, it has CDU Messages While Closed, All Annunciator Lights and All Switches From Any Source to silence a whole kind at once, a “Switches:” row for each panel, a “Light:” row for each light and a “Switch:” row for each switch, and at the end the rows for the displays: Flight Mode Annunciator, EICAS messages, Thrust reference, Engine gauge colors, EICAS status messages, EHSI messages and ADI messages. A display’s row also silences BA’s own “stopped”, “unavailable” and “resumed” messages for it; the windows still list everything. Your choices persist across sessions. See The Monitor Manager.

Take-off callouts. The 757 plays its own “80 knots”, V1 and rotate calls, and its own altitude callouts. So on this aircraft Takeoff Assist does not call “80 knots”. Its “100 knots”, centerline tone and pitch calls work as on every other aircraft.

Things to know

TFDi MD-11

The TFDi Design MD-11 is a three-engine airliner with a cockpit unlike any other aircraft in BA. Its six display units are drawn inside the aircraft’s own code with no text behind them, so BA cannot read the PFD, navigation display or engine display directly. What it can read — and read very well — is everything else: all three MCDUs as text, the EFB, the flight control panel windows, the numbers TFDi publishes for external tools, and over 500 indicator lights. Together these replace the screens.

Before you fly

How the panels are organised

The panels follow the order you prepare the aircraft in, and use the names TFDi’s own Systems Guide uses:

How the panels behave:

The three engine fire handles are read-only rows: BA reads their position but cannot work them from the panel yet, and says “… cannot be operated from this panel yet.” if you try.

The flight control panel

The MD-11’s flight control panel is what other aircraft call the MCP or FCU.

Input Ctrl+P opens the MD-11 Flight Control Panel window. It opens on the Autoflight button, which reads its state, such as “Autoflight: AP 1, ATS on” or “Autoflight: off”. The other buttons:

The value windows, all in input mode, take typed values — no knob-winding:

The output readouts say what is selected: Shift+H “Selected heading dashed, NAV engaged” when NAV is flying; Shift+S “FMS speed engaged” when the window is dashed; Shift+A the selected altitude in feet or metres; Shift+V the vertical speed or flight path angle, or “not engaged”.

Note: PROF and Approach/Land have no cue on the panel — their state exists only on the flight mode annunciator on the PFD — so BA never reports them as engaged. A mode button only tells you it was pressed, not that the mode engaged. To hear the annunciator, use Output Alt+P (below).

The MCDUs

Input Shift+M opens the MD-11 MCDU window, on the Left (Captain’s) unit. All three MCDUs read fully, live, as the real screen. (In output mode, Shift+M reads the METAR instead.)

The MD-11 has no EXEC, DEL or PREV PAGE key — the real aircraft does not have them. It confirms with the line select keys and slews with the up and down keys instead. If a screen is momentarily empty, the window says “MCDU is blank - nothing on this screen.”

The EFB

Input Shift+T opens the MD-11 EFB, which works like the other tablet windows (Aircraft EFBs). All of it reads: Dispatch, Payload, Perf, Charts, Services, State and Options. Some examples of how it reads:

Pages the aircraft locks in flight, such as ground services, are still readable, but their controls are dimmed and cannot be pressed — exactly as on the real tablet.

Flaps and Dial-A-Flap

The MD-11 has one handle for flaps and slats together, plus a Dial-A-Flap thumbwheel that chooses the exact take-off flap angle. The handle detents, from clean to fully extended, are:

Dial-A-Flap sets the take-off angle anywhere from 10 to 25 degrees, one degree at a time. Because the handle position and the angle are two separate things, every flap readout tells you both: “Dial-A-Flap, 15 degrees”. Output L reads the handle, and always includes the Dial-A-Flap angle when the handle is in that detent. When the flaps move, BA says “flaps moving” and then the new position — on an aircraft with no flap gauge you can read, that is your confirmation the selection took.

Special windows: AI display reading

With an AI provider set up, these output mode keys read the screens by AI vision, moving the camera for you as described in AI Display Reading:

Aircraft-specific hotkeys and callouts

Take-off callouts: “V1”, “Rotate”, “V2” and “N1 70 percent”, as described in Takeoff Speed Callouts (TFDi’s MD-11 plays no callouts of its own).

When the FMS sets the speeds, BA announces them in one sentence: “V1 145, VR 150, V2 158, slat retraction speed 190, flap retraction speed 210 knots”. Starting BA with speeds already entered says nothing; a change does.

Also announced as they change: autopilot and autothrottle engagement, the captain’s altimeter (once the knob stops moving), the APU, the COM radios (active and standby for COM 1, 2 and 3), the squawk, the flaps, and every indicator light.

Things to know