- errors
- setup
- user aircraft
- sceneries
- visual
- performance
- debug
- traffic
- operations
- editor
- obj placer
- message.txt

Traffic is the term given to computer controlled aircraft in flight simulations. It is also known as AI (artificially intelligent) traffic and is made up of a number of components.

  • Airports
  • Aircraft
  • Flight plans
  • Random movements
  • Limitations

    Use the FSImp traffic dialog to access parameters when X-Plane is running


  • Special AFCAD format files describe the facilities at airports.
  • For an airport called icao, its AFCAD files is named AF2_icao.BGL (eg AF2_KJFK.BGL for KJFK, John F. Kennedy International, New York.).
  • Sometimes such files are part of an installed scenery.
  • You can also just drop them into the FSImp\traffic\AFCAD folder.

  • Use the traffic dialog Airport tab to select the active arrival and departure runways(s) for each airport.
  • You can also select what types of traffic are appropriate at each airport.
  • Changes that you make are saved automatically in a file.
  • This file is used by FSImp each time that X-Plane is started.


  • FSImp looks at the aircraft sub-folder of the FS root folder for any installed FS aircraft.
  • This sub-folder contains more sub-folders, one for each installed aircraft.
  • Each of these folders contains a configuration file (aircraft.cfg) and a flight model (.air), a 3D visual model folder and one or more sets of texture folders (paints).
  • FSImp ignores the flight model, cockpits, guages and sounds.

  • Use the traffic dialog Aircraft tab to say for each aircraft whether it can be used for planned traffic, random traffic and whether this aircraft is unique in which case it is not duplicated.

    Flight plans

  • These are usually in special format binary files called traffic*.bgl.
  • You can use a traffic dialog Paras tab button to browse for such a file.
  • FSImp also interprets any such files that you have dropped into the FSImp\Traffic\files folder or its subfolders.

  • FSImp can also parse additional text traffic files as it has a built in traffic compiler.
  • The compiler accepts text files which describe aircraft, airport positions and/or flight plans.
  • These are often available for download and can simply be dropped into a new subfolder of the FSImp\Traffic\files folder.
  • Instructions in such downloads about splitting into separate files and using traffic tools to compile them can usually be ignored.
  • FSImp extracts the individual airport, aircraft and flight plan components of these text files automatically
  • It re-generates a binary traffic file called compiled by fsimp.bgl in each subfolder if any of its text files change

    Random movements

  • As well as planned traffic, FSImp allows traffic to be randomly generated at the nearest airport.
  • In the traffic dialog Paras tab you can specifiy how often random arrivals are generated and how long they wait on arrival before turning around.
  • A button allows you to generate a number of random departures.


  • These are usually in special text files called icao.txt.
  • FSImp uses the SID and STAR definitions in these files when controlling traffic to and from terminal area.
  • The format that is currently supported is that used by Precision Manuals Development Group (PMDG .
  • These are usually generated to synchronise with the real world AIRAC-cycles.
  • They are available for free from number of websites, most notably from Richard Stefan's

  • Just drop such files into the FSImp\Traffic\sidstar folder.
  • If FSImp does not find a file for an airport it generates psuedo SID and STAR procedures to and from nearby navaids and/or waypoints.

    Current implementation limitations

  • All approaches are straight-in
  • Visible models have one fixed animation view (gear down, flaps 20 etc)
  • Speeds are not given by ATC
  • Collision avoidance only during taxi
  • Separation only on approach using a stack and on runway line-up

    FSImp plugin for X-Plane