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

---

Flow Commands Explained

LVAR

Used to control MSFS Local Variables.

Format:

1;1;LVAR;XMLVAR_StandbyPower_Selector=1=Standby Power

Meaning:

• XMLVAR_StandbyPower_Selector = LVAR name
• 1 = value
• Standby Power = display string

---

SIMVAR

Used to control MSFS Simulation Variables.

Format:

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

Meaning:

• 67271 = SIMVAR control number
• 1 = value (ON)

---

Play_Sapi_Copilot

Speaks text using the Copilot SAPI voice.

---

Play_Sapi_Pilot

Speaks text using the Pilot SAPI voice.

---

Play_Wav

Plays a 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 = Loads fuel from FSFO Flight Plan
• Readback = Reads back current fuel

---

Payload

• Load = Loads payload from FSFO Flight Plan
• Readback = Reads back current payload

---

Loadsheet

• Confirm = Confirms aircraft under MTOW

---

Walk_Around

Custom duration (seconds):

1;1;WALK_AROUND;965

Defaults:

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

Back to top

---

Manually Update Smart Flow Options

Close FSFO.

Navigate to:

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

Open:

userSettings.cfg

Locate and edit:

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. Click Get Started on the FSFO main page
   1. Click MAKE RWY on the New User window
   2. Follow the instructions
2. Or 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.