FLIGHT DEFINITIONS

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

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

 

When creating missions, you can generate the flight definition file within Microsoft Flight Simulator from the world view, and then use the option to save that file. This can then be used as the base flight definition for the mission you want to create.

The Sim UI For Saving A FLT File

Note that this file must be edited for missions, keeping in mind the following:

  • The CUSTOMFLIGHT.FLT file is based on a free flight, and as such it will add waypoints named TIMECRUIS and TIMEDSCNT. These will need deleted.
  • Waypoints may need re-numbering, eg: waypoint.4 ,waypoint.5, etc... from [ATC_ActiveFlightPlan.0] and [ATC_Aircraft.0]. Also WpInfo from [GPS_Engine] (depending on the mission).
  • Waypoints will need renaming to match those set in the flight plan (depending on the mission).
  • Correct the CountWP and NumberofWaypoints. Initially you should subtract 2 (for the previously removed TIMECRUIS and TIMEDSCNT waypoints), but this may need further editing depending on the mission type.

 

For Bush Trips the following template file is available for edition and examination:

 

For Landing Challenges the following template file is available for edition and examination:

 

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 example of this kind of file on the following page:

 

 

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

 

The available parameters are:

 

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

Enum :

  1. ASSISTANCE_PRESETSECTION_LANDINGCHALLENGE
  2. ASSISTANCE_PRESETSECTION_BUSHTRIP
  3. ASSISTANCE_PRESET_TUTORIALS
No
EventTriggersFileCount The number of event trigger files that are used by the flight/mission. Integer No
EventTriggersFile.N An event trigger file, where N starts at 0 and increments by 1 for each files added. This is the name of the file without the extension, and the file should be placed in the same location as the FLT file. String No

 

For more information on Event Triggers see the following page:

 

 

[Main]

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

 

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

String, one of the following:

  1. LandingChallenge
  2. FreeFlight
  3. BushTrip
  4. Tutorial
  5. Discovery
Yes
MissionSubType     No
MissionLocation The location of the flight. String No
OriginalFlight      
FlightType  

String:

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

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

Default value is "Cockpit".

String:

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

 

 

[Briefing]

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

 

Parameter Description Type Required
BriefingText This option is used to define the text that should be used on the mission briefing screen. String No
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 No

 

 

 

[Options]

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

 

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

String:

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

 

 

[Atc_Menu]

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

 

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

 

 

[Window.N]

This section deals with currently opened windows, where N is the window being referenced. Windows should always be numbered from 1 and there should always be at least 1 Window section. The available parameters are:

 

Parameter Description Type Required
Order Set to 0 if the main window is in focus, or the number of the window if another is in focus. Integer Yes
Active Set to True if this is the active window or False otherwise. Boolean Yes
Undocked Set to True if the window has been undocked or False otherwise. If set to True, the window will be located at UndocCoords. Boolean Yes
Maximized Set to True if the window is maximized, or False otherwise. When True, this will override screen co-ordinates. Boolean Yes
ScreenUniCoords The current screen co-ordinates of the window. See the note on Universal Screen Co-ordinates. The data for this parameter should be in a 4 value comma separated list, eg: ScreenUniCoords=2968, 811, 4304, 3702 4 Floats Yes
UndocCoords The co-ordinates of the window if it has been undocked. See the note on Universal Screen Co-ordinates. The data for this parameter should be in a 4 value comma separated list, eg: UndocCoords=0, 0, 0, 0 4 Floats Yes
CurrentCamera The GUID of the current camera (this will match one of the GUIDs in a [Camera.N.i] entry). Note that if a view option such as "Top Down View" is selected, then the current camera will be the GUID of one of the camera entries down in the list. String Yes
InstanceN Optional entries, counted from 1. If the camera is pointing at - or is inside - an AI controlled aircraft, then the type and tail number of that aircraft is stored here. For example: Instance1=C208B Grand Caravan String No

 

 

[Camera.N.i]

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

Camera.<window number>.<camera number>

The available parameters for each of these sections are:

 

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

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

This entry is not required for external views.

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

 

 

[EFIS]

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

 

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

String:

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

String:

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

String:

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

String:

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

 

 

[ResourcePath]

If the saved flight is a mission, this will be the path to the mission resources, such as the audio and briefings files. If it is not a mission it will reference the flights\other\folder. Note that the path is relative to the install location for the application, and that resource paths must be sub-folders within the install location. The available parameters are:

 

Parameter Description Type Required
Path The path to the files String Yes

 

 

[ObjectFile]

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

 

Parameter Description Type Required
NbFiles The number of additional "object" files that will be listed in this section. Integer Yes
File The path to the mission file. This is the path and filename without the extension. String Yes

 

 

[FreeFlight]

 

The available parameters are:

 

Parameter Description Type Required
FirstFlightState      

 

 

[Weather]

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

 

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

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

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

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

.\WeatherPresets\[PRESET_NAME]

For example:

WeatherPresetFile=.\WeatherPresets\ClearSky.WPR

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

 

 

[Departure]

Set the departure airport. The available parameters are:

 

Parameter Description Type Required
ICAO The ICAO code of the departure airport. String Yes
RunwayNumber The runway number. String Yes
RunwayDesignator The runway designator. String Yes

 

 

[Arrival]

Set the arrival airport. The available parameters are:

 

Parameter Description Type Required
ICAO The ICAO code of the arrival airport. String Yes
RunwayNumber The runway number. String Yes
RunwayDesignator The runway designator. String Yes

 

 

[Loading]

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

 

Parameter Description Type Required
ImageName.N The relative path and filename of the loading image to use. String Yes
TipsN

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

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

 

 

 

[Panels]

This section has the general panel control options. The available parameters are:

 

Parameter Description Type Required
Panel.On True if the main panel is visible, either in 2D cockpit or Virtual Cockpit view mode, or False otherwise. Boolean Yes
HUD.On If the panel.on setting is False, and this setting is True, then the mini panel is visible. If both panel.on and hud.on are False, then no panel is visible. Boolean Yes

 

 

[Panel.N]

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

 

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

 

 

[User Tip Window]

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

 

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

 

 

[ATC_AgentManager]

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

 

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

 

 

 

[ATC_Agent.n]

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

 

Parameter Description Type Required
AgentType The type of ATC agent.

String:

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

 

 

[ATC_Aircraft.N]

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

 

Parameter Description Type Required
ActiveFlightPlan This will be True if the user aircraft has a flight plan, or False otherwise. Boolean Yes
RequestedFlightPlan This will be True if the user aircraft has requested a new flight plan, and that request has not yet been answered, otherwise it will be False. Boolean Yes
AcState The current aircraft status.

Enum:

  1. ACSTATE_NONE

 

// IFR Clearance

  1. ACSTATE_PRETAXI_CLEARANCE
  2. ACSTATE_IFR_CLEARANCE_READBACK
  3. ACSTATE_IFR_CLEARANCE_WAIT_FOR_READBACK_GOOD

 

// Departure ground operations

  1. ACSTATE_CTAF_TAKEOFF
  2. ACSTATE_DYNAMIC_RUNWAY_CTAF_TAKEOFF
  3. ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_VFR_ATIS
  4. ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_VFR_NOATIS
  5. ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_IFR
  6. ACSTATE_TAXI_CLEARANCE_READBACK
  7. ACSTATE_TAXIING_OUT
  8. ACSTATE_ACKNOWLEDGE_HOLD_POSITION
  9. ACSTATE_ACKNOWLEDGE_CONTINUE_TAXI
  10. ACSTATE_TOWER_HOLDSHORT_ACKNOWLEDGE
  11. ACSTATE_TAKEOFF_POSITION_AND_HOLD_ACKNOWLEDGE
  12. ACSTATE_TAKEOFF_CLEARANCE_READBACK
  13. ACSTATE_DYNAMIC_RUNWAY_TAKEOFF

 

// Class D departure operations

  1. ACSTATE_TOWER_DEPARTING

 

// VFR enroute operations

  1. ACSTATE_VFR_ENROUTE_CONTACT
  2. ACSTATE_VFR_ENROUTE

 

// Flight Following and Airspace Transitions

  1. ACSTATE_ACKNOWLEDGE_SQUAWK
  2. ACSTATE_ACKNOWLEDGE_RADAR_CONTACT_FF
  3. ACSTATE_ACKNOWLEDGE_RADAR_CONTACT_TRANSITION
  4. ACSTATE_ACKNOWLEDGE_LEAVING_AIRSPACE_NOFF
  5. ACSTATE_ACKNOWLEDGE_TRANSITION_CLEARANCE_CLASS_BC
  6. ACSTATE_ACKNOWLEDGE_TRANSITION_CLEARANCE_CLASS_D

 

// Popup IFR States

  1. ACSTATE_ACKNOWLEDGE_INFLIGHT_IFR_CLEARANCE
  2. ACSTATE_INFLIGHT_IFR_CLEARANCE_WAIT_FOR_READBACK_GOOD

 

// Handoffs

  1. ACSTATE_AGENT_CONTACT
  2. ACSTATE_AGENT_HANDOFF

 

// IFR Enroute state

  1. ACSTATE_ARRIVAL
  2. ACSTATE_DYNAMIC_RUNWAY_ARRIVAL
  3. ACSTATE_DYNAMIC_APPROACH_ARRIVAL
  4. ACSTATE_DYNAMIC_APPROACH_TRANSITION_ARRIVAL
  5. ACSTATE_ARRIVAL_CANCEL_IFR

 

// States that loop back to ARRIVAL after aircraft responds

  1. ACSTATE_ARRIVAL_VECTOR
  2. ACSTATE_ARRIVAL_EXPECT
  3. ACSTATE_CRUISING_ALTITUDE_INCREASE
  4. ACSTATE_CRUISING_ALTITUDE_DECREASE
  5. ACSTATE_DYNAMIC_RUNWAY_ARRIVAL_EXPECT
  6. ACSTATE_DYNAMIC_APPROACH_ARRIVAL_EXPECT
  7. ACSTATE_DYNAMIC_APPROACH_TRANSITION_ARRIVAL_EXPECT
  8. ACSTATE_ARRIVAL_CLEARED
  9. ACSTATE_ARRIVAL_CLEARED_FULL_PROCEDURE
  10. ACSTATE_DYNAMIC_AIRPORT_LANDING

 

// Class D arrival operations

  1. ACSTATE_AGENT_HANDOFF_TOWER
  2. ACSTATE_TOWER_CONTACT
  3. ACSTATE_TOWER_CONTACT_IFR
  4. ACSTATE_TOWER_TRANSITION
  5. ACSTATE_TOWER_PATTERN_ENTRY
  6. ACSTATE_DYNAMIC_RUNWAY_PATTERN_ENTRY
  7. ACSTATE_TOWER_LANDING
  8. ACSTATE_DYNAMIC_RUNWAY_LANDING
  9. ACSTATE_TOWER_HANDOFF_GROUND
  10. ACSTATE_TOWER_CLEARED_TO_LAND
  11. ACSTATE_GO_AROUND_ACKNOWLEDGE
  12. ACSTATE_AGENT_HANDOFF_TOWER_MISSED_APPROACH
  13. ACSTATE_AGENT_CONTACT_MISSED_APPROACH

 

// CTAF Operations

  1. ACSTATE_CTAF_LANDING_TYPE
  2. ACSTATE_DYNAMIC_RUNWAY_CTAF_LANDING_TYPE
  3. ACSTATE_CTAF_LANDING
  4. ACSTATE_DYNAMIC_RUNWAY_CTAF_LANDING

 

// Arrival ground operations

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

String:

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

String:

  1. LANDING_NONE
  2. LANDING_IFR_EXPECTING_APPROACH
  3. LANDING_IFR_CLEARED_FOR_APPROACH
  4. LANDING_IFR_CLEARED_TO_LAND
  5. LANDING_VFR_FULL_STOP_REQUEST
  6. LANDING_VFR_FULL_STOP_FLYING_PATTERN
  7. LANDING_VFR_FULL_STOP_CLEARED_TO_LAND
  8. LANDING_VFR_TOUCH_AND_GO_REQUEST
  9. LANDING_VFR_TOUCH_AND_GO_FLYING_PATTERN
  10. LANDING_VFR_TOUCH_AND_GO_CLEARED_TO_LAND
Yes
DepartureRequest The departure request type.

String:

  1. DEPARTURE_VFR_REQUEST_REMAIN_IN_PATTERN
  2. DEPARTURE_VFR_REQUEST_DEPART_STRAIGHT_OUT
  3. DEPARTURE_VFR_REQUEST_DEPART_NORTH
  4. DEPARTURE_VFR_REQUEST_DEPART_SOUTH
  5. DEPARTURE_VFR_REQUEST_DEPART_EAST
  6. DEPARTURE_VFR_REQUEST_DEPART_WEST
  7. DEPARTURE_VFR_REQUEST_NONE
Yes
ParkingRequest The parking request.

String:

  1. PARKING_NAME_NONE
  2. PARKING_NAME_PARKING
  3. PARKING_NAME_N_PARKING
  4. PARKING_NAME_NE_PARKING
  5. PARKING_NAME_E_PARKING
  6. PARKING_NAME_SE_PARKING
  7. PARKING_NAME_S_PARKING
  8. PARKING_NAME_SW_PARKING
  9. PARKING_NAME_W_PARKING
  10. PARKING_NAME_NW_PARKING
  11. PARKING_NAME_GATE
Yes
ParkingTypeequest The parking request type.

String:

  1. PARKING_TYPE_NONE
  2. PARKING_TYPE_RAMP_GA
  3. FAC_TAXI_PARKING_TYPE_RAMP_GA_SMALL
  4. PARKING_TYPE_RAMP_GA_MEDIUM
  5. PARKING_TYPE_RAMP_GA_LARGE
  6. PARKING_TYPE_RAMP_CARGO
  7. PARKING_TYPE_RAMP_MIL_CARGO
  8. PARKING_TYPE_RAMP_MIL_COMBAT
  9. PARKING_TYPE_GATE_SMALL
  10. PARKING_TYPE_GATE_MEDIUM
  11. PARKING_TYPE_GATE_HEAVY
  12. PARKING_TYPE_DOCK_GA
  13. PARKING_TYPE_FUEL
  14. PARKING_TYPE_VEHICLE
Yes
PatternLeg  

String:

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

String:

  1. FLIGHT_FOLLOWING_NO
  2. FLIGHT_FOLLOWING_REQUEST
  3. FLIGHT_FOLLOWING_YES
Yes
AirspaceTransition  

String:

  1. AIRSPACE_TRANSITION_NONE
  2. AIRSPACE_TRANSITION_REQUEST
  3. AIRSPACE_TRANSITION_YES
Yes
BvAirspaceTransition  

String:

  1. BV_TYPE_NONE
  2. BV_TYPE_CENTER
  3. BV_TYPE_CLASS_A
  4. BV_TYPE_CLASS_B
  5. BV_TYPE_CLASS_C
  6. BV_TYPE_CLASS_D
  7. BV_TYPE_CLASS_E
  8. BV_TYPE_CLASS_F
  9. BV_TYPE_CLASS_G
  10. BV_TYPE_TOWER
  11. BV_TYPE_CLEARANCE
  12. BV_TYPE_GROUND
  13. BV_TYPE_DEPARTURE
  14. BV_TYPE_APPROACH
  15. BV_TYPE_MOA
  16. BV_TYPE_RESTRICTED
  17. BV_TYPE_PROHIBITED
  18. BV_TYPE_WARNING
  19. BV_TYPE_ALERT
  20. BV_TYPE_DANGER
  21. BV_TYPE_NATIONAL_PARK
  22. BV_TYPE_MODE_C
  23. BV_TYPE_MAX
Yes
BvAirspaceTransitionReq   Yes
TakeOffSequence  

String:

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

 

 

[ATC_AircraftData.N]

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

 

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

String:

  1. BV_TYPE_NONE
  2. BV_TYPE_CENTER
  3. BV_TYPE_CLASS_A
  4. BV_TYPE_CLASS_B
  5. BV_TYPE_CLASS_C
  6. BV_TYPE_CLASS_D
  7. BV_TYPE_CLASS_E
  8. BV_TYPE_CLASS_F
  9. BV_TYPE_CLASS_G
  10. BV_TYPE_TOWER
  11. BV_TYPE_CLEARANCE
  12. BV_TYPE_GROUND
  13. BV_TYPE_DEPARTURE
  14. BV_TYPE_APPROACH
  15. BV_TYPE_MOA
  16. BV_TYPE_RESTRICTED
  17. BV_TYPE_PROHIBITED
  18. BV_TYPE_WARNING
  19. BV_TYPE_ALERT
  20. BV_TYPE_DANGER
  21. BV_TYPE_NATIONAL_PARK
  22. BV_TYPE_MODE_C
  23. BV_TYPE_MAX
Yes
HasReachedClassD This value will be True if the aircraft has reached Class D airspace, or False otherwise. Boolean Yes

 

 

 

[ATC_ActiveFlightPlan.N]

This entry will exist if the user aircraft is flying with a current flight plan, either IFR or VFR. The available parameters are:

 

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

String:

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

Integer:

  1. 0 = Direct (GPS)
  2. 1 = VOR to VOR
  3. 2 = Low altitude airways
  4. 3 = High altitude airways
Yes
cruising_altitude The assigned cruising altitude in the current flight plan. Float Yes
departure_id The ICAO of the departure airport, and its lat/lon/alt, in the DepartureLLA element of the PLN file. For example:
departure_id=KSEA, N47° 25.89', W122° 18.48', +000433.00
Comma separated list Yes
departure_position The runway number and optional designator of the departure. For example:
departure_position=34R
String Yes
destination_id The ICAO of the destination airport, and its lat/lon/alt, in the DestinationLLA element of the PLN file. For example:
destination_id=KLAX, N33° 56.16', W118° 25.13', +000126.00
Comma separated list Yes
departure_name The name of the departure airport. String Yes
destination_name The name of the destination airport. String Yes
waypoint.N The list of waypoints making up the route. Often this is only two waypoints, the departure and destination airports. Refer to the notes on Waypoint Format. Comma separated list  

 

 

[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_AircraftManager]

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

 

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

 

 

[ATC_MessageSystem]

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

 

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

 

 

[ATC_FrequencyNode.N]

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

 

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

 

 

[ATC_MessageNode.N.i]

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

 

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

 

 

[GPS_Engine]

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

 

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

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

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

Comma separated list Yes

 

 

 

[DateTimeSeason]

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

 

Parameter Description Type Required
Season The current season.

String:

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

 

 

[SimplifiedSim.N]

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

 

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

String:

  1. None
  2. AI_Air
  3. AI_Taxi
  4. AI_LandingTakeoff
  5. Data_Air
  6. Data_ground
Yes

 

 

[Sim.N]

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

 

Parameter Description Type Required
Sim The title of the aircraft, or object, in the aircraft or sim configuration file. String Yes
Pilot

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

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

String No
Copilot

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

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

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

 

 

[SimVars.N]

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

 

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

 

 

[Avionics.N]

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

 

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

Integer:

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

 

 

[Slew.N]

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

 

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

 

 

[Freeze.N]

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

 

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

 

 

[SystemFailureN.i]

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

 

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

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

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

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

 

 

[Engine Parameters.N.i]

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

 

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

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

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

Integer:

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

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

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

Float No

 

 

[Propeller.N.i]

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

 

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

 

 

[Hydraulic Parameters.N.i]

Defines one or more hydraulic system. Systems are defined from N upwards - starting from 0 - where each one first corresponds to an engine pump, then the subsequent ones correspond to an electric pump. For example if the aircraft has 2 engines and two electric pumps you would have the following sections:

[Hydraulic Parameters.0.0]
[Hydraulic Parameters.1.0]
[Hydraulic Parameters.2.0]
[Hydraulic Parameters.3.0]

The second section value (i) corresponds to the aircraft number (0 for the user aircraft).

 

The available parameters are:

 

Parameter Description Type Required
HydraulicPressure

Sets the Hydraulic pressure (in psf) of the hydraulic system N. When multiple systems are defined, engine pumps should be first then electrical pumps.

Float No

 

 

[Fuel.N]

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

 

Parameter Description Type Required
TankSelector Tank selector for the left engine(s), or for a single-engine aircraft

Integer:

  1. Off
  2. All
  3. Left
  4. Right
  5. Left Aux
  6. Right Aux
  7. Left Main
  8. Right Main
  9. Center
  10. Crossfeed Left to Right
  11. Crossfeed Right to Left
  12. Center 2
  13. Center 3
  14. Drop 1
  15. Drop 2
  16. Right Tip
  17. Left Tip
  18. Crossfeed
  19. Both
  20. Drop All
Yes
TankSelector1 Tank selector for the right engine(s). Same range of options as TankSelector. This entry will be present, but ignored, for a single-engine aircraft. Yes
Center Percentage of fuel in tank. These parameters are only required if you are using the simplified fuel system as setup using the [FUEL] section for the aircraft. Float Yes
Center 2 Percentage of fuel in tank. Float Yes
Center 3 Percentage of fuel in tank. Float Yes
LeftMain Percentage of fuel in tank. Float Yes
RightMain Percentage of fuel in tank. Float Yes
LeftAux Percentage of fuel in tank. Float Yes
RightAux Percentage of fuel in tank. Float Yes
LeftTip Percentage of fuel in tank. Float Yes
RightTip Percentage of fuel in tank. Float Yes
External 1 Percentage of fuel in tank. Float Yes
External 2 Percentage of fuel in tank. Float Yes

 

 

[FuelSystem.N]

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

 

Parameter Description Type Required
Tank.x The remaining quantity of fuel in the indexed tank, as a Percent Over 100. Float No
Valve.x Sets whether the indexed valve is open (1, TRUE) or not (0, FALSE). Bool No
Junction.x Sets the the index value corresponding to the option currently used by the indexed junction. For more information on junction options, please see here: Junction.N. Integer No
Pump.x

Used to set what state the the indexed pump is in One of the following values:

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

 

 

[BleedAir.N]

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

 

Parameter Description Type Required
BleedAirSource Initial value of BleedAirSource enum. Default is 0. Integer No
EngineAirBleed.1 True if EngineBleedAir is enabled for engine 1 Bool No
EngineAirBleed.2 True if EngineBleedAir is enabled for engine 2 Bool No
EngineAirBleed.3 True if EngineBleedAir is enabled for engine 3 Bool No
EngineAirBleed.4 True if EngineBleedAir is enabled for engine 4 Bool No
APUAirBleed True if APU AirBleed is enabled Bool No

 

 

[LocalVars.N]

This section can be used to define and initialise 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.

 

 

[Switches.N]

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

 

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

Integer:

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

Integer:

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

 

 

[Electrical.N]

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

 

Parameter Description SimVar Type Required
bus.N

Used to set the initial value of the connection between 2 buses.

Syntax: bus.N = bus.X:B

where N and X are the IDs of the buses and B is 0 for an opened connection, and 2 for a closed one. For more information, please see here: bus.N.

General / Buses String Yes
circuit.N

Used to set the initial value of the connection between a bus and a circuit.

Syntax: circuit.N = bus.X:B

where N and X are the IDs of the circuit and bus and B is 0 for an opened connection, and 2 for a closed one. For more information, please see here: circuit.N.

Circuits String Yes
battery.N

Used to set the initial value of the connection between a bus and a battery.

Syntax: battery.N = bus.X:B

where N and X are the IDs of the battery and bus and B is 0 for an opened connection, and 2 for a closed one. For more information, please see here: battery.N.

Batteries String Yes
alternator.N

Used to set the initial value of the connection between a bus and an alternator.

Syntax: alternator.N = bus.X:B

where N and X are the IDs of the alternator and bus and B is 0 for an opened connection, and 2 for a closed one. For more information, please see here: alternator.N.

Alternators String Yes

 

 

[Systems.N]

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

 

Parameter Description Type Required
BatterySwitch True if the switch is on. Boolean Yes
StructuralDeiceSwitch True if the switch is on. Boolean Yes
StructuralDeiceSwitch_EX1 True if the switch is on. Boolean Yes
PropDeiceSwitch True if the switch is on. Boolean Yes
Autobrakes Set to 1 if the aircraft has automatic brakes, 0 otherwise. Integer Yes
StandbyVacuum True if the switch is on. Boolean Yes
PropSync True if the switch is on. Boolean Yes
AutoFeatherSwitch True if the switch is on. Boolean Yes
FlightDirector True if the switch is on. Boolean Yes
PanelLights True if the switch is on. Boolean Yes
ExternalPowerSwitch True if the switch is on. Boolean Yes
AuxPowerUnitSwitch True if the switch is on. Boolean Yes
SeatBeltsSwitch True if the switch is on. Boolean Yes
NoSmokingSwitch True if the switch is on. Boolean Yes
LaunchBarSwitch True if the launchbar has been deployed. These next five properties apply only to carrier launched aircraft. Boolean Yes
LaunchBarState One of: 0 if the launchbar is retracted, 1 if it is extended. Integer No
TailhookHandle True if the tailhook handle has been deployed. Boolean No
TailhookState One of: 0 if the tailhook is retracted, 1 if it is extended. Integer No
FoldingWingsHandle True if the folding wings handle has been deployed. Boolean No
FoldingWingsState Two values for the left and right wings, set to 0 if the wings are in a flying state, and 1 if they are folded (to save space on deck). Integer No
ClutchSwitch For helicopters, this specifies whether the clutch is engaged (1, TRUE) or not (0, FALSE). Boolean No
GovernorSwitch For helicopters, this specifies whether the governor is engaged (1, TRUE) or not (0, FALSE). Boolean No

 

 

[Gauges.N]

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

 

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

 

 

[AutoPilot.N]

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

 

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

 

 

[Payload.N]

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

 

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

 

 

[Controls.N]

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

 

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

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

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

 

 

[Multiplayer]

This section controls the multiplayer air-traffic in-sim for a flight. The available parameters are:

 

Parameter Description Type Required
Status This parameter controls the status of the multiplayer air-traffic system. When set to 1 (TRUE) multiplayer air-traffic will be enabled, and when set to 0 (FALSE) it will be disabled. Bool Yes
RadiusAlpha No longer used by the simulation. Float No
RadiusCreate Float No
RadiusRemove Float No

 

 

[AirTraffic]

This section controls the live air traffic in-sim for a flight. The available parameters are:

 

Parameter Description Type Required
Status This parameter controls the status of live air-traffic. When set to 1 (TRUE) live air-traffic will be enabled, and when set to 0 (FALSE) it will be disabled. Bool Yes
RadiusAlpha No longer used by the simulation. Float No
RadiusCreate Float No
RadiusRemove Float No

 

 

[TrafficManager]

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

 

Parameter Description Type Required
disable

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

Default value is 0 (FALSE).

Bool No

 

 

[SimScheduler]

 

The available parameters are:

 

Parameter Description Type Required
SimSpeed The simulation rate. 1.0 = Normal. Float Yes
SimTime The time the simulation has been running (since the timer was started during initialization). This timer is not incremented when the simulation is paused, and is largely used for calculating relative elapsed simulation time. Float Yes

 

 

[SimVarForSpawningInTheAir]

This section can be added when the flight or mission is designed to start with the aircraft in the air, rather than on the ground. Note that adding this section will cause some of the other *.flt file parameters to be overriden. 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.

 

The available parameters are:

 

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

 

 

Universal Screen Co-ordinates

Universal screen coordinates is a system designed to make screen positions independent of screen resolution. The universal coordinates extend from (0, 0) in the top left hand corner to (8192, 6144) in the bottom right hand corner. So, for example: If the universal coordinates of a rectangle are (500, 400) and it has a width of 7192px and a height of 650px and the screen resolution is 1024x768px, then the actual screen coordinates and size of the rectangle would be calculated as follows:

X = 500 * (1024/8192) = 62.5
Y = 400 * (768/6144) = 50
W = 7192 * (1024/8192) = 899
H = 650 * (768/6144) = 81.25

So the pixel position of the top left hand corner of the rectangle is at position (62, 50) and will have with a width of 899px and a height of 81px.

 

 

ATC Agent Signatures

Air traffic control agents have signatures made up of four entries, for example:

AgentTracking=2,4,20287488,GREENLAKE

These four entries are made up of the following:

  • The first number is always 2
  • The second is the agent type (see the table below)
  • The third number is a coding of the frequency
  • The fourth entry is the callsign.

In the example given above, the frequency coding is 20287477. To get this value we have taken the COM frequency of 135.9, multiplied it by 1000 to get 1359000. This value is considered as a hexadecimal and converted to decimal, which gives us 20287477.

 

The table below shows the values for agent type and what they correspond to:

 

Value Agent Type
1 ATIS
2 ClearanceDelivery
3 Ground
4 Tower
5 Center
6 Approach
7 Departure
8 FSS
9 CTAF
10 ASOS

 

 

Waypoint Format

Waypoints in flight files consist of the following properties, separated by commas. The commas must be present even if there is no value.

 

Property Description
region The region code, such as K1.
ident The ICAO ident.
airport The name of the airport, which is not often used.
name ID The name ID, often the same as ident.
type

One of:

  1. A : airport
  2. I : intersection
  3. V : VOR
  4. N : NDB
  5. U : user
  6. T : ATC
latitude The latitude.
longitude The longitude.
altitude The altitude in feet.
airway ID The airway ID, such as J5.

 

 

Failure Code Table

The following table contains the various failure codes that can be used with the [SystemFailureN.i] option.

 

System Failure Code
EngineSystem D8E878B03ED5314E80CD7F7C8E88914D
EngineFire 7560338230229542B1FDD38DC1C66E16
ApuFire 6DE7E05C3EC8A44FB7DC30B258355CCF
ApuSystem EA5CCD0C0F952A48B6BCF40820FA77FC
PitotSystem EFCDD611FE9E20458D492844093EFF9A
VacuumSystem 68C7173F8652AC40B080EA160D38A554
NavSystem B23C937B4B84A64F9D06416007ED4AF7
ComSystem 6415DB341282EE46A3B2CB3B3E95AC4E
ADFSystem A55DB93B35664A4B90D6801273934018
TransponderSystem 1234B6A9747D1144B0E842E32C5AD3B0
GPSSystem AE5F6115E438D90D3A839CA92B6DC3
LeftAileronSystem 6D2CE23C4D3B0449AA2815BDF9169527
RightAileronSystem 1E612FE63C9FC740A0BD756DCF8A86A2
ElevatorSystem 30DDFE695CBB8040A58489B8954F7C17
RudderSystem 912F51490DC40243BFB1655CD031E35A
LeftWingSystem 3B9EC4840BC0E44D826A81E1AF7A11CD
LeftFlapSystem 61F24A643F60154FA7D301B40C4F2686
LeftWingTipSystem 30CB57184BB48F409CE378797CC1F934
RightWingSystem 6089EA6411A7504C84C4C981FBDEFE9
RightFlapSystem 138575C0ADB52240A04B797FD6A12135
RightWingTipSystem 09DE7461A56C8442AC0B735C5B1F0B1
RearTailSystem 3DF24F6BC22BC74FAEB0EFADF7915EC
ElectricalSystem 8DBAC47552B96545BACC76849A654616
Generator BFADE0210473CBFF23012EB6AAF749
EngineFuelPump 9A3FD510474C9943BECA62624C95FA7E
FuelLeak 91CF40E7685C8941AFEAAC3CDAF7B223
OilSystem 83461181C2F8224DBAE0BE528D890A1E
OilLeak 1113B63BDD3B92498A98CD2E9FC19E5
TurbineIgnition C2C18DC111DB124DAA194AD938471C2
LeftBrakeSystem 599A3810A48BA14090B52156EF4A35C5
RightBrakeSystem 73E8072D9A94AA40A18F2CC189A6601E
BrakeSystemHydraulicSource BF9751430FA5FF47ABC538816080489B
CenterGearSystem 368B8A9CA2DBB942B509DDE8B9AD59FA
LeftGearSystem 0345E01CF415081ADFEEABE5B63C44B
RightGearSystem 0D617D2B58966A4184FD3476918977
AuxGearSystem B303FBA304A32A8418295218B15FB
HydraulicPumpFailure F9CB7A7FB2A52E4E9D7D8F30FBF262C2
HydraulicLeak 8B5B1849E34DFE47834EA03564E3621C
CoolantSystem 35B690B4859EAD49ACDB01DBEECFF237
LeftMagneto 9A313BA594DB2A4DA3DC38DFBD9091A4
RightMagneto 23B5CD11E4C51A068A3DFF2E6858AC
StaticSystem 2C4143A26D954447929028EFD0634A8B
FlyByWire_ELAC E5F9A2BD86B3FE4B89D3E1E61E48B6C
FlyByWire_FAC 783497C19E53FB48AEB881FA2B5710AB
FlyByWire_SEC C539839D9022484CA7AF4575B49EAD3A
HoistMotor F4FE39AD7630E6418C7791D08B1C660
SlingCable F4637D4668470A4A96BF87BED627811D
Cylinder C37D80E3C7DEEC4CA53E8B2FD2FF9F21
Airspeed Gauge 816DCB2925F98B44AE0AE496E8217BC3
Altimeter Gauge 0FE25A6F5BC75E4CA45A02DF04AE01A0
Attitude Gauge F3C0CD056C26AE43B92BA50816ECDB23
Fuel Gauge 40E80DE5C3B34A4381B1D50060EF7D23
DG Gauge 5D7C0C1B7E910D46BCEB6A60EDE60B59
Compass Gauge DD4CC891F18BE04AB46BD2702DA4D460
Turncoord Gauge 61A7C72937FD9F4AB0607041F1AE0561
VSI Gauge B877841ED460654AAC060D81AA4A1A57