# FLT File Properties<no value>
The `<mission_name>.flt` file goes in the main mission folder beside the other files and is formatted like [CFG Files](../../../devmode/editors/project-editor/file-formats/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.

{{< callout context="caution" title="IMPORTANT!" icon="outline/alert-triangle" >}}

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.

{{< /callout >}}

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:

-   [FLT Files](../flt-files-general-information/)

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

-   [Complete FLT Example](../../mission-xml-files/flight-weather-and-event-examples/#complete-flt-example)


### [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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Title" />}}`Title` | The title of the flight/mission being defined. This will be used as the mission title in the simulation. | String | Yes |
| {{< anchor id="Description" />}}`Description` | A short description of the flight/mission. This will be shown to the user in the simulation. | String | Yes |
| {{< anchor id="AppVersion" />}}`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 |
| {{< anchor id="FlightVersion" />}}`FlightVersion` | The version number of this flight. Starts at 1 and increments. | Integer | Yes |
| {{< anchor id="MissionType" />}}`MissionType` | The type of mission that this file is for. | String, one of the following:<span></span>{{< params/smallfont >}} - LandingChallenge<span></span> - FreeFlight<span></span> - BushTrip<span></span> - Tutorial<span></span> - Discovery{{< /params/smallfont >}} | Yes |
| {{< anchor id="MissionSubType" />}}`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:<span></span>{{< params/smallfont >}} - Landing Challenge:<span></span> - Famous<span></span> - Epic<span></span> - StrongWind<span></span> - Discovery:<span></span> - Core<span></span> - WU<span></span> - Training:<span></span> - A320<span></span> - BasicHandling<span></span> - LocalFlight<span></span> - VFRNavigation{{< /params/smallfont >}} | No |
| {{< anchor id="MissionLocation" />}}`MissionLocation` | The location of the flight. | String | No |
| {{< anchor id="OriginalFlight" />}}`OriginalFlight` |  |  |  |
| {{< anchor id="FlightType" />}}`FlightType` | The type of flight that the FLT is being used for.  | String:<span></span>{{< params/smallfont >}} - NORMAL<span></span> - LESSON<span></span> - TEMPORARY<span></span> - AUXILIARY<span></span> - SAVE{{< /params/smallfont >}} | No |
| {{< anchor id="StartingCameraCategory" />}}`StartingCameraCategory` | This sets the way that the in-sim camera will be set up when the flight starts.<span></span>Default value is "Cockpit". | String:<span></span>{{< params/smallfont >}} - "Cockpit"<span></span> - "Aircraft"<span></span> - "Scenery"<span></span> - "Custom"<span></span> - "FixedOnPlane"<span></span> - "Airport"<span></span> - "AirportTraffic"{{< /params/smallfont >}} | No |
| {{< anchor id="Difficulty" />}}`Difficulty` | This sets the "difficulty" of the mission the FLT file is being used for. In reality, currently it is only used for odering missions in the UI. For more information, please see here: [Mission Order](../flt-additional-information/#mission-order)<span></span>Default value is 0. | Integer | No |

{{< /table-wrapper >}}


### [Briefing]

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

{{< table-wrapper "200px" "" "300px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="BriefingText" />}}`BriefingText` | This option is used to define the text that should be used on the mission briefing screen. | String | Yes |
| {{< anchor id="BriefingImageN" />}}`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 |
| {{< anchor id="BriefingImageOverlayN" />}}`BriefingImageOverlayN` | Add text on the briefing screen. | String | No |
| {{< anchor id="BriefingInfoN" />}}`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:<span></span>{{< params/smallfont >}} - `FLIGHT_INFO_RUNWAY_DEPARTURE_NAME`<span></span>Name of the departure<span></span> - `FLIGHT_INFO_RUNWAY_DEPARTURE_ELEVATION`<span></span>Departure runway elevation, in meters<span></span> - `FLIGHT_INFO_RUNWAY_DEPARTURE_LENGTH`<span></span>Departure runway length, in meters<span></span> - `FLIGHT_INFO_RUNWAY_DEPARTURE_SLOPE`<span></span>Departure runway slope, in degrees<span></span> - `FLIGHT_INFO_RUNWAY_ARRIVAL_NAME`<span></span>Name of the arrival<span></span> - `FLIGHT_INFO_RUNWAY_ARRIVAL_ELEVATION`<span></span>Arrival runway elevation, in meters<span></span> - `FLIGHT_INFO_RUNWAY_ARRIVAL_LENGTH`<span></span>Arrival runway length, in meters<span></span> - `FLIGHT_INFO_RUNWAY_ARRIVAL_SLOPE`<span></span>Arrival runway slope (value in degrees)<span></span> - `FLIGHT_INFO_NUMBER_OF_LEGS`<span></span>Number of legs. Used only in Bushtrip activity.<span></span> - `FLIGHT_INFO_TOTAL_FLIGHT_DURATION`<span></span>Total duration of the flight, in seconds<span></span> - `FLIGHT_INFO_TOTAL_FLIGHT_LENGTH`<span></span>Total length of the flight, in meters<span></span> - `FLIGHT_INFO_WIND_ORIGIN`<span></span>Direction of the wind, in degrees<span></span> - `FLIGHT_INFO_WIND_SPEED`<span></span>Speed of the wind, in m/s{{< /params/smallfont >}} | No |
| {{< anchor id="StartUpLocationInfoN" />}}`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:<span></span>{{< params/smallfont >}} - `FLIGHT_INFO_RUNWAY_DEPARTURE_NAME`<span></span>Name of the departure<span></span> - `FLIGHT_INFO_RUNWAY_DEPARTURE_ELEVATION`<span></span>Departure runway elevation, in meters<span></span> - `FLIGHT_INFO_RUNWAY_DEPARTURE_LENGTH`<span></span>Departure runway length, in meters<span></span> - `FLIGHT_INFO_RUNWAY_DEPARTURE_SLOPE`<span></span>Departure runway slope, in degrees<span></span> - `FLIGHT_INFO_RUNWAY_ARRIVAL_NAME`<span></span>Name of the arrival<span></span> - `FLIGHT_INFO_RUNWAY_ARRIVAL_ELEVATION`<span></span>Arrival runway elevation, in meters<span></span> - `FLIGHT_INFO_RUNWAY_ARRIVAL_LENGTH`<span></span>Arrival runway length, in meters<span></span> - `FLIGHT_INFO_RUNWAY_ARRIVAL_SLOPE`<span></span>Arrival runway slope (value in degrees)<span></span> - `FLIGHT_INFO_NUMBER_OF_LEGS`<span></span>Number of legs. Used only in Bushtrip activity.<span></span> - `FLIGHT_INFO_TOTAL_FLIGHT_DURATION`<span></span>Total duration of the flight, in seconds<span></span> - `FLIGHT_INFO_TOTAL_FLIGHT_LENGTH`<span></span>Total length of the flight, in meters<span></span> - `FLIGHT_INFO_WIND_ORIGIN`<span></span>Direction of the wind, in degrees<span></span> - `FLIGHT_INFO_WIND_SPEED`<span></span>Speed of the wind, in m/s<span></span> - `FLIGHT_INFO_LOCATION_NAME`<span></span>Name of the location at mission start<span></span> - `FLIGHT_INFO_LOCATION_VISIBILITY`<span></span>Visibility in the location at mission start<span></span> - `FLIGHT_INFO_LOCATION_WIND`<span></span>Time of day at mission start<span></span> - `FLIGHT_INFO_LOCATION_ALTITUDE`<span></span>Altitude at mission start{{< /params/smallfont >}} | No |
| {{< anchor id="StartUpAircraftInfoN" />}}`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:<span></span>{{< params/smallfont >}} - `FLIGHT_INFO_AIRCRAFT_CRUISE_SPEED`<span></span>Cruise speed of the aircraft<span></span> - `FLIGHT_INFO_AIRCRAFT_STALL_SPEED`<span></span>Stall speed of the aircraft<span></span> - `FLIGHT_INFO_AIRCRAFT_MAX_ALTITUDE`<span></span>Max altitude reachable by the aircraft<span></span> - `FLIGHT_INFO_AIRCRAFT_IAS`<span></span>Indicated Air Speed of the aircraft at mission start<span></span> - `FLIGHT_INFO_AIRCRAFT_HEADING`<span></span>Heading of the aircraft at mission start<span></span> - `FLIGHT_INFO_AIRCRAFT_AUTONOMY`<span></span>Autonomy of the aircraft (depends on the amount of Fuel set in the [Fuel.N] section)<span></span> - `FLIGHT_INFO_AIRCRAFT_RANGE`<span></span>Range of the aircraft{{< /params/smallfont >}} | No |

{{< /table-wrapper >}}


### [Options]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Save" />}}`Save` |  | Boolean | Yes |
| {{< anchor id="SaveOriginalFlightPlan" />}}`SaveOriginalFlightPlan` |  | Boolean | Yes |
| {{< anchor id="Sound" />}}`Sound` | This option can be set to `True` or `False` to enable/disable sound. | Boolean | No |
| {{< anchor id="Moonlight" />}}`Moonlight` | This option can be set to `True` or `False` to enable/disable the rendering of moonlight in the simulation. | Boolean | No |
| {{< anchor id="TextDisplayPage" />}}`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 |
| {{< anchor id="SlewDisplayPage" />}}`SlewDisplayPage` | The information page to display whilst in slew mode. | Integer | No |
| {{< anchor id="AxisIndicator" />}}`AxisIndicator` | The axis indicator to use. | String:<span></span>{{< params/smallfont >}} - Off<span></span> - 4 dots<span></span> - Small V<span></span> - Large V{{< /params/smallfont >}} | No |
| {{< anchor id="Titles" />}}`Titles` | This option can be set to `True` or `False` to enable/disable window titles. | Boolean | No |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "200px" "" "300px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Preset" />}}`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:<span></span>{{< params/smallfont >}}**Freeflight**:<span></span> - `ASSISTANCE_PRESET_NEWCOMER`<span></span> - `ASSISTANCE_PRESET_AVERAGE_PLAYER`<span></span> - `ASSISTANCE_PRESET_TRUE_TO_LIFE`<span></span>**Bush Trip**:<span></span> - `ASSISTANCE_PRESET_BUSH_TRIP`<span></span>**Landing Challenge**:<span></span> - `ASSISTANCE_PRESET_LANDING_CHALLENGE`<span></span>**Training**:<span></span> - `ASSISTANCE_PRESET_TUTORIALS`<span></span> - `ASSISTANCE_PRESET_TUTORIALS_NAV`<span></span> - `ASSISTANCE_PRESET_TUTORIALS_A320_LANDING`<span></span>**SU10**:<span></span> - `ASSISTANCE_PRESET_LANDING_CHALLENGE_CARRIER` {{< /params/smallfont >}}| No |
| {{< anchor id="EventTriggersFileCount" />}}`EventTriggersFileCount` | The number of event trigger files that are used by the flight/mission. | Integer | No |
| {{< anchor id="EventTriggersFile.N" />}}`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 |

{{< /table-wrapper >}}

For more information on **Event Triggers** see the following page:

-   [Event Trigger Definitions](../../mission-xml-files/event-trigger-xml-properties/)


### [AutoPilot.*N*]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

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

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Active-EFIS" />}}`Active` | This should be set to `True` if the EFIS is active or `False` otherwise. | Boolean | Yes |
| {{< anchor id="NavAid" />}}`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:<span></span>{{< params/smallfont >}} - VOR 1<span></span> - VOR 2{{< /params/smallfont >}} | Yes |
| {{< anchor id="Type" />}}`Type` | The type of visuals to use. | String:<span></span>{{< params/smallfont >}} - Rectangles<span></span> - Telephone Poles<span></span> - Yellow Brick Road<span></span> - Hoops{{< /params/smallfont >}} | Yes |
| {{< anchor id="Density-EFIS" />}}`Density` | The visual density. | String:<span></span>{{< params/smallfont >}} - Thin<span></span> - Medium<span></span> - Thick{{< /params/smallfont >}} | Yes |
| {{< anchor id="Range" />}}`Range` | The distance between the visuals. | String:<span></span>{{< params/smallfont >}}- Short<span></span> - Medium<span></span> - Long{{< /params/smallfont >}} | Yes |
| {{< anchor id="Altitude-EFIS" />}}`Altitude` | Altitude (above {{< glossterm >}}MSL{{< /glossterm >}}) below which the visual guides should be drawn. | Float | Yes |
| {{< anchor id="Flags" />}}`Flags` | Flags for the EFIS. 0 indicates no flags. | Integer | Yes |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="NbFiles" />}}`NbFiles` | The number of additional "object" files that will be listed in this section. | Integer | Yes |
| {{< anchor id="File.N" />}}`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 |

{{< /table-wrapper >}}


### [FreeFlight]

Set the freeflight state. The available parameters are:

{{< table-wrapper "200px" "" "250px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="FirstFlightState" />}}`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:<span></span>{{< params/smallfont >}} - `PREFLIGHT_GATE`<span></span> - `PREFLIGHT_PUSHBACK`<span></span> - `PREFLIGHT_TAXI`<span></span> - `PREFLIGHT_HOLDSHORT`<span></span> - `FLIGHT_RUNWAY`<span></span> - `FLIGHT_INITIAL_CLIMB`<span></span> - `FLIGHT_CLIMB`<span></span> - `FLIGHT_CRUISE`<span></span> - `FLIGHT_DESCENT`<span></span> - `LANDING_APPROACH`<span></span> - `LANDING_FINAL`<span></span> - `LANDING_TAXI`<span></span> - `LANDING_GATE`{{< /params/smallfont >}} | No |

{{< /table-wrapper >}}


### [NIGHT_VISION]

In this section you can control certain aspects of the night-vision system for the aircraft. The available parameters are:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Displayed" />}}`Displayed` | Sets whether the flight should be with night vision enabled (1, True) or not (0, false). Note that if the aircraft does not have night vision `Available`, then this parameter will have no effect. | Bool | No |

{{< /table-wrapper >}}


### [Weather]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="UseWeatherFile" />}}`UseWeatherFile` | Set to `true` to use the [WPR](../../mission-xml-files/weather-xml-wpr-file-properties/) file within the mission folder. Set to `false` otherwise. | Boolean | No |
| {{< anchor id="UseLiveWeather" />}}`UseLiveWeather` | Set to `true` to enable live weather, or `false` to disable it. | Boolean | No |
| {{< anchor id="WeatherPresetFile" />}}`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:<span></span>{{< params/smallfont >}} - `BrokenClouds.WPR`<span></span> - `ClearSky.WPR`<span></span> - `FewClouds.WPR`<span></span> - `HighLevelClouds.WPR`<span></span> - `Overcast.WPR`<span></span> - `Rain.WPR`<span></span> - `ScatteredClouds.WPR`<span></span> - `Snow.WPR`<span></span> - `Storm.WPR`{{< /params/smallfont >}}<span></span>The string to access these files should be formatted like this:<span></span>`.\WeatherPresets\[PRESET_NAME]`<span></span>For example:<span></span>`WeatherPresetFile=.\WeatherPresets\ClearSky.WPR` | String | No |
| {{< anchor id="WeatherCanBeLive" />}}`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 |
| {{< anchor id="CloudmapPosOverride" />}}`CloudmapPosOverride` | Set to `true` to override the cloudmap position using the `CloudmapInitialPosX`/`Y` parameters, or `false` otherwise. | Boolean | No |
| {{< anchor id="CloudmapInitialPosX" />}}`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 |
| {{< anchor id="CloudmapInitialPosY" />}}`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. | Float | No |
| {{< anchor id="FixedClouds" />}}`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 |

{{< /table-wrapper >}}


### [BingMap]

This section controls certain online interactions between the simulation and [BingMaps](https://www.bing.com/maps/). The available parameters are:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="MinWeight" />}}`MinWeight` | This parameter is used to filter the display of Bing {{< glossterm >}}poi{{< /glossterm >}}. The input must be a value between 0 and 1500, where 0 means that all Bing {{< glossterm >}}poi{{< /glossterm >}} are displayed in the world, while 1500 means that none of them will be displayed. | Integer | No |

{{< /table-wrapper >}}


### [Departure]

Set the departure airport. The available parameters are:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="ICAO-Departure" />}}`ICAO` | The {{< glossterm >}}icao_code{{< /glossterm >}} of the departure airport. | String | Yes |
| {{< anchor id="RunwayNumber-Departure" />}}`RunwayNumber` | The runway number. | String | Yes |
| {{< anchor id="RunwayDesignator-Departure" />}}`RunwayDesignator` | The runway designator. | String | Yes |
| {{< anchor id="GateNumber-Departure" />}}`GateNumber` | The gate number (only used if the mission starts on a Parking spot). | Integer | No |
| {{< anchor id="GateName-Departure" />}}`GateName` | The gate name (only used if the mission starts on a Parking spot). | String | No |
| {{< anchor id="GateSuffix-Departure" />}}`GateSuffix` | The gate suffix (only used if the mission starts on a Parking spot). | String | No |

{{< /table-wrapper >}}


### [Arrival]

Set the arrival airport. The available parameters are:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="ICAO-Arrival" />}}`ICAO` | The {{< glossterm >}}ICAO code{{< /glossterm >}} of the arrival airport. | String | Yes |
| {{< anchor id="RunwayNumber-Arrival" />}}`RunwayNumber` | The runway number. | String | Yes |
| {{< anchor id="RunwayDesignator-Arrival" />}}`RunwayDesignator` | The runway designator. | String | Yes |
| {{< anchor id="GateNumber-Arrival" />}}`GateNumber` | The gate number (only used if the mission ends on a Parking spot). | Integer | No |
| {{< anchor id="GateName-Arrival" />}}`GateName` | The gate name (only used if the mission ends on a Parking spot). | String, only one of the following:<span></span>{{< params/smallfont >}} - PARKING (for a ramp)<span></span> - GATE_*N* (where N is the gate letter){{< /params/smallfont >}} | No |
| {{< anchor id="GateSuffix-Arrival" />}}`GateSuffix` | The gate suffix (only used if the mission ends on a Parking spot). | String | No |

{{< /table-wrapper >}}


### [Loading]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="ImageNameN" />}}`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 |
| {{< anchor id="TipsN" />}}`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:<span></span><code>Tips0=TT:LOADING.TIPS.MISSIONNAME_000<span></span>Tips1=TT:LOADING.TIPS.MISSIONNAME_001<span></span>Tips2=TT:LOADING.TIPS.MISSIONNAME_002</code> | String | No |

{{< /table-wrapper >}}


### [TrafficManager]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="disable" />}}`disable` | When set to 1 (TRUE) the traffic manager is disabled and there will be no offline traffic.<span></span>Default value is 0 (FALSE). | Bool | No |

{{< /table-wrapper >}}


### [LivingWorld]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="AirportLife" />}}`AirportLife` | Set to 1 (`True`) to remove airport life (parked aircrafts, ambient traffic, services, idle workers). Default value is 0 (`False`). | Boolean | No |
| {{< anchor id="RoadTraffic" />}}`RoadTraffic` | Set to 1 (`True`) to remove road traffic. Default value is 0 (`False`). | Boolean | No |
| {{< anchor id="BoatTraffic" />}}`BoatTraffic` | Set to 1 (`True`) to remove boat traffic. Default value is 0 (`False`). | Boolean | No |

{{< /table-wrapper >}}


### [User Tip Window]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Undocked-User Tip Window" />}}`Undocked` | Set to `True` if the window has been undocked, in which case the window will be located at [`UndocCoords`](#UndocCoords). | Bool | No |
| {{< anchor id="ScreenUniCoords-User Tip Window" />}}`ScreenUniCoords` | The current screen co-ordinates of the panel window. See the note on [Universal Screen Co-ordinates](../flt-additional-information/#universal-screen-co-ordinates). | 4 Floats | Yes |
| {{< anchor id="UndocCoords-User Tip Window" />}}`UndocCoords` | The co-ordinates of the window if it has been undocked. See the note on [Universal Screen Co-ordinates](../flt-additional-information/#universal-screen-co-ordinates). | 4 Floats | Yes |

{{< /table-wrapper >}}


### [Atc_Menu]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="ScreenUniCoords-Atc_Menu" />}}`ScreenUniCoords` | The current screen co-ordinates of the ATC window. See the note on [Universal Screen Co-ordinates](../flt-additional-information/#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 |
| {{< anchor id="UndocCoords-Atc_Menu" />}}`UndocCoords` | The co-ordinates of the window if it has been undocked. See the note on [Universal Screen Co-ordinates](../flt-additional-information/#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 |
| {{< anchor id="Undocked-Atc_Menu" />}}`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 |

{{< /table-wrapper >}}


### [ATC_AgentManager]

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

{{< table-wrapper "300px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="NumberofAgents" />}}`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 |

{{< /table-wrapper >}}


### [ATC_AircraftManager]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="NumberofAircraft" />}}`NumberofAircraft` | The number of aircraft. Usually 1. | Integer | Yes |

{{< /table-wrapper >}}


### [ATC_MessageSystem]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="FrequencyNodes" />}}`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]`](#atc_frequencynoden) entry and usually an [`[ATC_MessageNode.N.i]`](#atc_messagenoden) entry. | Integer | Yes |

{{< /table-wrapper >}}


### [ATC_Agent.*N*]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="AgentType" />}}`AgentType` | The type of ATC agent. | String:<span></span>{{< params/smallfont >}} - ATIS<span></span> - ClearanceDelivery<span></span> - Ground<span></span> - Tower<span></span> - Center<span></span> - Approach<span></span> - Departure<span></span> - FSS<span></span> - CTAF<span></span> - ASOS{{< /params/smallfont >}} | Yes |
| {{< anchor id="CallSign" />}}`CallSign` | The callsign of the ATC agent. | String | Yes |
| {{< anchor id="Frequency-ATC_Agent.n" />}}`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 |
| {{< anchor id="NumberOfAircraft" />}}`NumberOfAircraft` | The number of aircraft the agent is tracking. Usually 1. | Integer | Yes |
| {{< anchor id="SecLastMessage" />}}`SecLastMessage` | Simtime of the last message. | Float | Yes |

{{< /table-wrapper >}}


### [ATC_Aircraft.*N*]

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

{{< table-wrapper "200px" "" "300px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="ActiveFlightPlan" />}}`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 |
| {{< anchor id="RequestedFlightPlan" />}}`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 |
| {{< anchor id="AcState" />}}`AcState` | The current aircraft status. | Enum:<span></span>{{< params/smallfont >}} - `ACSTATE_NONE`<span></span>// IFR Clearance<span></span> - `ACSTATE_PRETAXI_CLEARANCE`<span></span> - `ACSTATE_IFR_CLEARANCE_READBACK`<span></span> - `ACSTATE_IFR_CLEARANCE_WAIT_FOR_READBACK_GOOD`<span></span>// Departure ground operations<span></span> - `ACSTATE_CTAF_TAKEOFF`<span></span> - `ACSTATE_DYNAMIC_RUNWAY_CTAF_TAKEOFF`<span></span> - `ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_VFR_ATIS`<span></span> - `ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_VFR_NOATIS`<span></span> - `ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_IFR`<span></span> - `ACSTATE_TAXI_CLEARANCE_READBACK`<span></span> - `ACSTATE_TAXIING_OUT`<span></span> - `ACSTATE_ACKNOWLEDGE_HOLD_POSITION`<span></span> - `ACSTATE_ACKNOWLEDGE_CONTINUE_TAXI`<span></span> - `ACSTATE_TOWER_HOLDSHORT_ACKNOWLEDGE`<span></span> - `ACSTATE_TAKEOFF_POSITION_AND_HOLD_ACKNOWLEDGE`<span></span> - `ACSTATE_TAKEOFF_CLEARANCE_READBACK`<span></span> - `ACSTATE_DYNAMIC_RUNWAY_TAKEOFF`<span></span>// Class D departure operations<span></span> - `ACSTATE_TOWER_DEPARTING`<span></span>// VFR enroute operations<span></span> - `ACSTATE_VFR_ENROUTE_CONTACT`<span></span> - `ACSTATE_VFR_ENROUTE`<span></span>// Flight Following and Airspace Transitions<span></span> - `ACSTATE_ACKNOWLEDGE_SQUAWK`<span></span> - `ACSTATE_ACKNOWLEDGE_RADAR_CONTACT_FF`<span></span> - `ACSTATE_ACKNOWLEDGE_RADAR_CONTACT_TRANSITION`<span></span> - `ACSTATE_ACKNOWLEDGE_LEAVING_AIRSPACE_NOFF`<span></span> - `ACSTATE_ACKNOWLEDGE_TRANSITION_CLEARANCE_CLASS_BC`<span></span> - `ACSTATE_ACKNOWLEDGE_TRANSITION_CLEARANCE_CLASS_D`<span></span>// Popup IFR States<span></span> - `ACSTATE_ACKNOWLEDGE_INFLIGHT_IFR_CLEARANCE`<span></span> - `ACSTATE_INFLIGHT_IFR_CLEARANCE_WAIT_FOR_READBACK_GOOD`<span></span>// Handoffs<span></span> - `ACSTATE_AGENT_CONTACT`<span></span> - `ACSTATE_AGENT_HANDOFF`<span></span>// IFR Enroute state<span></span> - `ACSTATE_ARRIVAL`<span></span> - `ACSTATE_DYNAMIC_RUNWAY_ARRIVAL`<span></span> - `ACSTATE_DYNAMIC_APPROACH_ARRIVAL`<span></span> - `ACSTATE_DYNAMIC_APPROACH_TRANSITION_ARRIVAL`<span></span> - `ACSTATE_ARRIVAL_CANCEL_IFR`<span></span>// States that loop back to ARRIVAL after aircraft responds<span></span> - `ACSTATE_ARRIVAL_VECTOR`<span></span> - `ACSTATE_ARRIVAL_EXPECT`<span></span> - `ACSTATE_CRUISING_ALTITUDE_INCREASE`<span></span> - `ACSTATE_CRUISING_ALTITUDE_DECREASE`<span></span> - `ACSTATE_DYNAMIC_RUNWAY_ARRIVAL_EXPECT`<span></span> - `ACSTATE_DYNAMIC_APPROACH_ARRIVAL_EXPECT`<span></span> - `ACSTATE_DYNAMIC_APPROACH_TRANSITION_ARRIVAL_EXPECT`<span></span> - `ACSTATE_ARRIVAL_CLEARED`<span></span> - `ACSTATE_ARRIVAL_CLEARED_FULL_PROCEDURE`<span></span> - `ACSTATE_DYNAMIC_AIRPORT_LANDING`<span></span>// Class D arrival operations<span></span> - `ACSTATE_AGENT_HANDOFF_TOWER`<span></span> - `ACSTATE_TOWER_CONTACT`<span></span> - `ACSTATE_TOWER_CONTACT_IFR`<span></span> - `ACSTATE_TOWER_TRANSITION`<span></span> - `ACSTATE_TOWER_PATTERN_ENTRY`<span></span> - `ACSTATE_DYNAMIC_RUNWAY_PATTERN_ENTRY`<span></span> - `ACSTATE_TOWER_LANDING`<span></span> - `ACSTATE_DYNAMIC_RUNWAY_LANDING`<span></span> - `ACSTATE_TOWER_HANDOFF_GROUND`<span></span> - `ACSTATE_TOWER_CLEARED_TO_LAND`<span></span> - `ACSTATE_GO_AROUND_ACKNOWLEDGE`<span></span> - `ACSTATE_AGENT_HANDOFF_TOWER_MISSED_APPROACH`<span></span> - `ACSTATE_AGENT_CONTACT_MISSED_APPROACH`<span></span>// CTAF Operations<span></span> - `ACSTATE_CTAF_LANDING_TYPE`<span></span> - `ACSTATE_DYNAMIC_RUNWAY_CTAF_LANDING_TYPE`<span></span> - `ACSTATE_CTAF_LANDING`<span></span> - `ACSTATE_DYNAMIC_RUNWAY_CTAF_LANDING`<span></span>// Arrival ground operations<span></span> - `ACSTATE_REQUEST_TAXI_CLEARANCE_IN`<span></span> - `ACSTATE_TAXI_CLEARANCE_IN_READBACK`<span></span> - `ACSTATE_TAXIING_IN`<span></span> - `ACSTATE_ACKNOWLEDGE_HOLD_POSITION_IN`<span></span> - `ACSTATE_ACKNOWLEDGE_CONTINUE_TAXI_IN`{{< /params/smallfont >}} | Yes |
| {{< anchor id="TaxiRouteAirport" />}}`TaxiRouteAirport` | The ICAO for the airport taxi route. | String | No |
| {{< anchor id="TaxiRoute.N" />}}`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:<span></span><code>TaxiRoute.0=27,11,2,0,2<span></span>TaxiRoute.1=26,10,2,0,0<span></span>TaxiRoute.2=25,9,2,0,0</code> | String | No |
| {{< anchor id="NumTaxiRoute" />}}`NumTaxiRoute` | The number of TaxiRoute entries. | Integer | No |
| {{< anchor id="NumberofWaypoints" />}}`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](#ActiveFlightPlan), if there is such a flight plan. | Integer | Yes |
| {{< anchor id="ClearanceFlags" />}}`ClearanceFlags` | Hex number containing Boolean flags:<span></span>{{< params/smallfont >}}- **0x0001**: User is IFR<span></span>- **0x0002**: User has been assigned a new altitude<span></span>- **0x0004**: User has been assigned a new heading<span></span>- **0x0008**: User has been assigned a left turn<span></span>- **0x0010**: User has arrived at their cleared altitude<span></span>- **0x0020**: User has declared missed and needs an altitude assignment<span></span>- **0x0040**: User is requesting Popup IFR clearance<span></span>- **0x0080**: This is the first assigned approach for the user<span></span>- **0x0100**: User has declared missed and is flying published missed approach<span></span>- **0x0200**: User is descending to their arrival airport<span></span>The following example shows the flags for an aircraft that has just declared a missed approach:<span></span>`ClearanceFlags=2F`{{< /params/smallfont >}} | Hex | Yes |
| {{< anchor id="CtCur" />}}`CtCur` | Current clearance. | String:<span></span>{{< params/smallfont >}} - `CLEARANCE_NONE`<span></span> - `CLEARANCE_OWNNAV`<span></span> - `CLEARANCE_VECTORS_INTERCEPT_LEFT`<span></span> - `CLEARANCE_VECTORS_INTERCEPT_RIGHT`<span></span> - `CLEARANCE_VECTORS_ROUTE`{{< /params/smallfont >}} | Yes |
| {{< anchor id="WaypointNext" />}}`WaypointNext` | The waypoint the aircraft is currently heading for. Note that waypoints are indexed from zero. | Integer | Yes |
| {{< anchor id="AltCleared" />}}`AltCleared` | The altitude the aircraft has been instructed to fly at, in {{< glossterm >}}ft{{< /glossterm >}}. | Float | Yes |
| {{< anchor id="HdgAssigned" />}}`HdgAssigned` | The assigned heading, in radians, or -1 if no heading has been assigned. | Float | Yes |
| {{< anchor id="SquawkAssigned" />}}`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:<span></span>`SquawkAssigned=543650387` | Integer | Yes |
| {{< anchor id="LandingSequence" />}}`LandingSequence` | The landing sequence identifier. | String:<span></span>{{< params/smallfont >}} - `LANDING_NONE`<span></span> - `LANDING_IFR_EXPECTING_APPROACH`<span></span> - `LANDING_IFR_CLEARED_FOR_APPROACH`<span></span> - `LANDING_IFR_CLEARED_TO_LAND`<span></span> - `LANDING_VFR_FULL_STOP_REQUEST`<span></span> - `LANDING_VFR_FULL_STOP_FLYING_PATTERN`<span></span> - `LANDING_VFR_FULL_STOP_CLEARED_TO_LAND`<span></span> - `LANDING_VFR_TOUCH_AND_GO_REQUEST`<span></span> - `LANDING_VFR_TOUCH_AND_GO_FLYING_PATTERN`<span></span> - `LANDING_VFR_TOUCH_AND_GO_CLEARED_TO_LAND`{{< /params/smallfont >}} | Yes |
| {{< anchor id="DepartureRequest" />}}`DepartureRequest` | The departure request type. | String:<span></span>{{< params/smallfont >}} - `DEPARTURE_VFR_REQUEST_REMAIN_IN_PATTERN`<span></span> - `DEPARTURE_VFR_REQUEST_DEPART_STRAIGHT_OUT`<span></span> - `DEPARTURE_VFR_REQUEST_DEPART_NORTH`<span></span> - `DEPARTURE_VFR_REQUEST_DEPART_SOUTH`<span></span> - `DEPARTURE_VFR_REQUEST_DEPART_EAST`<span></span> - `DEPARTURE_VFR_REQUEST_DEPART_WEST`<span></span> - `DEPARTURE_VFR_REQUEST_NONE`{{< /params/smallfont >}} | Yes |
| {{< anchor id="ParkingRequest" />}}`ParkingRequest` | The parking request. | String:<span></span>{{< params/smallfont >}} - `PARKING_NAME_NONE`<span></span> - `PARKING_NAME_PARKING`<span></span> - `PARKING_NAME_N_PARKING`<span></span> - `PARKING_NAME_NE_PARKING`<span></span> - `PARKING_NAME_E_PARKING`<span></span> - `PARKING_NAME_SE_PARKING`<span></span> - `PARKING_NAME_S_PARKING`<span></span> - `PARKING_NAME_SW_PARKING`<span></span> - `PARKING_NAME_W_PARKING`<span></span> - `PARKING_NAME_NW_PARKING`<span></span> - `PARKING_NAME_GATE`{{< /params/smallfont >}} | Yes |
| {{< anchor id="ParkingTypeequest" />}}`ParkingTypeequest` | The parking request type. | String:<span></span>{{< params/smallfont >}} - `PARKING_TYPE_NONE`<span></span> - `PARKING_TYPE_RAMP_GA`<span></span> - `FAC_TAXI_PARKING_TYPE_RAMP_GA_SMALL`<span></span> - `PARKING_TYPE_RAMP_GA_MEDIUM`<span></span> - `PARKING_TYPE_RAMP_GA_LARGE`<span></span> - `PARKING_TYPE_RAMP_CARGO`<span></span> - `PARKING_TYPE_RAMP_MIL_CARGO`<span></span> - `PARKING_TYPE_RAMP_MIL_COMBAT`<span></span> - `PARKING_TYPE_GATE_SMALL`<span></span> - `PARKING_TYPE_GATE_MEDIUM`<span></span> - `PARKING_TYPE_GATE_HEAVY`<span></span> - `PARKING_TYPE_DOCK_GA`<span></span> - `PARKING_TYPE_FUEL`<span></span> - `PARKING_TYPE_VEHICLE`{{< /params/smallfont >}} | Yes |
| {{< anchor id="PatternLeg" />}}`PatternLeg` |  | String:<span></span>{{< params/smallfont >}} - `PATTERN_LEG_NONE`<span></span> - `PATTERN_LEG_DOWNWIND`<span></span> - `PATTERN_LEG_CROSSWIND`<span></span> - `PATTERN_LEG_SHORT_FINAL`<span></span> - `PATTERN_LEG_FINAL`<span></span> - `PATTERN_LEG_BASE`<span></span> - `PATTERN_LEG_UPWIND`{{< /params/smallfont >}} | Yes |
| {{< anchor id="ApproachIndex" />}}`ApproachIndex` | The index number of the approach for the destination airport, or -1 if no approach has cleared. | Integer | Yes |
| {{< anchor id="ApproachTransitionIndex" />}}`ApproachTransitionIndex` | The index number of the approach transition for the destination airport, of -1 if no approach transition has been cleared. | Integer | Yes |
| {{< anchor id="ApproachRequestIndex" />}}`ApproachRequestIndex` | The index number of the approach that has been requested by the pilot, but has not yet been cleared. | Integer | Yes |
| {{< anchor id="ApproachTransitionRequestIndex" />}}`ApproachTransitionRequestIndex` | The index number of the approach transition that has been requested by the pilot, but has not yet been cleared. | Integer | Yes |
| {{< anchor id="RunwayIndex" />}}`RunwayIndex` | The index number of the destination airport runway, or -1 if no runway has been assigned. | Integer | Yes |
| {{< anchor id="RunwayRequestIndex" />}}`RunwayRequestIndex` | The index number of the destination airport runway requested by the pilot, but has not yet been assigned. | Integer | Yes |
| {{< anchor id="ParkingIndex" />}}`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 |
| {{< anchor id="FlightFollowing" />}}`FlightFollowing` |  | String:<span></span>{{< params/smallfont >}} - `FLIGHT_FOLLOWING_NO`<span></span> - `FLIGHT_FOLLOWING_REQUEST`<span></span> - `FLIGHT_FOLLOWING_YES`{{< /params/smallfont >}} | Yes |
| {{< anchor id="AirspaceTransition" />}}`AirspaceTransition` |  | String:<span></span> - `AIRSPACE_TRANSITION_NONE`<span></span> - `AIRSPACE_TRANSITION_REQUEST`<span></span> - `AIRSPACE_TRANSITION_YES` | Yes |
| {{< anchor id="BvAirspaceTransition" />}}`BvAirspaceTransition` |  | String:<span></span>{{< params/smallfont >}} - `BV_TYPE_NONE`<span></span> - `BV_TYPE_CENTER`<span></span> - `BV_TYPE_CLASS_A`<span></span> - `BV_TYPE_CLASS_B`<span></span> - `BV_TYPE_CLASS_C`<span></span> - `BV_TYPE_CLASS_D`<span></span> - `BV_TYPE_CLASS_E`<span></span> - `BV_TYPE_CLASS_F`<span></span> - `BV_TYPE_CLASS_G`<span></span> - `BV_TYPE_TOWER`<span></span> - `BV_TYPE_CLEARANCE`<span></span> - `BV_TYPE_GROUND`<span></span> - `BV_TYPE_DEPARTURE`<span></span> - `BV_TYPE_APPROACH`<span></span> - `BV_TYPE_MOA`<span></span> - `BV_TYPE_RESTRICTED`<span></span> - `BV_TYPE_PROHIBITED`<span></span> - `BV_TYPE_WARNING`<span></span> - `BV_TYPE_ALERT`<span></span> - `BV_TYPE_DANGER`<span></span> - `BV_TYPE_NATIONAL_PARK`<span></span> - `BV_TYPE_MODE_C`<span></span> - `BV_TYPE_MAX`{{< /params/smallfont >}} | Yes |
| {{< anchor id="BvAirspaceTransitionReq" />}}`BvAirspaceTransitionReq` |  | String:<span></span>{{< params/smallfont >}} - `BV_TYPE_NONE`<span></span> - `BV_TYPE_CENTER`<span></span> - `BV_TYPE_CLASS_A`<span></span> - `BV_TYPE_CLASS_B`<span></span> - `BV_TYPE_CLASS_C`<span></span> - `BV_TYPE_CLASS_D`<span></span> - `BV_TYPE_CLASS_E`<span></span> - `BV_TYPE_CLASS_F`<span></span> - `BV_TYPE_CLASS_G`<span></span> - `BV_TYPE_TOWER`<span></span> - `BV_TYPE_CLEARANCE`<span></span> - `BV_TYPE_GROUND`<span></span> - `BV_TYPE_DEPARTURE`<span></span> - `BV_TYPE_APPROACH`<span></span> - `BV_TYPE_MOA`<span></span> - `BV_TYPE_RESTRICTED`<span></span> - `BV_TYPE_PROHIBITED`<span></span> - `BV_TYPE_WARNING`<span></span> - `BV_TYPE_ALERT`<span></span> - `BV_TYPE_DANGER`<span></span> - `BV_TYPE_NATIONAL_PARK`<span></span> - `BV_TYPE_MODE_C`<span></span> - `BV_TYPE_MAX`{{< /params/smallfont >}} | Yes |
| {{< anchor id="TakeOffSequence" />}}`TakeOffSequence` |  | String:{{< params/smallfont >}}<span></span> - `TAKEOFF_SEQUENCE_NONE`<span></span> - `TAKEOFF_SEQUENCE_HOLDSHORT`<span></span> - `TAKEOFF_SEQUENCE_TAXI_AND_HOLD`<span></span> - `TAKEOFF_SEQUENCE_CLEARED`<span></span> - `TAKEOFF_SEQUENCE_OUT_OF_AREA`{{< /params/smallfont >}} | Yes |
| {{< anchor id="LandingsSquenceNumber" />}}`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 |
| {{< anchor id="TaxiRouteCurrent" />}}`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 |
| {{< anchor id="CruisingAltitude" />}}`CruisingAltitude` | The current cruising altitude. | Float | Yes |
| {{< anchor id="RequestedCruisingAltitude" />}}`RequestedCruisingAltitude` | The requested cruising altitude, if an altitude change has been requested, or -1 if there is no such request. | Float | Yes |
| {{< anchor id="ExpectedAltitude" />}}`ExpectedAltitude` | The altitude the user aircraft pilot is told to expect, in feet, or -1 if this does not apply. | Float | Yes |
| {{< anchor id="AircraftSignature-ATC_Aircraft.N" />}}`AircraftSignature` | The aircraft signature. This will be 1,0 for the user aircraft. | 2 value list | Yes |
| {{< anchor id="AgentTracking" />}}`AgentTracking` | The signature of the ATC agent (refer to [ATC Agent Signatures](../flt-additional-information/#atc-agent-signatures)). | 4 float values | Yes |
| {{< anchor id="Waypoint.N" />}}`Waypoint.N` | The list of waypoints making up the IFR or VFR flight plan. Refer to the notes on [Waypoint Format](../flt-additional-information/#waypoint-format). | Comma separated list | Yes |
| {{< anchor id="AgentHandoff" />}}`AgentHandoff` | The signature of the ATC agent the aircraft will be handed off to (refer to [ATC Agent Signatures](../flt-additional-information/#atc-agent-signatures)). | 4 float values | Yes |
| {{< anchor id="ActiveVfrAirport" />}}`ActiveVfrAirport` | The active VFR airport. This will be present even if the aircraft is flying under IFR rules. | String | Yes |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "200px" "" "200px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="AircraftSignature-ATC_AircraftData.N" />}}`AircraftSignature` | The aircraft signature. 1,0 for the user aircraft. | Float | Yes |
| {{< anchor id="Contacted" />}}`Contacted` | This will be `True` if the ATC agent has made contact with the aircraft or `False` otherwise. | Boolean | Yes |
| {{< anchor id="SecLastDing" />}}`SecLastDing` | Time of the last ding (correcting message), or 0 if there was none. | Integer | Yes |
| {{< anchor id="NumDings" />}}`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 |
| {{< anchor id="LastDing" />}}`LastDing` | The [ATC Message ID](../flt-additional-information/#atc-message-id) of the last ding, or 0 if there was no last ding. | Integer | Yes |
| {{< anchor id="LastMessage" />}}`LastMessage` | The last transmitted [ATC Message ID](../flt-additional-information/#atc-message-id). | Integer | Yes |
| {{< anchor id="HandedOff" />}}`HandedOff` | This will be `True` if the aircraft has been handed off to another ATC agent or `False` otherwise. | Boolean | Yes |
| {{< anchor id="TimeStampOnRunway" />}}`TimeStampOnRunway` | The number of seconds an aircraft has been on the runway, after landing, or 0 if the aircraft has not just landed. |  |  |
| {{< anchor id="BVAirspaceTransitionPrev" />}}`BVAirspaceTransitionPrev` | The previous transition value. | String:<span></span>{{< params/smallfont >}} - `BV_TYPE_NONE`<span></span> - `BV_TYPE_CENTER`<span></span> - `BV_TYPE_CLASS_A`<span></span> - `BV_TYPE_CLASS_B`<span></span> - `BV_TYPE_CLASS_C`<span></span> - `BV_TYPE_CLASS_D`<span></span> - `BV_TYPE_CLASS_E`<span></span> - `BV_TYPE_CLASS_F`<span></span> - `BV_TYPE_CLASS_G`<span></span> - `BV_TYPE_TOWER`<span></span> - `BV_TYPE_CLEARANCE`<span></span> - `BV_TYPE_GROUND`<span></span> - `BV_TYPE_DEPARTURE`<span></span> - `BV_TYPE_APPROACH`<span></span> - `BV_TYPE_MOA`<span></span> - `BV_TYPE_RESTRICTED`<span></span> - `BV_TYPE_PROHIBITED`<span></span> - `BV_TYPE_WARNING`<span></span> - `BV_TYPE_ALERT`<span></span> - `BV_TYPE_DANGER`<span></span> - `BV_TYPE_NATIONAL_PARK`<span></span> - `BV_TYPE_MODE_C`<span></span> - `BV_TYPE_MAX`{{< /params/smallfont >}} | Yes |
| {{< anchor id="HasReachedClassD" />}}`HasReachedClassD` | This value will be `True` if the aircraft has reached Class D airspace, or `False` otherwise. | Boolean | Yes |

{{< /table-wrapper >}}


### [ATC_ActiveFlightPlan.*N*]

This entry will exist if the user aircraft is flying with a current flight plan, either {{< glossterm >}}ifr{{< /glossterm >}} or {{< glossterm >}}vfr{{< /glossterm >}}. 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:

{{< table-wrapper "200px" "" "200px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="title" />}}`title` | The title of the flight plan, taken from the Title entry in the [PLN](../../mission-xml-files/flight-plan-xml-pln-file-properties/) file. | String | Yes |
| {{< anchor id="description" />}}`description` | The Description entry from the [PLN](../../mission-xml-files/flight-plan-xml-pln-file-properties/) file. | String | Yes |
| {{< anchor id="type" />}}`type` | The flight plan type. | String:<span></span> - IFR<span></span>VFR | Yes |
| {{< anchor id="routetype" />}}`routetype` | This entry will be 0 if `type` is VFR. For IFR it will be one of the integer values shown. | Integer:<span></span>{{< params/smallfont >}} - 0 = Direct (GPS)<span></span>1 = VOR to VOR<span></span>2 = Low altitude airways<span></span>3 = High altitude airways{{< /params/smallfont >}} | Yes |
| {{< anchor id="cruising_altitude" />}}`cruising_altitude` | The assigned cruising altitude in the current flight plan. | Float | Yes |
| {{< anchor id="departure_id" />}}`departure_id` | The ICAO of the departure airport, and its lat/lon/alt, in the DepartureLLA element of the [PLN](../../mission-xml-files/flight-plan-xml-pln-file-properties/) file. For example: `departure_id=KSEA, N47° 25.89', W122° 18.48', +000433.00` | Comma separated list | Yes |
| {{< anchor id="departure_position" />}}`departure_position` | The runway number and optional designator of the departure. For example:<span></span>`departure_position=34R`<span></span>Note that this must be identical to that which is set in the `[Departure]` section. | String | Yes |
| {{< anchor id="destination_id" />}}`destination_id` | The ICAO of the destination airport, and its lat/lon/alt, in the DestinationLLA element of the [PLN](../../mission-xml-files/flight-plan-xml-pln-file-properties/) file. For example: `destination_id=KLAX, N33° 56.16', W118° 25.13', +000126.00` | Comma separated list | Yes |
| {{< anchor id="departure_name" />}}`departure_name` | The name of the departure airport. | String | Yes |
| {{< anchor id="destination_name" />}}`destination_name` | The name of the destination airport. | String | Yes |
| {{< anchor id="waypoint.N" />}}`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](../flt-additional-information/#waypoint-format). Note that you should have as many waypoints defined as already listed in the `[ATC_Aircraft.N]` section. | Comma separated list | Yes |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Frequency-ATC_FrequencyNode.N" />}}`Frequency` | Com frequency (120.1 in the example). | Float | yes |
| {{< anchor id="CurrMessage" />}}`CurrMessage` | `True` if the current message is saved, in which case an [`[ATC_MessageNode.N.i]`](#atc_messagenodeni) entry should exist for the message. | Boolean | Yes |
| {{< anchor id="TotalMessageCount" />}}`TotalMessageCount` | The number of messages. Usually 1. | Integer | Yes |

{{< /table-wrapper >}}


### [ATC_MessageNode.*N*.*i*]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Seconds-ATC_MessageNode.N.i" />}}`Seconds` | The time it will take to read the message, in seconds. | Float | Yes |
| {{< anchor id="MessageID" />}}`MessageID` | The [ATC Message ID](../flt-additional-information/#atc-message-id) of the message. | Integer | Yes |
| {{< anchor id="TimeStamp" />}}`TimeStamp` | Simtime of the message. | Float | Yes |
| {{< anchor id="CommUnitFrom" />}}`CommUnitFrom` | The agent the message is from (refer to [ATC Agent Signatures](../flt-additional-information/#atc-agent-signatures)). | Comma separated list | Yes |
| {{< anchor id="CommUnitTo" />}}`CommUnitTo` | The signature of the aircraft the message is to. Usually 1,0 for the user aircraft. | 2 value list | Yes |

{{< /table-wrapper >}}


### [GPS_Engine]

A `[GPS_Engine]` entry will be present if the user aircraft is flying under ATC rules - {{< glossterm >}}ifr{{< /glossterm >}} or {{< glossterm >}}vfr{{< /glossterm >}} - and has an active flightplan. The available parameters are:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Filename" />}}`Filename` | The name the [flight plan file](../../mission-xml-files/flight-plan-xml-pln-file-properties/), without the file extension. | String | Yes |
| {{< anchor id="position" />}}`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 |
| {{< anchor id="Time" />}}`Time` | Current Zulu time. | Integer | Yes |
| {{< anchor id="TimeWP" />}}`TimeWP` | {{< glossterm >}}zulu_time{{< /glossterm >}} (in seconds) when the aircraft passed the last waypoint. | Integer | Yes |
| {{< anchor id="ArriveTime" />}}`ArriveTime` | Estimated time en route, in seconds. | Integer | Yes |
| {{< anchor id="CountWP" />}}`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 |
| {{< anchor id="NextWP" />}}`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 |
| {{< anchor id="PlaneStarted" />}}`PlaneStarted` | `True` when the aircraft takes off, `False` otherwise. | Boolean | Yes |
| {{< anchor id="WpInfoN" />}}`WpInfoN` | Waypoint information in the order:<span></span>{{< params/smallfont >}}- estimated knots,<span></span>- actual knots,<span></span>- height in meters,<span></span>- actual time enroute,<span></span>- estimated time of arrival,<span></span>- fuel remaining when arrived,<span></span>- estimate of fuel required for the leg,<span></span>- actual fuel used for the leg.{{< /params/smallfont >}}<span></span>Some of the values may be unknown and recorded as zero. For example:<span></span>`WpInfo0=473, 0, 131, 0, 8459, 2909.8, 0.0, 0.0`<span></span>`WpInfo1=473, 0, 161, 0, 47577, 2909.8, 0.2, 0.0`<span></span>`WpInfo2=473, 0, 5486, 0, 48856, 0.0, 137.0, 0.0` | Comma separated list | Yes |
| {{< anchor id="CountFP" />}}`CountFP` | The number of flight path points recorded. | Integer | Yes |
| {{< anchor id="FpN" />}}`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:<span></span>`128 ((latitude as a decimal value) (90.0 / 10001750))`<span></span>The longitude is coded as:<span></span>`(((longitude as a decimal value) ((65536.0/360.0) 65536.0 )))`<span></span>For example:<span></span>`FP0=293ede80,a83d7546,293eee26,a83d2f9e,293efe7a,a83ce5ff,293f14d8,a83c8046` | Comma separated list | Yes |

{{< /table-wrapper >}}


### [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 fly, and as such this section and its parameters is only required in the `hangar.flt` and `apron.flt`. For more information, please see the following page:

-   [Preflight](../../careers/general-career-information/preflight/)

{{< callout context="caution" title="IMPORTANT!" icon="outline/alert-triangle" >}}

It should be noted that the the <code>[Covers]</code> section is <em>optional</em> and does not have to be included, however if it is omitted, it will <strong>need to be omitted in all FLT files for the aircraft</strong>. The same is true if you have setup preflight checks and included the <code>[Covers]</code> section and some - or all - of the available parameters: **these parameters will need to exist in all FLT files for the aircraft**, and be set to <code>TRUE</code> / <code>FALSE</code> as appropriate.

{{< /callout >}}

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="chock" />}}`chock` | Sets whether the chocks should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).<span></span>Default value is 0. | Boolean | No |
| {{< anchor id="engine" />}}`engine` | Sets whether the engine covers should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).<span></span>Default value is 0. | Boolean | No |
| {{< anchor id="pitot" />}}`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).<span></span>Default value is 0. | Boolean | No |
| {{< anchor id="static_port" />}}`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).<span></span>Default value is 0. | Boolean | No |
| {{< anchor id="rotor" />}}`rotor` | Sets whether the rotor covers should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).<span></span>Default value is 0. | Boolean | No |
| {{< anchor id="landing_gear" />}}`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).<span></span>Default value is 0. | Boolean | No |
| {{< anchor id="propeller" />}}`propeller` | Sets whether the propeller covers should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).<span></span>Default value is 0. | Boolean | No |
| {{< anchor id="windshield" />}}`windshield` | Sets whether the windshield cover should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE).<span></span>Default value is 0. | Boolean | No |
| {{< anchor id="generic.N" />}}`generic.N` | Sets whether a "generic" cover should be in place at the start of the flight (1, On, TRUE) or not (0, Off, FALSE). The index value `N` refers to the value defined using the `<GENERIC_COVER_INDEX>` element in the the `ASOBO_ET_COMMON_Cover_Interaction_And_Visibility_Template`, and should be between 1 and 16, inclusive.<span></span>Default value is 0. | Boolean | No |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Runway" />}}`Runway` | Defines how much runway dirt will be present on the aircraft. Value is expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}. | Float | No |
| {{< anchor id="Regular" />}}`Regular` | Defines how much general dirt from use and wear and tear will be present on the aircraft. Value is expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}. | Float | No |
| {{< anchor id="FadedPaint" />}}`FadedPaint` | Defines how faded the aircraft paint will appear. Value is expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}. | Float | No |
| {{< anchor id="Mud" />}}`Mud` | Defines how much mud will be present on the aircraft. Value is expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}. | Float | No |
| {{< anchor id="Dust" />}}`Dust` | Defines how much dust will be present on the aircraft. Value is expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}. | Float | No |

{{< /table-wrapper >}}


### [DateTimeSeason]

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

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Season" />}}`Season` | The current season. | String:<span></span>{{< params/smallfont >}} - Winter<span></span> - Spring<span></span> - Summer<span></span> - Fall{{< /params/smallfont >}} | Yes |
| {{< anchor id="Year" />}}`Year` | The current year. | Integer | Yes |
| {{< anchor id="Day" />}}`Day` | The current day (0 to 365). | Integer | Yes |
| {{< anchor id="Hours" />}}`Hours` | The current hour (0 to 23), local time. | Integer | Yes |
| {{< anchor id="Minutes" />}}`Minutes` | The current minute (0 to 57). | Integer | Yes |
| {{< anchor id="Seconds-DateTimeSeason" />}}`Seconds` | The current second (0 to 57). | Float | Yes |
| {{< anchor id="UseZuluTime" />}}`UseZuluTime` | Set to `True` to use {{< glossterm >}}zulu_time{{< /glossterm >}} or `False` otherwise. | Boolean | Yes |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Guid" />}}`Guid` | The {{< glossterm >}}GUID{{< /glossterm >}} of the camera. One of these entries will match the GUID for the `CurrentCamera` in each of the [](#WindowN) sections. See here for how to generate these ID string: [GUIDs](../../../introduction/using-the-sdk/#guids). | String | Yes |
| {{< anchor id="Zoom" />}}`Zoom` | Zoom factor of the camera (refer to the [Camera Configuration](../../cfg-files/cameras.cfg/) documentation for more details). | Float | Yes |
| {{< anchor id="Translation" />}}`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 |
| {{< anchor id="Rotation" />}}`Rotation` | Rotation of the camera for pitch, bank and heading. This is a 3 value comma separated list, for example: `Rotation=-1,0,0`<span></span>This entry is not required for external views. | 3 Floats | No |
| {{< anchor id="ChaseDirection" />}}`ChaseDirection` | The chase camera direction. This entry is not required for external views. | Float | No |
| {{< anchor id="ChaseDistance" />}}`ChaseDistance` | The chase camera distance. This entry is not required for external views. | Float | No |
| {{< anchor id="ChaseAltitude" />}}`ChaseAltitude` | The chase camera altitude. This entry is not required for external views. | Float | No |

{{< /table-wrapper >}}


### [SimplifiedSim.*N*]

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

{{< table-wrapper "300px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Mode" />}}`Mode` | The implied simulation mode to use. | String:<span></span>{{< params/smallfont >}} - None<span></span>AI_Air<span></span>AI_Taxi<span></span>AI_LandingTakeoff<span></span>Data_Air<span></span>Data_ground{{< /params/smallfont >}} | Yes |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Sim" />}}`Sim` | The [title](../../cfg-files/aircraft.cfg/#title) of the aircraft, or object, in the [aircraft.cfg](../../cfg-files/aircraft.cfg/). | String | Yes |
| {{< anchor id="Livery" />}}`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 |
| {{< anchor id="Pilot" />}}`Pilot` | This is the *title* of the SimObject - as set in the [sim.cfg](../../modular-simobjects/simobjects/living-things/) 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](../../cfg-files/aircraft-sim/aircraft.cfg-and-sim.cfg-additional-information/#pilot_list).<span></span>**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](../../cfg-files/flight_model.cfg/) has not defined a pilot `station_load.N`** **then NO pilot will be spawned**, regardless of the `[PILOT]` configuration. | String | No |
| {{< anchor id="Copilot" />}}`Copilot` | This is the *title* of the SimObject - as set in the [sim.cfg](../../modular-simobjects/simobjects/living-things/) 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](../../cfg-files/aircraft-sim/aircraft.cfg-and-sim.cfg-additional-information/#pilot_list).<span></span>**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](../../cfg-files/flight_model.cfg/) has not defined a pilot `station_load.N`** **then NO copilot will be spawned**, regardless of the `[PILOT]` configuration. | String | No |
| {{< anchor id="Instructor" />}}`Instructor` | This is the *title* of the SimObject - as set in the [sim.cfg](../../modular-simobjects/simobjects/living-things/) 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](../../cfg-files/aircraft-sim/aircraft.cfg-and-sim.cfg-additional-information/#pilot_list). 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 |
| {{< anchor id="TailNumber" />}}`TailNumber` |  |  |  |
| {{< anchor id="AirlineCallSign" />}}`AirlineCallSign` |  |  |  |
| {{< anchor id="FlightNumber" />}}`FlightNumber` |  |  |  |
| {{< anchor id="AppendHeavy" />}}`AppendHeavy` |  |  |  |
| {{< anchor id="SimFile" />}}`SimFile` | Load a specific aircraft configuration at the start of the mission, depending on the Sim state you need. | String, one of the following:<span></span>{{< params/smallfont >}} - apron.flt<span></span>runway.flt<span></span>climb.flt<span></span>cruise.flt<span></span>final.flt<span></span>taxi.flt{{< /params/smallfont >}} | No |
| {{< anchor id="ChecklistFolder" />}}`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 |

{{< /table-wrapper >}}


### [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](../../cfg-files/panel.cfg/). The available parameters are:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="ScreenUniCoords-Panel.N" />}}`ScreenUniCoords` | The current screen co-ordinates of the panel window. See the note on [Universal Screen Co-ordinates](../flt-additional-information/#universal-screen-co-ordinates). | 4 Floats | Yes |
| {{< anchor id="UndocCoords-Panel.N" />}}`UndocCoords` | The co-ordinates of the window if it has been undocked. See the note on [Universal Screen Co-ordinates](../flt-additional-information/#universal-screen-co-ordinates). | 4 Floats | Yes |
| {{< anchor id="Visible-Panel.N" />}}`Visible` | `True` if the window is visible, `False` otherwise. | Boolean | Yes |
| {{< anchor id="Undocked-Panel.N" />}}`Undocked` | Set to `True` if the window has been undocked, in which case the window will be located at undoccoords. | Boolean | Yes |
| {{< anchor id="HiddenOn" />}}`HiddenOn` | Unused. Always False. | Boolean | No |
| {{< anchor id="ID-Panel.N" />}}`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, {{< glossterm >}}g{{< /glossterm >}} meter, Race penalty, and Countdown) which are saved off even if a mission is not being run. | Integer | Yes |
| {{< anchor id="ViewsOn" />}}`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 |

{{< /table-wrapper >}}


### [Avionics.*N*]

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

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Comm1Active" />}}`Comm1Active` | Frequency of COM1. | Float | Yes |
| {{< anchor id="Comm1Standby" />}}`Comm1Standby` | Frequency of COM1 standby. | Float | Yes |
| {{< anchor id="Comm2Active" />}}`Comm2Active` | Frequency of COM2. | Float | Yes |
| {{< anchor id="Comm2Standby" />}}`Comm2Standby` | Frequency of COM2 standby. | Float | Yes |
| {{< anchor id="Comm3Active" />}}`Comm3Active` | Frequency of COM3. | Float | Yes |
| {{< anchor id="Comm3Standby" />}}`Comm3Standby` | Frequency of COM3 standby. | Float | Yes |
| {{< anchor id="Nav1Active" />}}`Nav1Active` | Frequency of NAV1. | Float | Yes |
| {{< anchor id="Nav1Standby" />}}`Nav1Standby` | Frequency of NAV1 standby. | Float | Yes |
| {{< anchor id="OBS1" />}}`OBS1` | Position of the OBS for NAV1, in degrees. | Float | Yes |
| {{< anchor id="Nav2Active" />}}`Nav2Active` | Frequency of NAV2. | Float | Yes |
| {{< anchor id="Nav2Standby" />}}`Nav2Standby` | Frequency of NAV2 standby. | Float | Yes |
| {{< anchor id="OBS2" />}}`OBS2` | Position of OBS for NAV2, in degrees. | Float | Yes |
| {{< anchor id="Nav3Active" />}}`Nav3Active` | Frequency of NAV3. | Float | Yes |
| {{< anchor id="Nav3Standby" />}}`Nav3Standby` | Frequency of NAV3 standby. | Float | Yes |
| {{< anchor id="OBS3" />}}`OBS3` | Position of OBS for NAV3, in degrees. | Float | Yes |
| {{< anchor id="Nav4Active" />}}`Nav4Active` | Frequency of NAV4. | Float | Yes |
| {{< anchor id="Nav4Standby" />}}`Nav4Standby` | Frequency of NAV4 standby. | Float | Yes |
| {{< anchor id="OBS4" />}}`OBS4` | Position of OBS for NAV4, in degrees. | Float | Yes |
| {{< anchor id="Transponder" />}}`Transponder` | Frequency of transponder (an octal code number that should match the coded assigned squawk number from the `[ATC_Aircraft.N]` section). | String | Yes |
| {{< anchor id="TransponderState" />}}`TransponderState` | The transponder state. | Integer:<span></span>{{< params/smallfont >}} - 0 = Off<span></span>1 = Standby<span></span>2 = Test<span></span>3 = On<span></span>4 = Alt<span></span>5 = Ground{{< /params/smallfont >}} | Yes |
| {{< anchor id="ADFActive" />}}`ADFActive` | The frequency of ADF 1 (automatic direction finder). | Float | Yes |
| {{< anchor id="ADF2Active" />}}`ADF2Active` | The frequency of ADF 2. | Float | Yes |
| {{< anchor id="DMESelected" />}}`DMESelected` | The selected DME, either 1 or 2. | Integer | Yes |
| {{< anchor id="ComTransmit" />}}`ComTransmit` | The selected COM channel, either 1 or 2. | Integer | Yes |
| {{< anchor id="ComReceiveBoth" />}}`ComReceiveBoth` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="Com1Receive" />}}`Com1Receive` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="Com2Receive" />}}`Com2Receive` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="Com3Receive" />}}`Com3Receive` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="AudioNav1Listen" />}}`AudioNav1Listen` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="AudioNav2Listen" />}}`AudioNav2Listen` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="AudioMarkerListen" />}}`AudioMarkerListen` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="AudioDmeListen" />}}`AudioDmeListen` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="AudioAdfListen" />}}`AudioAdfListen` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="AudioAdf2Listen" />}}`AudioAdf2Listen` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |
| {{< anchor id="AvionicsSwitch" />}}`AvionicsSwitch` | `True` if the switch is on, `False` otherwise. | Boolean | Yes |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Active-Slew.N" />}}`Active` | `True` indicates the object is in slew mode, `False` means it is not. | Boolean | Yes |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Location" />}}`Location` | `True` if the simulation is not to alter the location of the aircraft, `False` otherwise. | Boolean | Yes |
| {{< anchor id="Altitude-Freeze.N" />}}`Altitude` | `True` if the simulation is not to alter the altitude of the aircraft, `False` otherwise. | Boolean | Yes |
| {{< anchor id="Attitude" />}}`Attitude` | `True` if the simulation is not to alter the attitude (pitch, bank and heading) of the aircraft, `False` otherwise. | Boolean | Yes |

{{< /table-wrapper >}}


### [SystemFailure*N*.*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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="ID-SystemFailureN.i" />}}`ID` | One entry from the [Failure Code Table](../flt-additional-information/#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 |
| {{< anchor id="SubIndex" />}}`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 |
| {{< anchor id="Health" />}}`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 |
| {{< anchor id="Armed" />}}`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`.<span></span>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 |
| {{< anchor id="ArmedFailureFromTime" />}}`ArmedFailureFromTime` | Time in seconds from the start of the simulation when the component might fail. | Float | Yes |
| {{< anchor id="ArmedFailureToTime" />}}`ArmedFailureToTime` | Time in seconds from the start of the simulation when the component will fail. | Float | Yes |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "300px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="ThrottleLeverPct" />}}`ThrottleLeverPct` | Percentage that the throttle lever has been applied, from 0 to 1.0. | Float | Yes |
| {{< anchor id="PropellerLeverPct" />}}`PropellerLeverPct` | Percentage that the propeller lever has been applied, from 0 to 1.0. | Float | No |
| {{< anchor id="MixtureLeverPct" />}}`MixtureLeverPct` | Percentage that the mixture lever has been applied, from 0 to 1.0. | Float | No |
| {{< anchor id="Pct Engine RPM" />}}`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 |
| {{< anchor id="MaxReachedEngineRPM" />}}`MaxReachedEngineRPM` | Some gauges record the maximum rpm reached on a flight, so this value is recorded here. | Float | No |
| {{< anchor id="Pct N1" />}}`Pct N1` | Set the {{< glossterm >}}N1{{< /glossterm >}} value that the aircraft should start with, expressed as a percentage (0 - 100). | Float | No |
| {{< anchor id="Pct N2" />}}`Pct N2` | Set the {{< glossterm >}}N2{{< /glossterm >}} value that the aircraft should start with, expressed as a percentage (0 - 100). | Float | No |
| {{< anchor id="LeftMagneto" />}}`LeftMagneto` | True if the switch is on. | Boolean | No |
| {{< anchor id="RightMagneto" />}}`RightMagneto` | True if the switch is on. | Boolean | No |
| {{< anchor id="GeneratorSwitch" />}}`GeneratorSwitch` | True if the switch is on. | Boolean | No |
| {{< anchor id="CowlFlapPct" />}}`CowlFlapPct` | Percentage that the cowl flaps are open. This affects the cylinder head temperature cooling as follows:<span></span>`CHTCooling = true_airspeed_fps density_ratio / temperature_ratio + cowl_flaps_pos 80` | Float | No |
| {{< anchor id="FuelPumpSwitch" />}}`FuelPumpSwitch` | True if the switch is on. The corresponding SimVar is `GENERAL ENG FUEL PUMP SWITCH`. | Boolean | No |
| {{< anchor id="FuelPumpSwitch_EX1" />}}`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 |
| {{< anchor id="FuelValveOpen" />}}`FuelValveOpen` | True if the valve is open. | Boolean | No |
| {{< anchor id="FuelPressurePSF" />}}`FuelPressurePSF` | Set the fuel pressure level (in {{< glossterm >}}psf{{< /glossterm >}}). The corresponding SimVar is `GENERAL ENG FUEL PRESSURE`. | Float | No |
| {{< anchor id="OilTemperature_DegR" />}}`OilTemperature_DegR` | Sets the temperature of the engine oil, in {{< glossterm >}}Rankine{{< /glossterm >}}. | Float | No |
| {{< anchor id="CarbHeat/DeiceSwitch" />}}`CarbHeat/DeiceSwitch` | True if the switch is on. | Boolean | No |
| {{< anchor id="EngineMasterSwitch" />}}`EngineMasterSwitch` | True if the switch is on. | Boolean | No |
| {{< anchor id="GlowPlugTemperaturePct" />}}`GlowPlugTemperaturePct` | Sets the glow plug temperature, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}. | Float | No |
| {{< anchor id="RadiatorTemperature_DegR" />}}`RadiatorTemperature_DegR` | Sets the temperature of the radiator, in {{< glossterm >}}Rankine{{< /glossterm >}}. | Float | No |
| {{< anchor id="CHT_DegR" />}}`CHT_DegR` | Sets the temperature of the cylinder head, in {{< glossterm >}}Rankine{{< /glossterm >}}. | Float | No |
| {{< anchor id="IgnitionSwitch" />}}`IgnitionSwitch` | Used to set the initial value of the SimVar `TURB_ENG_IGNITION_SWITCH_EX1`. | Integer:<span></span>{{< params/smallfont >}} - 0 = Not Igniting<span></span>1 = Auto<span></span>2 = On{{< /params/smallfont >}} | No |
| {{< anchor id="StarterSwitch" />}}`StarterSwitch` | Sets whether or not the Starter is enabled. | Boolean | No |
| {{< anchor id="EGT_DegR" />}}`EGT_DegR` |  |  | No |
| {{< anchor id="ITT_DegR" />}}`ITT_DegR` |  |  | No |
| {{< anchor id="Afterburner" />}}`Afterburner` | Optional entry, recording the stage of the afterburner. | Integer | No |
| {{< anchor id="CorrectedFF" />}}`CorrectedFF` | Sets the corrected Fuel flow at spawn, in {{< glossterm >}}lbs{{< /glossterm >}} per hour.<span></span>Default value is 0 if the aircraft is spawned on the ground and 500 if spawned in the air. | Float | No |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="prop_beta" />}}`prop_beta` | The "prop beta" is the pitch of the blades of the propeller. | Float | No |
| {{< anchor id="prop_max_rpm_percent" />}}`prop_max_rpm_percent` | The propeller maximum RPM expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}. | Float | No |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Reservoir[Name]" />}}`Reservoir[Name]` | This parameter takes a hashmap with a single key - `FillRatio` - which sets up the named [reservoir](../../cfg-files/system/modular-hydraulics-system-information/#reservoirn) with an initial quantity of fluid, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span>For example:<span></span>```Reservoir[Name]= FillRatio:0.98```<span></span>**NOTE**: Take care setting the quantity value. A full reservoir will prevent actuators from emptying themselves when moving, thus preventing them from moving at all. | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Valve[Name]-HYDRAULICS_SYSTEM_EX1.N" />}}`Valve[Name]` | This parameter takes a hashmap with a single key - `Status` - which sets the named [valve](../../cfg-files/system/modular-hydraulics-system-information/#valven) initial state, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}, where 0 is fully closed and 1 is fully open.<span></span>For example:<span></span>`Valve[Name]= Status:1.0` | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Junction[Name]-HYDRAULICS_SYSTEM_EX1.N" />}}`Junction[Name]` | This parameter takes a hashmap with up to two keys - `FillRatio`, and `Pressure` - which sets up the named [junction](../../cfg-files/system/modular-hydraulics-system-information/#junctionn) with initial values where:<span></span>{{< params/smallfont >}} - **FillRatio**: The amount of fluid in the junction, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span> - **Pressure**: The pressure of the hydraulic fluid in the junction, in {{< glossterm >}}psi{{< /glossterm >}}.{{< /params/smallfont >}}<span></span>For example:<span></span>`Junction[Name]= FillRatio:0.98 #Pressure:1500` | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Pump[Name]-HYDRAULICS_SYSTEM_EX1.N" />}}`Pump[Name]` | This parameter takes a hashmap with up to three keys - `FillRatio`, `Pressure`, and `Active` - which sets up the named [pump](../../cfg-files/system/modular-hydraulics-system-information/#pumpn) with initial values where:<span></span>{{< params/smallfont >}} - **FillRatio**: the amount of fluid in the pump, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span> - **Pressure**: the pressure of the hydraulic fluid in the pump, in {{< glossterm >}}psi{{< /glossterm >}}.<span></span> - **State**: the initial state of the pump, either on (1, True) or off (0, False).{{< /params/smallfont >}}<span></span>For example:<span></span>`Pump[Name]= FillRatio:0.510 #Pressure:14.500 #Active:False` | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="PTU[Name]" />}}`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](../../cfg-files/system/modular-hydraulics-system-information/#ptun) with initial values where:<span></span>{{< params/smallfont >}} - **Active**: Whether the PTU is active (1, True) or not (0, False).<span></span> - **Reversed**: Whether the PTU is reversed (1, True) or not (0, False). This is only valid for reversible PTUs.<span></span> - **PumpPressure**: The internal pressure of the PTU pump, in {{< glossterm >}}psi{{< /glossterm >}}.<span></span> - **MotorPressure**: The internal pressure of the PTU motor, in {{< glossterm >}}psi{{< /glossterm >}}.<span></span> - **PumpFillRatio**: The amount of fluid in the PTU pump, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span> - **MotorFillRatio**: The amount of fluid in the PTU motor, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.{{< /params/smallfont >}}<span></span>For example:<span></span>`PTU[Name] = Active:False #Reversed:False #PumpFillRatio:0.247 #PumpPressure:14.500 #MotorFillRatio:0.000 #PumpPressure:14.500` | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Accumulator[Name]" />}}`Accumulator[Name]` | This parameter takes a hashmap with up to two keys - `FillRatio`, and `Pressure` - which sets up the named [accumulator](../../cfg-files/system/modular-hydraulics-system-information/#accumulatorn) with initial values where:<span></span>{{< params/smallfont >}} - **FillRatio**: The amount of fluid in the accumulator, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span> - **Pressure**: The pressure of the hydraulic fluid in the accumulator, in {{< glossterm >}}psi{{< /glossterm >}}.{{< /params/smallfont >}}<span></span>For example:<span></span>`Accumulator[Name]= FillRatio:0.98 #Pressure:2000` | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Actuator[Name]" />}}`Actuator[Name]` | This parameter takes a hashmap two possible keys:<span></span>{{< params/smallfont >}} - **FillRatio** - sets the named [actuator](../../cfg-files/system/modular-hydraulics-system-information/#actuatorn) with an initial quantity of fluid, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span> - **Pressure** - The pressure of the hydraulic fluid in the actuator, in {{< glossterm >}}psi{{< /glossterm >}}.{{< /params/smallfont >}}<span></span>For example:<span></span>`Actuator[Name]= FillRatio:1.0 #Pressure:2000` | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Line[Name]" />}}`Line[Name]` | This parameter takes a hashmap with up to 4 keys - `InputFillRatio`, `OutputFillRatio`, `InputPressure`, and `OutputPressure` - which sets up the named [line](../../cfg-files/system/modular-hydraulics-system-information/#linen) with initial values where:<span></span>{{< params/smallfont >}} - **InputFillRatio**: The amount of fluid in the input side of the line, expressed as a Percent Over 100.<span></span> - **OutputFillRatio**: The amount of fluid in the output side of the line, expressed as a Percent Over 100.<span></span> - **InputPressure**: The internal fluid pressure of input side of the line, in {{< glossterm >}}psi{{< /glossterm >}}.<span></span> - **OutputPressure**: The internal fluid pressure of output side of the line, in {{< glossterm >}}psi{{< /glossterm >}}.{{< /params/smallfont >}}<span></span>For example:<span></span>`Line[Name] = InputFillRatio:1.000 #InputPressure:2932.298 #OutputFillRatio:1.000 #OutputPressure:2932.298` | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Tank[Name]" />}}`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 {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span>Default value is:<span></span>`Tank[Name]: #LevelPct:0.4`<span></span>or whatever setting the user has made in the main menu.<span></span> For more information on tank options, please see here: [Tank.N](../../cfg-files/flight-model/modular-fuel-system-information/#tankn) | Float | No |
| {{< anchor id="Valve[Name]-FuelSystem.N" />}}`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).<span></span>Default value is:<span></span>`Valve[Name]: #IsOpen:TRUE`<span></span>For more information on valve options, please see here: [Valve.N](../../cfg-files/flight-model/modular-fuel-system-information/#valven) | Bool | No |
| {{< anchor id="Junction[Name]-FuelSystem.N" />}}`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.<span></span>Default value is:<span></span>`Junction[Name]: #SelectedOption:1`<span></span>For more information on junction options, please see here: [Junction.N](../../cfg-files/flight-model/modular-fuel-system-information/#junctionn) | Integer | No |
| {{< anchor id="Pump[Name]-FuelSystem.N" />}}`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:<span></span>{{< params/smallfont >}} - 0 = Off<span></span> - 1 = On<span></span> - 2 = Auto{{< /params/smallfont >}}<span></span>Default value is:<span></span>`Pump[Name]: #Active:0`<span></span>For more information on pump options, please see here: [Pump.N](../../cfg-files/flight-model/modular-fuel-system-information/#pumpn) | Integer | No |
| {{< anchor id="Trigger[Name]" />}}`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.<span></span>Default value is:<span></span>`Trigger[Name]: #State:TRUE`<span></span>For more information on trigger options, please see here: [Trigger.N](../../cfg-files/flight-model/modular-fuel-system-information/#triggern) | Integer | No |

{{< /table-wrapper >}}


### [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.

The available parameters are:

{{< table-wrapper "300px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Engine[name]" />}}`Engine[name]` | This hashmap is used to set up the named [Engine](../../cfg-files/system/modular-pneumatics-system-information/#enginen) or [APU](../../cfg-files/system/modular-pneumatics-system-information/#apun) component. You supply the engine/APU name, and then the hashmap which has the following keys:<span></span>{{< params/smallfont >}} - **Bleed**: Sets the bleed air status of the named Engine or APU component to enabled (1, TRUE) or disabled (0, FALSE).{{< /params/smallfont >}}<span></span>For example:<span></span>`Engine[APU]=Bleed: False`<span></span>There are no default values, just do not include the parameter if not needed. | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Pack[name]" />}}`Pack[name]` | This hashmap is used to set up the named [Pack](../../cfg-files/system/modular-pneumatics-system-information/#packn) component. You supply the pack name, and then the hashmap which has the following keys:<span></span>{{< params/smallfont >}} - **Active**: Sets the status of the named Pack component to enabled (1, TRUE) or disabled (0, FALSE).<span></span> - **Switch**: Sets the status of the named Pack overhead switch to enabled (1, TRUE) or disabled (0, FALSE).<span></span> - **Flow**: Sets the percentage of airflow through the named Pack component, as a Percent Over 100.<span></span> - **Mode**: Sets the initial mode of the named Pack component, which can be one of the following:<span></span>&nbsp;&nbsp;&nbsp;&nbsp;- 0: Low<span></span>&nbsp;&nbsp;&nbsp;&nbsp;- 1: Normal (default when the Mode key is not included)<span></span>&nbsp;&nbsp;&nbsp;&nbsp;- 2: High<span></span> - **Auto**: Sets whether the named Pack component is set to "Auto" (1, TRUE) or not (0, FALSE).{{< /params/smallfont >}}<span></span>For example:<span></span>`Pack[LeftPack]=Active: False #Switch: False #Flow: 1.000 #Mode: Normal #Auto: True`<span></span>There are no default values, just do not include the parameter if not needed. | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Area[name]" />}}`Area[name]` | This hashmap is used to set up the named [Area](../../cfg-files/system/modular-pneumatics-system-information/#arean) component. You supply the area name, and then the hashmap which has the following keys:<span></span>{{< params/smallfont >}} - **Pressure**: Sets the current pressure (in kiloPascals) for the named Area component.<span></span> - **Temperature**: Sets the current temperature (in °C) for the named Area component.<span></span> - **TargetTemperature**: Sets the target temperature (in °C) for the named Area component. Only useful if automatic temperature regulation is installed.{{< /params/smallfont >}}<span></span>For example:<span></span>`Area[Cockpit]=TargetTemperature: 24 #Temperature: 24 #Pressure: 100`<span></span>There are no default values, just do not include the parameter if not needed. | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Valve[name]" />}}`Valve[name]` | This hashmap is used to set up the named [Valve](../../cfg-files/system/modular-pneumatics-system-information/#valven) component. You supply the valve name, and then the hashmap which has the following keys:<span></span>{{< params/smallfont >}} - **Status**: Sets the percentage that the named Valve component is opened, as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span> - **TargetStatus**: Sets the target percentage that the named Valve component should open to, as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span> - **Mode**: Sets the initial mode of the named Valve component, which can be one of the following:<span></span>&nbsp;&nbsp;&nbsp;&nbsp;- Auto<span></span>&nbsp;&nbsp;&nbsp;&nbsp;- Manual<span></span>&nbsp;&nbsp;&nbsp;&nbsp;- Open<span></span>&nbsp;&nbsp;&nbsp;&nbsp;- Closed{{< /params/smallfont >}}<span></span>For example:<span></span>`Valve[OutflowValve]=Status: 0.000 #TargetStatus: 0.000 #Mode: Auto`<span></span>There are no default values, just do not include the parameter if not needed. | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Fan[name]" />}}`Fan[name]` | This hashmap is used to set up the named [Fan](../../cfg-files/system/modular-pneumatics-system-information/#fann) component. You supply the fan name, and then the hashmap which has the following keys:<span></span>{{< params/smallfont >}} - **Status**: Sets the percentage speed at which the named Fan component is running, as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span> - **Switch**: Sets whether the named Fan component is enabled (1, TRUE) or not (0, FALSE).{{< /params/smallfont >}}<span></span>For example:<span></span>`Fan[OutflowFan] = Status: 1.000 #Switch: True`<span></span>There are no default values, just do not include the parameter if not needed. | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Junction[name]" />}}`Junction[name]` | This hashmap is used to set up the named [Junction](../../cfg-files/system/modular-pneumatics-system-information/#junctionn) component. You supply the junction name, and then the hashmap which has the following keys:<span></span>{{< params/smallfont >}} - **LineStatus**: this is a comma separated list of [Line](../../cfg-files/system/modular-pneumatics-system-information/#linen) component names, where each named line is assigned a value, in brackets, to define it's open status. There should be one LineStatus entry for each attached line.{{< /params/smallfont >}}<span></span>For example:<span></span>`Junction[CabinHeatSelector] = LineStatus: CabinToAftCabin(0.5), CabinToFwdCabin(0.5)`<span></span>There are no default values, just do not include the parameter if not needed. | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="PacksOnDefaultValues" />}}`PacksOnDefaultValues` | Sets whether the packs are using the default temperature output values (1, TRUE) or not (0, FALSE).<span></span>Default value is 0 (FALSE). | Boolean | No |
| {{< anchor id="AircraftTargetAltitude_ft" />}}`AircraftTargetAltitude_ft` | Sets the target pressure of Areas so that it matches the ambient pressure of the given altitude, in {{< glossterm >}}ft{{< /glossterm >}}.<span></span>Default value is 7000. | Float | No |

{{< /table-wrapper >}}


### [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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | SimVar | Type | Required |
|---|---|---|---|:---:|
| {{< anchor id="Circuit[name]" />}}`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:<span></span>{{< params/smallfont >}} - **Switch**: Whether the circuit is on (1, True) or off (0, False).<span></span> - **PowerSetting**: the ratio of the power setting, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.{{< /params/smallfont >}}<span></span>Default value is:<span></span>`Circuit[name] = Switch:True #PowerSetting:1.0 `<span></span>For more information on circuits, please see here: [Circuit](../../cfg-files/system/modular-electrical-system-information/#circuitn). | [Circuits](../../../programming-apis/simvars/aircraft-simvars/aircraft-electrics-variables/#circuits) | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Battery[name]" />}}`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:<span></span>{{< params/smallfont >}} - **Switch**: Whether the battery is on (1, True) or off (0, False).<span></span> - **Capacity**: The remaining capacity in Ah (Ampere hours) of the battery.{{< /params/smallfont >}}<span></span>Default value is:<span></span>`Battery[name] = Switch:True #Capacity:13.6 `<span></span>For more information on batteries, please see here: [Battery](../../cfg-files/system/modular-electrical-system-information/#batteryn). | [Batteries](../../../programming-apis/simvars/aircraft-simvars/aircraft-electrics-variables/#batteries) | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Generator[name]" />}}`Generator[name]` | This parameter takes a hashmap with one key - `Switch` - which sets whether the generator is on (1, True) or off (0, False).<span></span>Default value is:<span></span>`Generator[name] = Switch:True`<span></span>For more information on generators, please see here: [Generator](../../cfg-files/system/modular-electrical-system-information/#generatorn). | N/A | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="ExternalPower[name]" />}}`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).<span></span>Default value is:<span></span>`ExternalPower[name] = Switch:True`<span></span>For more information on external power sources, please see here: [ExternalPower](../../cfg-files/system/modular-electrical-system-information/#externalpowern). | [External Power](../../../programming-apis/simvars/aircraft-simvars/aircraft-electrics-variables/#external-power) | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Line[name]" />}}`Line[name]` | This parameter takes a hashmap with one key - `Connected` - which sets whether the line is connected (1, True) or not (0, False).<span></span>Default value is:<span></span>`Line[name] = Connected:True`<span></span>For more information on lines, please see here: [Line](../../cfg-files/system/modular-electrical-system-information/#linen). | [Lines](../../../programming-apis/simvars/aircraft-simvars/aircraft-electrics-variables/#lines) | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Breaker[lineName]" />}}`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](../../cfg-files/system/modular-electrical-system-information/#linen), not the breaker itself.<span></span>{{< params/smallfont >}} - **Pulled**: Whether the breaker has been pulled (1, True) or not (0, False).<span></span> - **Timer**: the current trip time of the breaker.{{< /params/smallfont >}}<span></span>Default value is:<span></span>`Breaker[lineName] = Pulled:False #Timer:0.0 ` <span></span><span></span>For more information on breakers, please see here: [Breaker](../../cfg-files/system/modular-electrical-system-information/#breakern).| [Breakers](../../../programming-apis/simvars/aircraft-simvars/aircraft-electrics-variables/#breakers) | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |

{{< /table-wrapper >}}


### [Liquid Dropping System.*N*]

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

The available parameters are:

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Tank[name]" />}}`Tank[name]` | The volume of liquid that should be stored in the named [Tank](../../cfg-files/system/modular-liquid-dropping-system-information/#tankn), in {{< glossterm >}}gallons{{< /glossterm >}}. | Float | Yes |

{{< /table-wrapper >}}


### [Water Ballast System.*N*]

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

The available parameters are:

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Tank.N" />}}`Tank.N` | The volume of liquid that should be stored in the indexed [Tank](../../cfg-files/systems.cfg/#Tank.N-WATER-BALLAST-SYSTEM), in {{< glossterm >}}gallons{{< /glossterm >}}. | Float | Yes |

{{< /table-wrapper >}}


### [Burner_System.N]

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

The available parameters are:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Burner[ID]" />}}`Burner[ID]` | The initial setup for a [Burner](../../cfg-files/systems.cfg/#Burner.N). 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:<span></span>`Burner[ID] = Combustion:<true_false>`<span></span>For example:<span></span><code>Burner[Burner_1] = Combustion:true<span></span>Burner[Burner_2] = Combustion:true</code> | [Hash Map](../../cfg-files/cfg-files-general-information/#hash-map) | No |
| {{< anchor id="Valve[ID]" />}}`Valve[ID]` | The initial setup for a [Valve](../../cfg-files/systems.cfg/#valven-Burner_System). 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:<span></span>`Valve[ID] = Combustion:<true_false>`<span></span>For example:<span></span><code>Valve[Burner2_Whisper] = Status:0.0<span></span>Valve[Burner2_Pilot] = Status:1.0</code> | Float | No |

{{< /table-wrapper >}}


### [Switches.*N*]

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

{{< table-wrapper "200px" "" "200px" "150px" "100px" >}}

| Parameter | Description | SimVar | Type | Required |
|---|---|---|---|:---:|
| {{< anchor id="PitotHeat" />}}`PitotHeat` | `True` if the switch is on. | [`PITOT HEAT SWITCH`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#PITOT-HEAT-SWITCH) | Boolean | Yes |
| {{< anchor id="PitotHeat_EX1" />}}`PitotHeat_EX1` | An extended version of the PitotHeat parameter which offers more control. | [`PITOT HEAT SWITCH`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#PITOT-HEAT-SWITCH) | Integer:<span></span> - 0 = OFF<span></span> - 1 = ON<span></span> - 2 = AUTO | No |
| {{< anchor id="WindshieldDeice" />}}`WindshieldDeice` | Sets the state of the windshield de-icer | [`WINDSHIELD DEICE SWITCH`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#WINDSHIELD-DEICE-SWITCH) | Integer:<span></span> - 0 = OFF<span></span> - 1 = ON<span></span> - 2 = AUTO | Yes |
| {{< anchor id="BeaconLights" />}}`BeaconLights` | `True` if the lights are on. | [`LIGHT BEACON`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-BEACON) | Boolean | Yes |
| {{< anchor id="LandingLights" />}}`LandingLights` | `True` if the lights are on. | [`LIGHT LANDING`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-LANDING) | Boolean | Yes |
| {{< anchor id="LogoLights" />}}`LogoLights` | `True` if the lights are on. | [`LIGHT LOGO`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-LOGO) | Boolean | Yes |
| {{< anchor id="NavLights" />}}`NavLights` | `True` if the lights are on. | [`LIGHT NAV`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-NAV) | Boolean | Yes |
| {{< anchor id="PanelLights-Switches.N" />}}`PanelLights` | `True` if the lights are on. | [`LIGHT PANEL`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-PANEL) | Boolean | Yes |
| {{< anchor id="RecognitionLights" />}}`RecognitionLights` | `True` if the lights are on. | [`LIGHT RECOGNITION`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-RECOGNITION) | Boolean | Yes |
| {{< anchor id="StrobeLights" />}}`StrobeLights` | `True` if the lights are on. | [`LIGHT STROBE`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-STROBE) | Boolean | Yes |
| {{< anchor id="TaxiLights" />}}`TaxiLights` | `True` if the lights are on. | [`LIGHT TAXI`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-TAXI) | Boolean | Yes |
| {{< anchor id="WingLights" />}}`WingLights` | `True` if the lights are on. | [`LIGHT WING`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-WING) | Boolean | Yes |
| {{< anchor id="CabinLights" />}}`CabinLights` | `True` if the lights are on. | [`LIGHT CABIN`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-CABIN) | Boolean | Yes |
| {{< anchor id="GlareshieldLights" />}}`GlareshieldLights` | `True` if the lights are on. | [`LIGHT GLARESHIELD`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-GLARESHIELD) | Boolean | Yes |
| {{< anchor id="PedestalLights" />}}`PedestalLights` | `True` if the lights are on. | [`LIGHT PEDESTRAL`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-PEDESTRAL) | Boolean | Yes |
| {{< anchor id="AmbientLights" />}}`AmbientLights` | `True` if the lights are on. | Not linked to a SimVar | Boolean | Yes |
| {{< anchor id="BeaconLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-BEACON) | Boolean | No |
| {{< anchor id="LandingLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-LANDING) | Boolean | No |
| {{< anchor id="LogoLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-LOGO) | Boolean | No |
| {{< anchor id="NavLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-NAV) | Boolean | No |
| {{< anchor id="PanelLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-PANEL) | Boolean | No |
| {{< anchor id="RecognitionLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-RECOGNITION) | Boolean | No |
| {{< anchor id="StrobeLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-STROBE) | Boolean | No |
| {{< anchor id="TaxiLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-TAXI) | Boolean | No |
| {{< anchor id="WingLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-WING) | Boolean | No |
| {{< anchor id="CabinLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-CABIN) | Boolean | No |
| {{< anchor id="GlareshieldLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-GLARESHIELD) | Boolean | No |
| {{< anchor id="PedestalLightsNight" />}}`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`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-PEDESTRAL) | Boolean | No |
| {{< anchor id="AmbientLightsNight" />}}`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 |
| {{< anchor id="Potentiometer.N" />}}`Potentiometer.N` | Sets the state of the light potentiometer *N*. A value between 0 and 1 is required. | [`LIGHT POTENTIOMETER`](../../../programming-apis/simvars/aircraft-simvars/aircraft-system-variables/#LIGHT-POTENTIOMETER) | Float | Yes |

{{< /table-wrapper >}}


### [Systems.*N*]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="BatterySwitch" />}}`BatterySwitch` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="StructuralDeiceSwitch" />}}`StructuralDeiceSwitch` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="StructuralDeiceSwitch_EX1" />}}`StructuralDeiceSwitch_EX1` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="PropDeiceSwitch" />}}`PropDeiceSwitch` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="Autobrakes" />}}`Autobrakes` | Set to 1 if the aircraft has automatic brakes, 0 otherwise. | Integer | Yes |
| {{< anchor id="StandbyVacuum" />}}`StandbyVacuum` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="PropSync" />}}`PropSync` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="AutoFeatherSwitch" />}}`AutoFeatherSwitch` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="FlightDirector" />}}`FlightDirector` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="PanelLights-Systems.N" />}}`PanelLights` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="ExternalPowerSwitch" />}}`ExternalPowerSwitch` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="AuxPowerUnitSwitch" />}}`AuxPowerUnitSwitch` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="SeatBeltsSwitch" />}}`SeatBeltsSwitch` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="NoSmokingSwitch" />}}`NoSmokingSwitch` | `True` if the switch is on. | Boolean | Yes |
| {{< anchor id="LaunchBarSwitch" />}}`LaunchBarSwitch` | `True` if the launchbar has been deployed. These next five properties apply only to carrier launched aircraft. | Boolean | Yes |
| {{< anchor id="LaunchBarState" />}}`LaunchBarState` | One of: 0 if the launchbar is retracted, 1 if it is extended. | Integer | No |
| {{< anchor id="TailhookHandle" />}}`TailhookHandle` | `True` if the tailhook handle has been deployed. | Boolean | No |
| {{< anchor id="TailhookState" />}}`TailhookState` | One of: 0 if the tailhook is retracted, 1 if it is extended. | Integer | No |
| {{< anchor id="FoldingWingsHandle" />}}`FoldingWingsHandle` | `True` if the folding wings handle has been deployed. | Boolean | No |
| {{< anchor id="FoldingWingsState" />}}`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 |
| {{< anchor id="ClutchSwitch" />}}`ClutchSwitch` | For helicopters, this specifies whether the clutch is engaged (1, TRUE) or not (0, FALSE). | Boolean | No |
| {{< anchor id="GovernorSwitch" />}}`GovernorSwitch` | For helicopters, this specifies whether the governor is engaged (1, TRUE) or not (0, FALSE). | Boolean | No |
| {{< anchor id="DecisionHeight" />}}`DecisionHeight` | This parameter is used to set the value of the `DECISION HEIGHT` SimVar (in {{< glossterm >}}ft{{< /glossterm >}}). If this is not defined, the value will default to 200. |  | No |
| {{< anchor id="GovernorTarget" />}}`GovernorTarget` | For helicopters, this specifies the target {{< glossterm >}}rpm{{< /glossterm >}}, 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. | {{< glossterm >}}percent_over_100{{< /glossterm >}} | No |

{{< /table-wrapper >}}


### [Airship_System.N]

This section is only used when the aircraft is an **airship**. It is used to setup the flight state of the airship for the step of the flight that the FLT refers to. The available parameters are:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="FansPowerPct" />}}`FansPowerPct` | Sets the percentage of power being applied to the air intake fans, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}.<span></span>Note that air intake fans are not defined explicitly, but are added automatically by the simulation, one per-compartment that is of the gas type "Air". Non-air compartments do *not* have air intake fans. | Float | No |
| {{< anchor id="Valve_State[ID]" />}}`Valve_State[ID]` | Sets the state of the named (or indexed) [valve](../../cfg-files/flight_model.cfg/#valve.N-AIRSHIP_SYSTEM). This can be set to one of the following values:<span></span>{{< params/smallfont >}}0: Locked<span></span>1: Unlocked<span></span>2: Forced Open{{< /params/smallfont >}} | Enum | No |
| {{< anchor id="Damper_State[ID]" />}}`Damper_State[ID]` | Sets the state of the named (or indexed) [gas compartment](../../cfg-files/flight_model.cfg/#gas_compartment.N) damper. This can be set to one of the following values:<span></span>{{< params/smallfont >}}0: Locked<span></span>1: Unlocked<span></span>2: Forced Open{{< /params/smallfont >}}<span></span>It should be noted that dampers are not defined explicitly, but are added automatically by the simulation, one per-compartment that is of the gas type "Air". Non-air compartments do *not* have dampers. | Enum | No |

{{< /table-wrapper >}}


### [Gauges.*N*]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="kollsmansetting" />}}`kollsmansetting` | Records the Kollsman setting (barometric pressure at sea level, in inches of mercury). | Float | Yes |
| {{< anchor id="AutoBaroSetting" />}}`AutoBaroSetting` | If this parameter is set to true, the simulation will call the [BAROMETRIC](../../../programming-apis/key-events/aircraft-instrumentation-events/#barometric) key event to set the barometer level at the start of the flight.<span></span>Default value is false (0). | Boolean | No |

{{< /table-wrapper >}}


### [BleedAir.*N*]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="BleedAirSource" />}}`BleedAirSource` | Initial value of BleedAirSource enum. Default is 0. | Integer | No |
| {{< anchor id="EngineAirBleed.N" />}}`EngineAirBleed.N` | True if EngineBleedAir is enabled for the indexed engine. | Bool | No |
| {{< anchor id="APUAirBleed" />}}`APUAirBleed` | True if {{< glossterm >}}apu{{< /glossterm >}} AirBleed is enabled. | Bool | No |

{{< /table-wrapper >}}


### [Navigation_Graph.*N*]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="PayloadList" />}}`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](../../cfg-files/aircraft.cfg/). | Comma separated list | Yes |

{{< /table-wrapper >}}


### [CabinService.*N*]

This section can be added when the flight or mission requires the use of some [Navigation Service](../../navigation-services//navigation-services-and-interactions/). 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:

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Name" />}}`Name` | The name of the navigation service to use on the mission. This is the name as defined in the [services.XML](../../navigation-services/navigation-services-xml-properties/) file. | String | Yes |
| {{< anchor id="GraphPath" />}}`GraphPath` | The path to the [navigation graph CFG](../../cfg-files/navigation_graph.cfg/) file that is to be used. | String | No |
| {{< anchor id="CharacterQuality" />}}`CharacterQuality` | Sets the quality of the characters inside of the cabin service. Can be one of the following:<span></span>{{< params/smallfont >}}1. "Primary"<span></span>2. "Secondary"{{< /params/smallfont >}} | String | No |

{{< /table-wrapper >}}


### [CabinServiceObject.N]

This section can be added to define a single behaviour object that will be used as part of a [Navigation Service](../../navigation-services/navigation-services/). 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:

{{< table-wrapper "300px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="CabinServiceName" />}}`CabinServiceName` | The name of the navigation service that will be using this behaviour object. This is the name as defined in the [services.XML](../../navigation-services/navigation-services-xml-properties/) file. | String | Yes |
| {{< anchor id="BehaviourName" />}}`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](../../navigation-services/navigation-services-xml-properties/). | String | Yes |
| {{< anchor id="NodeTag" />}}`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`](#Density) parameter.<span></span>Note that you can only use this parameter *or* `Quantity` to define spawn quantity. You cannot use both parameters together. | String | No<span></span>{{< params/smallfont >}}(Yes if [`Density`](#Density) or [`CountByMass`](#CountByMass) is defined){{< /params/smallfont >}} |
| {{< anchor id="Quantity" />}}`Quantity` | Defines the number of behaviour objects that should be spawned.<span></span>Note that you can only use this parameter *or* [`NodeTag`](#NodeTag) to define spawn quantity. You cannot use both parameters together. | Float | No<span></span>{{< params/smallfont >}}(Yes if [`NodeTag`](#NodeTag) is not defined){{< /params/smallfont >}} |
| {{< anchor id="Density-CabinServiceObject.N" />}}`Density` | This is a percentage value that is *only* required when using the [`NodeTag`](#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.<span></span>Default value is 100. | Float | No |
| {{< anchor id="CountByMass" />}}`CountByMass` | If this is set to 1 (TRUE) then the simulation will deduce the quantity of behaviour objects to generate according the the mass defined in the [station_load.N](../../cfg-files/flight_model.cfg/#station_loadn) linked to the [[MassSection.N]](../../cfg-files/navigation_graph.cfg/#masssectionnn) of the node with the [`NodeTag`](#NodeTag). Note that this will also change the mass of those behaviour objects to exactly match the requested mass.<span></span>If this is set to 0 (FALSE) then [`Quantity`](#Quantity) will be used, and if that isn't set then [`Density`](#Density) will be used.<span></span>Default value is 0 (FALSE). | Boolean | No |
| {{< anchor id="RemoveOnFlightReset" />}}`RemoveOnFlightReset` | Defines whether the behaviour object should be removed on flight reset (1, TRUE) or not (0, FALSE).<span></span>Default value is 1 (TRUE). | Boolean | No |
| {{< anchor id="GeneratedCharacters" />}}`GeneratedCharacters` | Here you give one of the available pre-generated characters to be used as the spawned object.<span></span>If this is used then you cannot use the `SimObject.N` parameter. | String | No<span></span>{{< params/smallfont >}}(Yes if [`SimObject.N`](#SimObject.N) is defined){{< /params/smallfont >}} |
| {{< anchor id="SimObject.N" />}}`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.<span></span>If this is used then you cannot use the [`GeneratedCharacters`](#GeneratedCharacters) parameter. | String | No<span></span>{{< params/smallfont >}}(Yes if [`GeneratedCharacters`](#GeneratedCharacters) is defined){{< /params/smallfont >}} |
| {{< anchor id="ReduceQuantityOnSharedSeatWithCopilot" />}}`ReduceQuantityOnSharedSeatWithCopilot` | When this is set to true (1), reduce the behavior quantity if it is sharing a seat with a copilot.<span></span>Default value is false. | Boolean | No |

{{< /table-wrapper >}}


### [InteractivePoints.*N*]

{{< callout context="caution" title="IMPORTANT!" icon="outline/alert-triangle" >}}

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

{{< /callout >}}

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|---|
| {{< anchor id="InteractivePoint.N" />}}`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 |

{{< /table-wrapper >}}


### [WEAR_AND_TEAR_SYSTEM.N]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="inhibitAll" />}}`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 |
| {{< anchor id="inhibitCategory" />}}`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:<span></span>`inhibitCategory=Engine,Controls,LandingGear`<span></span>The available failure categories are as follows:<span></span>{{< params/smallfont >}} - Autopilot<span></span> - Controls<span></span> - Deicing<span></span> - Doors<span></span> - Electrical<span></span> - EmergencyOxygen<span></span> - Engine<span></span> - FuelSystem<span></span> - GroundContact<span></span> - HydraulicsSystem<span></span> - Instruments<span></span> - LandingGear<span></span> - Lights<span></span> - Miscellaneous<span></span> - Navigation<span></span> - OilSystem<span></span> - PneumaticSystem<span></span> - Sensors{{< /params/smallfont >}}<span></span>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](../../cfg-files/cfg-files-general-information/#list) of strings | No |

{{< /table-wrapper >}}


### [Controls.*N*]

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

{{< table-wrapper "200px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="SpoilersHandle" />}}`SpoilersHandle` | Percentage of maximum spoilers handle position. | Float | Yes |
| {{< anchor id="FlapsHandle" />}}`FlapsHandle` | Percentage of maximum flap handle position. | Float | Yes |
| {{< anchor id="LeftFlap" />}}`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 |
| {{< anchor id="RightFlap" />}}`RightFlap` | Percentage of maximum flap position of right flaps. If the maximum flap position is 40 degrees, then the example of 2.50 indicates the flaps are at 1 degree. | Float | Yes |
| {{< anchor id="GearsHandle" />}}`GearsHandle` | Percentage of maximum gear handle position. 0 is fully retracted. | Float | Yes |
| {{< anchor id="Gear1" />}}`Gear1` | Percentage of maximum extended gear position - for the center wheel gear. | Float | Yes |
| {{< anchor id="Gear2" />}}`Gear2` | Percentage of maximum extended gear position - for the left wheel gear. | Float | Yes |
| {{< anchor id="Gear3" />}}`Gear3` | Percentage of maximum extended gear position - for the right wheel gear. | Float | Yes |
| {{< anchor id="YokeY" />}}`YokeY` | Position of the yoke in the forward/backward direction. 0 is fully forward, 100 fully backward, 50 is dead center. | Float | Yes |
| {{< anchor id="YokeX" />}}`YokeX` | Position of the yoke in the left/right direction. 0 is fully left, 100 is fully right, 50 is dead center. | Float | Yes |
| {{< anchor id="YokeLock" />}}`YokeLock` | With this parameter you can choose to lock the yoke or not. The parameter takes one of the following strings:<span></span>{{< params/smallfont >}} - **Free**: The yoke can move freely.<span></span> - **Center**: The yoke is locked in the center position.<span></span> - **Freeze**: The yoke is locked at the last position it was set to.{{< /params/smallfont >}} | String:<span></span>{{< params/smallfont >}} - Free<span></span> - Center<span></span> - Freeze{{< /params/smallfont >}} | No |
| {{< anchor id="LeftBrake" />}}`LeftBrake` | Percentage of maximum application of left brake. | Float | Yes |
| {{< anchor id="RightBrake" />}}`RightBrake` | Percentage of maximum application of right brake. | Float | Yes |
| {{< anchor id="ParkingBrake" />}}`ParkingBrake` | Percentage of maximum application of parking brake. | Float | Yes |
| {{< anchor id="ElevatorTrim" />}}`ElevatorTrim` | Percentage of maximum application of elevator trim where 0 is the down limit, 100 is the up limit, and 50 would be the midpoint between the limits (not necessarily an angle of 0°). Linked to the SimVar [`ELEVATOR TRIM PCT EX1`](../../../programming-apis/simvars/aircraft-simvars/aircraft-control-variables/#ELEVATOR-TRIM-PCT-EX1). | Float | Yes |
| {{< anchor id="Rudder" />}}`Rudder` | Position of the rudder expressed as a percentage of its full range of movement. | Float | Yes |
| {{< anchor id="RudderLock" />}}`RudderLock` | With this parameter you can choose to lock the rudder or not. The parameter takes one of the following strings:<span></span>{{< params/smallfont >}} - **Free**: The rudder can move freely.<span></span> - **Center**: The rudder is locked in the center position.<span></span> - **Freeze**: The rudder is locked at the last position it was set to.{{< /params/smallfont >}} | String:<span></span>{{< params/smallfont >}} - Free<span></span> - Center<span></span> - Freeze{{< /params/smallfont >}} | No |
| {{< anchor id="RudderTrimPct" />}}`RudderTrimPct` | The amount of maximum application of rudder trim, between -1 and 1. Linked to the SimVar [`RUDDER TRIM PCT`](../../../programming-apis/simvars/aircraft-simvars/aircraft-control-variables/#RUDDER-TRIM-PCT). | Float | Yes |
| {{< anchor id="AileronTrimPct" />}}`AileronTrimPct` | The amount of maximum application of aileron trim, between -1 and 1. Linked to the SimVar [`ELEVATOR TRIM PCT`](../../../programming-apis/simvars/aircraft-simvars/aircraft-control-variables/#ELEVATOR-TRIM-PCT). | Float | Yes |
| {{< anchor id="AileronTrimDisabled" />}}`AileronTrimDisabled` | Used to set the initial value of the SimVar [`AILERON TRIM DISABLED`](../../../programming-apis/simvars/aircraft-simvars/aircraft-control-variables/#AILERON-TRIM-DISABLED), which disables the aileron trim. | Boolean | Yes |
| {{< anchor id="ElevatorTrimDisabled" />}}`ElevatorTrimDisabled` | Used to set the initial value of the SimVar [`ELEVATOR TRIM DISABLED`](../../../programming-apis/simvars/aircraft-simvars/aircraft-control-variables/#ELEVATOR-TRIM-DISABLED), which disables the elevator trim. | Boolean | Yes |
| {{< anchor id="RudderTrimDisabled" />}}`RudderTrimDisabled` | Used to set the initial value of the SimVar [`RUDDER TRIM DISABLED`](../../../programming-apis/simvars/aircraft-simvars/aircraft-control-variables/#RUDDER-TRIM-DISABLED), which disables the rudder trim. | Boolean | Yes |
| {{< anchor id="GLimiterSetting" />}}`GLimiterSetting` | This controls the setting of the G-limiter on an aircraft. This value can then be accessed through the SimVar [`G LIMITER SETTING`](../../../programming-apis/simvars/aircraft-simvars/aircraft-flight-model-variables/#G-LIMITER-SETTING). Possible values are:<span></span>{{< params/smallfont >}} - 0 = Off<span></span> - 1 = On<span></span> - 2 = Override{{< /params/smallfont >}} | Integer. | Yes |
| {{< anchor id="SpoilersArmed" />}}`SpoilersArmed` | Sets whether the spoilers are armed (1, TRUE) or not (0, FALSE). | Boolean | Yes |
| {{< anchor id="AntiSkidActive" />}}`AntiSkidActive` | Controls whether the anti-skid breaking system is active or not. This setting can be accessed using the [`ANTISKID BRAKES ACTIVE`](../../../programming-apis/simvars/aircraft-simvars/aircraft-brake-and-landing-gear-variables/#ANTISKID-BRAKES-ACTIVE) SimVar. | Boolean | Yes |
| {{< anchor id="TailwheelLock" />}}`TailwheelLock` | Controls whether the tail wheel is locked or not. This setting can be accessed using the [`TAILWHEEL LOCK ON`](../../../programming-apis/simvars/aircraft-simvars/aircraft-brake-and-landing-gear-variables/#AILWHEEL-LOCK-ON) SimVar. | Boolean | Yes |
| {{< anchor id="NosewheelLock" />}}`NosewheelLock` | Controls whether the nose wheel is locked or not. This setting can be accessed using the [`NOSEWHEEL LOCK ON`](../../../programming-apis/simvars/aircraft-simvars/aircraft-brake-and-landing-gear-variables/#NOSEWHEEL-LOCK-ON) SimVar. | Boolean | Yes |
| {{< anchor id="Collective" />}}`Collective` | Sets the collective position for helicopters, as a percentage between 0 1nd 100. | Float | No |
| {{< anchor id="LateralTrim" />}}`LateralTrim` | Sets the lateral trim for helicopters, where 0 is -100% trim, 50 is neutral (0%) trim, and 100 is 100% trim. | Float | No |
| {{< anchor id="LongitudinalTrim" />}}`LongitudinalTrim` | Sets the longitudinal trim for helicopters, where 0 is -100% trim, 50 is neutral (0%) trim, and 100 is 100% trim. | Float | No |

{{< /table-wrapper >}}


### [SimVars.*N*]

There will be one SimVars entry for each SimObject saved off. The available parameters are:

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Latitude" />}}`Latitude` | Latitude of aircraft. | Float | Yes |
| {{< anchor id="Longitude" />}}`Longitude` | Longitude of aircraft. | Float | Yes |
| {{< anchor id="Altitude-SimVars.N" />}}`Altitude` | Altitude of aircraft, in feet. | Float | Yes |
| {{< anchor id="Pitch" />}}`Pitch` | Pitch of the aircraft, in degrees. | Float | Yes |
| {{< anchor id="Bank" />}}`Bank` | Bank of the aircraft, in degrees. | Float | Yes |
| {{< anchor id="Heading" />}}`Heading` | Heading of the aircraft, in degrees. | Float | Yes |
| {{< anchor id="PVelBodyAxis" />}}`PVelBodyAxis` | Pitch rotational velocity, in radians per second. | Float | Yes |
| {{< anchor id="BVelBodyAxis" />}}`BVelBodyAxis` | Bank rotational velocity, in radians per second. | Float | Yes |
| {{< anchor id="HVelBodyAxis" />}}`HVelBodyAxis` | Heading rotational velocity, in radians per second. | Float | Yes |
| {{< anchor id="XVelBodyAxis" />}}`XVelBodyAxis` | Velocity in the X (sideways) direction, in feet per second. | Float | Yes |
| {{< anchor id="YVelBodyAxis" />}}`YVelBodyAxis` | Velocity in the Y (vertical) direction, in feet per second. | Float | Yes |
| {{< anchor id="ZVelBodyAxis" />}}`ZVelBodyAxis` | Velocity in the Z (forward) direction expressed as {{< glossterm >}}tas{{< /glossterm >}}, in feet per second. | Float | Yes |
| {{< anchor id="ZVelBodyAxis_IAS" />}}`ZVelBodyAxis_IAS` | Velocity in the Z (forward) direction expressed as {{< glossterm >}}ias{{< /glossterm >}}, in feet per second. | Float | Yes |
| {{< anchor id="SimOnGround" />}}`SimOnGround` | `True` if the aircraft is on the ground, which includes the deck of a carrier, or `False` otherwise. | Boolean | Yes |
| {{< anchor id="OnPlatformHeight" />}}`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 |

{{< /table-wrapper >}}


### [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](../../../programming-apis/reverse-polish-notation/), and if you are using the [JavaScript](../../../programming-apis/javascript/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](../../../programming-apis/reverse-polish-notation/), and if you are using the [JavaScript](../../../programming-apis/javascript/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).

Note that the convention used in the MSFS 2024 [model behaviors](../models/modelbehaviors/model-behaviors/) is to prefix all these variables with `XMLVAR_*`, for example:

``` cpp
[LocalVars_EX1.0]
XMLVAR_COVER_WING_LEFT=0
XMLVAR_COVER_WING_RIGHT=0
```


### [SimScheduler]

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

{{< table-wrapper "150px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="SimSpeed" />}}`SimSpeed` | The simulation rate. This parameter can only accept the following values:<span></span>{{< params/smallfont >}}0.25<span></span>0.5<span></span>1<span></span>2<span></span>4<span></span>8<span></span>16<span></span>32<span></span>64<span></span>128{{< /params/smallfont >}}<span></span>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 |
| {{< anchor id="SimTime" />}}`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 |

{{< /table-wrapper >}}


### Obsolete Parameters

In this section we list the parameters that are **obsolete** in Microsoft Flight Simulator 2024, and can therefor be removed from your FLT files.


#### [Options]

{{< table-wrapper "300px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Pause" />}}`Pause`<span class="obsolete"></span> | This option can be set to `True` or `False` to enable/disable the simulation pause state at the start or the finish. | Boolean | No |

{{< /table-wrapper >}}


#### [Atc_Menu]

{{< table-wrapper "300px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Visible-Atc_Menu" />}}`Visible`<span class="obsolete"></span> | Set to True if the window is visible, or false otherwise. | Boolean | Yes |

{{< /table-wrapper >}}


#### [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.

{{< callout context="note" title="NOTE" icon="outline/bulb" >}}

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

{{< /callout >}}

The available parameters are:

{{< table-wrapper "300px" "" "150px" "150px">}}

| Parameter | Description | Type | Required |
|---|---|---|:---:|
| {{< anchor id="Altitude-SimVarForSpawningInTheAir" />}}`Altitude`<span class="obsolete"></span> | The altitude at which the plane should spawn, measured in {{< glossterm >}}ft{{< /glossterm >}}. | Float | No |
| {{< anchor id="Slope" />}}`Slope`<span class="obsolete"></span> | The slope of the aircraft when the flight/mission starts, in degrees. | Float | No |
| {{< anchor id="IAS" />}}`IAS`<span class="obsolete"></span> | The {{< glossterm >}}ias{{< /glossterm >}} at which the plane should be flying when the flight/mission starts. Value is in {{< glossterm >}}ft{{< /glossterm >}} per seconds. | Float | No |
| {{< anchor id="FlapsDegree" />}}`FlapsDegree`<span class="obsolete"></span> | The level of flaps, in degrees. | Float | No |
| {{< anchor id="ThrottlePct" />}}`ThrottlePct`<span class="obsolete"></span> | This sets the position of the throttle, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}, where 0 is no throttle and 1 is full throttle. | Float | No |
| {{< anchor id="PropellerPct" />}}`PropellerPct`<span class="obsolete"></span> | This sets the position of the propeller lever, expressed as a {{< glossterm >}}percent_over_100{{< /glossterm >}}. | Float | No |

{{< /table-wrapper >}}