I wouldn't ever put a visual into the files (if I were to develop). It defeats the purpose.Visual approaches are flown visually, with reference to landmarks outside. Keep your head up and out....plus, having the plane fly the riv-vis kills all the challenge/fun.

I wouldn't ever put a visual into the files (if I were to develop). It defeats the purpose.Visual approaches are flown visually, with reference to landmarks outside. Keep your head up and out....plus, having the plane fly the riv-vis kills all the challenge/fun.

Its fun to have the LNAV route and hand fly it to the T, without using TIR it is somewhat difficult to keep adjusting the view while hand flying.

Hi DanI was looking at one of these and noticed you used a "colocated" fix definition. It was my understanding that this type of fix definition does not work with the NGX. Do you know otherwise? I really could not get it to work no matter what I did, so would be interesting to find out if there are conditions under which it works.Thanks

It's the NAVAID keyword that references the navdata files in PMDG/navdata that was deprecated for the NGX because its use could result in SIDSTAR files that wouldn't work without the proper base navdata files. FIX is the only one that works now, but you can still use COLOCATED as long as it references another FIX that's in the file.

I wouldn't ever put a visual into the files (if I were to develop). It defeats the purpose.Visual approaches are flown visually, with reference to landmarks outside. Keep your head up and out....plus, having the plane fly the riv-vis kills all the challenge/fun.

Actually, it's not hugely unrealistic - I know of multiple visual procedures that airlines code FMC procedures for so that there's a reference. The Innsbruck one in the new tutorial that's coming with SP1c is one such procedure.

Actually, it's not hugely unrealistic - I know of multiple visual procedures that airlines code FMC procedures for so that there's a reference. The Innsbruck one in the new tutorial that's coming with SP1c is one such procedure.

Yeah, I know I've seen a visual in the navdata somewhere (can't remember where I was flying into). My comment was somewhat more related to the earlier comment, though I didn't actually say that:

[...]; as a controller on VATSIM, my worst enemies are the pilots who are a slave to the magenta line, and around here I have to do my share of "a break in the magenta line isn't the end of the world." I see why you'd put it in there, though.

I can see the merits of it, as with the RivVis, they have advised altitudes that would be nice for reference to glance at the ND instead of glancing back down for a piece of paper (clipped to the yoke or otherwise).

Food for thought. Maybe I'll go back to kbwi and add the interstate visual, I assume if some are listed then you would expect all to be there otherwise there is a criteria. Interesting.

That one at least has an aspect of intercepting a radial, which requires a little bit of instrument work prior to the visual bit.

Kyle, would you mind giving the interstate visual a shot? I've added it to the KBWI procedure file. Rather than vectors from OTT I have you routed via FIX DEALE same as OTT arrival then follow the R-176 until about 5.5nm then the interstate (used google earth to pick a couple of inflection points on that path) and final is a straight shot in. I've provide vertical path guidance from 10nm.Let me know how it looks and any suggestions. Thanks.

Kyle, would you mind giving the interstate visual a shot? I've added it to the KBWI procedure file. Rather than vectors from OTT I have you routed via FIX DEALE same as OTT arrival then follow the R-176 until about 5.5nm then the interstate (used google earth to pick a couple of inflection points on that path) and final is a straight shot in. I've provide vertical path guidance from 10nm.Let me know how it looks and any suggestions. Thanks.

I'll give it a shot tonight and let you know. It looks kind of oddly set up in the text alone, but I have faith it'll be all in order when I'm in the sim.