Prepar3D 6 min read

How do I add AI traffic in Prepar3D?

Adam McEnroe
In short

Learn how to add AI traffic in Prepar3D using aircraft, traffic BGL files or an injector, plus fixes for missing, duplicate and low-FPS traffic.

To add AI traffic in Prepar3D, install both the AI aircraft and their compiled traffic BGL, place them in folders Prepar3D recognises, then raise the airline or general-aviation traffic sliders above zero. A complete traffic package handles both parts; a traffic injector supplies schedules dynamically while it is running.

Which Prepar3D AI traffic method should I use?

Use a complete offline package for the easiest installation, manual traffic BGLs for precise control, or an injector for traffic generated while the simulator is running.

MethodBest forMain limitation
Complete traffic packageInstalling aircraft, liveries and schedules togetherOlder installers may target FSX or an earlier P3D version
AI aircraft plus traffic BGLCustom airlines, airports and timetablesAircraft titles and flight plans must match exactly
Traffic injectorDynamic or changing schedulesThe injector must be running and connected to Prepar3D

Our collection of pre-built airline, cargo, general-aviation and military traffic packages provides both models and flight plans. Check the package description against your Prepar3D generation: compatibility with FSX or one P3D release does not guarantee compatibility with every later release.

How do I install a traditional AI traffic package?

Install the aircraft folders and the traffic BGL separately unless the package supplies a Prepar3D-aware installer or registered add-on package.

  1. Close Prepar3D and inspect the download. Identify the AI aircraft folders, texture folders and files ending in .bgl. Read any included instructions before copying files.
  2. Back up anything that will be replaced. Do not overwrite an existing aircraft configuration or traffic file without preserving the original.
  3. Install the AI aircraft. The traditional location is <Prepar3D>\SimObjects\Airplanes\. Each complete aircraft folder normally contains an aircraft.cfg, model files and one or more texture folders. If the package supplies a registered Prepar3D add-on structure, use that instead of copying files into the simulator's core directory.
  4. Install the traffic BGL. The conventional location is <Prepar3D>\Scenery\World\scenery\. A BGL may instead be placed in the scenery subfolder of a custom scenery area, but that area must be active. Our AI aircraft and flight-plan installation walkthrough illustrates how these components fit together.
  5. Check aircraft-title matching. A compiled schedule references an exact title= entry from an aircraft's [fltsim.x] section. A missing livery, changed title or incomplete aircraft folder leaves that flight without a usable model.
  6. Enable traffic in Prepar3D. Open the traffic settings and move Airline traffic density or General aviation traffic density above zero. Start at a moderate level; setting both to maximum can overload large airports and reduce frame rate.
  7. Restart and test at the right place and time. Use an airport served by the package and a scheduled day and time. Traffic BGLs contain timetables, so an empty airport does not necessarily indicate a failed installation.

If you want to build schedules rather than install them, our explanation of aircraft titles, airport codes and compiled traffic BGLs covers the core flight-plan logic inherited by Prepar3D.

Why is AI traffic not showing in Prepar3D?

Missing AI traffic nearly always comes down to an inactive schedule, an unresolved aircraft title, incompatible content or a traffic slider that is too low.

  • Traffic density is zero or below the plan's activity level: compiled flight plans carry percentage values, and lower simulator settings filter some of them out. Temporarily increase the appropriate slider while testing.
  • The BGL is not active: confirm that it is under Scenery\World\scenery or another enabled scenery area. A traffic BGL placed inside SimObjects will not work.
  • The aircraft is missing: verify that the expected title= exists and that the aircraft folder is in a recognised SimObjects path.
  • The model is incompatible: an old FSX or legacy Prepar3D model may install correctly but fail to render in another P3D generation. Test with a package that explicitly supports your version.
  • A legacy BGL is conflicting: in some FSX-derived traffic setups, one old-format traffic file can prevent newer-format plans from appearing. Remove the newly added BGL temporarily and retest before changing anything else.
  • The injector is not connected: confirm that its application is running, connected to Prepar3D and configured for the installed simulator version.
  • The aircraft is present but invisible or untextured: this points to a missing texture, incorrect texture reference or incompatible model rather than a schedule problem.

Change one component at a time. Removing every AI file at once makes it much harder to identify the bad aircraft, schedule or legacy BGL.

Why are AI aircraft parked but not moving?

An aircraft at a gate may be static scenery rather than scheduled AI, or its departure may simply be outside the time being simulated.

Static aircraft supplied with airport scenery never taxi or depart. Genuine AI may also remain stuck when the airport lacks a usable taxi route, the assigned parking space cannot connect to a runway, or heavy traffic has created a departure queue. Test the same schedule at a simple default airport to separate an airport-layout problem from a traffic-package problem.

How do I prevent duplicate AI traffic and low frame rates?

Use one main schedule source for each type of traffic and use models designed specifically for AI operation.

  • Do not run an offline airline schedule, a second package covering the same routes and an injector together unless their documentation explains how duplicates are suppressed.
  • Disable duplicate schedule BGLs rather than deleting shared AI aircraft, because another package may still reference those models.
  • Avoid using detailed flyable aircraft as AI. Their virtual cockpits, effects and high-detail models consume far more resources than purpose-built AI models.
  • Reduce airline density first at major hubs and general-aviation density around busy regional airports. The two sliders control different traffic pools.
  • If an injector requires the built-in traffic sliders to be disabled, follow that requirement; otherwise stock and injected flights may occupy the same routes and gates.

A mistake we see constantly is installing several schedule collections to make airports busier, then trying to solve the resulting congestion with higher traffic settings. One clean schedule set, correct aircraft titles and AI-optimised models produce a more reliable result than overlapping packages.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members