Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Asobo ATR72 VOR needles missing

Featured Replies

No matter what I do, I can't get either of the two VOR needles to display - even though they're both tuned and receiving (sometimes with DME information).

Both ADF pointers/needles display correctly. This is with the MS Store version, SU14.

Any ideas?

NZFSIM_Signature_257_60.png

 

Do you have the nav source knob switched to V/ILS?  Right to the left of the HDG auto pilot button. 

Edited by Bdub22

43 minutes ago, Adamski_NZ said:

No matter what I do, I can't get either of the two VOR needles to display - even though they're both tuned and receiving (sometimes with DME information).

Both ADF pointers/needles display correctly. This is with the MS Store version, SU14.

Any ideas?

Hit the two Bearing buttons on the pedestal right below the parking brake (BRG1 & BRG2):

 

1702352357?v=1

  • Author

Thanks!

I've always used those two buttons (BRG1 & BRG2): they cycle through VOR/ADF/OFF. As I said, I get the ADF needles to show, but not the VOR ones - and, yes, I have the NAV source switches set to VOR/ILS.

Do you see them OK?

I'll see if I can upload an screenshot or two.

NZFSIM_Signature_257_60.png

 

  • Author

UPDATE: I think I've found the problem. Not all VOR beacons work as advertised. I've been doing test flights from NZWU (Whanganui) to NZAA (Auckland) and it appears that the VORs around NZWU don't work (even though they show as tuned) and even show DME distances. On nearing NZAA, Tauranga and Hamilton VORs work correctly. Similarly, some ADF beacons work and some don't (again, they tune OK but don't work).

It may be some incorrect info in the NAV database the ATR is using (though I have the latest Navigraph installed).

Edited by Adamski_NZ

NZFSIM_Signature_257_60.png

 

7 hours ago, Adamski_NZ said:

On nearing NZAA, Tauranga and Hamilton VORs work correctly.

VORs are line-of-sight, so if it’s mountainous terrain (I don’t know the area but I know NZ tends to be hilly at the very least), you may not pick them up until you get closer in. 

  • Author
6 hours ago, mryan75 said:

VORs are line-of-sight, so if it’s mountainous terrain (I don’t know the area but I know NZ tends to be hilly at the very least), you may not pick them up until you get closer in. 

Good theory - and I wonder whether MSFS actually models that (it'd be great if it did!). However - with the problem VORs, I was at 12,000ft and within 5-10nm - so terrain masking probably wasn't the case.

As a test, I might make a note of my location(s) when it happens and overfly the same areas in different aircraft. 

NZFSIM_Signature_257_60.png

 

16 hours ago, Adamski_NZ said:

Good theory - and I wonder whether MSFS actually models that (it'd be great if it did!). However - with the problem VORs, I was at 12,000ft and within 5-10nm - so terrain masking probably wasn't the case.

As a test, I might make a note of my location(s) when it happens and overfly the same areas in different aircraft. 

Yeah in that case it’s unlikely. In the US you could look up the VOR in the chart supplement and see any distance and direction limitations. I have no idea how you do that for NZ. 

On 1/3/2024 at 6:39 AM, Adamski_NZ said:

it appears that the VORs around NZWU don't work (even though they show as tuned) and even show DME distances.

Which VORs specifically?

Whanganui 116.0 MHz appears to be a pure DME, colocated with the WU NDB, which would explain why you aren't receiving a VOR signal from it. (Tellingly, there's an NDB DME approach but no VOR DME approach.) 

Edit: Just confirmed in the New Zealand AIP, WU 116.0 is a pure DME. 

 

 

Edited by martinboehme
Typo

  • Author

Many thanks. I'd no idea that so many of the VORs in NZ would be DME-only. I've just downloaded the AIP chart (table 3.7) which lists the lot - and I can see which ones are VOR+DME and which are DME-only.
In MSFS, I flew down NZ North-South and tested all of them along the way. Here's a breakdown (all the NDB beacons work fine):

DME only:
------------------------------
KT (H) Kaitaia          115.80
KK (H) Kerikeri         116.10
WR (H) Whangarei        117.30
TG (H) Tauranga         113.20
WK (H) Whakatane        117.70
AP (H) Taupo            116.70
OR (H) Ohura            113.00
WU (H) Whanganui        116.00
PP (H) Paraparaumu      117.30
WS (H) Westport         116.90
HK (H) Hokitika         117.50
CI (H) Chatham Islands  116.20
RY (H) Mount Mary       112.50
TU (H) Timaru           115.90
HL     Henley           115.70

VOR+DME:
------------------------------
WP (H) Whenuapai        116.40
AA (H) Auckland         114.80
HN (H) Hamilton         114.00
RO (H) Rotorua          112.10
GS (H) Gisborne         114.20
NP (H) New Plymouth     114.40
NR (H) Napier           113.80
OH (H) Ohakea           117.10
PM (H) Palmerston North 113.40
WN (H) Wellington       112.30
WB (H) Woodbourne       115.60
CH (H) Christchurch     115.30
QN (H) Queenstown       113.60
SW (H) Swampy           112.70
NV    Invercargill      116.80

Edited by Adamski_NZ

NZFSIM_Signature_257_60.png

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.