Web planner missing airports present in sim

ISSUE DESCRIPTION

Description of the issue:

Several airports are missing from web planner, which renders VFR planning impossible. These airports are shown in the EFB however.

If applicable, which aircraft is experiencing this issue:

Not applicable for aircraft

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

Community empty and no add-ons.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

Everytime

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Open planner.flightsimulator.com
  2. Look for SATZ airports, should find none (screenshot below)
  3. Open the EFB or map in MSFS 2024 and look for SATZ, should find it near Tornquist in Buenos Aires, Argentina.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

Not relevant, but no mods nor add-ons

What peripherals are you using, if relevant:

Not relevant

[PC Only] Are you using Developer Mode or have you made any changes to it?

No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

Not applicable, it’s a MSFS 2024 and web planner issue

[PC Only] What GPU (Graphics Card) do you use?

No relevant

[PC Only] What other relevant PC specs can you share?

Not relevant

MEDIA

Please add a screenshot or video of the issue occurring.

SATZ results in planner.flightsimulator.com

[END OF FIRST USER REPORT]

SATZ in Map

SATZ in EFB


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Flying in Career Mode I have noticed airports being wrongly labeled. For example a small airfield in Kenya who’s IATA code is (HKKU) in the Sim it’s showing as HK47. On the web planner it’s also correctly labeled with it’s IATA code. But not in the game itself. Needless to say I’ve noticed this around the globe.

1 Like

SATZ isn’t an assigned code which is why it’s not showing in the planner.

Same deal with Navigraph…

I was disappointed to see that Navigraph a paying app none the less, that is collaborating with Jeppesen is missing lots of small airfields.

Looks like it has a local code of AR-0355.

I have encountered this same problem flying in South Africa.

FADQ/PZL is missing from the web planner but is present in the sim.

1 Like

Nah but that’s not the issue described. There are a lot of small strips that aren’t present in navigraph, as @SXAVC pointed out, but those strips do exist in the sim. The one I mentioned is an example but there are a lot, particularly affecting small airstrips used for VFR flights.

The issue is why planner doesn’t show at least the same info as the EFB. This makes planning both IFR and VFR difficult and cumbersome since the only two interfaces for flight planning -EFB and planner- don’t show the same.

1 Like

The planner has up-to-date and accurate data as does the Navigraph charts app. The EFB is pulling whatever is on the world map which has airports that don’t exist and thus given fictional codes, airports with wrong codes, and airports that are closed.

Rialto Municipal for example was closed in 2014. You can find it on the world map and EFB but not the planner. You will also not find it on the Navigraph charts app.





No, please double check. I’m sure you’ll find examples as the ones you mention, but others are exactly as I mentioned.

There’s an official list of Argentina airports with ICAO code (here) and several are completely missing in planner (SAVA, SAVR, SATI, SAWS, SADZ, to name a few).

All of them exist. Heres SADZ in Wikipedia for an example. It’s also in Volanta, so I’d assume it’s in Navigraph:

However it doesn’t show up in Planner.

Heck even the Trevelin airport, which recently had an X-STOL fly-in with Trent Palmer and others widely known bush pilots isn’t in Planner! And of course, it’s in Volanta:

So no, the planner doesn’t have accurate data (I wish it had of course)

I also cannot use the offline planner 90% of the time due to GROSS level of mismatches between the sim/EFB and the planner (granted I’ve mostly been flying around south Africa, Indonesia, and central Europe. I don’t even care if it matches the real world (although that would be nice sometimes) so much as the offline planner and the game itself should at least closely match in what they have.

The web planner and the game are using different datasets. IMO the planner is using basically the standard LIDO dataset while the game’s data is a mixture of multiple sources. That explains why there is inconsistency.

Only in regards to airports and airport layouts. In the sim, airports are graphical scenery items and not navdata items. Changes and updates to airports are not handled by navdata but instead by the scenery teams (and in the future, WoldHub users), as worldwide AIRAC doesn’t really have enough data in it to actually build out airports (the ARINC spec only has airport codes and runways, not anything else about the airports such as taxiways, parking, facilities, etc).

The online planner uses the complete worldwide LIDO dataset, and all airports contained within. The sim, because it has access to the actual airport scenery packages themselves, may have additional airports not found in the worldwide AIRAC. The remainder of the entirety of the navdata (i.e. everything nav related other than airport scenery) in the sim is the full LIDO dataset.

So far, any airports not found in the LIDO dataset have been non-ICAO airports. We will have to investigate the provided examples to see if we expect them in the LIDO dataset or not.

1 Like

If it helps, I can check all the Argentina airports that have an ICAO code (they’re in the link above), and check which of them aren’t in the LIDO dataset (searching for them in planner, I don’t have access to the lido dataset in any format). Let me know.

I would guess it’s because while some may have an ICAO code, perhaps not all are commercial airports. But that’s an hypothesis.

In our investigations, any airports missing were also not in the aerodrome’s (FAA, EuroControl, AirCanada, etc) AIP either. The LIDO data sources from national/aerodrome data so it would surprise me if official AIP airports were missing (commercial or non-commercial is not a factor), but if that is the case, then we can certainly talk to them about it.

Databases ingame and MSFS FP are not synced, I suspect that the simulator creates airports based on other factors besides the ones currently known. A good example is Isola-2000/ FR-0284, it doesnt exist in real life and its absolutely not suitable to land on… its more of a parking lot/ski track.

So while MSFS FP is not up to date on a lot of airports that are real (mostly small, glider etc) the problem is also that the simulator has to much freedom in identifying them. On top of that, even if they both exists the RWY numbers are often off by 10 degrees, RWY 05 in EFB can be 06 in MSFS FP… maybe on is using True and the other Magnetic?

I would very much like it if the MS products at least have the same options available to make flight planning a bit easier and not switch between too many 3rd party options.
Screenshot is showing Isola2000 in Volanta, I guess Volanta just draws from multiple databases.
(Latest beta)

I can deal with the differences, as long as it’s correctly documented.

If the case is that only airports with ICAO code in the AIP of each country are in the web planner, and the world map adds all airports not in the AIP -I’m not considering errors here like non existant airports, let’s assume all of them exist but are smaller bushtrip air strips, gliders and other facilities-, it’s fine, but should be documented given it makes the web planner nearly useless for VFR and bushtrip planning -it simply lacks the strips. Hence we can use each tool appropriately.

A different issue is the thing about airports with ICAO code not present in the I’ve found some airports which do have an ICAO code but aren’t in the web planner, which I referenced above. However I did also find that my country has different official info on airports, since in the link in my previous post the airport SADZ has ICAO code but another official source removes the ICAO code and just maintains the IATA code (which is MAT). The issue could be derived from those differences in official data.

So I guess the fix would be to have them both showing the same information and airports, and explicitly mentioning the origin, or have them showing different information correctly documented so we know the purposes of each one.