MSFS Blind Assist

General Flying Concepts

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

Chapter 1 of 1 in Part 9: General Flying Concepts of the MSFS Blind Assist user guide.

This chapter steps back from individual aircraft: how an airline flight is put together, how airliner automation thinks, what ATC expects of you, and how to keep a picture of the flight in your head with BA. Nothing here is specific to one type. Where Airbus and Boeing do things differently, both are described. Everything is written for the simulator: real-world flying needs real training, real manuals and a real instructor, and nothing in this guide replaces them.

Tip: You do not need to read this chapter in one go. If you are brand new to airliners, read the phases of flight first (and the example flight in A Flight with BA, Start to Finish, in Part 2), then come back to automation and the FMA once you have flown a few circuits.

The Phases of a Flight

Every airline flight follows the same broad shape. Knowing which phase you are in tells you what to expect next and which BA features matter right now.

Building a Listening Scan

A sighted pilot keeps a “scan”: the eyes move over the instruments in a pattern, again and again, so nothing drifts unnoticed. You can do the same with your ears. BA gives you two kinds of information: automatic announcements, which come to you, and readout hotkeys, which you ask for. A good scan uses both.

Let the automatic announcements do the watching for you. Master warnings and cautions, mode changes, gear and flap movement and altitude crossings are announced as they happen on most aircraft. If an announcement is too chatty for you, silence just that one in the Monitor Manager (Output Ctrl+M) rather than ignoring the lot.

Then ask for what matters in each phase. The readout keys are listed in Readout Hotkeys. A sensible pattern:

Two habits make the scan work. First, after you change anything, read it back: set 5,000 feet, then press Output Shift+A to hear that the FCU or MCP really says 5,000. Second, whenever you hear a mode change, ask yourself whether it is the one you expected. Surprises are where mistakes begin.

Tip: Fewer, well-chosen checks beat constant ones. If you press a key every few seconds in the cruise, the important announcement you are waiting for may get talked over.

Automation: Who Is Flying the Aircraft?

A modern airliner has layers of automation. Understanding them is the single most important thing for flying one well, sighted or not.

The autopilot needs to know what to follow. That is where modes come in.

Selected and managed modes

Every axis (speed, lateral path, vertical path) can be told what to do in one of two ways:

Pilots mix the two all the time. A common example: ATC gives you a heading to fly away from your route, so you select a heading, and later they clear you back “direct to” a waypoint, so you return to managed or LNAV navigation.

Airbus FCU and Boeing MCP

Airbus and Boeing put the same ideas on very different panels.

On an Airbus, the panel is the FCU (Flight Control Unit). Each knob can be pushed or pulled. Pushing a knob usually hands that axis to the FMS (managed); pulling it means “use the number I have dialled” (selected). So pulling the heading knob flies the selected heading, and pushing it returns to the flight plan route. Pushing the altitude knob climbs or descends in managed mode, respecting the route’s altitude constraints; pulling it climbs or descends in open mode straight to the selected altitude. BA’s Airbus aircraft give you push and pull keys and windows for each knob — see Autopilot Windows.

On a Boeing, the panel is the MCP (Mode Control Panel). There is a button for each mode: LNAV and VNAV for the flight plan, HDG SEL for a selected heading, LVL CHG or FLCH for a climb or descent at a set speed, V/S for a set vertical speed, ALT HOLD to stay level, and LOC and APP for the approach. You press the button for the mode you want, and the windows hold the numbers it uses.

Autothrust and autothrottle

The two makers also differ on thrust. On a Boeing, the autothrottle physically moves the thrust levers, so the levers always show the thrust the engines are making. On an Airbus, the thrust levers sit in fixed positions called detents, and in normal flight they stay in the CLB detent from shortly after takeoff until just before landing; the autothrust changes the thrust without moving them. That is why Airbus pilots talk about “thrust levers to CLB” after takeoff and “idle” at touchdown. On some Airbus aircraft, such as the FlyByWire A380X, BA announces each lever detent as you reach it.

Warning: In both designs, disconnecting the autothrust or autothrottle without a plan can leave you with the wrong thrust. Know what the engines will do before you disconnect anything.

The Flight Mode Annunciator (FMA)

The FMA is a strip at the top of the primary flight display that tells you, at every moment, exactly which modes are active and which are armed (waiting to become active). It is how a pilot answers the question “what is the aircraft going to do next?”

On an Airbus, the FMA has five columns, read left to right:

Active modes are shown in green on the top line; armed modes are shown underneath in blue or magenta.

On a Boeing, the FMA shows the autothrottle mode on the left, the roll (lateral) mode in the middle and the pitch (vertical) mode on the right, for example SPD, LNAV, VNAV PTH. Armed modes appear underneath. Above it, the autopilot status shows FD, CMD, or LAND 3 during an autoland.

Why it matters to you: the FMA is the truth, and the panel is only a request. Pressing APPR or APP does not mean the aircraft will capture the glideslope; the FMA showing G/S armed, and then G/S active, does. On aircraft where BA reads the FMA aloud, listen for each change and check it against what you expected. On aircraft where it does not, use the engaged-mode readouts in the autopilot panel or window your aircraft provides.

Approach Types in Plain Terms

An approach is a published path from the end of the arrival down to the runway. There are three kinds you will fly most often.

Every instrument approach has a minimum: a decision altitude or height (DA or DH), or a minimum descent altitude (MDA). At that point you must be able to see the runway, or go around. Minimums are printed on the approach chart and are not part of the navigation data BA reads, so BA cannot tell you what they are; you set them in the aircraft from the chart or your flight plan.

Stable Approach Basics

Airlines require an approach to be stable by a set height, typically 1,000 feet above the runway in cloud and 500 feet in good weather. If it is not stable by then, the crew goes around. That rule exists because unstable approaches cause a large share of landing accidents, and it is just as useful in the simulator.

Typical stable approach criteria are:

With BA, check these with Output Shift+G (gear), Output L (flaps), Output S (speed), Output V (vertical speed) and Output Ctrl+D or Ctrl+I (distance and path) as you pass through about 1,500 feet above the ground.

Tip: A go-around is a normal manoeuvre, not a failure. If your approach is not stable, go around, climb away, and try again. BA’s flare assist even tells you “Go around detected. Flare assist rearmed.” so you are ready for the next attempt.

ATC Basics

Air traffic control keeps aircraft apart and tells you where to go. In the simulator you might talk to the simulator’s own ATC, to an AI service such as SayIntentions, or to real people on a network such as VATSIM. The principles are the same everywhere.

Frequencies and who you talk to

At a large airport you will typically speak to several controllers in turn:

When a controller says “contact Tower on 118.7”, you change to that frequency and call them.

Clearances and readbacks

A clearance is permission to do something specific. Until you are cleared, you do not do it. When you receive a clearance you read it back, repeating the important parts so the controller can check you heard them correctly.

Always read back:

End your readback with your callsign. If you did not understand something, say “say again”. It is always better to ask than to guess.

Taxi phraseology

These are the words you will hear most often on the ground, and what they mean.

BA’s Taxi Planner is built around these clearances: you enter the taxiways in the order ATC gave them and tell it which runways to hold short of. Entering an ATC Clearance has worked examples. If you fly with SayIntentions, BA can even fill the planner in from the controller’s last taxi instruction — see SayIntentions.

The altimeter setting

The altimeter needs to know the air pressure to show your height correctly. Near the ground, ATC gives you the local pressure, called QNH, in hectopascals (for example 1013) or inches of mercury (for example 29.92). Above the transition altitude you change to the standard setting (1013 hPa or 29.92 inches) so everyone at high level uses the same reference; heights are then flight levels, such as FL350 for about 35,000 feet. On the way down you switch back to QNH at the transition level. Output B reads your altimeter setting on most aircraft.

Runway Safety for a Blind Pilot

Runways are the most dangerous place on an airport. A runway incursion, an aircraft on a runway where it should not be, is one of the most serious events in aviation. In the simulator it costs you nothing but your flight, but on an online network it can spoil someone else’s, and good habits here are good habits everywhere.

Checklists

Airline crews work from two kinds of procedure. Flows are the sequences of actions you do from memory as you work around the cockpit, such as setting up the overhead panel. Checklists are short lists read afterwards to confirm the most important items were done. They are read at fixed points: before start, after start, before takeoff, after takeoff, approach, landing, after landing and shutdown.

Use checklists in the simulator even when nobody is watching. They catch the forgotten item — the parking brake still set, flaps not selected for takeoff, the altimeter not reset — before it matters. The First Officer and Checklists explains the flows and checklists BA’s First Officer runs with you, and some aircraft, such as the FlyByWire A380X, have their own electronic checklists that BA can read.

Note: BA’s built-in checklists are a convenience, not an official procedure. For the real sequence, use the documentation that came with your aircraft.

Where to Learn More

You will learn fastest by flying, but these kinds of resources help a great deal: