ILS HATAY RWY04 not working?

[Qiou87]

EDIT: probably not a map bug, only a game engine bug (wind at or close to 7kts).

 

Hi,

 

I read other threads about ILS not working in Incirlik and it was actually due to wind, so I checked this. I noticed twice, in separate missions (auto-gen from DCS Liberation), that the ILS for Hatay RWY 04 is not working (108.90MHz if my memory is correct).

Both times, I entered it twice (to make sure after seeing that it wasn't working the first time) in my Viper after checking in F10 view the exact ILS frequency for the runway, ILS ON, course 40°. Each time, the aircraft is not picking up the ILS. It works fine on RWY23.

 

Wind was 020 at 4m/s according to ATC. I used RWY04 based on instruction from ATC (250.15Mhz), because I know that wind direction affects runway selection. I basically fly the approach as vectored by the ATC, but the ILS is never picked up. Due to some low-level fog, it made for some very difficult approaches (luckily my mission had a steerpoint on the runway).

Edited September 22, 2020 by Qiou87

[drPhibes]

The wind threshold is >7 kts.

Edited September 22, 2020 by drPhibes
typo

[Qiou87]

The wind threshold is >7m/s.

 

Are you sure? I read 7kts somewhere, which is 3,6m/s. As I said the wind was announced by ATC at 4m/s, so over the threshold. It would be pretty weird to have a high 14kts (7m/s) threshold for ILS.

[Nealius]

ATC wind and ME wind often differ by a large margin.

[drPhibes]

Are you sure? I read 7kts somewhere, which is 3,6m/s. As I said the wind was announced by ATC at 4m/s, so over the threshold. It would be pretty weird to have a high 14kts (7m/s) threshold for ILS.

 

 

Sorry. Typo. Kts is correct.

[Ramsay]

Wind was 020 at 4m/s according to ATC. I used RWY04 based on instruction from ATC (250.15Mhz), because I know that wind direction affects runway selection. I basically fly the approach as vectored by the ATC, but the ILS is never picked up.

 

Unfortunately I wasn't able to reproduce your issue, so it looks like you were operating near a borderline case (~3.6 m/s) where ATC and ILS RWY logic desync.

 

I tested 8 knots towards 20° and 200° in the ME using the A-10C and in both cases Hatay's ATC and ILS functioned correctly.

 

I could only get ATC and ILS to desync on RWY 04 after dropping the wind to 5 knot towards 200°T

 

An important difference (when using 8 knot towards 200°T) compared to your experience was that ATC reported "wind 020 at 5 meters per second" for RWY 04 i.e. +1 m/s

 

 

Can you share the mission ?

 

Tested using A-10C and F-16C in Open Beta 2.5.6.54046

Edited September 22, 2020 by Ramsay
OP already said he was in the Viper

[Qiou87]

Can you share the mission ?

 

I would if I could, it is a DCS Liberation mission (it is always overwriting the same "liberation_nextturn.miz") which has quite a lot of scripts in it. I tried sharing one with someone before, and basically it won't open in the ME due to those scripts (I think it is reporting the mission results to DCS Liberation using those scripts).

 

Since it was the last one I played I can open it again, check the wind in the ME. Maybe ATC makes a rounding up and it is, like you say, a borderline case.

 

Thanks for taking the time to check, so probably not a map issue and only a game engine issue. It is very stupid to have this limitation, as fog usually happens when wind is low, and fog is when you need ILS. In that case the runway was barely visible until I was at 100ft AGL, landing would have been totally impossible without the steerpoint on the runway. IRL I would have diverted for sure.

[Rongor]

As of today, ILS of Hatay still doesn't work.

No indications on the needles.

No morse identification.

[Recoil16]

1 hour ago, Rongor said:

As of today, ILS of Hatay still doesn't work.

No indications on the needles.

No morse identification.

I just tried and cannot reproduce your issue. Can you please attach a short track showing the issue?