Hi fellas,I've run into a situation that has me stumped and I thought I would lay it out and see what you guys think. BTW, I've also posted to the Orbx forum yesterday and I am waiting to see if someone there has an idea.I've been taking a long, meandering trip in Orbx' PNW starting from the Nace Family airstrip (OG 41). I am in the Quest Kodiak and flying VFR using VORs and NDBs along with Topo landmarks. Everything was going just fine until I noticed as I was flying from KOLM to KPEA that the PEA VOR was not deflecting my HSI. I verified the fact that the Kodiak was receiving a signal from PEA because the distance to the PEA VOR was being properly displayed by my Garmin 1000. I also could not get the Kodiak's autopilot to navigate successfully to the VOR. Same issue with both the Comox (UQQ) and the Port Hardy (YZT) VORs.I used Plan G to create my flightplan. The frequencies listed are:PAE - 110.60 MhzUQQ - 110.40 MhzYZT - 112.00 MhzI double checked the accuracy of the frequencies by going to the FSX/World/Map and retrieving the frequencies there.Finally, I created new flights in other areas of PNW (lower Oregon again, Olympia area, Seattle), and outside of the Orbx scenery area (South Carolina) and had no trouble with the VORs located in those areas. I could easily dial them up while on the ground, take off and fly in their general direction and have the HSI needle pick them up once they got in range. I could, of course, also navigate to all of them using the Kodiak's autopilot.Anybody have any ideas? I'm presently parked at CYZT and so I don't know if the problem will persist as I continue to make my way North. I'm sure open to any suggestions and ideas!Thanks!John

Do you have the G1000 CDI set to NAV1?

Hi, sorry, maybe is my poor english language, but there is something I don't understand; first, you're speaking about flying to KPEA using PEA VOR, but PEA in my database exist only as an NDB at 257 KHz, and in fact, later you speak about PAE VOR at 110.6 MHz, but PAE is near Seattle, PEA and eventually KPEA are in Iowa.UQQ is a TACAN so, in FSX is correct to have only the DME portion, cause military TACANs share the DME with civilian receivers.YZT is a VOR DME, and should be correctly received from the VOR, if in FSX the frequency is the correct one (on mine it is).Mauro

Hi Bert - Yes, I do have the G1000 CDI set to NAV1. I was actually meandering up from lower Oregon and using the various VORs along the way. Each time I would land, go get a cup of tea and then set off again entering in the new VOR information. When I got to the area serviced by PAE (Paine/Everett) things went badly. I don't have a clue as to why.Hi Mauro - I apologize for my typing skills. My reference to "PEA" is incorrect. It should have been "PAE". I did not notice that UQQ is a TACAN. That explains the issue with UQQ. Now, If I can resolve the issues with PAE and YZT I'll be in good shape! Thanks Mauro for the tip! John

John... I am not sure what is going on either...I just tried myself in the Kodiak (v. 2.6)... PNW KOLM - KPAE had 110.6 dialed in... on the ground... as soon as I swapped it from 'stby' to 'use' the little DME window pops up (left side of the HSI) with PAE nav/loc (distance is blank). A few minutes airborne then "60.0NM" is displayed and the CDI on the HSI comes alive (deflects).So yeah... not sure either.-Rob

I just tried the same flight. On the ground at KOLM you do not get a good signal from PAE, butthat is not unusual. Once you are airborne and within 60 nm, the reception is there... again,not unusual.. seems to work OK.. :(

Hi Bert & Rob,I believe I have gotten to the bottom of the problem. Yesterday PM, while warming up the Kodiak on the tarmac at CYZT getting ready to head off to Bella Coola (CYBT), I dialed in the YZT VOR on the ground just to see if it would "come alive" as I departed CYZT - and it did! I aborted the flight and relocated the Kodiak down at CYQQ. There, I departed CYQQ again for CYZT with the YZT info dialed in and the AP powered up and armed with the altitude settings. I wanted to slave the AP to the YZT VOR just as I had planned the first time. No success. I thought about it and realized I had noticed this problem (disregard the UQQ "problem" - as Mauro correctly pointed out, UQQ is a TACAN and I neglected to notice that) occurred when I had my AP powered up. Again, I went back to CYQQ and reset the flight - this time simply taking off and flying in the general direction of CYZT but the NAV1 is not set and the AP is off. After getting deep into expected range of the YZT VOR I input the YZT frequency in the NAV1 and - success. I then powered up the AP and was able to slave the AP to the YZT VOR through my NAV1. The problem seemed to have been generated by having both the NAV1 and the AP on, primed and waiting for the VOR to come into range. Something wasn't right here.At that time I shut down FSX, un-installed and then re-installed my Kodiak. I then restarted FSX and went back to CYQQ. I reset the flight to CYZT, presetting the NAV1, powering up and arming the AP with the desired altitude and departed Comox. Everything worked fine.Don't know exactly what happened, didn't notice any power "spikes" or "blinks" but something must have happened that introduced some type of "corruption". I really appreciate being able to get on here and talk this stuff out with Y'all. It's great to have a forum of fellas that are willing to listen and offer suggestions and ideas!Thanks again!John

It's also critical to keep in mind that there are two different types of VORs; low-altitude and high-altitude.LA VORs have shorter range, and also cannot normally be received reliably (or at all for that matter) at flight levels.HA VORs have longer range, but conversely cannot normally be received reliably (or at all) at low altitudes.DMEs are frequently co-located at VOR, TACAN and localizer facilities, but actually use not only a separate frequency, but also a different, more omni-directional antenna system. Because of this, it is not at all unusual to be able to receive a solid DME signal while on the ground, but not receive any omni-range signal at all.

Thanks Bill. Good grief! Not only am I - a South Carolina "flat-lander" - venturing into uncharted (for me, anyway) territory up in the great PNW, PFJ and Tongass Fjiords regions - but now you tell me I've got to have sense enough to take into proper consideration LA & HA VORs? Now Y'all know that's asking a lot from the likes of someone who loves to hang his elbow out the left-hand window!I appreciate the info and your willingness to pass it on Buddy! That's what makes this hobby and the AVSIM forums just a great source of enjoyment - certainly for me!Take care!John

Thanks Bill. Good grief! Not only am I - a South Carolina "flat-lander" - venturing into uncharted (for me, anyway) territory up in the great PNW, PFJ and Tongass Fjiords regions - but now you tell me I've got to have sense enough to take into proper consideration LA & HA VORs? Now Y'all know that's asking a lot from the likes of someone who loves to hang his elbow out the left-hand window!

Just to confuse ya mo, there are actually 3 types of VOR's :-) (sorry, the formatting isnt working) US Standard Service Volumes (excerpted from FAA AIM T (Terminal) From 1,000 feet above ground level (AGL) up to and including 12,000 feet AGL at radial distances out to 25 NM. L (Low Altitude) From 1,000 feet AGL up to and including 18,000 feet AGL at radial distances out to 40 NM. H (High Altitude) From 1,000 feet AGL up to and including 14,500 feet AGL at radial distances out to 40 NM. From 14,500 AGL up to and including 60,000 feet at radial distances out to 100 NM. From 18,000 feet AGL up to and including 45,000 feet AGL at radial distances out to 130 NM.

Well, that does it. Jay, you've got my blood up now. I'm getting ready to do some serious research cause I can't be messin around up in these parts - ignorant soul that I am - without knowing what it is I'm about to dial up on the ol' NAV1 ! That could get a guy killed, if ya know what I mean. What you're saying to me is - it makes a big difference how high I am and what i'm fixin to tune to. Thanks for the heads up, brother!Take care,John

This link should give you just about everything you ever wanted to know, and a bit more you dont need to know :-)Have fun!http://www.navfltsm.addr.com/

I've got 'er bookmarked!Thank you Buddy!