April 12, 20224 yr Author 9 minutes ago, JRBarrett said: In LNM with Navigraph active, BGH shows as an H VOR. With Navigraph inactive, it shows as a T (terminal) VOR, which would have a very low range. You're right - I just checked that. So...am I to assume therefore that BGH always has a T VOR's range ( 38nm) even if I have Navigraph active and it's showing as an H VOR that's supposed to have a range of 130nm ? Surely not everybody was kung fu fighting. https://rationalwiki.org
April 12, 20224 yr 1 hour ago, Paul K said: You're right - I just checked that. So...am I to assume therefore that BGH always has a T VOR's range ( 38nm) even if I have Navigraph active and it's showing as an H VOR that's supposed to have a range of 130nm ? Do you have Navigraph installed in MSFS, or just LNM? Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
April 12, 20224 yr Author 13 minutes ago, JRBarrett said: Do you have Navigraph installed in MSFS, or just LNM? Just in LNM. Surely not everybody was kung fu fighting. https://rationalwiki.org
April 12, 20224 yr You might want to install it in MSFS too. If you have a Navigraph subscription, it costs you nothing extra, though you would need to download the Navigraph data manager for MSFS to install it. I find the Navigraph MSFS navdata is generally more accurate than the default MSFS NavBlue data. Here’s the weird thing. In LNM, if I turn Navigraph off, the VOR BGD(112.9) changes from an H VOR to a T VOR. But, at the same time a second VOR appears on the map left of BGD with the identifier “IB” and a frequency of 112.4 That VOR is shown as an H VOR with a range of 195 NM. It must be baked into the default MSFS scenery for ORBI. There is no “IB” VOR shown on any current enroute or approach chart for Baghdad. Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
April 13, 20224 yr Author 11 minutes ago, JRBarrett said: You might want to install it in MSFS too. If you have a Navigraph subscription, it costs you nothing extra, though you would need to download the Navigraph data manager for MSFS to install it. I find the Navigraph MSFS navdata is generally more accurate than the default MSFS NavBlue data. Here’s the weird thing. In LNM, if I turn Navigraph off, the VOR BGD(112.9) changes from an H VOR to a T VOR. But, at the same time a second VOR appears on the map left of BGD with the identifier “IB” and a frequency of 112.4 That VOR is shown as an H VOR with a range of 195 NM. It must be baked into the default MSFS scenery for ORBI. There is no “IB” VOR shown on any current enroute or approach chart for Baghdad. I've been looking at Navigraph, and thinking about a subscription, so thanks for your recommendation. Yes, I also noticed the second VOR appear when LNM's Navigraph was turned off. In fact, it rang a bell from many years ago, and so I went to check - sure enough, a second VOR, DGO (L), magically appears on an island near Jacksons (AYPY) in Papua New Guinea, under the same circumstances. I remember that my NAV radios could not detect it, even though it was there on the flight planner - maybe the second Baghdad one is the same. I will check when leaving Baghdad for Bushehr. Thanks for your time and assistance, Jim - very much appreciated. Surely not everybody was kung fu fighting. https://rationalwiki.org
Archived
This topic is now archived and is closed to further replies.