IdealFlight help

Flight Generator

Flight Generator Properties

Duration Hours: Min, Max Set the minimum and maximum flight duration for a new random flight. The searched airport drop down list, when filled, contains locations that can be reached within the specified times.

If no airports are found, you must alter the search area. Setting a longer flight duration time, increases the diameter of the search area.

The next flight time is usually calculated from the advancing Profile Time function which adds time for fuel and maintenance.

The System Time checkbox sets the flight file so that whatever time you run the flight, the time will become the current System Time as it is then. Push Back Time is not assessed during de-brief and scoring if the loaded flight file (.FLT) has no date and time setting.

Note: Paused / Pause settings are ignored when a flight is generated to use System Time.

Override Profile Flight Start Time:

Start Date & Time and Time Now: These date/time settings override the Profile Next Flight Time calculation.

The Time Now button sets the current system time. The profile time will be set to this new time when you generate the flight.

Hint: Hold Shift or Ctrl during flight builds to force ASAP time, only the service time for the aircraft is added to the next flight time. Use Time Now to avoid adding service time. Use System Time to set the flight off at the current time set in FSX.

Plan Type: Choose the type of flight plan (IFR/VFR/Waypoint Only/None).

Climb and Descent Tops Ignored: Routes will not include Top of Climb (TOC) and Top of Descent (TOD) altitude markers. TOC and TOD can appear in undesirable places with some very small routes or add-in plans; TOC and TOD may not be desired with some FMC's; in these cases please deselect TOC/TOD plan types and try again.

Route End Navs Included: Add a Nav waypoint at the end of the flight plan if it is nearby the destination airport, and also provide information in the route table for a nearby Nav waypoint at the departure airport (if any). These are added to the route table, but not into the .PLN file itself. The End Navs cannot be used in the plan file itself since ATC and GPS programs can become confused about your position en-route. The End Nav Headings shown in the table are the direction to the airport from the Nav location, and are preceded with the "↑" and "↓" symbols to denote the direction is to the airport. The distance to the airport from the Nav is also preceded with the same "↑" and "↓" symbols for clarity. End navs are not entered into the actual .PLN plan file, and so the Tilde "~" symbol is used rather than a dash on these end nav route entries for improving clarity. Information for these Navs can also be found in the Nav section of the briefing so end navs can be ignored to reduce the route table length.

Approach Waypoints: Add a waypoint or sequence of waypoints to the end of the flight plan. The computed approach will create a GPS runway approach anywhere. Minimum approach section times can be modified in the Settings.ini, and with the >augmented upgrade approach leg times can be adjusted on the Mission page. Note: Computed approaches choose the side of the airport with lowest terrain. In the Mission page, soft and loose runways can be prioritised for use where available. ATC may instruct you elsewhere, these plans are ideal for VFR and non-ATC flying. If you need to clear a runway of Ai traffic, choose IF: Main Menu - Remove Ai Aircraft. Choose other approach types after upgrading with >augmented.

  • Landing Distance: The distance from the start of the final leg altitude down to the runway altitude 2000ft below, descending at 500fpm, and at the approximate aircraft landing speed (full flaps stall speed + 25 knots): = 4 minutes of flight.
  • Final Leg: The descent onto the runway. This leg distance = Landing Distance x 5/4 = 5 minutes to touchdown.
  • Thirty Degree Approach Leg: This leg distance = Landing Distance x 3/4 = 3 minutes. A final turn of thirty degrees is required before descent onto the runway.
  • Second Leg: This leg distance = Landing Distance x 3/4 = 3 minutes. Ends with a turn of sixty degrees onto the thirty degree approach leg.
  • First Leg: This leg is calculated for a descent from the minimum altitude for the area, down an approach altitude 2000ft above the runway = 1 minutes for each 500ft of descent. However the first leg minimum distance = Landing Distance x 3/4 = 3 minutes minimum. This waypoint is ignored if TOD is present and closer to the destination. May have a turn of Sixty degrees onto the second leg.
  • Thirty Degree Approach Leg, Second Leg, and First Leg: Default 2 minutes minimum with smaller aircraft.
  • The "Go to Approach" function will use these waypoints. If high altitude terrain surrounds the airport, the first waypoint will be clear of the mountains and have enough distance to descend from. Otherwise the second waypoint shall be the location your aircraft is moved to.

SID, STAR, IDF, FAF: Choose the types of departure and approach routes. Published Approaches and Departures are route descriptions that are not compatible with the flight plan itself in terms of GPS waypoints. However the Initial Departure Fix (IDF), and Final Approach Fix (FAF); are waypoints usually placed directly out from the runway and work well in the GPS route. The Standard Instrument Departure (SID), and the Standard Terminal Arrival Route (STAR); are route descriptions that contain local Navigation Aids and Waypoints to direct traffic to, from, and around busy airports. Ideal Flight's auto-planner chooses the most relevant waypoints from the SID and STAR for the flight plan to join. A GPS flight plan contains waypoints to and from the airports between Transition waypoints, but SID and STAR routing is by way of flight instructions. Most of these waypoints won't make sense in the GPS route. The pilot loads up the aircraft navigation system with the SID and STAR instructions when the time comes in the flight. These special routes around airports are not part of a GPS plan. (>augmented)

Use the "Approaches" plan type and select the "Computed Approach" mission item, for a waypoint assisted approach and landing. Set the Departure mission item to "Initial Departure Fix" (IDF), for departure waypoint assistance.

Plan Builder: Choose the type of route.

"Follow Airways" routes stick to designated airways, either high or low altitude, Jet or Victor. (Generally with AIRAC Integrated Nav Data Sets, use "Follow Airways", and select aircraft parameter "Jet Routes").

"Any Airways" routes use all the airways Jet or Victor.

"VOR to VOR" routes ignore Intersections along the route for ease of navigation, but remember; missing intersections and going direct to the next VOR waypoint can lead your route through a mountain.

"Avoid Controlled Airspaces" can add interest to routes, trying to keep to route sections having minimum altitudes below cruise altitude. "Direct to Destination" is simply a straight path, or rather the great circle route, to the destination location.

If no routes are found for your aircraft, another type of route will be chosen if one exists.

Set Jet or Victor routes on the Aircraft Flight Parameters page.

"Ignore Airways" routes simply go to each next Navigation Equipment waypoint found on the way to the destination, but will avoid high altitude terrain if necessary to maintain a low cruise altitude. (>augmented)

The button "..." Route Width, sets percentage search area for the route, 0..100% of roughly 300Nm either side of the great circle arc between departure and destination. In the case of "Ignore Airways" routes, the same button "..." Nav Density, cuts out less useful navaids if too many are found, 0..100% of roughly one navaid every 2Nm if available.

The route width button enables range adjustment for the planner to search for waypoints in a greater or lesser area. With "Ignore Airways" routes, this button enables adjustment of the relative density of navaids appearing en-route, as some areas can be quite crowded. (>augmented)

Final Cruise Altitude Rules: Odd 1000s for East, even 1000s for West, and 500ft extra for VFR plans.

Since the altitude depends on which direction and plan type you are flying it makes no sense to keep cruise altitude at a particular height.

In Ideal Flight, the altitude calculation depends on the Aircraft Flight Parameters Max Alt (the highest you want to fly) and a percentage gives your preferred altitude.

Say for a route across the alps (VFR going south east):

If I put in 18000 for max and 50% for cruise the planner tries to fit in at around 9500ft.

The reported cruise altitude in FSX may say 9500ft, if that's what the plan states, the IF briefing may have Minimum Altitudes showing as 13500ft (sticking to the altitude rules) along the route if there is an 11000ft minimum along the route. The plan may show increased altitude along the route in the briefing. FSX .PLN's don't recognise multiple cruise altitudes so none are specified in the plan. IF uses the initial cruise altitude for the plan, the altitude may show an increase along the route up to your Max Alt setting.

If you are a small plane with a high cruise altitude and a heavy load, your cruise speed will be reduced from the preferred speeds.

Also please remember that for very short flights one may not be in the air long enough to reach preferred altitudes, and may not clear mountains. Ultimately, it's the pilot's responsibility to determine and fly at a safe altitude.

Export Files: File export records are created by selecting the required file type from the menu. Each item exports a particular File Type to a Folder Location. Please see more about Exporting Files below. (>augmented)

Low Altitude Restriction: Alt. and Speed Flight plans restrict the speeds when flying below a certain altitude. Generally for aircraft flying below 10,000ft, speeds are restricted to 250 Knots.

Speed Restriction Defaults Button: Sets the low altitude speed restriction defaults of 10,000ft and 250 Knots.

Runway/Helipad Start: Initialise the aircraft on the runway or helipad, rather than the parked location. A glider always starts on a runway, waiting for the tow command. If a grass runway is available, the glider starts on that.

Aircraft Location: Choose the parking place for the aircraft. If Runway/Helipad Start has been chosen, choose from the available runways/helipads.

The Active Runway is unknown until FSX is running, so the best guess has to be made. Starting from the Active Runway may not always place the aircraft at the ATC required end of the runway for takeoff. In this case, the aircraft can be taxied, or moved in the simulator map view to the proper ATC runway start position.

Preparation Minutes / Payload Quantity: Choose how long to spend with the aircraft parked, setting up before pushback. Include extra preparation time when intending to call the fuel truck, for example. Payload tries to fit into the aircraft a specified percentage of possible loading. Press the button repeatedly until your chosen units are shown: %, Lb, Kg, Config Default, or Random %. Config Default: This creates a .FLT file with no payload entry so that FSX uses specifications from the aircraft.cfg file.

Note that the loads are proportional to the specified station available weight in the Flight Parameters Payload Definitions page. Selecting 1000Kg will only show 500Kg if the specified station available weight is set to half station weight in the Flight Parameters Payload Definitions page. The "[4300]" bracketed value shown in the Flight Parameters Payload Definitions page, is the maximum useable load for the aircraft, and can be reduced with large fuel loads.

Some aircraft have custom cargo or passenger settings. Ideal Flight computes the passenger count and cargo weight and displays it in the briefing. Only FSX compatible aircraft stations are loaded. Aircraft with custom cargo loading software may need the software to fill the aircraft. For best results, fill with the amount computed for the flight, as shown in the briefing.

Fuel: Taxi Minutes, Reserve, and Loading:

Fuel Taxi Minutes: Choose how long the aircraft may be required to taxi, halved for Runway Starts.

Fuel Hold Minutes: Choose how long the aircraft may be required to hold. Briefing includes fuel weight breakdown; taxi, hold, reserve, and flight fuel weights. (>augmented)

Reserve: Reserve minutes fuel time. Choose how long the aircraft is required to be able to cruise on reserve, hold, go around, and make any other manoeuvres in flight or on the ground. All Minutes = Cruise Fuel Minutes.

Even Fuel Loading; fills each tank to the required percentage fuel value (try first with add-on aircraft).

Inboard Loading; keeps the fuel in tanks nearer to the centre of gravity of the aircraft.

Outboard Loading; keeps the fuel in tanks farther from the centre of gravity of the aircraft.

Basic Fuel Reserve Rules Required by Law:

VFR: 30 minutes by day and 45 minutes by night for fixed wing aircraft and 20 minutes for rotorcraft.

IFR: Sufficient fuel to divert to a nearby airport with up to 30 minutes holding at 1500 feet for turbine engine aircraft, and 45 minutes for others.

The route distance, and hence time, is calculated for shortest path along the route, plus departure and approach vectoring (DP/STAR) as ATC would guide it.

The IF fuel calculation is computed very accurately. When the correct parameters have been set for an aircraft (Range, Cruise Speed etc.) and set zero reserve and taxi, fuel can run out while landing. Reserve must comprise the safety reserve recommended for the aircraft, usually 30-45 minutes. Use Taxi Time alone as it is halved for Runway Starts. Use Reserve Time to include any other extra fuel time that may be required for perhaps going around, holding, and other manoeuvres; All fuel time is calculated at cruise speed fuel rate.

Fuel Reserve Minutes Example: Let's say 30 mins reserve at cruise burn + 20mins holding at 50% cruise burn = 40mins at 100% cruise burn.

Fuel Taxi Minutes Example:Let's say 10 mins taxi at cruise burn = 20mins at 50% cruise burn. If you start on a runway the taxi time is halved.

Fuel Hold Minutes: Let's say 40mins holding at 50% cruise burn = 20mins at 100% cruise burn. (>augmented)

Setting fuel amounts manually: A flight must be ready built to enter the fuel manually and override the fuel planned, and the flight must be rebuilt to recalculate values and rewrite the briefing.

Empty Fuel Tanks: There is always a slight amount of fuel to be found in empty tanks. MinFuelAmount=10% has been set as the minimum value: Some aircraft can experience engine running problems starting up with totally empty tanks. DefFuelAmount=20% for Free Flights: Free Flight fuel is calculated from the maximum trip time on the Flight Generator page. See Settings.ini file

[FlightParams]
DefFuelAmount=20
MinFuelAmount=10
Windows XP: see "C:\Documents and Settings\All Users\Application Data\Ideal Flight 10\Profiles\Settings.ini"
Windows Vista and above: see "C:\ProgramData\Ideal Flight 10\Profiles\Settings.ini"

Default Warm Cockpit / Cold & Dark Selection: Disable the Cold and Dark settings screen and set up the default warm cockpit. When unchecked, the Cold & Dark settings can be used.

Cold & Dark Selection Button: Go to the Cold and Dark configuration screen.

Hide Parked Aircraft: Hide your parked aircraft when parked on runways, parking spaces, and helipads. Ai aircraft will use these places and will draw over parked aircraft in the simulation.

Max Ai Count and Ai Selection: Alter the amount of AI aircraft Ideal Flight should create, press "Ai Select" and choose aircraft for Ai operations. Ideal Flight schedules Ai Aircraft around your flight time, and generates aircraft around the departure and destination areas, and around several airports along the route, if available. These aircraft are in addition to any AI aircraft added with FSX settings and traffic add-ons. Use your traffic add-on aircraft by choosing them in the Ai Selection page; press "Ai Select". See the Ai Aircraft section below.

Destination Airport: Shows the current destination ICAO. Type in the ICAO of any airport and press Find.

Choose Destination: Select a new destination from the searched airport drop down list. When Flying Helicopters, navigation equipment stations are also used as locations.

Edit Plan: Edit the plan using a text list dialog.

When choosing to edit a plan, the departure and arrival runways should be selected first and the plan rebuilt. Once the runways are selected, the plan can be edited. These are for a more accurate fuel and ETA calculation. To place your aircraft on a runway to start the flight: choose from the "Runway Start / Aircraft Location" drop down list. The Edit Plan button text shows the runways and plan edited: (9L--) shows the departure runway has been selected, and (-+27C) shows the plan has been edited, and the arrival runway has been selected, the departure runway is on automatic.

Delete the flight files with the Clear Flight button (!).

The list shows each waypoint broken down into its waypoint type, waypoint ICAO ID, and Lat Lon Alt Location. You may want to keep the last two IF approach waypoints, they align the runway with a 5 minute approach path, from 1 minute flight at landing speed + 4 minutes descent at 500fpm

Here are the last three waypoints from an IF computed approach route. Above them is placed the last waypoint of a Navigraph STAR sequence.

Make up waypoint data the same as you see in the list:

  FIX 06FA LATLON N 26 54.48918 W 80 19.70484

    Waypoint ID: APP1  // runway radial                ← a comment
      Plan Item: User
    Lat Lon Alt: N41 27.61817 W8 44.224 2200.00

    Waypoint ID: TDWN  // runway touchdown
      Plan Item: User
    Lat Lon Alt: N41 15.76367 W8 41.10617 228.00

    Waypoint ID: LPPR
      Plan Item: Airport
    Lat Lon Alt: N41 14.13317 W8 40.68333 228.00
  Waypoint Name: LPPR // destination

// comment

/*
comments
- add comments to your library of SIDs/STARs
- no need to worry about copy and paste
*/

Altitudes can be omitted (last item in location).

Enter locations as: "N47° 40' 45.56",W117° 19' 52.10",+001953.00", or "N 47 40.75933 W 117 19.86833 1953.00", or "N47 40.75933 W117 19.86833 1953.00"

Make up waypoint data with the following Plan Items:

  Plan Item: Airport
  Plan Item: VOR
  Plan Item: NDB
  Plan Item: Intersection
  Plan Item: User

AIRAC SID/STAR

Copy and Paste some types of AIRAC waypoint data lines straight in from the AIRAC text files; example:

"FIX 06FA LATLON N 26 54.48918 W 80 19.70484"

Once an IF plan is edited, the route table in the briefing will always show all the waypoints including the IF computed approach waypoints: APPR3, APPR2, APPR1, TCHDWN. When IF makes approach routes, and TOD is close to APPR3, then APPR3 may be replaced with TOD.

Filter: ILS/Helipads, Tower, Parking, Fuel, Cargo, Military, Quadrants: During airport searches the Quadrants block allows searches to be made in one to four quadrants around your present location. The top row of filters are to ONLY INCLUDE those airports with the facility. The bottom row of filters are to EXCLUDE all those airports with the facility. Include or exclude tower; refers to available Tower contact frequencies. Include only airports with parking places. Include or exclude fuel parking airports; fuel parking airports have fuel parking ramps. Include or exclude cargo airports; cargo airports have cargo ramps. Include only airports with military parking ramps, or exclude all airports with military parking ramps. the military filter only works with airports that have military parking ramps defined. You will find many military airports irrespective of these filter settings.

Note; when in the map screen, uncheck the "Show All" box or there is no airport filtering anyway - Flight Generation filtering is not affected by this checkbox.

! Clear List Button: Clears the Searched Airports List and shows the Favourites.

! Clear Flight Button: Clears the Destination Airport and the flight files.

Search Button: Search for airports reachable within the current set of parameters.

? Check ICAO Button: Checks for the existence of an airport when an ICAO has been typed into the Destination Airport box.

Flight Parameters Button: Go to the Aircraft Flight Parameters screen, where values such as cruise speed and range can be adjusted. Adjusting these values will determine how the routes and flight plans are generated.

Mission: Go to the Mission and Monitor screen, where settings such as Monitor No Smoking Sign can be adjusted. Adjusting these values will determine how the flight scoring is calculated.

From the Pop-Up Menu, saved settings for the current aircraft can be replaced with default values.

Other destinations available are Boats at sea for spotting or landing, and VOR type or NDB Navigation Sites for landing nearby.

Boat Spotting: To successfully locate a vessel at sea, have the vessel in the forward view, within 1 Nm, and less than 1000 feet above it.

Boat Landing: Land on a vessel at sea. Landing and returning, counts as two flights.

VOR type or NDB Navigation Equipment Sites: Landing nearby one of these sites for maintenance, counts as a regular flight. Not all VOR type or NDB sites can be landed nearby since some may be slightly submerged in water.

Successfully landing anywhere other than an Airport, is referred to as a Landing Site.

Popup Menu

Default Aircraft/Tower Settings: Deletes the information saved for the aircraft when you used the IF: Main Menu, Save Aircraft Settings function in the sim. These are the settings for panel positions and cameras.

Airport Subsets

Airport subset text (.txt) files provide lists of airport ICAO codes for IF's filter to refer to.

Please choose a file from the drop down menu at the bottom of the page. When an airport subset is chosen, only those airports listed in the text (.txt) file will be available.

Remember, you will need to be within range of an airport in the subset to get a flight generated. You may need to choose a departure nearby the airports in the subset, for them to be located as possible destinations.

A list of major hub airports has been provided. Delete this file and a fresh one is created the next time IF is started.

Add and delete your own airport subsets. Alternatively; place your own ICAO .txt files in the Profiles\Airports folder alongside "Hub Airports.txt", and "My Airports.txt".

In the map screen; you can add the browsed airport to the current subset, or you can choose a subset to add the airport to if you do not have a subset selected, with the popup menu command: "Add Airport to Subset".

Only fly between add-on airports in your collection: A good idea might be to make a subset called "Add-on Airports" and add all of those add-ons as you collect them. Then you can readily make flights choose only from airports in your add-on collection. Make sure you keep a backup of your Profiles folder as the subset files are stored in the Airports directory.

Round the World trip: Another idea is to include only airports of a long journey, perhaps a round the world trip. When you configure the quadrants in the searches, only the next airport in a trip would be filtered out for the next leg of the journey!

A subset called "My Airports" is created automatically for convenience. You can choose to not have it created again if you delete it.

A subset called "Filtered Airports" is created automatically when the "View Scenery List" function is used, and the "Include filtered airport list?" option is accepted. The file is overwritten each time, make copies and name them accordingly before creating the next filtered airport list.

A subset called "Soft Strips Airports" is created and updated when the Scenery Index is created or updated. Can be switched off with; Config.ini: [Indexes], AddSoftAirports=False.

A subset called "Water Strips Airports" is created and updated when the Scenery Index is created or updated. Can be switched off with; Config.ini: [Indexes], AddWaterAirports=False.

A subset called "AIRAC Common Subset" is created and updated when the AIRAC Integrated Scenery Index is created. This reduces the airport list to only those found in both the simulation scenery and the selected AIRAC. (>augmented)

Windows XP: see "C:\Documents and Settings\All Users\Application Data\Ideal Flight 10\Profiles\Airports"
Windows Vista and above: see "C:\ProgramData\Ideal Flight 10\Profiles\Airports"

Import Files

Use the popup menu item "Open File" to import FSX XML .PLN files and FS9 text .PLN files.

Import file types currently supported:

  • FS9 .PLN - FS2004
  • FSX .PLN - FSX .XML

The number of plan file types supported is increased and also FMC files are supported with the ">augmented" upgrade installed;

Additional Import file types currently supported with >augmented upgrade installed:

  • PMDG .rte v1 - J4100
  • PMDG .rte v2/3 - 737
  • PMDG .rt2 v1 - 747
  • QW .RTE v1 - RJ100
  • Level-D .rte v1 - 767
  • iFly .FLTPLAN v1 - 737

Export Files

Choose directory locations for various file types to be exported. (>augmented)

First choose an Export File type from the dropdown list, the top item displays the entire list but items cannot be edited, the required file type must be selected for editing Export File Locations.

Once the export file type is displayed in the box the Export File Locations can be added. Add an Export File Location and choose a directory location to receive the exported file. Note: Later, these export locations can be checked for access rights by running the IF10 Installer and choosing Update to refresh the installation.

To edit the file name, click on the file directory name in the list, then edit the filename in the edit box above the locations list.

The directory name can be unchecked in the list to avoid exporting the file while preserving the location for future use.

Add directory locations for the file type and edit the file name in the window provided. Unchecking the checkbox allows the export for that file to be ignored without losing the setting. Only the enable/disable checkbox setting can be changed when viewing all file types.

Note: Run Ideal Flight Setup to ensure access rights are enabled for creating and writing files in the chosen directories. If files do not get created, re-run IF Setup Installer, this will update the installation to ensure access rights are enabled on the chosen Export directories.

Please also note that wide characters (special character sets) appearing in file and folder names are unsupported for reverse compatibility.

Popular FMC Flight Plan Folder Locations:

  • Aerosoft Airbus X Extended = "C:\Users\UserName\Documents\Aerosoft\AerosoftAirbusExtended\Flightplans" (.flp).
  • PMDG = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\FLIGHTPLANS" (.rte, .rt2)
  • Quality Wings = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\QualityWIngs\FlightPlans" (.RTE).
  • iFly 737 = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\iFly\737NG\navdata\FLTPLAN" (.FLTPLN).
  • Level-D 767 = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Level-D Simulations\navdata\Flightplans" (.rte).
  • Majestic Q400 Dash 8 = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\mjc8q400\nav\routes" (.fpr).
  • Carousel IV-AC INS Waypoints = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Civa\ADEU" (.AWC).
  • Carousel IV-AC INS DME Stations = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Civa\ADEU" (.ADC).

Export file types currently supported (shown along with example aircraft):

  • FS9 .PLN - FS2004
  • FSX .PLN - FSX .XML
  • PMDG .rte v1 - J4100
  • PMDG .rte v2/3 - 737, 777
  • PMDG .rt2 v1 - 747
  • PMDG .WX v1 - 777 weather
  • iFly .FLTPLAN v1 - 737
  • QW .RTE v1 - RJ100
  • Aerosoft Airbus X Extended .flp - AXE
  • Level-D .rte v1 - 767
  • Majestic .fpr vQ400 - Dash 8
  • Carousel IV-AC INS .AWC WP - FSL Concorde-X, Waypoints data cards
  • Carousel IV-AC INS .ADC DME - FSL Concorde-X, DME Station data cards
  • VATSIM prefile - Saves individual VATSIM setup, ID, and Passord, for each IF10 profile.
  • IFB .htm - IF Briefing
  • IFBE .htm - IF Briefing Extra Large
  • FSX .FLT - FSX Save
  • Tower .FLT - FSX Save
  • Arrival Tower .FLT - FSX Save

Note with FSX .PLN - FSX .XML: The flight name (normally "Ideal_Flight") can be used, which will then match the GPS setup when exporting the .FLT file.

File name keywords

ICAOICAO: With the keyword file name: "ICAOICAO", we can instruct IF10 to use the ICAO names of the departure and destination airports to construct the final file name:

With the flight departure LSMP and destination LEAL the file name in the export window:

..\PMDG\FLIGHTPLANS\ICAOICAO.RTE

becomes on disk:

..\PMDG\FLIGHTPLANS\LSMPLEAL.RTE

A number can be included:

..\PMDG\FLIGHTPLANS\ICAOICAO01.RTE

becomes on disk:

..\PMDG\FLIGHTPLANS\LSMPLEAL01.RTE

Notes: Some files must always be saved with a particular name, usually made from the Airport ICAO's (LSMPLEAL), and sometimes with a number (LSMPLEAL01). The PMDG WX file must always be constructed purely with the departure and destination ICAO's (LSMPLEAL.WX), but the PMDG plan files can be named almost anything, something convenient to remember can be used (IF.RTE). Aerosoft AXE files are forced into the ICAO name convention. File names that do not change (IF10.RTE) automatically overwrite the old file each time. File names that change each flight (LSMPLEAL.rte) do not overwrite the last file exported, so the number of files in the folder grows. However, the PMDG and AXE files are tracked by IF10 so that old ICAO named files are deleted when the next flight files are exported. The CIVA Clear export simply clears the instrument to zeros ready for input and calibration. The .Isd file is deleted when exports are made and also just before the flight is started each time. The CIVA CDU must be started by manually entering the first waypoint in POS, then switch to DSRTK/STS and set the MSU to alignment.