Update of ILS stations: current status and limitations

[fsaerodata]

ILS stations are tied to a physical runway on flight simulator; an update of ILS elements is difficult in many cases, unless a complete revision of airport layout is carried out.

What is currently updated on fsAerodata database:
The original airport database is based on aeronautical data from 2005, with several runway and ILS modifications during this period of time.
fsAerodata basically updates the ILS stations on stock/default airports, correcting errors at the time the flight simulator database was frozen or changes produced on existing ILS over the past 10 years.

The following errors are corrected:
• Slight errors on localizer coordinates, either shifted out of runway, or displaced along the runway length.
• Update of magnetic heading to align with Approach Charts,
• Update of ILS offset over the past years.
• New ILS stations added on existing runways

Changes on airports over last 10 years:
• Slight changes of localizer coordinates, due to changes on runway width or length,
• Revision of ILS naming, including up to-date runway heading (e.g. ILS/MLS/GLS 33L CAT III, instead original ILS 33L).
• Update of localizer frequency.

ILSs are disabled on following cases:
• Airport has been decommissioned,
• ILS has been decommissioned,

Effects on 3rd party airports:
- Bear in mind, fsAerodata does not correct any ILS on 3rd party addons. By updating default database, it may correct most of the issues on 3rd party addons, though.
- As long as fsAerodata has a higher priority on the scenery list, ILS will override those from other addon airports. Otherwise, addon airport ILS stations will be taken by simulator instead.

- When a default ILS cannot not be updated, due to significant changes on coordinates or on runway geometry, they may bring conflicts on addon airport that includes a correct runway layout. In those cases, it's advisable to set the addon airport with a higher priority.
- On airport addons where runway length has changed significantly versus default airport, the user may encounter problems with glideslope angle due to the original ILS location.

What is not updated or current limitations:
- No new ILS are added on stock airport, if that runway does not exist.
- ILS stations with relevant location errors or changes over the past years.
- Special cases due to airport complexity.


In summary, updating ILS stations is a relevant issue that has no easy solution on many cases, with several compromises to take on development, unless the complete airport layout is brought up to-date.

Status as of AIRAC cycle 1801:
Total of original ILS stations on FSX/P3D: 3,450
Total of ILS stations updated: 3,100
Total of ILS stations disabled: 360
Special cases fixed: 102
Total of new ILS stations added: 510

[Langyboy63]

Hi

I have recently added some add on airports EKCH and LPPR and have found the ILS approaches are not working, I select the correct frequency, ILS inspectoris saying there are a number of ILS not in the Airac, I will email support witht the details.

[fsaerodata]

Hi, please give us some additional data; those ICAOs they both have the correct ILS stations on database. FSAD ILS stations take preference over other add-ons only when they have a higher priority on the scenery list; otherwise, the addon data is used by flightsim.
Regards,

[lowmein]

Hello!

I recently purchased your product and, it may be coincidence, my ILS facilities seem "off" now. I wonder if FSaerodata can cause this? If so, how can i fix it? Here's an example...

I was flying the ILS W 19 approach at KVPS. The aircrafts (I tried multiple payware and default FSX planes) all captured the Localizer and Glide Slope no problems. As I flew down the approach, at about 500 feet AGL the localizer and the Glideslope both quit working. It was as if they just shut off, the glide slope guidance bar and the localizer bar quit showing up on my instruments.

Could there be a problem with FSaerodata and FSX? Like maybe the sim thought the airport was 500 feet higher (and further north)? or somehow FSX and FSaerodata disagree on the airports exact location?

Additional info: I have zero add-on scenery installed, pure FSX only,

I'm not very technical minded about stuff like this, and thank you for any help

[fsaerodata]

Hi,
I've just checked the data and found the error, which is quite unusual.
KVPS has two ILS stations on Rwy19 and 30. Both share the same freq. 109.10, with the current navdata (on the stock FSX, IVPS is 100.3 and ICAH 109.1). Having same freq. seems to confuse the flight simulator and it's the reason of the effect you observe.
I haven't detected a similar case in other airport, so it's likely there is no solution, but let me think more in detail.
Thanks for reporting it,

[lowmein]

Solution or not, that is fantastic support! Thank you very much.

I also noticed that they both shared the same frequency, which would seem to cause an issue in Real Life too one would think.

I will check back in later to see what/if you came up with.

[somagic]

i have recently purchased the product and no one airport have ils all over the europe ... can anyone advice ?
many thanks
sakis

[fsaerodata]

i have recently purchased the product and no one airport have ils all over the europe ... can anyone advice ?
many thanks
sakis

Hello,
Once enabled the database via the config tool, check out the following topic on our FAQs section:
Navaids or Approaches are not available on GPS, map, or when tuning ILS/VOR ?
https://www.fsaerodata.com/forum/viewtopic.php?f=5&t=35

There must be related to the database entries not been enabled on your addons or scenery list.