How do I create AI traffic flight plans in a flight sim?

To create AI traffic flight plans in a flight simulator, choose a planner or traffic compiler compatible with your sim, define the AI aircraft and airports, build timed route legs, then compile or export the schedule into the format its traffic engine reads. Test one aircraft first before expanding the timetable.

For flight simulators in general, there is no universal AI flight-plan format. FS2004, FSX and Prepar3D commonly use compiled traffic schedules, while Microsoft Flight Simulator, X-Plane, DCS and FlightGear each handle scheduled AI differently.

Which AI traffic flight-plan format should I use?

Use the format required by the simulator's traffic engine or by the specific traffic add-on controlling the aircraft.

On Xbox, and on the PlayStation 5 edition of MSFS 2024, arbitrary local traffic files cannot be installed in the same way as PC packages. Console users must use traffic features and add-ons supported by their platform.

How do I build an AI traffic schedule?

Build a small, continuous aircraft rotation before attempting a full airline timetable.

1. Choose the traffic system. Select a planner or compiler that explicitly supports your simulator and, where relevant, the traffic add-on you use. A tool merely stating that it exports BGL files does not guarantee compatibility with every BGL-based simulator.
2. Prepare the AI aircraft. Install or select a traffic-optimised model and its livery. In FS2004, FSX and many Prepar3D workflows, the aircraft entry must match the variation's exact title= value; a spelling or punctuation difference can prevent it from loading.
3. Verify the airports. Check each ICAO identifier and make sure both airports have suitable runways and parking. An airliner assigned to an airport with only small parking positions may never spawn, even when its schedule is valid.
4. Create the route legs. Enter the origin, destination, flight number or callsign, departure or arrival time, cruise altitude and IFR or VFR rule where the format requires them. The next leg should begin at the airport where the previous leg ended.
5. Use the correct time basis. Traditional AI schedules normally use UTC rather than airport local time. Check the day as well as the hour when a flight crosses midnight, and leave enough turnaround time between arrival and the next departure.
6. Set the repeat period. Choose the daily, weekly or other cycle supported by the traffic engine. Every outbound aircraft should have a workable return or onward leg before that cycle repeats.
7. Compile or export the plan. Save the result in the location expected by the simulator or package system. Read the compiler log: malformed records may be skipped even when an output file is produced.
8. Test one movement. Position at the departure airport several minutes before the scheduled time, raise the relevant traffic setting above the plan's density threshold and confirm that the aircraft parks, taxis and departs correctly.

For the traditional three-file method, our complete FSX aircraft, airport and traffic-BGL workflow shows how those records fit together. Large FSX schedules are easier to organise with our spreadsheet-based AI flight-plan planning tool.

What makes a valid AI aircraft rotation?

A valid rotation keeps one aircraft moving through connected airports without overlapping times or impossible repositioning.

For example, an aircraft can fly from EGLL to EHAM, remain there for a suitable turnaround, and then return to EGLL. If its next leg instead starts at EDDF, some traffic systems will reject the leg, while others may remove and reposition the aircraft rather than operating a continuous rotation.

• Use UTC consistently; do not mix UTC with local airport times.
• Allow for flight duration, taxi time and turnaround.
• Keep each aircraft's legs inside the selected repeat cycle.
• Check whether the planner expects altitude in feet, hundreds of feet or flight levels.
• Assign an aircraft whose range and performance suit the route and airports.
• Avoid giving the same aircraft two flights that overlap.

Why does my compiled AI traffic not appear?

Missing AI traffic is usually caused by an aircraft-reference error, unsuitable parking, incorrect schedule time, a disabled traffic file or a density setting below the plan's threshold.

• No aircraft at the gate: verify the model or livery reference, dependencies, parking radius and gate type.
• Traffic appears on the wrong day: recheck UTC conversion, repeat period and midnight rollover.
• The compiler reports errors: correct every rejected aircraft, airport or leg record rather than assuming the remaining BGL is complete.
• The file has no effect: confirm that its scenery area or package is active and that the simulator has rebuilt or reloaded its traffic data.
• Default traffic disappears in FSX: look for an old-format traffic BGL. Legacy traffic files can conflict with newer-format FSX traffic and may need recompiling or removal.
• Duplicate aircraft appear: search for another active package or BGL containing the same schedule.

When a plan compiles but remains invisible, work through our AI traffic visibility and troubleshooting checks before rebuilding the timetable.

Can I create plans from real-world airline schedules?

Yes, but a published timetable must be converted into the simulator's format and checked for UTC times, seasonal changes, aircraft availability and complete rotations.

A timetable alone does not supply compatible AI models, liveries, airport parking or real-time position data. If the aim is moving live or near-live traffic rather than a fixed handcrafted schedule, the workflow is different; our guide to MSFS real-world traffic sources and injectors explains that distinction.