Advanced Users Guide

Advanced Users Guide

This guide is intended for advanced FSFO users who want to manually customize SOPs, create their own flows and checklists, tune Smart Flows, and manage the FSFO airport database.

Quick navigation
Jump to a settings group:

• SOP File Location
• SOP File Structure
• Phases
• Types (Flow vs Checklist)
• Creating Custom Flows and Checklists
• Flow Commands Explained
• Manually Update Smart Flow Options
• FSFO Airport Database Tool

SOP File Location

All SOPs are stored in:

C:\Users\[Your Name]\AppData\Local\FSFO_V6\FlowsChk

Replace [Your Name] with your Windows user name.

Each SOP file must begin with two required header lines:

type;AIRBUS;;
user;;;

• The first line identifies the aircraft type (BOEING or AIRBUS).
• The second line is reserved for user-generated flows and checklists.

Back to top

SOP File Structure

Each line in an SOP file uses the following structure:

Phase;Type;System;Response

Example:

1;1;Auto_Brakes;MAX

Where:

• Phase = Flight phase number
• Type = Flow or Checklist
• System = Target system or command
• Response = Desired value or action

Back to top

Phases

The following numeric values define flight phases:

1  = Preflight or Cockpit Preparation
2  = Before Start
3  = Engine Start
4  = After Start
5  = Taxi
6  = Before Takeoff or Lineup
7  = After Takeoff
8  = Descent
9  = Approach
10 = Landing
11 = After Landing
12 = Shutdown or Parking
13 = Runway Change
100 = Turn Around
14 = User Defined
15 = User Defined
16 = User Defined

Back to top

Types (Flow vs Checklist)

1 = Flow
2 = Checklist

Flow A memorized, spatial sweep of switches and controls used to configure the aircraft. Flows are fast, heads-up, and done from memory.

Checklist A short, written challenge-response used to verify critical items are correctly set.

How they work together:

• Normal operations: Flow → Checklist
• Abnormal or emergencies: Use QRH or abnormal checklist

The flow performs the actions, the checklist verifies them.

Back to top

Creating Custom Flows and Checklists

Always create a backup copy of your SOP file before making manual edits.

To add user-defined flows (for example: Single Engine and Go-Around):

Update the second line of your SOP file:

type;AIRBUS;;
user;Single_Eng;Go_Around;

Then add new phase lines at the end of your file:

13;2;Takeoff_Speeds;READBACK
13;2;Altitude;READBACK
14;2;Action;Value
14;2;Action;Value
15;2;Action;Value
15;2;Action;Value

Mapping:

• Phase 14 = Supplemental Flow One
• Phase 15 = Supplemental Flow Two
• Phase 16 = Supplemental Flow Three

Voice commands:

• “Supplemental checklist one”
• “Supplemental flow one”

Back to top

Set Commands

PACKS: Sets packs according to the option selected on the FSFO Departure Performance page.
ALTITUDE: Sets the autopilot altitude to the Initial Altitude (or Planned Altitude) selected on the FSFO Flight Plan page.
HEADING: Sets the heading bug to the departure runway heading selected on the FSFO Departure Performance page.
AIRSPEED: Sets IAS to the V2 speed entered on the FSFO Departure Performance page.
AUTO_BRAKES: Sets according to the option selected on the FSFO Arrival Performance page.
FLAPS: Sets according to the option selected on the FSFO Departure Performance page.
COCKPIT_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
DOME_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
WING_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
ANTI-ICE: Turns ENGINE_ANTI_ICE and WING_ANTI_ICE ON when OAT < 10°C and precipitation is detected; otherwise OFF.

A SET Commands used during the flows will result in the above.

Back to top

Flow Commands Explained

LVAR

This command is intended for advanced users who are comfortable working with MSFS Local Variables (LVARs) and know how to acquire and use them. To use it, add the LVAR command, then enter the LVAR name, an equals sign (=), and the desired value/state (i.e., LVAR_NAME=VALUE). FSFO also supports PMDG Rotor Brake commands (Toggle and Push Only) by using the ROTOR_BRAKE option after LVAR in the format ROTOR_BRAKE=<SwitchID>=<Label>. For example: 1;1;LVAR;ROTOR_BRAKE=101=Battery; — in this case, ROTOR_BRAKE tells FSFO to use the Rotor Brake command type, 101 is the SwitchID, and Battery is the label that will be displayed (and spoken) on the SOPs page.

Format:

1;1;LVAR;XMLVAR_StandbyPower_Selector=1=Standby Power
1;1;LVAR;ROTOR_BRAKE=101=Battery

Meaning:

• XMLVAR_StandbyPower_Selector = LVAR name
• 1 = value
• Standby Power = Label that will be displayed (and spoken) on the SOPs page

Rotor_Brake Meaning:

• ROTOR_BRAKE = Tells FSFO to use the Rotor Brake command type
• 101 = SwitchID
• Battery = Label that will be displayed (and spoken) on the SOPs page

---

SIMVAR

Used to control MSFS Simulation Variables.

Format:

1;1;SIMVAR;67271=1=Parking Brake

Meaning:

• SIMVAR = Tells FSFO to use the SIMVAR command type
• 67271 = SIMVAR control number (complete list here: SIMVAR Control Numbers)
• 1 = value (ON)
• Parking Brake = abel that will be displayed (and spoken) on the SOPs page

---

Play_Sapi_Copilot

FSFO will use Microsoft SAPI to speak the text you enter using the Copilot voice selected in Settings. If no Copilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.

---

Play_Sapi_Pilot

FSFO will use Microsoft SAPI to speak the text you enter using the Pilot voice selected in Settings. If no Pilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.

---

Play_Wav

Plays a WAV file. You must enter the full path of the wav file.

Format:

1;1;Play_Wav;C:\Users\name\FSFO\boarding_Noise.wav

---

Misc_Text

Displays reminder text under the Pilot section.

Example:

1;1;Misc_Text;Start ACARS

---

Capt_Actions

Displays reminder text under the Captain Actions section.

---

Flight_Plan

Loads the most recent flight plan from:

C:\Users\[name]\AppData\Local\FSFO_V6\Download

---

Landing_Data

Reads back minimums and Vref speeds.

---

Fuel

• Load = FSFO will load the fuel amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
• Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

---

Payload

• Load = FSFO will load the payload amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
• Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

---

Loadsheet

• Confirm = Ground crew will confirm the aircraft is under Max Takeoff Weight (MTOW). If it is over MTOW, they will warn you and request that you check your loadsheet.

---

Doors

• Toggle_0 through Toggle_6 = Will open/close the doors; for example, Toggle_1 will open/close the 1L(Main) Door on most aircraft.

---

Walk_Around

While the default values are SHORT, MED, and LONG, advanced users can open the SOP text file and enter any numeric value (seconds) they like for the copilot to perform the walk-around. As an example:

1;1;WALK_AROUND;965

Defaults:

• SHORT = 150 seconds
• MED = 300 seconds
• LONG = 600 seconds

Back to top

Manually Update Smart Flow Options

You can still manually update your SMART AutoFlow options by updating the userSettings.cfg file by following these steps:

1. Close FSFO
2. Navigate to C:\Users\[Your Name]\AppData\Local\FSFO_V6\UserData Folder
   1. You can also just click on the UserData button on FSFO’s front page
3. Right-Click on userSettings.cfg and click Open with Notepad
4. Locate and edit these lines1; ensure no trailing white space or empty lines

Flows_PreFltStart=10
Flows_BeforeTakeoffStart=800
Flows_AfterTakeoffStart=3000
Flows_DescentStart=20
Flows_ApproachStart=10000
Flows_LndgStart=1500

Units:

Flows_PreFltStart        = Seconds
Flows_BeforeTakeoffStart = Feet to runway threshold
Flows_AfterTakeoffStart  = AGL feet
Flows_DescentStart       = Nautical miles
Flows_ApproachStart      = AGL feet
Flows_LndgStart          = AGL feet

Back to top

FSFO Airport Database Tool

FSFO Make Runway is a separate program that builds the runway database using SIMCONNECT and MSFS APIs.

Installation

You can install it in two ways:

1. From FSFO
   1. Click Get Started on the FSFO main page
   2. Click MAKE RWY on the New User window
   3. Follow the installation instructions
2. Manually:
   1. Navigate to *\Flight Simulator First Officer V6\Res\Exe
      1. * represents your FSFO V6 directory; just right-click on the Flight Simulator First Officer V6 shortcut and select "Open File Location"
   2. Right-Click FSFO_Make_Runway.exe and Select "Run as Administrator"

---

Building the Database

1. Start MSFS or MSFS24 and load into the cockpit
2. Click FSFO NAV PATH and select the FSFO NavData folder
3. Click Connect
4. Click Build

Note: This process can take over two hours.

---

Manual Database Updates

Runway data file:

• *\FSFO_V6\NavData\runways.csv

Note 1 (Runway Code):

• Stored as a 3-digit code where the last digit indicates the side:
  • 0 = none
  • 1 = Left (L)
  • 2 = Right (R)
  • 3 = Center (C)
  • 4 = Water (W)

• Examples:
  • 330 = Runway 33
  • 331 = Runway 33L
  • 332 = Runway 33R
  • 333 = Runway 33C
  • 090 = Runway 9
  • 091 = Runway 9L

Note 2 (Latitude/Longitude format):

• Lat/Lon values must be in decimal degrees (DD) format (example: 42.193545).
• Threshold lat/lon represent the runway threshold (AFCAD “runway start”).

Note 3 (Feet):

• Elevation, length, width, and threshold offset values are (must be) in feet.

Note 4 (Heading):

• Runway heading is the magnetic runway heading.

Note 5 (ILS frequency):

• ILS frequency is stored as nnn.nn (example: 109.50) or 0 if no ILS is available.

Note 6 (Magnetic variation):

• Magnetic variation (in degrees) is the value applied to convert magnetic to true heading: True Heading = Magnetic Heading + Magnetic Variation

Back to top

---

For standard setup and everyday operation, see Getting Started and User Settings Reference.