MSFS Blind Assist

The First Officer and Checklists

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 3: The First Officer of the MSFS Blind Assist user guide.

What it is

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

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

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

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

When to use it

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

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

How to use it

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

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

The Flows tab

The Flows tab has:

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

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

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

The BlueBird 757

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

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

The Checklists tab

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

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

The buttons below the tree:

Loading SimBrief

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

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

What you will hear

While a flow runs:

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

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

Settings

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

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

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

If something goes wrong