reported earlier Soganlug ATC navigates to the right RWY, but says the wrong one

[virgo47]

I tried takeoff/landing on Soganlug airfield with various winds, and got totally confused by its ATC.

For example, I took off on 14, expected to be navigated back and land on 14, but Soganlug ATC said: "Fly heading 312 for 12, QFE..., runway 32, ..." As the airfield was just behind me on ~320 deg, it was strange. How can I fly 312 for 12 km and then land on runway 32?!

It all makes sense if I actually believe the ATC, just flip the named runway (14/32), then it all makes sense and it also navigates properly to go upwind on landing.

So I suggest - fix the ATC messages to say the right runway number. Just exchange them.

I tried this in L-39C and Su-25T, so I guess it's not plane specific. I'm on updated OpenBeta.

Edited August 11, 2022 by virgo47

[draconus]

On 8/11/2022 at 10:51 PM, virgo47 said:

How can I fly 312 for 12 km and then land on runway 32?!

Just as it says. If you follow the message you'll end up at the fix for final to the rwy 32 and then make appropriate turn. Your take off on 14 was your idea or ATC advice?

There are different airports in DCS. Some are one way only, independent on the wind. Some change depending on the wind. Some always make you take off one way and land the other.

Btw: the distance of 12 is in nm. Fix is around 5 nm from the runway.

Edited September 22, 2022 by draconus

[Volator]

On 8/11/2022 at 10:51 PM, virgo47 said:

Fly heading 312 for 12, QFE..., runway 32, ...

As Draconus already wrote, ATC in its current state will always vector you to sort of a "final approach fix" of the active runway. From there you can start the final approach to the active runway. It works adequately well in IMC, but depending on your inbound course to that said fix you'd have to use additional procedure turns to get on the final approach course, because you would overshoot the localiser / extended runway centerline significantly by just turning directly towards the runway.

[virgo47]

No, no... I'll add the image.

I asked Lochini and it navigated me to roughly my current position - as you can see, it makes sense to land on 13 from there.

But when I asked Soganlug, it sends me all the way somewhere to the point (2) (roughly) - and then it sends me to runway 14 (blue arrow). How does that make any sense? I'm already way beyond runway 14, I'd need to land on the opposite runway.

The messages for both directions have reversed landing runways for Soganlug.

As for various aerodromes, I tried them all on Caucasus, without wind and with wind in both directions. I compiled my personal kneeboard for that and I know that some aerodromes are one way (Gelendzhik, Sochi, Batumi and Nalchik) regardless of the wind, but Soganlug is "normal" except for the message.

In the mission on the picture there is no wind, Soganlug prefers RWY 32 in that case, Lochini RWY 13. That's also the direction of the hot start on each aerodrome if you create a simple mission for it.

Edited January 4, 2023 by virgo47

[virgo47]

On 9/22/2022 at 3:05 PM, draconus said:

Your take off on 14 was your idea or ATC advice?

I set up the hot start mission with wind to reverse the preferred RWY which is 32 for Soganlug. I was already on the runway. But whatever runway you go, it doesn't make sense. It sends you around - which is expected, but tells you to land on the opposite runway than the one you start - which is bogus.

[Ironhand]

Virgo47 is correct. Soganlug ATC provides the wrong runway number for landing. Take off from 14 and ATC informs you that you will be landing on 32. And vice-versa. TRKs provided.

Soganlug Runway 32-14.trk Soganlug Runway 14-32.trk

[virgo47]

So this now seems to be reported as a part of:

I guess this is a duplicate now.