For some reason in the few recent navdata releases provided by Navigraph, the localizer range seems to have been reduced in Indian Airports to 20-19nm, which is incorrect. I’ve noticed this issue in both X-Plane 11 and MSFS. Almost all airports here have LLZ range of 27nm which is inline with what I’ve seen IRL (aircraft being made to intercept LLZ from 25nm). Please fix this issue as it’s resulting in botched LLZ interceptions from Approach controllers in VATSIM.
Hi,
thanks for the example. According the AIP India, the LLZ has a range (+/- 35°) of 17NM and outer coverage (+/- 10°) of 25 NM above 3500 feet. So, it depends on your angle …
But anyway, both sim´s (X-Plane and MSFS) has a static range for X-Plane 18 NM and MSFS I guess 27 NM. That´s per default and is not what we offer. The reason is, that many countries doesn´t offer these values and therefore it´s not included in all records.
Well you have the info about LOC range of VABB so you can modify that at least. The AIP mentions a certified range of 25nm for the LLZ but in reality the signal can be received from even farther (refer to this video of Silkway West B744 landing on RW09 @ VABB, where the DME signal starts from 31nm+ and LOC signal is also visible more than 25nm). Whereas in the sim we are able to receive it from 23nm only, regardless of the intercept angle. In X-Plane it’s a total mess.
In VABB it’s very common to be made to intercept localizer from 20nm+ due to the MSA in east direction aircraft have to be intercepted on 14nm or more @ 3800’ to capture the ILS for RW27. 23nm means only 9nm of workable LOC signal for controllers (and only 4nm in XP11), therefore spoiling the controller’s efforts.
Also I’ve tested the issue in Fenix A320 in MSFS with the latest AIRAC @ VABB 27 & 09 with a straight line intercept onto the runway course. In MSFS right now only the Localizer DME is starting from 25nm instead of the LOC itself. The actual LOC signal starts getting received from 23nm onwards which is incorrect.
So my request is to increase the LLZ range to minimum 25nm in VABB at least (even better if done on all Indian airports) across all simulators. Urging you to please consider this.
Hi,
the source data depends on the quality of the AIPs of each country and what they offered. We may not add/change existing real-world data which we get from our service provider.
As I have wrote, the sims have normally static default values, which you can overwritten but will not used (at least in MSFS).