Probably too close to the others.

it was on the departure field. how are you ever going to progress it? you only progress checkpoints in departure and center. you don't get credit for any checkpoints on tower

Oh, well, if it's that complicted... ;-)Shows me for not actually looking at the plan. :-lol

Ooops! I was looking at it differently and incorrectly it seems! I use the AST VOR to intercept the 20-degree radial and to keep oriented up to the RINDS waypoint.The flight plan itself was generated using the FSNavigator auto calculate function (low altitude airways).In the future, unless I have a SID for the airport in the flight plan, I should not have a waypoint within 'some number of' nautical miles from the departure airport?Thank you all for the help; I am learning :)p.s. I wonder why FSNav puts AST in the flight plan? You can still use the VOR without making a waypoint out of it... is there some super secret pilot reason for including in it in the list?

>I was looking at it differently and incorrectly it seems! I >use the AST VOR to intercept the 20-degree radial and to >keep oriented up to the RINDS waypoint. >>The flight plan itself was generated using the FSNavigator >auto calculate function (low altitude airways). >>p.s. I wonder why FSNav puts AST in the flight plan? You can >still use the VOR without making a waypoint out of it... is >there some super secret pilot reason for including in it in >the list? Did you mark the VOR a "Bearing Point" in FS Navigator? I dont hink it'll be in the exported .pln file if you do.

Great suggestion. I went back and added the AST VOR again as a bearing and checked the .pln file: it was not included.Thank you :)

Christopher,In the real world you would plan on transitioning a radial from the VOR. So it's a good idea to put an intersection where you intercept the radial into the plan. What really happens is that Clearance/Dep will usually give you the transition point, but in RC you have to do it yourself.I pick a good intersection that'll allow me to fly off any runway so I know I'll make it, and it's in the plan as RC sees it. If there's no intersection I just put in the first route point, usually a VOR, even if it's 100 miles away, as my first point.

Scott, thank you for the explanation, but you did a fly by! Would you please give me a couple of examples of how this works? And would you use the intersection technique even for real world GA aircraft? It sounds like I need to put intersections into all of my flight plans--as I want to get as close as possible to real world flight planning (and flying for that matter).

Hey, that did the trick!Okay, but what does the fact that there are a lot FN19s have to do with the fact that I got such strange vectors in the first place? The one I had my flightplan is the right one. The coordinates show that.How do I avoid this next time? Check to see if my last waypoint is a navaid at the airport itself?Thanks!Robert-Jan

Robert-Jan,You don't need a fix on the airport with V3. I only put one in if there's a VOR.The issue with the intersection is a minor bug in RC. JD would have to confirm, but I'm guessing that there's not a long eough table to find the right one all the time. Also, if the waypoint data is slightly off, RC may ignore the right one.

Hi Scott,I'll go with your hint next time to avoid the detour :-) This was the first time I encountered something like this.CheersRobert-Jan