Hi folks I have a problem with Departure; they keep sending me to strange headings. I was flying from Sydney YSSY to Canberra YSCB the flight plan, setup in MSFS9 and transferred to RCv3.1, took me south to Woolongong, YWOL my first waypoint at heading 194 degrees. No matter how I depart Sydney when I get on to departure I am asked to fly 345 degrees. No matter what runway I take the result is the same. With Flexible dep proc set or clear I get sent to heading 345. My first waypoint is more than 30 miles south so should not constitute part of a DP as far as I can tell. On one flight, with Flexible dep OFF, I got as far south as Woolongong when I was once again sent to 345, I was expecting something like 180 for the next leg to Nowra YSNW.I have tried a number of different flights from Melbourne and Canberra but still end up on 345, one flight from Melbourne was south to Hobart. I should mention that once on a heading of 345 I have remained there, with some movement for traffic, for over 200 miles, then I shut down the flight. All the flights are flown with standard FS9 fair weather. Winds calm. I did have one completely successful flight from Melbourne to Sydney, I don/t know what the difference was but Departure set me on the correct heading and ATC got me all the way to an IFR landing. I am not a pilot so it is more than likely that I am stuffing things up somewhere in the planing.Any thoughts would be helpful.

That does seem strange. What heading does it show for the waypoint in the advdisp window? Could you post the flightplan itself?

A few things to check:As in the reply above, check out in the adv window the waypoint and heading you are expected to cross next. If you do not pass through it you will not be credited for it (it helps to have the audio ding turned on in options) and may be reversed on course until you fly through it. You must be on departure control to get credit and be allowed to proceed to the next point.If you have already passed it before contacting departure you will be vectored back to it. I see YWOL is 41 nm from YSSY. You MUST be on departure before you get there or you will not get credited for it and be vectored back. Since you are on flex you may not get any warnings, etc. Be sure to promptly contact departure when advised by tower controlled airports and also promptly contact enroute center.Note in your takeoff clearance if it states proceed as filed. This means you will not get vectoring to the first waypoint and need to navigate on your own insuring you get credited for it. That is where comparison with the heading on the adv display window comes in handy. This should not however be applicable in this case.If you never get a resume own nav, then I would expect the waypoint has not been credited.If you wish you can also include waypoints within 30 nm and you will be required to navigate them on your own. I took a quick look at a southern departure. What a mess it can be. So many to choose from!One more note to highlight. When you do get a resume own nav, fly direct to the next waypoint as shown in the window, not return to a displayed plan track om the GPS or EHSI. Attempting to join your original path may carry you outside of the heading tolerance generating correction vectors.

Thanks for the info, When I load the flight plan in to RCv3.1 I get a list of waypoints (I think) on the RC opening screen it looks like thisYSSY to YSCB@15000 (Alt1- , Alt2-) / YM.YM.YM.YM.YM.YM. after starting RC my first fix appears as 2030m 345 Degrees.Clearly this has nothing to do with the flight plan to Canberra via Woolongong. I set off for YM and discovered it is located well out over the water to the north east of Papua New Guinea.Here are some other flight plansYSSY to YMML@22000 (Alt1- , Alt2-) / YM.YM.YM.YM.YM.YM.YM.YM.YM.YMML to YMHB@5000 (Alt1- , Alt2-) / YM.YM.YM.YM.EGLL to EINN@31000 (Alt1- , Alt2-) / EG.EG.EG.EG.EG.EG.EI.EI.EI.EI.I do have some that look sane, as followsYMML to YSSY@36000 (Alt1- , Alt2-) / YSSY.YSSY to WMKK@36000 (Alt1- , Alt2-) / WMKK.I will try and attach the sydney plan,Have tried numerous suggestions but still end up on 345 heading for YM. Any further ideas would be appreciated. and THANKS again folks.

Good grief, whatever did you use to produce the YSSY-YSCB plan? Whatever it was, it's produced a corrupt flight plan - all those YMs should not be there and I'd guess your having the same problem with the plans that contain lots of EGs and EIs. It's no wonder RC was having problems sorting it out.So that you can check that it's your flight planner that's causing the problem, I've recreated (as near as I can) your flight plan in the proper format. I removed YGLB form the route as this is an airport (Goulburn) which is not suitable as an navaid in an IFR plan and you've already got the Goulburn NDB (GLB) which is on the airport so only one is necessary anyway. Also, you had both the Canberra VOR (CB) and the Canberra NDB(CB) in the plan so I left one out for ease of planning. I think you'll find this cures your departure problem.Pete

As the other poster stated, this flight plan does not resemble either the rc2 (adventure) export or rc3 (FS export). What planner did you use to create it?I used the freeware nav3.1 alpha to produce both. Be sure you are using in fact the FS export format of your planning utility. You have got extra fields in each entry in your examples (which do not match either plan I produced) and the second entry does not make sense.One more thing to be careful of if you are using a database search for your entries is that if you search for ICAO navaid codes, you choose the correct one from a list that uses the same identifier.I have seen other posts that regard these extra fields in this format so others here have experienced the same problem. I believe they had exported the plan in the wrong format but I do not know which planner they were using. You might try a search of this forum. I do recall they mentioned the EI, EI string and YM, YM entries which are bogus.

Hi Again, Thanks Petep for the modified plan, will give it a go. All the flight plans are created in FS9 flight planner,the ones that work and the ones that don't. not the best I gather, I am looking at some others at present. I am no expert in flight planning but all this info is puting the poeces together. I could see that something was corrupt in the plan once it got to RC but have no idea what or where the problem was.Thanks Folks.

Since you created these plans with FS9, I suggest running a scandisk to check the integrity of your FS9 partition. The scenery database that FS9 uses I am not certain of. Have you patched FS9 to 9.1?I do not think the FS9 integrated AFCAD bgls are used for this.Have you installed any add-on scenery for Australia/New Zealand?

You're welcome - let me know if it cures the problem.There are many better flight planners available than the built-in FS9 one and each has its strengths and weaknesses - and its fan club! However, for a complete novice, I'd recommend Ernie Alston's FSBuild2. It's payware, but worth every penny.Pete

Hi again, I have flown the flight plan YSSY-YSCB and it worked fine. I have deleted all the troublesome flight plans and created a new one, another YSSY-YSCB and again it doesn