Create AI traffic flight plans in FS2004 with Traffic Tools, correct aircraft titles, UTC schedules and fixes for traffic that does not appear.
To create AI traffic flight plans in FS2004, use Traffic Tools v2.02 to define the aircraft, airports and timed route legs in three linked text databases, then compile them into a traffic BGL. Aircraft titles must match aircraft.cfg exactly, schedules must form a valid cycle, and FS2004's AI traffic slider must meet the plan's percentage.
Which FS2004 AI flight-plan tool should I use?
Traffic Tools v2.02 is the best choice when you want complete control over aircraft, timings, routes, flight numbers and traffic density. Our Traffic Tools v2.02 download for FS2004 includes the compiler and format documentation needed to build the text databases.
| Method | Choose it when | Trade-off |
|---|---|---|
| Traffic Tools | You need multi-leg, daily or weekly schedules with precise timings | The text format is strict and small errors can stop compilation |
| Simple AI | You only need straightforward departure-and-return traffic | It offers less control over complex rotations |
For quick out-and-back routes, Simple AI can generate the schedule automatically from installed aircraft and known airports.
How do I build a Traffic Tools flight plan?
The reliable method is to create separate aircraft, airport and flight-plan source files, validate their references, and compile them into one custom traffic BGL.
- Make a working folder and backups. Do not edit or overwrite FS2004's stock traffic BGL. Use the examples supplied with Traffic Tools, or decompile a copy of an existing traffic file to obtain correctly formatted source records.
- Define each AI aircraft. The aircraft source file links an
AC#identifier to a cruise speed and an installed aircraft title. Copy the value aftertitle=from the aircraft's[fltsim.x]section exactly, including spaces and punctuation. - Provide the airport records. Every airport used by the schedule must have the correct ICAO code and position in the airport source file. Stock airport records can normally be retained from a known-good database.
- Create one rotation per physical aircraft. A flight-plan line represents one AI airframe, not an unlimited pool of aircraft. Give it a registration, traffic percentage, repetition period, flight rules and a sequence of timed legs.
- Enter times in UTC. Account for day changes when a flight crosses midnight. Leave enough time on the ground between arrival and the next departure; overlapping legs or implausibly short turnarounds commonly break a rotation.
- Close the schedule cycle. The final leg should return the aircraft to the location required for the beginning of its next daily or weekly cycle. Traffic Tools will flag many incomplete or overlapping schedules during compilation.
- Compile and install the BGL. Correct every compiler error, give the custom traffic file a recognisable name, and place it in an active scenery folder—normally
FS2004\Scenery\World\scenery. Restart FS2004 after changing traffic files. - Test at full density. Set the AI traffic slider to 100%, select the correct UTC day and time, and load the departure airport well before the scheduled pushback. Reduce the slider after confirming that the plan works.
What do the main flight-plan fields control?
Each Traffic Tools schedule combines one aircraft reference with operating rules and a repeating series of route legs.
| Field | What it controls | Common mistake |
|---|---|---|
| Aircraft reference | The AC# entry used for the entire rotation | Referencing an aircraft number absent from the aircraft database |
| Traffic percentage | The minimum FS2004 traffic-slider setting at which the plan can appear | Testing a 50% plan with the simulator slider below 50% |
| Repeat period | How often the schedule repeats, usually daily or weekly | Failing to return the aircraft before the next cycle starts |
| Flight rules | Whether the rotation operates as IFR or VFR traffic | Using inconsistent rules for the intended operation |
| Departure and arrival | The UTC operating times for each leg | Entering local time or mishandling midnight |
| Cruise altitude | The planned altitude in hundreds of feet | Entering 35000 instead of 350 for 35,000 feet |
| Destination | The ICAO airport used for that leg | A misspelt code or airport missing from the airport database |
Why does my custom AI traffic not appear?
Missing FS2004 AI traffic is usually caused by an aircraft-title mismatch, the wrong UTC time, insufficient parking, a density threshold or a BGL installed in the wrong folder.
- Check
title=, not the menu name. The title in the aircraft database must match the installedaircraft.cfgentry character for character. - Confirm the schedule's percentage. A plan assigned 70% will not appear with the simulator's AI slider set to 69% or lower.
- Check UTC day and time. Local-time testing can put you several hours away from the scheduled departure.
- Inspect parking capacity. The airport needs a free parking position large enough for the aircraft. Busy default traffic can occupy every suitable stand.
- Verify the complete rotation. Look for overlapping legs, reversed arrival times and an aircraft stranded away from its next starting airport.
- Restart FS2004. Traffic BGL changes are not reliably picked up while a flight is already running.
If compilation succeeds but nothing appears, follow our FS2004 AI traffic inspection and troubleshooting checks to separate schedule faults from parking, aircraft and scenery problems.
Can AI flight plans use add-on airports?
Yes, custom AI schedules can use an add-on airport when its ICAO code is recognised and the active airport layout provides suitable runways, taxi links and parking.
If an add-on changes an airport's code, elevation or position, update the airport record used by Traffic Tools rather than copying an obsolete default entry. Our guide to using add-on airports in FS2004 flight plans covers replacement AFCAD layouts, duplicate airports and parking-related failures.
Will custom flight plans replace the default traffic?
Custom traffic BGLs normally run alongside FS2004's default schedules rather than replacing them. This can create duplicate airline services or fill the parking required by your new aircraft, so temporarily reduce or disable the stock traffic file when testing a replacement schedule.