Fix AIG Traffic Controller crashes in MSFS by checking packages, SimConnect, traffic conflicts, density, security settings and damaged configuration.
AIG Traffic Controller usually crashes in Microsoft Flight Simulator because its components or AI packages are mismatched, a model or livery is damaged, SimConnect loses the session, another traffic injector is active, or the traffic load is too high. Update AIG, verify its packages, use one injector, reset its configuration and test at low density.
This troubleshooting applies to Windows PC installations of MSFS 2020 and MSFS 2024. AIG Traffic Controller, often shortened to AIGTC, is an external Windows application and cannot be installed on Xbox or PlayStation consoles.
Is AIG Traffic Controller crashing, or is MSFS crashing?
The process that closes first determines where to concentrate your troubleshooting. Check Windows Reliability Monitor or the Application section of Event Viewer immediately after the crash, then note the faulting application and module.
| Symptom | Likely area | First test |
|---|---|---|
| AIGTC closes before connecting | Damaged configuration, blocked file or missing Windows runtime | Reset its configuration and check the Windows crash report |
| AIGTC closes when injection starts | Broken AI package, excessive traffic or incompatible AIG components | Verify packages and inject at minimum density |
| MSFS closes but AIGTC remains open | AI model, simulator add-on, memory pressure or simulator instability | Run MSFS without injection, then test a small traffic load |
| Both programmes freeze or disconnect | SimConnect overload or competing traffic tools | Use one injector and reduce the injection radius |
If this is a new installation, compare it with our MSFS 2020 AIG connection and injection checks or the separate MSFS 2024 package-path and traffic-source checks. A wrong path can resemble a crash when the controller is actually failing during package discovery or connection.
How do I fix crashes during traffic injection?
The quickest method is to establish a clean, low-traffic baseline and add complexity one item at a time.
- Test MSFS without AIGTC. Load a flight using a default aircraft and an unmodified airport. If Microsoft Flight Simulator crashes before AIGTC is opened, the controller is not the immediate cause.
- Start the controller after the flight has loaded. First confirm that AIGTC can connect and remain open without injecting aircraft. Begin injection only after the simulator is settled at the airport.
- Update the AIG components together. Close MSFS and use AIG's own manager or updater to check Traffic Controller, AI Manager, flight plans and aircraft packages. Mixing an older controller with changed package data is a common source of failures.
- Run one traffic injector. Close FSLTL's injector and any other external traffic programme. For diagnosis, disable MSFS real-time and offline AI traffic as well. If FSHud is involved, configure it so that only the intended programme performs the injection rather than allowing two tools to create aircraft.
- Verify the AI aircraft library. Use AI Manager's available verification or update functions and repair flagged aircraft, liveries and flight plans. Our AIG aircraft and traffic package workflow explains how those dependencies fit together. Do not delete the entire library because one package is damaged.
- Reduce the traffic load. Lower the injection radius, airborne traffic limit, ground traffic and parked-aircraft density. The precise labels can vary between AIGTC builds, but the aim is the same: prove that a small injection works before raising one limit at a time.
- Reset AIGTC's configuration. Back up any settings you need, use a built-in reset option if provided, or rename the controller's local configuration folder so it can create a clean one. Re-enter the simulator and package paths afterwards; do not remove the AI aircraft library itself.
- Check permissions and security software. Run MSFS and AIGTC under the same Windows account and privilege level, normally without administrator elevation. Restore any quarantined AIG file only after confirming it belongs to your trusted installation, and create narrowly targeted permissions rather than disabling antivirus protection.
- Isolate unrelated add-ons. Temporarily move non-AIG packages out of the Community folder and repeat the same flight. If MSFS still crashes with AIGTC closed and no injected traffic, follow our systematic MSFS crash-isolation procedure instead.
Why does AIGTC crash at one airport or after several minutes?
A repeatable location or delay usually separates a damaged package from simple traffic overload.
- The crash occurs as soon as aircraft appear: suspect an AI model, livery, flight plan or package-path problem.
- The same airline or airport triggers it: verify packages associated with that carrier or location, especially anything installed or updated immediately before the problem began.
- It fails gradually at a large hub: reduce the injection radius and ground traffic. Increasing aircraft counts also increases model loading, SimConnect activity and simulator memory use.
- It fails at unrelated locations with injection disabled: investigate AIGTC's configuration, Windows runtime or security logs rather than the aircraft library.
- MSFS crashes with AIGTC closed: treat it as a simulator, driver, hardware or other add-on problem until testing proves otherwise.
Repeat each test at the same airport, time and traffic settings. Changing the location and several settings together makes a bad package look like a random crash.
Should I reinstall AIG Traffic Controller?
A full reinstall should be the last step, because it will not fix duplicate injectors, excessive traffic or a separate MSFS crash. Reset the controller configuration first, then verify its programme files and repair only the package associated with a repeatable injection failure.
Reinstall the controller itself if its updater cannot repair missing files or Windows reports a damaged controller component. Rebuild the complete AI library only when package verification reports widespread corruption; preserve a record of your package location and settings before removing anything.