FLT FILE PROPERTIES

The <mission_name>.flt file goes in the main mission folder beside the other files and is formatted like CFG Files and can be edited by using any text editor. This file is responsible for what happens when the mission is launched, and tells the simulation which files to use and which not, as well as setting basic parameters like plane selection. It's also in charge of all the information displayed in the simulation briefing screen.

IMPORTANT! This is a complex file with a lot of parameters. A single error will make the whole mission misbehave - or potentially not even work at all - and you wont get any information on what is failing. So edit this file slowly and test every change.

 

Below you can find information on the different sections used in the <mission_name>.flt file as well as what parameters and values are expected within them. Note that all file paths in the <mission_name>.flt are relative to the directory the FLT file resides in, and some of the sections listed will only be used on certain types of flights - such as missions - and the exact number of sections will depend on the type of aircraft being flown.

 

You can find an overview of how to create and edit FLT files on the following page:

 

You can find an example of this kind of file on the following page:

 

[Main]

This section is used for defining certain items of meta-data related to the flight or mission that the files is defining. The available parameters are:

 

Parameter Description Type Required
Title The title of the flight/mission being defined. This will be used as the mission title in the simulation. String Yes
Description A short description of the flight/mission. This will be shown to the user in the simulation. String Yes
AppVersion What version of Microsoft Flight Simulator 2024 the flight/mission is designed for. This value should be 10.0 or greater, otherwise the simulation will interpret the file as being from a legacy product. Float Yes
FlightVersion The version number of this flight. Starts at 1 and increments. Integer Yes
MissionType The type of mission that this file is for.

String, one of the following:

  1. LandingChallenge
  2. FreeFlight
  3. BushTrip
  4. Tutorial
  5. Discovery
Yes
MissionSubType The sub-type of the chosen mission. The sub-type chosen will depend on the MissionType parameter.

String, one of the following, based on the mission type:

  1. Landing Challenge:
    1. Famous
    2. Epic
    3. StrongWind
  2. Discovery:
    1. Core
    2. WU
  3. Training:
    1. A320
    2. BasicHandling
    3. LocalFlight
    4. VFRNavigation
No
MissionLocation The location of the flight. String No
OriginalFlight
FlightType

String:

  1. NORMAL
  2. LESSON
  3. TEMPORARY
  4. AUXILIARY
  5. SAVE
No
StartingCameraCategory

This sets the way that the in-sim camera will be set up when the flight starts.

Default value is "Cockpit".

String:

  1. "Cockpit"
  2. "Aircraft"
  3. "Scenery"
  4. "Custom"
  5. "FixedOnPlane"
  6. "Airport"
  7. "AirportTraffic"
No

 

 

[Briefing]

In this section you can setup how the mission briefing should look. The available parameters are:

 

Parameter Description Type Required
BriefingText This option is used to define the text that should be used on the mission briefing screen. String Yes
BriefingImageN This option can be used to set the relative path to a one or more image file which will be used for the briefing. For each image N should be incremented by 1, starting from 0. Images should be high-resolution PNG files, authored at 2460px * 1440px. String Yes
BriefingImageOverlayN Add text on the briefing screen. String No
BriefingInfoN Add specific information below the briefing text (Flight duration / Runway length / ...). You can have a maximum of 3 "BriefingInfo", and for each info text N should be incremented by 1, starting from 0.

Enum, can be one of the following:

  1. FLIGHT_INFO_RUNWAY_DEPARTURE_NAME
    Name of the departure
  2. FLIGHT_INFO_RUNWAY_DEPARTURE_ELEVATION
    Departure runway elevation, in meters
  3. FLIGHT_INFO_RUNWAY_DEPARTURE_LENGTH
    Departure runway length, in meters
  4. FLIGHT_INFO_RUNWAY_DEPARTURE_SLOPE
    Departure runway slope, in degrees
  5. FLIGHT_INFO_RUNWAY_ARRIVAL_NAME
    Name of the arrival
  6. FLIGHT_INFO_RUNWAY_ARRIVAL_ELEVATION
    Arrival runway elevation, in meters
  7. FLIGHT_INFO_RUNWAY_ARRIVAL_LENGTH
    Arrival runway length, in meters
  8. FLIGHT_INFO_RUNWAY_ARRIVAL_SLOPE
    Arrival runway slope (value in degrees)
  9. FLIGHT_INFO_NUMBER_OF_LEGS
    Number of legs. Used only in Bushtrip activity.
  10. FLIGHT_INFO_TOTAL_FLIGHT_DURATION
    Total duration of the flight, in seconds
  11. FLIGHT_INFO_TOTAL_FLIGHT_LENGTH
    Total length of the flight, in meters
  12. FLIGHT_INFO_WIND_ORIGIN
    Direction of the wind, in degrees
  13. FLIGHT_INFO_WIND_SPEED
    Speed of the wind, in m/s
No
StartUpLocationInfoN Add specific information during intro RTC. You can have a maximum of 4 StartUpLocationInfo, and for each info text N should be incremented by 1, starting from 0.

Enum, can be one of the following:

  1. FLIGHT_INFO_RUNWAY_DEPARTURE_NAME
    Name of the departure
  2. FLIGHT_INFO_RUNWAY_DEPARTURE_ELEVATION
    Departure runway elevation, in meters
  3. FLIGHT_INFO_RUNWAY_DEPARTURE_LENGTH
    Departure runway length, in meters
  4. FLIGHT_INFO_RUNWAY_DEPARTURE_SLOPE
    Departure runway slope, in degrees
  5. FLIGHT_INFO_RUNWAY_ARRIVAL_NAME
    Name of the arrival
  6. FLIGHT_INFO_RUNWAY_ARRIVAL_ELEVATION
    Arrival runway elevation, in meters
  7. FLIGHT_INFO_RUNWAY_ARRIVAL_LENGTH
    Arrival runway length, in meters
  8. FLIGHT_INFO_RUNWAY_ARRIVAL_SLOPE
    Arrival runway slope (value in degrees)
  9. FLIGHT_INFO_NUMBER_OF_LEGS
    Number of legs. Used only in Bushtrip activity.
  10. FLIGHT_INFO_TOTAL_FLIGHT_DURATION
    Total duration of the flight, in seconds
  11. FLIGHT_INFO_TOTAL_FLIGHT_LENGTH
    Total length of the flight, in meters
  12. FLIGHT_INFO_WIND_ORIGIN
    Direction of the wind, in degrees
  13. FLIGHT_INFO_WIND_SPEED
    Speed of the wind, in m/s
  14. FLIGHT_INFO_LOCATION_NAME
    Name of the location at mission start

    FLIGHT_INFO_LOCATION_VISIBILITY
    Visibility in the location at mission start

    FLIGHT_INFO_LOCATION_WIND
    Time of day at mission start

    FLIGHT_INFO_LOCATION_ALTITUDE
    Altitude at mission start

No
StartUpAircraftInfoN Add specific information on the Aircraft used during the intro RTC. You can have a maximum of 4 StartUpAircraftInfo, and for each info text N should be incremented by 1, starting from 0.

Enum, can be one of the following:

  1. FLIGHT_INFO_AIRCRAFT_CRUISE_SPEED
    Cruise speed of the aircraft

    FLIGHT_INFO_AIRCRAFT_STALL_SPEED
    Stall speed of the aircraft

    FLIGHT_INFO_AIRCRAFT_MAX_ALTITUDE
    Max altitude reachable by the aircraft

    FLIGHT_INFO_AIRCRAFT_IAS
    Indicated Air Speed of the aircraft at mission start

    FLIGHT_INFO_AIRCRAFT_HEADING
    Heading of the aircraft at mission start

    FLIGHT_INFO_AIRCRAFT_AUTONOMY
    Autonomy of the aircraft (depends on the amount of Fuel set in the [Fuel.N] section)

    FLIGHT_INFO_AIRCRAFT_RANGE
    Range of the aircraft

No

 

 

[Options]

In this section you can set some miscellaneous options for the flight. The available parameters are:

 

Parameter Description Type Required
Save Boolean Yes
SaveOriginalFlightPlan Boolean Yes
Sound This option can be set to True or False to enable/disable sound. Boolean No
Pause This option can be set to True or False to enable/disable the simulation pause state at the start or the finish. Boolean No
Moonlight This option can be set to True or False to enable/disable the rendering of moonlight in the simulation. Boolean No
TextDisplayPage The information text page to display. These pages often contain single lines of information such as PAUSE, STALL, or the simulation rate for example. Integer No
SlewDisplayPage The information page to display whilst in slew mode. Integer No
AxisIndicator The axis indicator to use.

String:

  1. Off
  2. 4 dots
  3. Small V
  4. Large V
No
Titles This option can be set to True or False to enable/disable window titles. Boolean No

 

 

[Assistance]

This section of the FLT file is used to override the different assistance options and show notifications. Certain missions - for example, Landing Challenges - will require that the user performs actions unassisted and so you can use the parameters in this section to disable specific assistance options that would normally be available in the simulation options menu. Note that if this section is not used, the activity will use the assistance's set by the user.

 

The available parameters are:

 

Parameter Description Type Required
Preset The assistance options to override. Different options will be disabled depending on the preset type chosen.

Enum, one of the following depending on the mission type:

  1. Freeflight:
    1. ASSISTANCE_PRESET_NEWCOMER
      ASSISTANCE_PRESET_AVERAGE_PLAYER
      ASSISTANCE_PRESET_TRUE_TO_LIFE
  2. Bush Trip:
    1. ASSISTANCE_PRESET_BUSH_TRIP
  3. Landing Challenge:
    1. ASSISTANCE_PRESET_LANDING_CHALLENGE
  4. Training:
    1. ASSISTANCE_PRESET_TUTORIALS
      ASSISTANCE_PRESET_TUTORIALS_NAV
      ASSISTANCE_PRESET_TUTORIALS_A320_LANDING
  5. SU10:
    1. ASSISTANCE_PRESET_LANDING_CHALLENGE_CARRIER
No
EventTriggersFileCount The number of event trigger files that are used by the flight/mission. Integer No
EventTriggersFile.N An event trigger file, where N starts at 0 and increments by 1 for each files added. This is the name of the file without the extension, and the file should be placed in the same location as the FLT file. String No

 

For more information on Event Triggers see the following page:

 

 

[AutoPilot.N]

There will be one autopilot entry for each aircraft. The available parameters are:

 

Parameter Description Type Required
MasterSwitch True if the switch is on (the autopilot is engaged). Boolean Yes
WingLeveler True if the switch is on. Boolean Yes
Nav1Lock True if the switch is on. Boolean Yes
HeadingLock True if the switch is on. Boolean Yes
HeadingValue The heading set into the autopilot. Float Yes
AltitudeLock True if the switch is on. Boolean Yes
AltitudeValue The Altitude set into the autopilot. Float Yes
AttitudeHold True if the switch is on. Boolean Yes
AirspeedHold True if the switch is on. Boolean Yes
AirspeedValue The airspeed value set into the autopilot. Float Yes
MachHold True if the switch is on. Boolean Yes
MachValue The Mach value set into the autopilot. Float Yes
VerticalSpeedHold True if the switch is on. Boolean Yes
VerticalSpeedValue The vertical speed set into the autopilot. Float Yes
RPMHold True if the switch is on. Boolean Yes
RPMValue The RPM value set into the autopilot. Float yes
GlideslopeHold True if the switch is on. Boolean Yes
ApproachHold True if the switch is on. Boolean Yes
BackCourseHold True if the switch is on. Boolean Yes
YawDamper True if the switch is on. Boolean Yes
ToGa True if the switch is on. Boolean Yes
AutoThrottleArm True if the switch is on. Boolean Yes
GPSdrivesNAV1 True if the switch is on. Boolean Yes
IsUsedForLesson True if the autopilot is being used as part of a lesson, so some functionality is disabled. Usually False. Boolean Yes
ForceDisplayUI
AutopilotDisengaged True if autopilot is disengaged. Boolean Yes
MaxBankIndex
AltitudeSlotIndex
RPMSlotIndex
SpeedSlotIndex
VSSlotIndex

 

 

[EFIS]

The EFIS (electronic flight information system) entry corresponds to the Visual Flight Path dialog. This is simply the visual aid given to identify the route the pilot should be following. The available parameters are:

 

Parameter Description Type Required
Active This should be set to True if the EFIS is active or False otherwise. Boolean Yes
NavAid The linked radio. These entries correspond to NAV1 and NAV2, which will provide the VOR or ILS signal that will be used to place the visual guides.

String:

  1. VOR 1
  2. VOR 2
Yes
Type The type of visuals to use.

String:

  1. Rectangles
  2. Telephone Poles
  3. Yellow Brick Road
  4. Hoops
Yes
Density The visual density.

String:

  1. Thin
  2. Medium
  3. Thick
Yes
Range The distance between the visuals.

String:

  1. Short
  2. Medium
  3. Long
Yes
Altitude Altitude (above MSL) below which the visual guides should be drawn. Float Yes
Flags Flags for the EFIS. 0 indicates no flags. Integer Yes

 

 

[ObjectFile]

This entry will be present when a mission is saved off, or it can be added to define the files used by a mission (when multiple XML files are used). The available parameters are:

 

Parameter Description Type Required
NbFiles The number of additional "object" files that will be listed in this section. Integer Yes
File.N The path to the mission file. This is the path and filename without the extension, and the parameter counts from 0 up to NbFiles - 1. String Yes

 

 

[FreeFlight]

Set the freeflight state. The available parameters are:

 

Parameter Description Type Required
FirstFlightState Sets the free-flight state for the aircraft. Only for missions without an XML setting the free-flight state.

String, one of the following:

  1. PREFLIGHT_GATE
  2. PREFLIGHT_PUSHBACK
  3. PREFLIGHT_TAXI
  4. PREFLIGHT_HOLDSHORT
  5. FLIGHT_RUNWAY
  6. FLIGHT_INITIAL_CLIMB
  7. FLIGHT_CLIMB
  8. FLIGHT_CRUISE
  9. FLIGHT_DESCENT
  10. LANDING_APPROACH
  11. LANDING_FINAL
  12. LANDING_TAXI
  13. LANDING_GATE
No

 

 

[Weather]

This section controls the way the weather will be created for the flight. The available parameters are:

 

Parameter Description Type Required
UseWeatherFile Set to true to use the WPR file within the mission folder. Set to false otherwise. Boolean No
UseLiveWeather Set to true to enable live weather, or false to disable it. Boolean No
WeatherPresetFile

Here you can select one of the pre-defined weather presets included as part of the default Microsoft Flight Simulator 2024 installation. The available files are:

  1. BrokenClouds.WPR
  2. ClearSky.WPR
  3. FewClouds.WPR
  4. HighLevelClouds.WPR
  5. Overcast.WPR
  6. Rain.WPR
  7. ScatteredClouds.WPR
  8. Snow.WPR
  9. Storm.WPR

The string to access these files should be formatted like this:

.\WeatherPresets\[PRESET_NAME]

For example:

WeatherPresetFile=.\WeatherPresets\ClearSky.WPR

String No
WeatherCanBeLive Set to true to permit the user to set the weather to "live" from the Weather Panel (if available) during the mission. Set to false to not let the change this setting. Boolean No
CloudmapPosOverride Set to true to override the cloudmap position using the CloudmapInitialPosX/Y parameters, or false otherwise. Boolean No
CloudmapInitialPosX This is an arbitrary offset value that can be used to reposition the cloudmap along the X axis (in meters). This can be useful to move clouds away from the initial position of the aircraft or purely for aesthetic reasons. The value will be ignored if the CloudmapPosOverride parameter is set to false. Float No
CloudmapInitialPosY This is an arbitrary offset value that can be used to reposition the cloudmap along the Y axis (in meters). This can be useful to move clouds away from the initial position of the aircraft or purely for aesthetic reasons. The value will be ignored if the CloudmapPosOverride parameter is set to false. No
FixedClouds Set to true to fix the cloud map so it doesn't change over time, or set to false to permit it to change. Boolean No

 

 

[BingMap]

This section controls certain online interactions between the simulation and BingMaps. The available parameters are:

 

Parameter Description Type Required
MinWeight This parameter is used to filter the display of Bing POI. The input must be a value between 0 and 1500, where 0 means that all Bing POI are displayed in the world, while 1500 means that none of them will be displayed. Integer No

 

 

[Departure]

Set the departure airport. The available parameters are:

 

Parameter Description Type Required
ICAO The ICAO code of the departure airport. String Yes
RunwayNumber The runway number. String Yes
RunwayDesignator The runway designator. String Yes
GateNumber The gate number (only used if the mission starts on a Parking spot). Integer No
GateName The gate name (only used if the mission starts on a Parking spot). String No
GateSuffix The gate suffix (only used if the mission starts on a Parking spot). String No

 

 

[Arrival]

Set the arrival airport. The available parameters are:

 

Parameter Description Type Required
ICAO The ICAO code of the arrival airport. String Yes
RunwayNumber The runway number. String Yes
RunwayDesignator The runway designator. String Yes
GateNumber The gate number (only used if the mission ends on a Parking spot). Integer No
GateName The gate name (only used if the mission ends on a Parking spot).

String, only one of the following:

  1. PARKING (for a ramp)
  2. GATE_N (where N is the gate letter)
No
GateSuffix The gate suffix (only used if the mission ends on a Parking spot). String No

 

 

[Loading]

Set one or more images for loading the flight along with one or more accompanying tips text. The available parameters are:

 

Parameter Description Type Required
ImageNameN The relative path and filename of the loading image to use for the mission. Images should be PNG or JPEG format and 3840*2160px in size. String Yes
TipsN

This is a "tip" text that will be shown along with the loading image. You can have multiple tips for any image, counted from 0, and these tips can be localisable. For example:

Tips0=TT:LOADING.TIPS.MISSIONNAME_000
Tips1=TT:LOADING.TIPS.MISSIONNAME_001
Tips2=TT:LOADING.TIPS.MISSIONNAME_002
String No

 

 

[TrafficManager]

This section controls the offline traffic manager. The available parameter is:

 

Parameter Description Type Required
disable

When set to 1 (TRUE) the traffic manager is disabled and there will be no offline traffic.

Default value is 0 (FALSE).

Bool No

 

 

[LivingWorld]

This section controls the offline traffic manager. The available parameters are:

 

Parameter Description Type Required
AirportLife Set to 1 (True) to remove airport life (parked aircrafts, ambient traffic, services, idle workers). Default value is 0 (False). Boolean No
RoadTraffic Set to 1 (True) to remove road traffic. Default value is 0 (False). Boolean No
BoatTraffic Set to 1 (True) to remove boat traffic. Default value is 0 (False). Boolean No

 

 

[User Tip Window]

This section controls the window for user tips. The available parameters are:

 

Parameter Description Type Required
Undocked Set to True if the window has been undocked, in which case the window will be located at UndocCoords. Bool No
ScreenUniCoords The current screen co-ordinates of the panel window. See the note on Universal Screen Co-ordinates. 4 Floats Yes
UndocCoords The co-ordinates of the window if it has been undocked. See the note on Universal Screen Co-ordinates. 4 Floats Yes

 

 

[Atc_Menu]

This section is related to the ATC menu window. The available parameters are:

 

Parameter Description Type Required
Visible Set to True if the window is visible, or false otherwise. Boolean Yes
ScreenUniCoords The current screen co-ordinates of the ATC window. See the note on Universal Screen Co-ordinates. The data for this parameter should be in a 4 value comma separated list, eg: ScreenUniCoords=2968, 811, 4304, 3702 4 Floats No
UndocCoords The co-ordinates of the window if it has been undocked. See the note on Universal Screen Co-ordinates. The data for this parameter should be in a 4 value comma separated list, eg: UndocCoords=0, 0, 0, 0 4 Floats No
Undocked Set to True if the window has been undocked or False otherwise. When set to True, the window will be located at UndocCoords and undocked windows will have a border and title. Boolean No

 

 

[ATC_AgentManager]

This section is for defining the number of ATC agents within the simulation. The available parameter is:

 

Parameter Description Type Required
NumberofAgents Number of current ATC agents. If this number is 0, there will be no [ATC_Aircraft.N] or [ATC_Agent.n] entries. There will be an ATC agent if an aircraft is flying with a flight plan. Integer Yes

 

 

[ATC_AircraftManager]

This defines the number of aircraft in the ATC manager. The available parameters are:

 

Parameter Description Type Required
NumberofAircraft The number of aircraft. Usually 1. Integer Yes

 

 

[ATC_MessageSystem]

Sets up the ATC message system. The available parameters are:

 

Parameter Description Type Required
FrequencyNodes Usually this value is 0. It will be non-zero if the flight has been saved mid-message. In this case there should be an [ATC_FrequencyNode.N] entry and usually an [ATC_MessageNode.N.i] entry. Integer Yes

 

 

[ATC_Agent.n]

There will be an [ATC_Agent] entry for each agent, which can be none in free flight.

 

Parameter Description Type Required
AgentType The type of ATC agent.

String:

  1. ATIS
  2. ClearanceDelivery
  3. Ground
  4. Tower
  5. Center
  6. Approach
  7. Departure
  8. FSS
  9. CTAF
  10. ASOS
Yes
CallSign The callsign of the ATC agent. String Yes
Frequency The COM frequency of the ATC agent. This is an integer value, for example: 1294000, which would be translated to 129.4000. Integer Yes
NumberOfAircraft The number of aircraft the agent is tracking. Usually 1. Integer Yes
SecLastMessage Simtime of the last message. Float Yes

 

 

[ATC_Aircraft.N]

This section is for defining properties to specific aircraft involved int he flight. The available parameters are:

 

Parameter Description Type Required
ActiveFlightPlan This will be True if the user aircraft has a flight plan, or False otherwise. The ATC will follow the flightplan and markers will be placed in the simulation - if the assistances allows it - when True. Boolean Yes
RequestedFlightPlan This will be True if the user aircraft has requested a new flight plan, and that request has not yet been answered, otherwise it will be False. Contrary to the ActiveFlightPlan field, ATC and in-simulation markers will not be active. Boolean Yes
AcState The current aircraft status.

Enum:

  1. ACSTATE_NONE

// IFR Clearance

  1. ACSTATE_PRETAXI_CLEARANCE
    ACSTATE_IFR_CLEARANCE_READBACK
    ACSTATE_IFR_CLEARANCE_WAIT_FOR_READBACK_GOOD

// Departure ground operations

  1. ACSTATE_CTAF_TAKEOFF
    ACSTATE_DYNAMIC_RUNWAY_CTAF_TAKEOFF
    ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_VFR_ATIS
    ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_VFR_NOATIS
    ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_IFR
    ACSTATE_TAXI_CLEARANCE_READBACK
    ACSTATE_TAXIING_OUT
    ACSTATE_ACKNOWLEDGE_HOLD_POSITION
    ACSTATE_ACKNOWLEDGE_CONTINUE_TAXI
    ACSTATE_TOWER_HOLDSHORT_ACKNOWLEDGE
    ACSTATE_TAKEOFF_POSITION_AND_HOLD_ACKNOWLEDGE
    ACSTATE_TAKEOFF_CLEARANCE_READBACK
    ACSTATE_DYNAMIC_RUNWAY_TAKEOFF

// Class D departure operations

  1. ACSTATE_TOWER_DEPARTING

// VFR enroute operations

  1. ACSTATE_VFR_ENROUTE_CONTACT
    ACSTATE_VFR_ENROUTE

// Flight Following and Airspace Transitions

  1. ACSTATE_ACKNOWLEDGE_SQUAWK
    ACSTATE_ACKNOWLEDGE_RADAR_CONTACT_FF
    ACSTATE_ACKNOWLEDGE_RADAR_CONTACT_TRANSITION
    ACSTATE_ACKNOWLEDGE_LEAVING_AIRSPACE_NOFF
    ACSTATE_ACKNOWLEDGE_TRANSITION_CLEARANCE_CLASS_BC
    ACSTATE_ACKNOWLEDGE_TRANSITION_CLEARANCE_CLASS_D

// Popup IFR States

  1. ACSTATE_ACKNOWLEDGE_INFLIGHT_IFR_CLEARANCE
    ACSTATE_INFLIGHT_IFR_CLEARANCE_WAIT_FOR_READBACK_GOOD

// Handoffs

  1. ACSTATE_AGENT_CONTACT
    ACSTATE_AGENT_HANDOFF

// IFR Enroute state

  1. ACSTATE_ARRIVAL
    ACSTATE_DYNAMIC_RUNWAY_ARRIVAL
    ACSTATE_DYNAMIC_APPROACH_ARRIVAL
    ACSTATE_DYNAMIC_APPROACH_TRANSITION_ARRIVAL
    ACSTATE_ARRIVAL_CANCEL_IFR

// States that loop back to ARRIVAL after aircraft responds

  1. ACSTATE_ARRIVAL_VECTOR
    ACSTATE_ARRIVAL_EXPECT
    ACSTATE_CRUISING_ALTITUDE_INCREASE
    ACSTATE_CRUISING_ALTITUDE_DECREASE
    ACSTATE_DYNAMIC_RUNWAY_ARRIVAL_EXPECT
    ACSTATE_DYNAMIC_APPROACH_ARRIVAL_EXPECT
    ACSTATE_DYNAMIC_APPROACH_TRANSITION_ARRIVAL_EXPECT
    ACSTATE_ARRIVAL_CLEARED
    ACSTATE_ARRIVAL_CLEARED_FULL_PROCEDURE
    ACSTATE_DYNAMIC_AIRPORT_LANDING

// Class D arrival operations

  1. ACSTATE_AGENT_HANDOFF_TOWER
    ACSTATE_TOWER_CONTACT
    ACSTATE_TOWER_CONTACT_IFR
    ACSTATE_TOWER_TRANSITION
    ACSTATE_TOWER_PATTERN_ENTRY
    ACSTATE_DYNAMIC_RUNWAY_PATTERN_ENTRY
    ACSTATE_TOWER_LANDING
    ACSTATE_DYNAMIC_RUNWAY_LANDING
    ACSTATE_TOWER_HANDOFF_GROUND
    ACSTATE_TOWER_CLEARED_TO_LAND
    ACSTATE_GO_AROUND_ACKNOWLEDGE
    ACSTATE_AGENT_HANDOFF_TOWER_MISSED_APPROACH
    ACSTATE_AGENT_CONTACT_MISSED_APPROACH

// CTAF Operations

  1. ACSTATE_CTAF_LANDING_TYPE
    ACSTATE_DYNAMIC_RUNWAY_CTAF_LANDING_TYPE
    ACSTATE_CTAF_LANDING
    ACSTATE_DYNAMIC_RUNWAY_CTAF_LANDING

// Arrival ground operations

  1. ACSTATE_REQUEST_TAXI_CLEARANCE_IN
    ACSTATE_TAXI_CLEARANCE_IN_READBACK
    ACSTATE_TAXIING_IN
    ACSTATE_ACKNOWLEDGE_HOLD_POSITION_IN
    ACSTATE_ACKNOWLEDGE_CONTINUE_TAXI_IN
Yes
TaxiRouteAirport The ICAO for the airport taxi route. String No
TaxiRoute.N This entry will only exist if the aircraft is currently following a cleared taxi route, and holds the taxiway route being followed. Each entry takes five numbers: the index of the TaxiwayPath, the TaxiwayPoint to head for, the direction along the path -- which will depend on the order in which the points were defined (1 = forward, 2 = backward), an unused number (always 0), and the runway index number if the route is along a runway. For example:
TaxiRoute.0=27,11,2,0,2
TaxiRoute.1=26,10,2,0,0
TaxiRoute.2=25,9,2,0,0
String No
NumTaxiRoute The number of TaxiRoute entries. Integer No
NumberofWaypoints The number of waypoints in the route (not taxiway points). This can be zero if the aircraft has not cleared a flight plan, is often two for a VFR or direct IFR route, but can be many more for a more complex IFR route. The waypoints will match exactly those in the ActiveFlightPlan, if there is such a flight plan. Integer Yes
ClearanceFlags Hex number containing Boolean flags:
  • 0x0001: User is IFR
  • 0x0002: User has been assigned a new altitude
  • 0x0004: User has been assigned a new heading
  • 0x0008: User has been assigned a left turn
  • 0x0010: User has arrived at their cleared altitude
  • 0x0020: User has declared missed and needs an altitude assignment
  • 0x0040: User is requesting Popup IFR clearance
  • 0x0080: This is the first assigned approach for the user
  • 0x0100: User has declared missed and is flying published missed approach
  • 0x0200: User is descending to their arrival airport
The following example shows the flags for an aircraft that has just declared a missed approach:
ClearanceFlags=2F
Hex Yes
CtCur Current clearance.

String:

  1. CLEARANCE_NONE
    CLEARANCE_OWNNAV
    CLEARANCE_VECTORS_INTERCEPT_LEFT
    CLEARANCE_VECTORS_INTERCEPT_RIGHT
    CLEARANCE_VECTORS_ROUTE
Yes
WaypointNext The waypoint the aircraft is currently heading for. Note that waypoints are indexed from zero. Integer Yes
AltCleared The altitude the aircraft has been instructed to fly at, in ft. Float Yes
HdgAssigned The assigned heading, in radians, or -1 if no heading has been assigned. Float Yes
SquawkAssigned The assigned squawk number. The saved value is a decimal number, that when converted to hexadecimal the last four digits will be the squawk number in octal. The example below gives the assigned number of 543650387. When converted to hex this gives 20677253, the last four digits -- 7253 -- are the squawk number in octal. Note that this number matches the code for the transponder in the [Avionics.N] section. The remaining digits are irrelevant and are ignored (this is a known issue). Example:
SquawkAssigned=543650387
Integer Yes
LandingSequence The landing sequence identifier.

String:

  1. LANDING_NONE
    LANDING_IFR_EXPECTING_APPROACH
    LANDING_IFR_CLEARED_FOR_APPROACH
    LANDING_IFR_CLEARED_TO_LAND
    LANDING_VFR_FULL_STOP_REQUEST
    LANDING_VFR_FULL_STOP_FLYING_PATTERN
    LANDING_VFR_FULL_STOP_CLEARED_TO_LAND
    LANDING_VFR_TOUCH_AND_GO_REQUEST
    LANDING_VFR_TOUCH_AND_GO_FLYING_PATTERN
    LANDING_VFR_TOUCH_AND_GO_CLEARED_TO_LAND
Yes
DepartureRequest The departure request type.

String:

  1. DEPARTURE_VFR_REQUEST_REMAIN_IN_PATTERN
    DEPARTURE_VFR_REQUEST_DEPART_STRAIGHT_OUT
    DEPARTURE_VFR_REQUEST_DEPART_NORTH
    DEPARTURE_VFR_REQUEST_DEPART_SOUTH
    DEPARTURE_VFR_REQUEST_DEPART_EAST
    DEPARTURE_VFR_REQUEST_DEPART_WEST
    DEPARTURE_VFR_REQUEST_NONE
Yes
ParkingRequest The parking request.

String:

  1. PARKING_NAME_NONE
    PARKING_NAME_PARKING
    PARKING_NAME_N_PARKING
    PARKING_NAME_NE_PARKING
    PARKING_NAME_E_PARKING
    PARKING_NAME_SE_PARKING
    PARKING_NAME_S_PARKING
    PARKING_NAME_SW_PARKING
    PARKING_NAME_W_PARKING
    PARKING_NAME_NW_PARKING
    PARKING_NAME_GATE
Yes
ParkingTypeequest The parking request type.

String:

  1. PARKING_TYPE_NONE
    PARKING_TYPE_RAMP_GA
    FAC_TAXI_PARKING_TYPE_RAMP_GA_SMALL
    PARKING_TYPE_RAMP_GA_MEDIUM
    PARKING_TYPE_RAMP_GA_LARGE
    PARKING_TYPE_RAMP_CARGO
    PARKING_TYPE_RAMP_MIL_CARGO
    PARKING_TYPE_RAMP_MIL_COMBAT
    PARKING_TYPE_GATE_SMALL
    PARKING_TYPE_GATE_MEDIUM
    PARKING_TYPE_GATE_HEAVY
    PARKING_TYPE_DOCK_GA
    PARKING_TYPE_FUEL
    PARKING_TYPE_VEHICLE
Yes
PatternLeg

String:

  1. PATTERN_LEG_NONE
    PATTERN_LEG_DOWNWIND
    PATTERN_LEG_CROSSWIND
    PATTERN_LEG_SHORT_FINAL
    PATTERN_LEG_FINAL
    PATTERN_LEG_BASE
    PATTERN_LEG_UPWIND
Yes
ApproachIndex The index number of the approach for the destination airport, or -1 if no approach has cleared. Integer Yes
ApproachTransitionIndex The index number of the approach transition for the destination airport, of -1 if no approach transition has been cleared. Integer Yes
ApproachRequestIndex The index number of the approach that has been requested by the pilot, but has not yet been cleared. Integer Yes
ApproachTransitionRequestIndex The index number of the approach transition that has been requested by the pilot, but has not yet been cleared. Integer Yes
RunwayIndex The index number of the destination airport runway, or -1 if no runway has been assigned. Integer Yes
RunwayRequestIndex The index number of the destination airport runway requested by the pilot, but has not yet been assigned. Integer Yes
ParkingIndex The index number of the parking spot assigned to the aircraft at the destination airport, or -1 if no parking spot has been assigned. Integer Yes
FlightFollowing

String:

  1. FLIGHT_FOLLOWING_NO
    FLIGHT_FOLLOWING_REQUEST
    FLIGHT_FOLLOWING_YES
Yes
AirspaceTransition

String:

  1. AIRSPACE_TRANSITION_NONE
    AIRSPACE_TRANSITION_REQUEST
    AIRSPACE_TRANSITION_YES
Yes
BvAirspaceTransition

String:

  1. BV_TYPE_NONE
    BV_TYPE_CENTER
    BV_TYPE_CLASS_A
    BV_TYPE_CLASS_B
    BV_TYPE_CLASS_C
    BV_TYPE_CLASS_D
    BV_TYPE_CLASS_E
    BV_TYPE_CLASS_F
    BV_TYPE_CLASS_G
    BV_TYPE_TOWER
    BV_TYPE_CLEARANCE
    BV_TYPE_GROUND
    BV_TYPE_DEPARTURE
    BV_TYPE_APPROACH
    BV_TYPE_MOA
    BV_TYPE_RESTRICTED
    BV_TYPE_PROHIBITED
    BV_TYPE_WARNING
    BV_TYPE_ALERT
    BV_TYPE_DANGER
    BV_TYPE_NATIONAL_PARK
    BV_TYPE_MODE_C
    BV_TYPE_MAX
Yes
BvAirspaceTransitionReq Yes
TakeOffSequence

String:

  1. TAKEOFF_SEQUENCE_NONE
    TAKEOFF_SEQUENCE_HOLDSHORT
    TAKEOFF_SEQUENCE_TAXI_AND_HOLD
    TAKEOFF_SEQUENCE_CLEARED
    TAKEOFF_SEQUENCE_OUT_OF_AREA
Yes
LandingsSquenceNumber If the aircraft is to land following other aircraft, this number is the aircraft's landing sequence number. For example, if this value is 3, then the aircraft is to follow two other aircraft. If this is not the case, then this property should be -1. Integer Yes
TaxiRouteCurrent The index number of the taxiroute entry the aircraft is currently on, or -1 if the aircraft is not on a taxiway route (so there are no TaxiRoute, or NumTaxiRoute entries). Integer Yes
CruisingAltitude The current cruising altitude. Float Yes
RequestedCruisingAltitude The requested cruising altitude, if an altitude change has been requested, or -1 if there is no such request. Float Yes
ExpectedAltitude The altitude the user aircraft pilot is told to expect, in feet, or -1 if this does not apply. Float Yes
AircraftSignature The aircraft signature. This will be 1,0 for the user aircraft. 2 value list Yes
AgentTracking The signature of the ATC agent (refer to ATC Agent Signatures). 4 float values Yes
Waypoint.N The list of waypoints making up the IFR or VFR flight plan. Refer to the notes on Waypoint Format. Comma separated list Yes
AgentHandoff The signature of the ATC agent the aircraft will be handed off to (refer to ATC Agent Signatures). 4 float values Yes
ActiveVfrAirport The active VFR airport. This will be present even if the aircraft is flying under IFR rules. String Yes

 

 

[ATC_AircraftData.N]

There will be an [ATC_AircraftData.N] entry for each aircraft flying with a flight plan, which can be none in free flight. When adding this entry, each one should be given a unique number, starting at 0. The available parameters are:

 

Parameter Description Type Required
AircraftSignature The aircraft signature. 1,0 for the user aircraft. Float Yes
Contacted This will be True if the ATC agent has made contact with the aircraft or False otherwise. Boolean Yes
SecLastDing Time of the last ding (correcting message), or 0 if there was none. Integer Yes
NumDings The number of times the pilot has been dinged. After three dings the pilot is removed from ATC control. After a forgiveness period the number of dings is reduced to zero. Integer Yes
LastDing The ATC Message ID of the last ding, or 0 if there was no last ding. Integer Yes
LastMessage The last transmitted ATC Message ID. Integer Yes
HandedOff This will be True if the aircraft has been handed off to another ATC agent or False otherwise. Boolean Yes
TimeStampOnRunway The number of seconds an aircraft has been on the runway, after landing, or 0 if the aircraft has not just landed.
BVAirspaceTransitionPrev The previous transition value.

String:

  1. BV_TYPE_NONE
    BV_TYPE_CENTER
    BV_TYPE_CLASS_A
    BV_TYPE_CLASS_B
    BV_TYPE_CLASS_C
    BV_TYPE_CLASS_D
    BV_TYPE_CLASS_E
    BV_TYPE_CLASS_F
    BV_TYPE_CLASS_G
    BV_TYPE_TOWER
    BV_TYPE_CLEARANCE
    BV_TYPE_GROUND
    BV_TYPE_DEPARTURE
    BV_TYPE_APPROACH
    BV_TYPE_MOA
    BV_TYPE_RESTRICTED
    BV_TYPE_PROHIBITED
    BV_TYPE_WARNING
    BV_TYPE_ALERT
    BV_TYPE_DANGER
    BV_TYPE_NATIONAL_PARK
    BV_TYPE_MODE_C
    BV_TYPE_MAX
Yes
HasReachedClassD This value will be True if the aircraft has reached Class D airspace, or False otherwise. Boolean Yes

 

 

[ATC_ActiveFlightPlan.N]

This entry will exist if the user aircraft is flying with a current flight plan, either IFR or VFR. Note that This section is only necessary if your mission has an active flightplan, and the parameter ActiveFlightPlan of the section [ATC_Aircraft.N] must be set to True. The available parameters are:

 

Parameter Description Type Required
title The title of the flight plan, taken from the Title entry in the PLN file. String Yes
description The Description entry from the PLN file. String Yes
type The flight plan type.

String:

  1. IFR
    VFR
Yes
routetype This entry will be 0 if type is VFR. For IFR it will be one of the integer values shown.

Integer:

  1. 0 = Direct (GPS)
    1 = VOR to VOR
    2 = Low altitude airways
    3 = High altitude airways
Yes
cruising_altitude The assigned cruising altitude in the current flight plan. Float Yes
departure_id The ICAO of the departure airport, and its lat/lon/alt, in the DepartureLLA element of the PLN file. For example:
departure_id=KSEA, N47° 25.89', W122° 18.48', +000433.00
Comma separated list Yes
departure_position

The runway number and optional designator of the departure. For example:

departure_position=34R

Note that this must be identical to that which is set in the [Departure] section.

String Yes
destination_id The ICAO of the destination airport, and its lat/lon/alt, in the DestinationLLA element of the PLN file. For example:
destination_id=KLAX, N33° 56.16', W118° 25.13', +000126.00
Comma separated list Yes
departure_name The name of the departure airport. String Yes
destination_name The name of the destination airport. String Yes
waypoint.N The list of waypoints making up the route. Often this is only two waypoints, the departure and destination airports. Refer to the notes on Waypoint Format. Note that you should have as many waypoints defined as already listed in the [ATC_Aircraft.N] section. Comma separated list Yes

 

 

[ATC_RequestedFlightPlan.N]

This entry will only be present if the user aircraft has requested a new flight plan, and has yet to receive confirmation that this flight plan has been cleared. In some cases a flight file will have both an [atc_activeflightplan.N] and an [atc_requestedflightplan.N] (when a change from one flight plan to another has been requested), and in others just either one of these entries. The property list is identical to that of [ATC_ActiveFlightPlan.N].

 

 

[ATC_FrequencyNode.N]

Defines an ATC frequency node to be used with the ATC message system. The available parameters are:

 

Parameter Description Type Required
Frequency Com frequency (120.1 in the example). Float yes
CurrMessage True if the current message is saved, in which case an [ATC_MessageNode.N.i] entry should exist for the message. Boolean Yes
TotalMessageCount The number of messages. Usually 1. Integer Yes

 

 

[ATC_MessageNode.N.i]

A message node for the ATC message system. The available parameters are:

 

Parameter Description Type Required
Seconds The time it will take to read the message, in seconds. Float Yes
MessageID The ATC Message ID of the message. Integer Yes
TimeStamp Simtime of the message. Float Yes
CommUnitFrom The agent the message is from (refer to ATC Agent Signatures). Comma separated list Yes
CommUnitTo The signature of the aircraft the message is to. Usually 1,0 for the user aircraft. 2 value list Yes

 

 

[GPS_Engine]

A [GPS_Engine] entry will be present if the user aircraft is flying under ATC rules - IFR or VFR - and has an active flightplan. The available parameters are:

 

Parameter Description Type Required
Filename The name the flight plan file, without the file extension. String Yes
position The lat/lon/alt position of the aircraft. Note that the minutes section is recorded as a decimal, and not as minutes and seconds. There can be a small discrepancy between this position, and that recorded in the [SimVars.N] section, which is due to the slower frequency that this position is recorded by the GPS system. Comma separated list Yes
Time Current Zulu time. Integer Yes
TimeWP Zulu Time (in seconds) when the aircraft passed the last waypoint. Integer Yes
ArriveTime Estimated time en route, in seconds. Integer Yes
CountWP The number of waypoints listed in this section. You must have as many waypoints as already created in the [ATC_Aircraft.N] section. Integer Yes
NextWP The next waypoint the aircraft is heading for. Note the waypoints are numbered from 0, so 1 for this value, with two waypoints, indicates the aircraft is heading for the second and last waypoint. Integer Yes
PlaneStarted True when the aircraft takes off, False otherwise. Boolean Yes
WpInfoN Waypoint information in the order:
  • estimated knots,
  • actual knots,
  • height in meters,
  • actual time enroute,
  • estimated time of arrival,
  • fuel remaining when arrived,
  • estimate of fuel required for the leg,
  • actual fuel used for the leg.
Some of the values may be unknown and recorded as zero. For example:

WpInfo0=473, 0, 131, 0, 8459, 2909.8, 0.0, 0.0
WpInfo1=473, 0, 161, 0, 47577, 2909.8, 0.2, 0.0
WpInfo2=473, 0, 5486, 0, 48856, 0.0, 137.0, 0.0

Comma separated list Yes
CountFP The number of flight path points recorded. Integer Yes
FpN

For each flight path point, a coded version of the latitude and longitude (in hex). Note that each line number (0 to N) holds four flight path points.
The latitude is coded as: 128 * ((latitude as a decimal value) * (90.0 / 10001750))
The longitude is coded as: (((longitude as a decimal value) * ((65536.0/360.0) * 65536.0 )))

For example:
FP0=293ede80,a83d7546,293eee26,a83d2f9e,293efe7a,a83ce5ff,293f14d8,a83c8046

Comma separated list Yes

 

 

[Covers]

This section is related to the preflight checks that are done to prepare an aircraft before takeoff. Each parameter relates to a cover or item that needs to be removed before the aircraft can fligh and as such this section and parameter is only required in the hanger.flt and apron.flt.

 

Parameter Description Type Required
chock

Sets whether the chocks should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).

Default value is 0.

Boolean No
engine

Sets whether the engine covers should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).

Default value is 0.

Boolean No
pitot

Sets whether the pitot head covers should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).

Default value is 0.

Boolean No
static_port

Sets whether the static port covers should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).

Default value is 0.

Boolean No
rotor

Sets whether the rotor covers should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).

Default value is 0.

Boolean No
landing_gear

Sets whether the landing gear pins should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).

Default value is 0.

Boolean No

 

 

[Dirt.N]

This section can be added to define the quantity of dirt, grime and general wear and tear the aircraft show show when spawned. The available parameters are:

 

Parameter Description Type Required
Runway

Defines how much runway dirt will be present on the aircraft. Value is expressed as a Percent Over 100.

Float No
Regular Defines how much general dirt from use and wear and tear will be present on the aircraft. Value is expressed as a Percent Over 100. Float No
FadedPaint Defines how faded the aircraft paint will appear. Value is expressed as a Percent Over 100. Float No
Mud Defines how much mud will be present on the aircraft. Value is expressed as a Percent Over 100. Float No
Dust Defines how much dust will be present on the aircraft. Value is expressed as a Percent Over 100. Float No

 

 

[DateTimeSeason]

Sets the date, time and seasonal details for the flight. The available parameters are:

 

Parameter Description Type Required
Season The current season.

String:

  1. Winter
  2. Spring
  3. Summer
  4. Fall
Yes
Year The current year. Integer Yes
Day The current day (0 to 365). Integer Yes
Hours The current hour (0 to 23), local time. Integer Yes
Minutes The current minute (0 to 57). Integer Yes
Seconds The current second (0 to 57). Float Yes
UseZuluTime Set to True to use Zulu Time or False otherwise. Boolean Yes

 

[Camera.N.i]

These sections are used for setting a camera for the flight and there can be a large number of these entries in every FLT file. The section is numbered using the following format:

Camera.<window number>.<camera number>

The available parameters for each of these sections are:

 

Parameter Description Type Required
Guid The GUID of the camera. One of these entries will match the GUID for the CurrentCamera in each of the [Window.N] sections. See here for how to generate these ID string: GUIDs. String Yes
Zoom Zoom factor of the camera (refer to the Camera Configuration documentation for more details). Float Yes
Translation The X, Y and Z offset of the camera. This is a 3 value comma separated list, for example: Translation=0,0,0 3 Floats Yes
Rotation

Rotation of the camera for pitch, bank and heading. This is a 3 value comma separated list, for example: Rotation=-1,0,0

This entry is not required for external views.

3 Floats No
ChaseDirection The chase camera direction. This entry is not required for external views. Float No
ChaseDistance The chase camera distance. This entry is not required for external views. Float No
ChaseAltitude The chase camera altitude. This entry is not required for external views. Float No

 

 

[SimplifiedSim.N]

This sets an optimised simulation type for the AI aircraft in the simulation. The available parameters are:

 

Parameter Description Type Required
Mode The implied simulation mode to use.

String:

  1. None
    AI_Air
    AI_Taxi
    AI_LandingTakeoff
    Data_Air
    Data_ground
Yes

 

 

[Sim.N]

There will be one sim entry for each sim object saved off. This will include one entry for the user aircraft, and one for each mission object. If mission objects are saved off then each one is noted by one [Sim.n], [SimVars.N], [Slew.N] and [Freeze.N] entry. The available parameters are:

 

Parameter Description Type Required
Sim The title of the aircraft, or object, in the aircraft.cfg. String Yes
Livery This is the name of the livery folder that is to be used for the activity that this section is assigned to. String No
Pilot

This is the title of the SimObject - as set in the sim.cfg file for a human SimObject - that is to be used as the pilot for the mission. If you do not set this parameter - or set it to an empty string - then the pilot that is set in the aircraft.cfg file will be used (see the [PILOT] section). For a list of pilots available without creating your own SimObjects, please see the List Of Included Pilot/Copilot/Instructor SimObjects.

NOTE: In "freeflight", this parameter will be created with an empty string as the parameter value as part of the automatic creation of the *.flt file. In these cases, if the aircraft Flight Model Config Definition has not defined a pilot station_load.N then NO pilot will be spawned, regardless of the [PILOT] configuration.

String No
Copilot

This is the title of the SimObject - as set in the sim.cfg file for a human SimObject - that is to be used as the copilot for the mission. If you do not set this parameter - or set it to an empty string - then the copilot that is set in the aircraft.cfg file will be used (see the [PILOT] section). For a list of copilots available without creating your own SimObjects, please see the List Of Included Pilot/Copilot/Instructor SimObjects.

NOTE: In "freeflight", this parameter will be created with an empty string as the parameter value as part of the automatic creation of the *.flt file. In these cases, if the aircraft Flight Model Config Definition has not defined a pilot station_load.N then NO copilot will be spawned, regardless of the [PILOT] configuration.

String No
Instructor This is the title of the SimObject - as set in the sim.cfg file for a human SimObject - that is to be used as the instructor in the aircraft. This title is only used for user aircraft (never AI ones). For a list of instructors available without creating your own SimObjects, please see the List Of Included Pilot/Copilot/Instructor SimObjects. Note that you may also set this to "default", in which case the instructor defined will be that which has been defined in the [PILOT] section of the aircraft.cfg file for the aircraft being flown. String No
TailNumber
AirlineCallSign
FlightNumber
AppendHeavy
SimFile Load a specific aircraft configuration at the start of the mission, depending on the Sim state you need.

String, one of the following:

  1. apron.flt
    runway.flt
    climb.flt
    cruise.flt
    final.flt
    taxi.flt
No
ChecklistFolder Used to load a specific checklist, overriding the one for the aircraft. If a checklist isn't needed by the activity, set this field to "NONE" to free memory and loading time. String No

 

 

[Panel.N]

For the user aircraft there is a [Panel.N] entry for every panel, such as the main panel, radio stack, GPS, throttle controls, and so on. The panels are numbered from 1, and will be in the same order that they appear in the Panel Configuration Files. The available parameters are:

 

Parameter Description Type Required
ScreenUniCoords The current screen co-ordinates of the panel window. See the note on Universal Screen Co-ordinates. 4 Floats Yes
UndocCoords The co-ordinates of the window if it has been undocked. See the note on Universal Screen Co-ordinates. 4 Floats Yes
Visible True if the window is visible, False otherwise. Boolean Yes
Undocked Set to True if the window has been undocked, in which case the window will be located at undoccoords. Boolean Yes
HiddenOn Unused. Always False. Boolean No
ID The ID number of the panel. A panel with the ID of 20000 is the mini-panel. Panels from 22001 to 22008 are racing aid panels used by the mission system (in the order: Point of interest, Timer, Dropable Object, Race map, Race Info, G meter, Race penalty, and Countdown) which are saved off even if a mission is not being run. Integer Yes
ViewsOn This value will be set to 1 if the panel should be displayed if the full cockpit is in view. The panel may not be visible though if the view is currently set to the mini-panel, or to no panel. Integer Yes

 

 

[Avionics.N]

There will be one avionics entry for each aircraft. The available parameters are:

 

Parameter Description Type Required
Comm1Active Frequency of COM1. Float Yes
Comm1Standby Frequency of COM1 standby. Float Yes
Comm2Active Frequency of COM2. Float Yes
Comm2Standby Frequency of COM2 standby. Float Yes
Comm3Active Frequency of COM3. Float Yes
Comm3Standby Frequency of COM3 standby. Float Yes
Nav1Active Frequency of NAV1. Float Yes
Nav1Standby Frequency of NAV1 standby. Float Yes
OBS1 Position of the OBS for NAV1, in degrees. Float Yes
Nav2Active Frequency of NAV2. Float Yes
Nav2Standby Frequency of NAV2 standby. Float Yes
OBS2 Position of OBS for NAV2, in degrees. Float Yes
Nav3Active Frequency of NAV3. Float Yes
Nav3Standby Frequency of NAV3 standby. Float Yes
OBS3 Position of OBS for NAV3, in degrees. Float Yes
Nav4Active Frequency of NAV4. Float Yes
Nav4Standby Frequency of NAV4 standby. Float Yes
OBS4 Position of OBS for NAV4, in degrees. Float Yes
Transponder Frequency of transponder (an octal code number that should match the coded assigned squawk number from the [ATC_Aircraft.N] section). String Yes
TransponderState The transponder state.

Integer:

  1. 0 = Off
    1 = Standby
    2 = On
    3 = Alt
    4 = Ground
Yes
ADFActive The frequency of ADF 1 (automatic direction finder). Float Yes
ADF2Active The frequency of ADF 2. Float Yes
DMESelected The selected DME, either 1 or 2. Integer Yes
ComTransmit The selected COM channel, either 1 or 2. Integer Yes
ComReceiveBoth True if the switch is on, False otherwise. Boolean Yes
Com1Receive Yes
Com2Receive Yes
Com3Receive Yes
AudioNav1Listen True if the switch is on, False otherwise. Boolean Yes
AudioNav2Listen True if the switch is on, False otherwise. Boolean Yes
AudioMarkerListen True if the switch is on, False otherwise. Boolean Yes
AudioDmeListen True if the switch is on, False otherwise. Boolean Yes
AudioAdfListen True if the switch is on, False otherwise. Boolean Yes
AudioAdf2Listen True if the switch is on, False otherwise. Boolean Yes
AvionicsSwitch True if the switch is on, False otherwise. Boolean Yes

 

 

[Slew.N]

There will be a slew entry for each simulation object saved off. In slew mode an object is simply being moved at a constant speed in various directions or orientations. Some, but not all, information on the slew movement is preserved in the [SimVars.N] section. The available parameters are:

 

Parameter Description Type Required
Active True indicates the object is in slew mode, False means it is not. Boolean Yes

 

 

[Freeze.N]

If the aircraft is under control from a SimConnect addon, for example, then the simulator is instructed not to alter certain parameters by "freezing" it out. The available parameters that can be frozen are:

 

Parameter Description Type Required
Location True if the simulation is not to alter the location of the aircraft, False otherwise. Boolean Yes
Altitude True if the simulation is not to alter the altitude of the aircraft, False otherwise. Boolean Yes
Attitude True if the simulation is not to alter the attitude (pitch, bank and heading) of the aircraft, False otherwise. Boolean Yes

 

 

[SystemFailureN.i]

Optional entries. These will only be present if one or more system failures are set, which can be from a mission. The first number (N) is the index of the failure, indexed from 0. The second number (i) is the aircraft reference, usually 0 for the user aircraft. So the first entry is usually [SystemFailure0.0], followed by [SystemFailure1.0], and so on. There can be up to 1000 failures on an aircraft. The available parameters that can be frozen are:

 

Parameter Description Type Required
ID One entry from the Failure Code Table, identifying the component that has, or is to, fail. Note that the alpha characters (A through F) must be in upper case. String Yes
SubIndex If there are multiple components, such as engines, this parameter gives the index of the component to fail, indexed from 0. Indexing starts from the left. Integer Yes
Health The percentage health of the system, from 0.0 (total failure) to 1.0(fully functional). The system will be set to this health value when the flight file is loaded -- so this is the current health, not the health to be applied when the system fails after a certain time. Float Yes
Armed

If set to True, the component is initially functional at the level set by the health property, but fails completely at some point between the ArmedFailureFromTime and the ArmedFailureToTime.

If set to False, the system will operate at the level set by the health property indefinitely. In this later case both ArmedFailureFromTime and ArmedFailureToTime should be present and set to zero.

Boolean Yes
ArmedFailureFromTime Time in seconds from the start of the simulation when the component might fail. Float Yes
ArmedFailureToTime Time in seconds from the start of the simulation when the component will fail. Float Yes

 

 

[Engine Parameters.N.i]

There is one of these entries for each engine, so - for example - a Cessna will have one entry, and a Boeing 747 will have four. The first number (N) is the engine number, starting at 1, and the second (i) is the aircraft number (0 for the user aircraft). The available parameters are:

 

Parameter Description Type Required
ThrottleLeverPct Percentage that the throttle lever has been applied, from 0 to 1.0. Float Yes
PropellerLeverPct Percentage that the propeller lever has been applied, from 0 to 1.0. Float No
MixtureLeverPct Percentage that the mixture lever has been applied, from 0 to 1.0. Float No
Pct Engine RPM Current engine rpm as a percentage of rated rpm. The normal range is 0 to 1.0, but for some engines going over the rated rpm is possible. Float No
MaxReachedEngineRPM Some gauges record the maximum rpm reached on a flight, so this value is recorded here. Float No
Pct N1 Set the N1 value that the aircraft should start with, expressed as a Percent Over 100. Float No
Pct N2 Set the N2 value that the aircraft should start with, expressed as a Percent Over 100. Float No
LeftMagneto True if the switch is on. Boolean No
RightMagneto True if the switch is on. Boolean No
GeneratorSwitch True if the switch is on. Boolean No
CowlFlapPct

Percentage that the cowl flaps are open. This affects the cylinder head temperature cooling as follows:

CHTCooling = true_airspeed_fps * density_ratio / temperature_ratio + cowl_flaps_pos * 80
Float No
FuelPumpSwitch True if the switch is on. The corresponding SimVar is GENERAL ENG FUEL PUMP SWITCH. Boolean No
FuelPumpSwitch_EX1 Overrides FuelPumpSwitch, but is an integer rather than a Boolean. Allows you to set GENERAL ENG FUEL PUMP SWITCH EX1 to "Auto". Defaults to -1, which means that FuelPumpSwitch is read instead. Integer No
FuelValveOpen True if the valve is open. Boolean No
FuelPressurePSF Set the fuel pressure level (in psf). The corresponding SimVar is GENERAL ENG FUEL PRESSURE. Float No
CarbHeat/DeiceSwitch True if the switch is on. Boolean No
EngineMasterSwitch True if the switch is on. Boolean No
GlowPlugTemperaturePct No
IgnitionSwitch Used to set the initial value of the SimVar TURB_ENG_IGNITION_SWITCH_EX1.

Integer:

  1. 0 = Not Igniting
    1 = Auto
    2 = On
No
StarterSwitch Sets whether or not the Starter is enabled. Boolean No
EGT_DegR No
ITT_DegR No
Afterburner Optional entry, recording the stage of the afterburner. Integer No
CorrectedFF

Sets the corrected Fuel flow at spawn, in lbs per hour.

Default value is 0 if the aircraft is spawned on the ground and 500 if spawned in the air.

Float No

 

 

[Propeller.N.i]

There is one of these entries for each propeller, and the first number (N) is the engine number that the propeller belongs to - starting at 1 - and the second (i) is the aircraft number (0 for the user aircraft). The available parameters are:

 

Parameter Description Type Required
prop_beta The "prop beta" is the pitch of the blades of the propeller. Float No
prop_max_rpm_percent No

 

 

[HYDRAULICS_SYSTEM_EX1.N]

This section is for setting the parameters required by the modular hydraulics system. These are only required if the [HYDRAULICS_SYSTEM_EX1] section has been set up for the aircraft. The available parameters are:

 

Parameter Description Type Required
Reservoir[Name]

This parameter takes a hashmap with a single key - FillRatio - which sets up the named reservoir with an initial quantity of fluid, expressed as a Percent Over 100.

  1. IMPORTANT! Take care setting the quantity value. A full reservoir will prevent actuators from emptying themselves when moving, thus preventing them from moving at all.

 

For example:

Reservoir[Name]= FillRatio:0.98

Hash Map

(see Data Types for more information)

No
Valve[Name]

This parameter takes a hashmap with a single key - Status - which sets the named valve initial state, expressed as a Percent Over 100, where 0 is fully closed and 1 is fully open.

For example:

Valve[Name]= Status:1.0
Junction[Name]

This parameter takes a hashmap with a single key - FillRatio - which sets the named junction with an initial quantity of fluid, expressed as a Percent Over 100.

For example:

Junction[Name]= FillRatio:0.98
Pump[Name]

This parameter takes a hashmap with up to three keys - FillRatio, Pressure, and Active - which sets up the named pump with initial values where:

  1. FillRatio: the amount of fluid in the pump, expressed as a Percent Over 100.
  2. Pressure: the pressure of the hydraulic fluid in the pump, in psi.
  3. State: the initial state of the pump, either on (1, True) or off (0, False).

 

For example:

Pump[Name]= FillRatio:0.510 #Pressure:14.500 #Active:False
PTU[Name]

This parameter takes a hashmap with up to six keys - Active, Reversed, PumpPressure, MotorPressure, PumpFillRatio, and MotorFillRatio - which sets up the named ptu with initial values where:

  1. Active: Whether the PTU is active (1, True) or not (0, False).
  2. Reversed: Whether the PTU is reversed (1, True) or not (0, False). This is only valid for reversible PTUs.
  3. PumpPressure: The internal pressure of the PTU pump, in psi.
  4. MotorPressure: The internal pressure of the PTU motor, in psi.
  5. PumpFillRatio: The amount of fluid in the PTU pump, expressed as a Percent Over 100.
  6. MotorFillRatio: The amount of fluid in the PTU motor, expressed as a Percent Over 100.

For example:

PTU[Name] = Active:False #Reversed:False #PumpFillRatio:0.247 #PumpPressure:14.500 #MotorFillRatio:0.000 #PumpPressure:14.500
Accumulator[Name]

This parameter takes a hashmap with up to two keys - FillRatio, and Pressure - which sets up the named accumulator with initial values where:

  1. FillRatio: The amount of fluid in the accumulator, expressed as a Percent Over 100.
  2. Pressure: The pressure of the hydraulic fluid in the accumulator, in psi.

 

For example:

Accumulator[Name]= FillRatio:0.98 #Pressure:2000
Actuator[Name]

This parameter takes a hashmap with a single key - FillRatio - which sets the named actuator with an initial quantity of fluid, expressed as a Percent Over 100.

For example:

Actuator[Name]= FillRatio:1.0
Line[Name]

This parameter takes a hashmap with up to 4 keys - InputFillRatio, OutputFillRatio, InputPressure, and OutputPressure - which sets up the named line with initial values where:

  1. InputFillRatio: The amount of fluid in the input side of the line, expressed as a Percent Over 100.
  2. OutputFillRatio: The amount of fluid in the output side of the line, expressed as a Percent Over 100.
  3. InputPressure: The internal fluid pressure of input side of the line, in psi.
  4. OutputPressure: The internal fluid pressure of output side of the line, in psi.

For example:

Line[Name] = InputFillRatio:1.000 #InputPressure:2932.298 #OutputFillRatio:1.000 #OutputPressure:2932.298

 

 

[FuelSystem.N]

This section is for setting the parameters required by the modular fuel system. These are only required if the [FUEL_SYSTEM] section has been set up for the aircraft. The available parameters are:

 

Parameter Description Type Required
Tank[Name]

This parameter takes a hashmap with a single key - LevelPct - which sets the remaining quantity of fuel in the named tank, as a Percent Over 100.

Default value is:

Tank[Name]: #LevelPct:0.4

or whatever setting the user has made in the main menu.

Float No
Valve[Name]

This parameter takes a hashmap with a single key - IsOpen - which sets whether the named valve is open (1, TRUE, On) or not (0, FALSE, Off).

Default value is:

Valve[Name]: #IsOpen:TRUE
Bool No
Junction[Name]

This parameter takes a hashmap with a single key - SelectedOption - which sets the index value corresponding to the option currently used by the named junction. For more information on junction options, please see here: Junction.N.

Default value is:

Junction[Name]: #SelectedOption:1
Integer No
Pump[Name]

This parameter takes a hashmap with a single key - Active - which is used to set what state the the named pump is in. Can be one of the following values:

  1. 0 = Off
  2. 1 = On
  3. 2 = Auto

Default value is:

Pump[Name]: #Active:0
Integer No
Trigger[Name]

This parameter takes a hashmap with a single key - State - which can be (1, TRUE, On) or (0, FALSE, Off), depending on the state you wish to set the trigger to.

Default value is:

Trigger[Name]: #State:TRUE
Integer No

 

 

[PNEUMATIC_SYSTEM_EX1.N]

This section is for setting the parameters required by the modular pneumatic system. These are only required if the [PNEUMATIC_SYSTEM_EX1] section has been set up for the aircraft, and even then they may be omitted if you wish to have the aircraft in its default state. It should be noted that multiple parameters require an index value. This is the index of the component that they are referring to.

 

The available parameters are:

 

Parameter Description Type Required
Engine_Bleed.N

Sets the bleed air status of the indexed Engine component to enabled (1, TRUE) or disabled (0, FALSE).

Default value is 0 (FALSE).

Boolean No
Pack_Active.N

Sets the status of the indexed Pack component to enabled (1, TRUE) or disabled (0, FALSE).

Default value is 1 (TRUE).

Boolean
Pack_Switch.N

Sets the status of the indexed Pack overhead switch to enabled (1, TRUE) or disabled (0, FALSE).

Default value is 1 (TRUE).

Boolean
Pack_PackFlow.N

Sets the percentage of airflow through the indexed Pack component, as a Percent Over 100.

Default value is 1.

Float
Pack_PackFlowMode.N

Sets the initial mode of the indexed Pack component, which can be one of the following:

  1. 0: Low
  2. 1: Normal
  3. 2: High

Default value is 1.

Integer
Pack_PackFlowAuto.N

Sets whether the indexed Pack component is set to "Auto" (1, TRUE) or not (0, FALSE).

Default value is 1 (TRUE).

Boolean
Area_TargetTemperature_C.N

Sets the target temperature (in °C) for the indexed Area component.

Default value is -1.

Float
Area_Temperature_C.N

Sets the current temperature (in °C) for the indexed Area component.

Default value is 0.

Float
Valve_OpeningStatus.N

Sets the percentage that the indexed Valve component is opened, as a Percent Over 100.

Default value is 1.

Float
Valve_TargetStatus.N

Sets the target percentage that the indexed Valve component should open to, as a Percent Over 100.

Default value is 1.

Float
Valve_Mode.N

Sets the initial mode of the indexed Valve component, which can be one of the following:

  1. 0: Auto
  2. 1: Manual
  3. 2: Open
  4. 3: Closed

Default value is 0.

Integer
PacksOnDefaultValues

Sets whether the packs are using the default temperature output values (1, TRUE) or not (0, FALSE).

Default value is 0 (FALSE).

Boolean
AircraftTargetAltitude_ft

The target cabin altitude for the aircraft, in ft.

Default value is 7000.

Float
AircraftTemperature_C

The initial temperature of the aircraft areas (average of all areas combined), in °C.

Default value is 0.

Float
AircraftPressure_kPa

The initial pressure of the aircraft areas (average of all areas combined), in kiloPascals.

Default value is 0.

Float

 

 

[Electrical.N]

This section sets up the electrical system for an aircraft. There should be one [Electrical.N] entry per aircraft. The available parameters are:

 

Parameter Description SimVar Type Required
Circuit[Name]

This parameter takes a hashmap with a two keys - Switch, and PowerSetting - which set the state and power of the named circuit, where:

  1. Switch: Whether the circuit is on (1, True) or off (0, False).
  2. PowerSetting: the ratio of the power setting, expressed as a Percent Over 100.

Default value is:

Circuit[name] = Switch:True #PowerSetting:1.0 

For more information on circuits, please see here: Circuit.

Circuits Hash Map No
Battery[Name]

This parameter takes a hashmap with a two keys - Switch, and Capacity - which set the state and power of the named battery, where:

  1. Switch: Whether the battery is on (1, True) or off (0, False).
  2. Capacity: The remaining capacity in Ah (Ampere hours) of the battery.

Default value is:

Battery[name] = Switch:True #Capacity:13.6 

For more information on batteries, please see here: Battery.

Batteries
Generator[Name]

This parameter takes a hashmap with one key - Switch - which sets whether the generator is on (1, True) or off (0, False).

Default value is:

Generator[name] = Switch:True

For more information on generators, please see here: Generator.

N/A

ExternalPower[Name]

This parameter takes a hashmap with one key - Switch - which sets whether the external power source is on (1, True) or off (0, False).

Default value is:

ExternalPower[name] = Switch:True

For more information on external power sources, please see here: ExternalPower.

External Power
Line[Name]

This parameter takes a hashmap with one key - Connected - which sets whether the line is connected (1, True) or not (0, False).

Default value is:

Line[name] = Connected:True

For more information on lines, please see here: Line.

Lines
Breaker[LineName]

This parameter takes a hashmap with a two keys - Pulled, and Timer - which control the state of the breaker. Note that breakers are governed by the line they are on, and so the name given is for the Line, not the breaker itself.

  1. Pulled: Whether the breaker has been pulled (1, True) or not (0, False).
  2. Timer: the current trip time of the breaker.

Default value is:

Breaker[line_name] = Pulled:False #Timer:0.0 
Breakers

 

 

[Liquid Dropping System.N]

There will be one entry of the liquid dropping system for each aircraft that requires it.

 

The available parameters are:

 

Parameter Description Type Required
Tank.N The volume of liquid that should be stored in the indexed Tank, in Gallons. Float Yes

 

 

[Burner_System.N]

There will be one entry of the burner system for each aircraft that requires it.

 

The available parameters are:

 

Parameter Description Type Required
Burner[ID]

The initial setup for a Burner. This parameter requires an ID (name or index) to specify which burner component is being targetted, and then you give a hashmap to set whether combustion is active or not, using the following format where "true" is active and "false" is inactive:

Burner[ID] = Combustion:<true_false>

 For example:

Burner[Burner_1] = Combustion:true
Burner[Burner_2] = Combustion:true

Hash Map

No
Valve[ID]

The initial setup for a Valve. This parameter requires an ID (name or index) to specify which valve component is being targetted, and then you give a hashmap to set the opening status, using the following format where a value of 0 is fully closed, and a value of 1 is fully open:

Valve[ID] = Combustion:<true_false>

 For example:

Valve[Burner2_Whisper] = Status:0.0
Valve[Burner2_Pilot] = Status:1.0
Float No

 

 

[Switches.N]

There will be one switches entry for each aircraft. The available parameters are:

 

Parameter Description SimVar Type Required
PitotHeat True if the switch is on. PITOT_HEAT_SWITCH Boolean Yes
PitotHeat_EX1 An extended version of the PitotHeat parameter which offers more control. PITOT_HEAT_SWITCH

Integer:

  1. 0 = OFF
  2. 1 = ON
  3. 2 = AUTO
No
WindshieldDeice Sets the state of the windshield de-icer WINDSHIELD_DEICE_SWITCH

Integer:

  1. 0 = OFF
  2. 1 = ON
  3. 2 = AUTO
Yes
BeaconLights True if the lights are on. LIGHT_BEACON Boolean Yes
LandingLights True if the lights are on. LIGHT_LANDING Boolean Yes
LogoLights True if the lights are on. LIGHT_LOGO Boolean Yes
NavLights True if the lights are on. LIGHT_NAV Boolean Yes
PanelLights True if the lights are on. LIGHT_PANEL Boolean Yes
RecognitionLights True if the lights are on. LIGHT_RECOGNITION Boolean Yes
StrobeLights True if the lights are on. LIGHT_STROBE Boolean Yes
TaxiLights True if the lights are on. LIGHT_TAXI Boolean Yes
WingLights True if the lights are on. LIGHT_WING Boolean Yes
CabinLights True if the lights are on. LIGHT_CABIN Boolean Yes
GlareshieldLights True if the lights are on. LIGHT_GLARESHIELD Boolean Yes
PedestalLights True if the lights are on. LIGHT_PEDESTRAL Boolean Yes
AmbientLights True if the lights are on. Not linked to a SimVar Boolean Yes
BeaconLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_BEACON Boolean No
LandingLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_LANDING Boolean No
LogoLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_LOGO Boolean No
NavLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_NAV Boolean No
PanelLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_PANEL Boolean No
RecognitionLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_RECOGNITION Boolean No
StrobeLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_STROBE Boolean No
TaxiLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_TAXI Boolean No
WingLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_WING Boolean No
CabinLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_CABIN Boolean No
GlareshieldLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_GLARESHIELD Boolean No
PedestalLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. LIGHT_PEDESTRAL Boolean No
AmbientLightsNight True if the light is on. This is an optional setting that, if set, will override the basic setting if the flight starts at night. Not linked to a SimVar Boolean No
Potentiometer.N Sets the state of the light potentiometer N. A value between 0 and 1 is required. LIGHT_POTENTIOMETER Float Yes

 

 

[Systems.N]

There will be one systems entry for each aircraft. The available parameters are:

 

Parameter Description Type Required
BatterySwitch True if the switch is on. Boolean Yes
StructuralDeiceSwitch True if the switch is on. Boolean Yes
StructuralDeiceSwitch_EX1 True if the switch is on. Boolean Yes
PropDeiceSwitch True if the switch is on. Boolean Yes
Autobrakes Set to 1 if the aircraft has automatic brakes, 0 otherwise. Integer Yes
StandbyVacuum True if the switch is on. Boolean Yes
PropSync True if the switch is on. Boolean Yes
AutoFeatherSwitch True if the switch is on. Boolean Yes
FlightDirector True if the switch is on. Boolean Yes
PanelLights True if the switch is on. Boolean Yes
ExternalPowerSwitch True if the switch is on. Boolean Yes
AuxPowerUnitSwitch True if the switch is on. Boolean Yes
SeatBeltsSwitch True if the switch is on. Boolean Yes
NoSmokingSwitch True if the switch is on. Boolean Yes
LaunchBarSwitch True if the launchbar has been deployed. These next five properties apply only to carrier launched aircraft. Boolean Yes
LaunchBarState One of: 0 if the launchbar is retracted, 1 if it is extended. Integer No
TailhookHandle True if the tailhook handle has been deployed. Boolean No
TailhookState One of: 0 if the tailhook is retracted, 1 if it is extended. Integer No
FoldingWingsHandle True if the folding wings handle has been deployed. Boolean No
FoldingWingsState Two values for the left and right wings, set to 0 if the wings are in a flying state, and 1 if they are folded (to save space on deck). Integer No
ClutchSwitch For helicopters, this specifies whether the clutch is engaged (1, TRUE) or not (0, FALSE). Boolean No
GovernorSwitch For helicopters, this specifies whether the governor is engaged (1, TRUE) or not (0, FALSE). Boolean No
GovernorTarget For helicopters, this specifies the target RPM, as a ratio of nominal RPM. For example, if the helicopter has a nominal RPM of 390, and its idle state is 52% of that, then setting this to 0.52 will make the governor target the proper 200 RPM idle state value. Percent Over 100 No

 

 

[Gauges.N]

There will be one gauges entry for each aircraft. The available parameters are:

 

Parameter Description Type Required
kollsmansetting Records the Kollsman setting (barometric pressure at sea level, in inches of mercury). Float Yes
AutoBaroSetting

If this parameter is set to true, the simulation will call the BAROMETRIC key event to set the barometer level at the start of the flight.

Default value is false (0).

Boolean No

 

 

[BleedAir.N]

Setup the bleed air system for the engines on an aircraft, one entry for each aircraft. The available parameters are:

 

Parameter Description Type Required
BleedAirSource Initial value of BleedAirSource enum. Default is 0. Integer No
EngineAirBleed.N True if EngineBleedAir is enabled for the indexed engine. Bool No
APUAirBleed True if APU AirBleed is enabled. Bool No

 

 

There will be one payload entry for each aircraft. The available parameters are:

 

Parameter Description Type Required
PayloadList If the aircraft is not carrying a payload, this will be -1. If it is then the payload weights in pounds in the list correspond to the payload locations defined in the aircraft configuration file. Comma separated list Yes

 

 

[CabinService.N]

This section can be added when the flight or mission requires the use of some Navigation Service. The section is indexed from 0, and if you need to define multiple navigation services for the aircraft or mission, then you can add more sections, incrementing the index N by 1 each time.

 

The available parameters are:

 

Parameter Description Type Required
Name The name of the navigation service to use on the mission. This is the name as defined in the services.XML file. String Yes
GraphPath The path to the navigation graph CFG file that is to be used. String No

 

 

[CabinServiceObject.N]

This section can be added to define a single behaviour object that will be used as part of a Navigation Service. The section is indexed from 0, and if you need to define multiple objects, then you can add more sections, incrementing the index N by 1 each time. These objects will usually be spawned by a mission file using the <SimMission.CreateCabinServiceObject> element.

 

The available parameters are:

 

Parameter Description Type Required
CabinServiceName The name of the navigation service that will be using this behaviour object. This is the name as defined in the services.XML file. String Yes
BehaviourName This is the name of the behaviour to assign to the object. The name must be the same as the one used in the <Behaviour> element of the associated navigation service XML. String Yes
Weight Defines how much the object weighs, in lbs. Float No
Quantity

Defines the number of behaviour objects that should be spawned.

Note that you can only use this parameter or NodeTag to define spawn quantity. You cannot use both parameters together.

Float No
(Yes if NodeTag is not defined)
NodeTag

A node tag. Using this parameter means that number of behaviour objects that should be spawned will be based on the number of nodes with the given tag on the navigation graph for the associated service. You may modify this value using the Density parameter.

Note that you can only use this parameter or Quantity to define spawn quantity. You cannot use both parameters together.

String No
(Yes if Quantity is not defined)
Density

This is a percentage value that is only required when using the NodeTag parameter. The percentage given here will be a modifier applied to the number of behaviour objects that are spawned. For example, if you have 75% here and there are 60 tagged nodes, then 45 objects will be spawned.

Default value is 100.

Float No
RemoveOnFlightReset

Defines whether the behaviour object should be removed on flight reset (1, TRUE) or not (0, FALSE).

Default value is 1 (TRUE).

Boolean No
GeneratedCharacters

Here you give one of the available pre-generated characters to be used as the spawned object.

If this is used then you cannot use the SimObject.N nor PropSetContainerGUID parameters.

String No
(Yes if neither SimObject.N nor PropSetContainerGUID is defined)
SimObject.N

Here you give the name of a SimObject to use as the spawned object. Objects should be indexed from 0 and increment by 1, and if you supply more than one SimObject then spawned objects will be picked randomly from list.

If this is used then you cannot use the GeneratedCharacters nor PropSetContainerGUID parameters.

String No
(Yes if neither GeneratedCharacters nor PropSetContainerGUID is defined)
PropSetContainerGUID

Here you give the GUID of a PropSetContainer to be used as the spawned object. If you supply this parameter, it must be accompanied with the PropSetFile parameter as well.

If this is used then you cannot use the GeneratedCharacters nor PropSetContainerGUID parameters.

String No
(Yes if neither GeneratedCharacters nor SimObject.N is defined)
PropSetFile The file that defines the PropSet to be used as the spawned object. This parameter is only used when a PropSetContainerGUID is supplied. String No

 

 

[InteractivePoints.N]

IMPORTANT! This section is currently not supported by Microsoft Flight Simulator 2024 and will be ignored. Future updates to the simulation will fix this.

There will be one interactive point section per-aircraft. The available parameters are:

 

Parameter Description Type Required
InteractivePoint.N Initialises the interactive point at the start of the flight. Value is between 0 and 1, where 0 is fully closed and 1 is fully open. There should be one parameter for each interactive point, indexed from 0. Float Yes

 

 

[WEAR_AND_TEAR_SYSTEM.N]

There will be one failure system entry for each aircraft. The available parameters are:

 

Parameter Description Type Required
inhibitAll If set to 1 (True) then this will inhibit all the failures on this aircraft, essentially disabling the failure system and meaning you do not need to use the inhibitCategory parameter. Boolean No
inhibitCategory

This parameter permits you to inhibit (disable) entire categories of failures. To do this, you need to give a comma separated list of each of the failure categories that you wish to inhibit, for example:

inhibitCategory=Engine,Controls,LandingGear

The available failure categories are as follows:

  1. Autopilot
    Controls
    Deicing
    Doors
    Electrical
    EmergencyOxygen
    Engine
    FuelSystem
    GroundContact
    HydraulicsSystem
    Instruments
    LandingGear
    Lights
    Miscellaneous
    Navigation
    OilSystem
    PneumaticSystem
    Sensors

 

The parameter has no default value, and if you do not wish to inhibit any categories, simply omit the parameter from the file. Note too that this requires that the inhibitAll parameter is set to 0 (False).

List of strings

(see Data Types for more information)

No

 

 

[Controls.N]

There will be one controls entry for each aircraft. The available parameters are:

 

Parameter Description Type Required
SpoilersHandle Percentage of maximum spoilers handle position. Float Yes
FlapsHandle Percentage of maximum flap handle position. Float Yes
LeftFlap Percentage of maximum flap position of left flaps. If the maximum flap position is 40 degrees, then the example of 2.50 indicates the flaps are at 1 degree. Float Yes
RightFlap Percentage of maximum flap position of right flaps. Float Yes
GearsHandle Percentage of maximum gear handle position. 0 is fully retracted. Float Yes
Gear1 Percentage of maximum extended gear position - for the center wheel gear. Float Yes
Gear2 Percentage of maximum extended gear position - for the left wheel gear. Float Yes
Gear3 Percentage of maximum extended gear position - for the right wheel gear. Float Yes
YokeY Position of the yoke in the forward/backward direction. 0 is fully forward, 100 fully backward, 50 is dead center. Float Yes
YokeX Position of the yoke in the left/right direction. 0 is fully left, 100 is fully right, 50 is dead center. Float Yes
Rudder Position of the rudder expressed as a percentage of its full range of movement. Float Yes
LeftBrake Percentage of maximum application of left brake. Float Yes
RightBrake Percentage of maximum application of right brake. Float Yes
ParkingBrake Percentage of maximum application of parking brake. Float Yes
ElevatorTrim Percentage of maximum elevator trim, linked to the SimVar ELEVATOR TRIM PCT. Float Yes
RudderTrimPct Percentage of maximum application of rudder trim, linked to the SimVar RUDDER_TRIM_PCT. Float Yes
AileronTrimPct Percentage of maximum application of aileron trim, linked to the SimVar AILERON TRIM PCT. Float Yes
AileronTrimDisabled Used to set the initial value of the SimVar AILERON TRIM DISABLED, which disables the aileron trim. Boolean Yes
ElevatorTrimDisabled Used to set the initial value of the SimVar ELEVATOR TRIM DISABLED, which disables the elevator trim. Boolean Yes
RudderTrimDisabled Used to set the initial value of the SimVar RUDDER_TRIM_DISABLED, which disables the rudder trim. Boolean Yes
GLimiterSetting

This controls the setting of the G-limiter on an aircraft. This value can then be accessed through the SimVar G_LIMITER_SETTING. Possible values are:

  1. 0 = Off
  2. 1 = On
  3. 2 = Override
Integer. Yes
SpoilersArmed Sets whether the spoilers are armed (1, TRUE) or not (0, FALSE). Boolean Yes
AntiSkidActive Controls whether the anti-skid breaking system is active or not. This setting can be accessed using the ANTISKID BRAKES ACTIVE SimVar. Boolean Yes
TailwheelLock Controls whether the tail wheel is locked or not. This setting can be accessed using the TAILWHEEL_LOCK_ON SimVar. Boolean Yes
NosewheelLock Controls whether the nose wheel is locked or not. This setting can be accessed using the NOSEWHEEL_LOCK_ON SimVar. Boolean Yes
Collective Sets the collective position for helicopters, as a percentage between 0 1nd 100. Float No
LateralTrim Sets the lateral trim for helicopters, where 0 is -100% trim, 50 is neutral (0%) trim, and 100 is 100% trim. Float No
LongitudinalTrim Sets the longitudinal trim for helicopters, where 0 is -100% trim, 50 is neutral (0%) trim, and 100 is 100% trim. Float No

 

 

[SimVars.N]

There will be one simvars entry for each sim object saved off. The available parameters are:

 

Parameter Description Type Required
Latitude Latitude of aircraft. Float Yes
Longitude Longitude of aircraft. Float Yes
Altitude Altitude of aircraft, in feet. Float Yes
Pitch Pitch of the aircraft, in degrees. Float Yes
Bank Bank of the aircraft, in degrees. Float Yes
Heading Heading of the aircraft, in degrees. Float Yes
PVelBodyAxis Pitch rotational velocity, in radians per second. Float Yes
BVelBodyAxis Bank rotational velocity, in radians per second. Float Yes
HVelBodyAxis Heading rotational velocity, in radians per second. Float Yes
XVelBodyAxis Velocity in the X (sideways) direction, in feet per second. Float Yes
YVelBodyAxis Velocity in the Y (vertical) direction, in feet per second. Float Yes
ZVelBodyAxis Velocity in the Z (forward) direction, in feet per second. Float Yes
SimOnGround True if the aircraft is on the ground, which includes the deck of a carrier, or False otherwise. Boolen Yes
OnPlatformHeight If an aircraft is initially placed on another object, such as a carrier, the height of the object, in feet, should be recorded here. If this is not the case enter -9999999999. Float Yes

 

 

[SimVarForSpawningInTheAir]

This section can be added when the flight or mission is designed to start with the aircraft in the air, rather than on the ground. Note that adding this section will cause some of the other *.flt file parameters to be overridden. This happens because when you have this section then start the simulation, the engine has to try and balance the plane using the requested configuration so it can start flying immediately. As such this will mean that some system and engine parameters will be overwritten.

NOTE: This section is not applicable to helicopters, and will have no effect on how they are spawned.

 

The available parameters are:

 

Parameter Description Type Required
Altitude The altitude at which the plane should spawn, measured in ft. Float No
Slope The slope of the aircraft when the flight/mission starts, in degrees. Float No
IAS The IAS at which the plane should be flying when the flight/mission starts. Value is in ft per seconds. Float No
FlapsDegree The level of flaps, in degrees. Float No
ThrottlePct This sets the position of the throttle, expressed as a Percent Over 100, where 0 is no throttle and 1 is full throttle. Float No
PropellerPct This sets the position of the propeller lever, expressed as a Percent Over 100. Float No

 

 

[LocalVars.N]

This section can be used to define and initialise un-scoped local variables to be used in missions. Localvars will be defined here using the same format as the rest of the options that exist in the configuration files, eg: varname = value. Unlike the local variables created in the [LocalVars] section of the systems.cfg file these variables are not persisted between runs. To access these variables in the code you need to use the "L:" var identifier using Reverse Polish Notation, and if you are using the JavaScript API then this is done using the same function as for SimVars: GetSimVarValue(name, unit, dataSource = ""). These variables are shared between aircraft if multiple instances of the aircraft are spawned. In general this is not what you want and you should use the scoped L:1 variable type instead, defined in the [LocalVars_EX1.N] section.

 

 

[LocalVars_EX1.N]

This section can be used to define and initialise scoped local variables to be used in missions. Localvars will be defined here using the same format as the rest of the options that exist in the configuration files, eg: varname = value. Unlike the local variables created in the [LocalVars] section of the systems.cfg file these variables are not persisted between runs. To access these variables in the code you need to use the "L:1" var identifier using Reverse Polish Notation, and if you are using the JavaScript API then this is done using the same function as for SimVars: GetSimVarValue(name, unit, dataSource = ""). These variables are scoped to each instance of the aircraft that use them, so each instance will have a unique version of the local variables you define in this section (unlike the un-scoped L var type defined in the [LocalVars.N] section).

 

 

[SimScheduler]

This section is for setting some very specific simulation parameters that will affect the way the simulation runs. The available parameters are:

 

Parameter Description Type Required
SimSpeed

The simulation rate. This parameter can only accept the following values:

  1. 0.25
  2. 0.5
  3. 1
  4. 2
  5. 4
  6. 8
  7. 16
  8. 32
  9. 64
  10. 128

Note that these values are multipliers and that 1 is the normal speed. Supplying any value other than those given above will default the simulation rate to 1.

Float Yes
SimTime Sets the time the simulation has supposed to have been running since the timer was started during initialization, in seconds. This timer is not incremented when the simulation is paused, and is largely used for calculating relative elapsed simulation time. Float Yes