Sorry to bother you all, but I have tried everything I know to do :(I have been trying to fly KAST to KOLM with RC for a few days now. Everything is looking good from KAST until I get handed over to approach at KOLM. At that point, they start vectoring me in to the runway, but then vector me out farther than the complete flight distance! They say they are sending me downwind for spacing, but never get back in touch (note: it is never the actual downwind for the runway or relative to the wind, but they may use downwind more broadly?).I used FSNavigator to make the pln file.KAST to KOLM@10000 / AST.RINDS.OLMAny suggestions? I am certain I am bone heading up something, I am just not sure what :)

Christopher,It's a 63 mile plan, and APC will take you out about 25 miles before turning you. Unless you are never turned, or you aren't given the straight-in approach to 35, you aren't doing anything wrong.I assume you're flying a jet. With a prop, APC will take you out about 20 miles or so. Try requesting short final 10 miles after you pass the airport.I'd also put OLM into your plan.

Thank you for the comments Scott :) I only fly GA aircraft, so I will try the Short Final request at 10 miles.Christopher

You could even ask for short final at 5 miles. :-)Rob

I had a similar strange problem. I did a flight from Cancun(MMUN) to Guatamala City (MGGT). So I came from the north and got vectors for runway 01. Rcv3 nicely vectored me past the airport until i was about 65nm south of MGGT. Then I had to fly heading 35 (or something like that) to catch the localizer. But since I was so far away from the airport, I was obviously way out of range from the ILS beam. I tried this flight 2 times, and both with the same result.Cheers!Robert-Jan

It depends on altitude. I made the 10-mile suggestion based on coming in at 10,000', but make the determination accordingly when you want to make the short call. You don't want to be too high or too close.Also, I'll repeat, make sure you are past the airport on the approach side to the runway. If you request short final before overflying the airport with an opposite side approach, strange things can happen.

i have never seen a 65 mile downwind leg :-)post your plan, let's see what is going on

Here is the .pln file. The last time I tried this, I ended up hitting a mountain at 35 nautical miles 'downwind.' I usually avoid the mountains when they send me out downwind forever and that is how I get so far before ending the simulation.They usually send me downwind on a heading of 085 degrees (that is really crosswind realitive to the runway selected last time, but you get the idea :) Thank you so much for looking into this![flightplan]title=KAST to KOLMdescription=KAST, KOLMtype=IFRroutetype=1cruising_altitude=9651departure_id=KAST, N46* 9.48', W123* 52.72', +000013.12departure_position=PARKING 7destination_id=KOLM, N46* 58.23', W122* 54.13', +000203.41departure_name=Astoria Regldestination_name=Olympiawaypoint.0=KAST, A, N46* 9.48', W123* 52.72', +000013.12,waypoint.1=AST, V, N46* 9.70', W123* 52.82', +000000.00,waypoint.2=RINDS, I, N46* 45.64', W123* 9.63', +000000.00,waypoint.3=OLM, V, N46* 58.30', W122* 54.11', +000000.00,waypoint.4=KOLM, A, N46* 58.23', W122* 54.13', +000203.41,

Hi JD,I've also never seen such a long downwind leg. First I thought rcv3 had crashed or something, because I didn't hear anything for some time. But when I started turning north by myself, I got slapped across the fingers for not following the correct heading :-)Here is my flightplan:[flightplan]title=MMUN to MGGTdescription=MMUN, MGGTtype=IFRroutetype=1cruising_altitude=35000departure_id=MMUN, N21* 2.25', W86* 52.62', +000022.97departure_position=GATE 3destination_id=MGGT, N14* 34.90', W90* 31.60', +004950.79departure_name=Cancun Intldestination_name=La Aurora Intlwaypoint.0=MMUN, A, N21* 2.25', W86* 52.62', +000022.97,waypoint.1=CZM, V, N20* 31.45', W86* 55.57', +000000.00,waypoint.2=CTM, V, N18* 30.23', W88* 19.40', +000000.00,waypoint.3=DEDAL, I, N17* 12.45', W89* 9.18', +000000.00,waypoint.4=NANDO, I, N16* 48.81', W89* 22.40', +000000.00,waypoint.5=TILOT, I, N15* 30.88', W90* 9.90', +000000.00,waypoint.6=RAB, V, N15* 0.55', W90* 28.20', +000000.00,waypoint.7=FN19, I, N14* 40.85', W90* 29.85', +000000.00,waypoint.8=MGGT, A, N14* 34.90', W90* 31.60', +004950.79,Is there anything wrong with my flightplan?Thanks in advance!Robert-Jan

i couldn't get it. just open the .pln, copy all, paste it into the message text area here

Done. I edited my previous message and cut and paste the plan. Thanks :)

drop the ast vor, and see what happens

drop fn19, and replace it with AUR (vor). see if that helps.there a dozen of intersections called FN19jd

I have come across duplicate intersection designations. To insure the integrity of a manually point by point created plan using NAV 3.1, I'll check the course and distance columns and occasionally verify the plan track on the map view magnifying suspect areas.When adding a point in Nav via the Search DB button, sometimes a few items with the same id will show up. Highlighting and clicking the detail button in the search window will show the type and coordinates of the item selected before you send it to the plan.Can't speak for other planners.I wonder how they account for dupes in GPS based director systems.

I removed the AST waypoint and voila, it works prefectly. Thank you for the help, JD!Why did removing that waypoint make a difference?