October 14, 20223 yr I have been using P2A for about three months. Great product! One thing I've noticed, though, is the ATC -- especially ARTCC center -- boundaries aren't very accurate. For example, I flew from KGPI (Glacier Park International, Kalispell, Montana, USA) to CYKA (Kamloops, British Columbia, Canada) via this route: KILLY1 RIDDG TWIGY J599 CFRBZ SILVR TENYA WTMAN OVENA and then the ILS09 approach to CYKA. At KGPI center is Salt Lake City. P2A did that right. Then we cross into Seattle center, but well short of TWIGY intersection (essentially the Canadian border), and not at the Salt Lake/Seattle ARTCC boundary, P2A switched me to Edmunton Center. Then it switched me a couple miles later to Vancouver Center, but still well short of TWIGY. I don't think we should be talking to Canadian ATC while still well within the USA. There are many other times when P2A assigns an incorrect center frequency and I wonder if this can be addressed?
October 14, 20223 yr Commercial Member You can see the Center Boundaries, Frequencies and Names in TaxiMnt. You can edit the names and frequencies. The updated AIRAC data does not have Center boundaries, so this is not something that is kept up to date automatically. fsAero used to offer updates, but even they seem to have stopped doing this. Dave
October 16, 20223 yr Author Dave, MSFS 2020 has all this in their database and if you use MSFS ATC (a problem in and of itself, and the reason we like P2A) the frequency switching is spot-on accurate. I do not believe there is any way a user like me should have to maintain ARTCC boundaries or ATC frequencies or any of that. I can't imagine suggesting users do this. Sorry, but in all honesty, I am quite disappointed by your answer. Paul
October 16, 20223 yr Commercial Member Until recently, the fsAero tool did just that. There is no replacement for that tool that I am aware of. I have it on a list of possible future enhancements to create such a tool, but it is not a trivial task. However, in looking at the specific flight plan example you gave, the boundaries seem to be correct. So, I will try and figure out why the controllers are being assigned the way you describe. Dave
October 17, 20223 yr Commercial Member I did find a bug that was causing the boundary detection to be off. It is now fixed in 2.6.3.2 Public Beta 8F. Dave
October 18, 20223 yr Good news indeed. Thanks Dave. This has been bugging me too for quite a whiile. And hats off to Paul for raising the issue. Edited October 18, 20223 yr by ang58 Added comment
November 11, 20223 yr Author Thanks, Dave. I appreciate the follow-up! Edited November 11, 20223 yr by ATP CFII MEI TMI
Archived
This topic is now archived and is closed to further replies.