• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

PV5 Airport List


Resource contributor
I have just discovered that PV5 has modified to some extent the majority of all 25000 airports and has added sixty new ones. While minor changes in position/elevation of the airports will have no affect on the operation of AIFP, large changes in position such that an airport in PV5 lies in a different sector from FSX/PV4 will. As well, at the moment, AIFP cannot access the new airports or those with changed IOAO codes.

It's not immediately obvious how AIFP should address the issue. The simplest way is to generate a separate airport list for PV5 (already done) and for the user to select which airport list he /she wants to use for any given flightplan. (If you only program for PV5 or, on the other hand, the earlier versions, the selection of airport list could be made semi-permanent.) Another approach would be to compare the two lists, extract the "problem" airports and alert the user when one of the problem airports is involved. While the latter seems preferable to the former, its a lot more work to implement and it will mean the user gets interrupted more frequently.

Your thoughts on the matter will be appreciated.
Last edited:


Resource contributor
Further to my earlier post, I have now had a chance to programmatically analyse the changes to PV5 airports. The numbers are shocking:
  • 1914 have name changes (i.e., Country/Region/City/Airport name)
  • 11018 have position changes, 193 of which were sufficient to change the AI sector in which they reside
  • 2068 introduce new ICAO codes
  • 2009 ICAOs have been deleted
This indicates there is a very good chance current FS9/FSX flight plan/traffic files will not work as expected when used in PV5.

More concerning for me (and I suspect some of you) is that even if you own PV5, AIFP will not recognize the new airports in PV5 and, where airport positions have changes sufficient to also change sector, AIFP will send AI to the wrong place.

I will attempt to address these issues. But, it will require major changes for AIFP to continue to provide the same seamless operation between FlightSim versions - and this will take a while.

In the meantime, if you are using PV5 and need to use one of the airports for which the ICAO has changed, defining the new ICAO as an alternate airport for the old should work. Unfortunately, I'm not aware of a workaround for any of the other situations.
Last edited: