reported Mozdok NDB (Approach East) not working in Hind

[Ian Boys UK]

Mozdok NDB (Approach East) not working in Hind. The Outer Marker (525 East) works fine, the inner marker (1060 East) doesn't work.

[Quati]

Did you had this issue only at Mozdok? Did you check the western runway Marker Beacons? Cause they should be turned on and off based on the active runway determined by the wind direction. Also on Flappie's Online DCS Map is showing that the Inner Marker Beacon should be 1065MHz.

 

I always thought odd to use the Marker Beacons as Navigation Beacons in DCS as they should transmit the signal through a vertically directional antenna.

"Marker antenna is highly directional, and is pointed straight up. The valid signal area is a 730m x 1,280m ellipse. When the aircraft passes over the outer marker antenna, its marker beacon receiver detects the signal."

Part of me wish that they fix that to be close to the real thing.

 

Edited July 14, 2022 by Quati
I learned new things today and it feels good!

[Aviator78]

1 hour ago, Quati said:

 

 

I always thought odd to use the Marker Beacons as Navigation Beacons in DCS as they should transmit the signal through a vertically directional antenna.

"Marker antenna is highly directional, and is pointed straight up. The valid signal area is a 730m x 1,280m ellipse. When the aircraft passes over the outer marker antenna, its marker beacon receiver detects the signal."

Part of me wish that they fix that to be close to the real thing.

 

 

 

For Soviet/Russian airbases this is correct, these are classic NDBs, not markers.

[randomTOTEN]

1 hour ago, Quati said:

Part of me wish that they fix that to be close to the real thing.

Nothing's broken here. They're co located Marker Beacons (Fan Markers) and NDB's (Homers a.k.a. Locators)

but yeah I can't receive 1060khz even though I can tune it, despite forcing it on via the winds.

Edited July 14, 2022 by randomTOTEN

[Quati]

2 hours ago, Aviator78 said:

For Soviet/Russian airbases this is correct, these are classic NDBs, not markers.

That's great! Everything makes sense to me now (how on earth should a Marker Beacon have it's own freq if it wasn't also a NDB ) and I won't feel like cheating when using them.

 

1 hour ago, randomTOTEN said:

Nothing's broken here. They're co located Marker Beacons (Fan Markers) and NDB's (Homers a.k.a. Locators)

but yeah I can't receive 1060khz even though I can tune it, despite forcing it on via the winds.

 

Did you try 1065MHz? On the tables made by Minsky also shows that frequency.

null

Edited July 14, 2022 by Quati

[randomTOTEN]

Nope I didn't try that one. 1065Khz works.

[Chump]

In the Beacons.lua file for Caucasus, it has the near beacon at Mozdok as:

frequency = 1065000.000000;

On the F10 map, it appears to truncate the value when in MHz. It should display 1.065 MHz in this format instead (or leave it in kilohertz as 1065).

I notice that it is correct in the Mission Editor map.

Edited July 14, 2022 by Chump

[randomTOTEN]

Here's the 1958 vintage combination ILS and 2xNDB approach to runway 04 in Newark, New Jersey in the United States of America.

You can see the two NDB's coincident with Marker Beacons identified EW (400khz) and WR (359khz). It wasn't just a Soviet thing. I believe they were everywhere.

Enjoy.

[Flappie]

16 hours ago, Chump said:

In the Beacons.lua file for Caucasus, it has the near beacon at Mozdok as:

frequency = 1065000.000000;

On the F10 map, it appears to truncate the value when in MHz. It should display 1.065 MHz in this format instead (or leave it in kilohertz as 1065).

I notice that it is correct in the Mission Editor map.

Thanks for the heads up!

Two issues reported:

• Mozdok frequencies in F10 view shown in MHz instead of kHz (it seems to be the only affected airbase).
• All Directional Beacons have a 0° angle in F10 view (the whole Caucasus terrain is affected - I couldn't find DBs in another terrain).