there's a really nice util call ScanAFD that finds and displays duplicate AFCADs and allows you to select one to delete or raname... VERY handy. In general, I'd recommend all the PAI afcads over UT ones, as PAI has gate assignments. Beyond that, i'd load 'em up in AFCAD and see which looks more accurate.Best,sg

I just looked at your airport diagram and the 5/23 ILS approaches. It looks like a nice commuter capable airport nested in the hills of Virginia with an interesting obstacle course on the final for 23. I don't know how close you are to DC, but there could be an interesting mix of traffic, heavy at times, during approach and departure. I see that it is on a border of VA and Tennesee. The 25nm relatively high MSA boundaries compared with the about 1500 foot field elevation I imagine can make for some interesting flying.I can certainly understand the desire for traffic here.

UT fit the bill for me and it has plenty of commuter flights with Saab's, ATR's, and RJ's flying all over the place. Candler is ASA's call sign not Comair's.UT models are PAI models but the plans and textures are better IMHO.I have replaced a good bit of the UT aircraft with AI Aardvark's models as they look a bit better. A lot boils down to whether you want a screenshot sim or a flying sim. I tend towards the latter so models and paintjobs dont need to be perfect for me. I just want something half way correct populating the airports. Plus its fun to watch what silly stuff the stupid AI does every now and then! :)Hornit

I promised to report back after settling on a possible freeware solution, so here it is.I installed about 10 or 12 PAI packages for US airlines and commuters, and set AI at 100%. I was surprised how easy this was, and pleased with the real-world traffic that resulted. I didn't remove the default commercial traffic, but will eventually. I was disappointed that the PAI packages did not seem to install many AFCADs with the package (perhaps I'm mistaken), as even with AI traffic at 100%, KATL has maybe four empty gates per parked jet. I know PAI has AFCAD collections that are evidently easy to install, but somehow I had thought the AFCADs would install with the packages (I'm not griping...I'm very grateful and impressed with what PAI offers as freeware). Still, for the minimal work involved, a good result.The PAI Delta (deluxe) package did not include Delta's commuter partners, as I had suspected. My proposed solution was to install MRAI's Delta flight plans, as these are automatically compiled from published flight plans, and I thought this would therefore include Delta's commuter flights. Then I would repaint a few commuter aircraft in Delta commuter liveries and assign them to the MRAI commuter flights. But it turns out I was wrong. MRAI's flight plans for Delta are evidently similar to or the same as those of PAI, and include only the Delta-owned flights. So although I did get a Northwest Airlink commuter at my local regional (commuter-only) airport from the PAI package, there seems to be no way to get the Delta Connection flights without doing it all manually.So, since it's been reported that Ultimate Traffic has Candler and Blue Streak at KTRI, it looks like I'll be purchasing UT soon.

I don't think you'll be disappointed dugan. And you're correct, the PAI packages don't install the AFCADS. You'll have to get those from their AFCAD section. If you don't see one for your airport, try searching here. If you can't find an appropriate AFCAD, they are really easy to modify. Just install AFCAD2 by Lee Swordy and open the airport. It's pretty intuitive.Cheers,Todd