BATC does an amazing job at handling the AI traffic. It just depends on the airport. As an example, at KATL there were lots of parked AIG models, plus taxiing airliners, taking off, and calling for landing. That's when it truly shines for me.

Just made a flight this morning hearing ATC call "Spirit Airlines" and thought to myself, "wow it would be great if BATC could take advantage of the Navigraph live data" LOL!

42 minutes ago, CFIJose said:

BATC does an amazing job at handling the AI traffic. It just depends on the airport. As an example, at KATL there were lots of parked AIG models, plus taxiing airliners, taking off, and calling for landing. That's when it truly shines for me.

Are you using the Experimental version?

21 minutes ago, RNAVV19R said:

Are you using the Experimental version?

No.

On 5/27/2026 at 8:23 AM, FPVSteve said:

I've seen BATC using different departure and arrival runways plenty of times. It lacks on ground handling though, more often than not you get cleared to taxi into AI traffic (or them through you).

I've found this to be the case which seems strange at best. In fact, it's as bad and sometimes worse than is FSLTL!

3 hours ago, Noel said:

I've found this to be the case which seems strange at best. In fact, it's as bad and sometimes worse than is FSLTL!

This "more often than not you get cleared to taxi into AI traffic (or them through you)." is a big problem, perhaps the biggest. It is the single most important reason I will not use native MSFS 2024 AI. FSLTL has the same problem but this risk is mitigated with the in-cockpit menu to reset traffic during critical times on the ground. I highlighted BATC's AI traffic management shortcomings in the survey they are running currently (subscribers only). With the upcoming integration of FR24 traffic into BATC, it sounds like this is a focus area for them. I hope I am right.

7 hours ago, zachlog said:

With the upcoming integration of FR24 traffic into BATC, it sounds like this is a focus area for them. I hope I am right.

I think you misunderstand what this will do. It will not, like default live traffic, actually take positional data from FR24. It will take live schedule data and then use that to populate its own injection. So in terms of who taxis on which taxiway, nothing will change.

Edited May 29May 29 by Farlis

I want to thank BATC for really committing to improving their product and giving us the best possible Air Traffic experience. I’ve used the program for about a month now and I’ve been nothing but impressed. BATC keeps making smart decisions and I think this program has a really strong future. I’m excited about this new feature and Keep up the great work!

3 hours ago, jspilot said:

I’ve been nothing but impressed.

I generally agree except for one major problem and I don't see any work around but hopefully that is not the case. Strangely to me, I'm not sure why others aren't as bothered by this as I am, but here it is: w/ BATC injection its traffic animation often is, for lack of a better phrase, herky jerky, and I understand the explanation for this versus FSLTL which delivers ultra smooth animation. The other factor for me is that I do use Premium voices in BATC, but only for the controller. If you use BATC traffic injection BATC will use the Premium voices for ALL controllers communicating w/ all traffic, so characters get used up much more quickly than if I use FSLTL's injector in which case BATC will then only use Premium characters for the one controller communicating with me. So typically I end up using FSLTL and Premium characters and despite the lack of actually control of all traffic, the experience ends up generally being better. Sometimes I use BATC's injection at small terminals where the animation quality is likely to be better, and when I do this I use Basic voices.

Edited May 29May 29 by Noel

6 hours ago, Farlis said:

I think you misunderstand what this will do. It will not, like default live traffic, actually take positional data from FR24. It will take live schedule data and then use that to populate its own injection. So in terms of who taxis on which taxiway, nothing will change.

I understand that there is no positional data coming from FR24 and frankly AI aircraft positional accuracy does not interest me. What I am interested in is BATC coordinating the positions of my A/C and AI aircraft so that there are no "collisions"/positional conflicts. This is where native MSFS 2024 AI traffic fails miserably and FSLTL mitigates the risk of such occurrences with its in-cockpit RESET TRAFFIC capability.

Is my expectation of BATC unrealistic ? Will the product not manage positional coordination ?

11 minutes ago, zachlog said:

Is my expectation of BATC unrealistic ? Will the product not manage positional coordination ?

Strange but true: BATC's ground traffic management is AS BAD and sometimes worse than in FSLTL's 'blind' operation. Frequently when I use BATC traffic I'll have other planes head right towards me in a Mexican Standoff or other variants of ground traffic conflict.

Just so I'm clear... if currently I have FSLTL + Navigraph Unlimited + BATC then I should turn off AI traffic in MSFS 2024, turn on AI traffic in BATC, not use the FSLTL / Flightradar24 injector as BATC handles traffic injection and use FSLTL just for the model matching only?

10 minutes ago, Tektolnes said:

Just so I'm clear... if currently I have FSLTL + Navigraph Unlimited + BATC then I should turn off AI traffic in MSFS 2024, turn on AI traffic in BATC, not use the FSLTL / Flightradar24 injector as BATC handles traffic injection and use FSLTL just for the model matching only?

Yes

On 5/28/2026 at 2:02 AM, SierraHotel BSc said:

BATC's AI Aircraft are controlled by a separate specially written program that runs parallel to but outside of MSFS, using any available AI aircraft models such as FSLTL, AIG, MSFS Default etc. This alleviates any FPS drop in MSFS

Is there much hope for a better program that can actually delivery ultra-smooth animation, like FSLTL's animation. And, I appreciate why FSLTL's is far superior. Right now, besides other issues w/ BATC well known that is a major issue for me. I only have traffic amount set to 3, except for parked at 8, and yet even w/ that modest amount of live moving traffic way too often animation is herky jerky, un-smooth, and is one of two reasons I end up using FSLTL for injection, and BATC only for ATC communication to yours truly. Thanks in advance

21 hours ago, G-YMML1 said:

So far PSXT is the only option for 100% IRL traffic, but it has its own limitations (not a part of overall ATC)

I'm using PSXT with a Real Traffic subscription of course, and find the 100% accuracy far outweighs (for me) not being part of the overall ATC especially given the latter's limitations/foibles. I get ATC clearance and flight following etc, but it doesn't 'see' PSXT's injected aircraft so I use LNM to see other aircraft movements and slot my plane in accordingly. I use an ATC chatter programme (can't remember its name) to keep radio comms 'alive'. It's great as well for a bit of plane spotting, seeing it replicate what is shown on FR24 , since it uses ADS-B data.

Not seen it mentioned so far, but I'm also very impressed with performance using PSXT, even though it injects alot of commercial and GA planes, both static and in the air (set at 60nm radius in my case). I have AIG, FSLTL and Ivao MTL model libraries which giving over 16000 liveries to draw on. Performance is better than when I used the FSLTL injector or BATC. For info my pc is AMD9800 X3D with RX7900XTX graphics card, 3440x1440 display.