Hi Dave - thanks for that. You've made me think a little, and I reckon the problem lies in the fact that there are two navaid databases - one in Little Nav Map ( LNM), which is AIRAC Cycle 1801, and another, separate one in the sim itself (MSFS), most likely an older AIRAC cycle. So, two different AIRAC cycles, and that means that a navaid that exists in one navaid database might not exist in the other.dfarrow wrote: ↑11 Jul 2022, 11:12Paul , Is the Tindal VOR a TACAN ? A TACAN is for Mil a/c. only , and is same frequency spectrum as VORs/ILSs.
One like Yeovilton VLN 111.0 ...is not received by real Civi a/c VORs . However the DME part of it sometimes is . But Flt Sim doesn't seem to know it's a TACAN and it operates as a VOR.
In the real a/c it's easier and more reliable to use the DME associated with Yeoviltons ILS 111.3 I-YEO .
Additionally some VORs and DMEs are not co-located , due to siting difficulties . Traditionally Stornoway's VOR and DME were about 7 nm apart , VOR [ if memory serves ] was on a hill to the East . and DME on the field . Thus the VOR approach was only a cloudbreak , and if using the opposite Rwy to the Localiser , it was an NDB/DME approach .
Parrotheads rool ok ! Didn't know there were Parrotheads on this forum , great to sail to . Not been able to fly to Jimmy B yet .
Thx again for the travelogue
rgds dave f .
PS. must be dislexic Great Australian FA .
When planning a flight in LNM, you get the choice of using either of the two databases (LNMs or MSFS). On a particular leg over India, I had done the flight plan using the LNM database, but during the actual flight a certain NDB wasn't detected by the aircraft's ADF. After the flight, I went back and checked - this particular NDB was there in the LNM database, but not in the MSFS database.
The problem might be that the only way the MSFS aircraft's radios can only read from the LNM database is if the two computer programs are running and connected. I normally run them both, but not connected. Once airborne, LNM acts merely as a paper chart, showing me the flight plan and route, but not showing me the aircraft's position.
However, none of this should be a problem if I do the planning, and do the flying, both on the same database (since the India NDB mystery mentioned above, I now stick to planning using MSFS's own database - not LNM's one).
Here's the situation at Tindal:
This first picture shows what I actually had on the flight plan during this leg from Darwin to Newcastle Waters. Note that in the drop-down menu, I have selected "Do not use Navigraph database". This means I am, by default, using the MSFS database. The VOR and DME are separate, but the same frequency ( 112.3 ). On the face of it, both should have worked, but I was only picking up the VOR.
This second picture shows what turns up if I select "Use Navigraph for Navaids and Procedures" i.e. LNM's own database. The VOR is still there, but the DME has changed to a TACAN - still with the same frequency, 112.3:
So, the DME exists in the MSFS database I am using, but it's a TACAN in the LNM database, which I am not using.
The question still arises - if it's a DME in the MSFS database, and the simulator is using that very same MSFS database, why should this be a problem ?
I daresay I'm missing something vital and simple - a setting in LNM maybe.
You're going to have to explain that one to me, too. Parrotheads ? Jimmy B ??Parrotheads rool ok ! Didn't know there were Parrotheads on this forum , great to sail to . Not been able to fly to Jimmy B yet .
By the way, Ben, this means that since the Hunter is TACAN-capable, you might not have the DME problem I had. Can you let us know whether everything was okay, and which navaid database the sim was using ? Ta.