I have loaded a flight plan KBUF to KPHL several times and get proper instruction to rwy and altitude changes but never vectored to destination. Have tried three times and always

wind up flying toward Montreal as if RC4 in clueless as to the KPHL destination.

Any suggestions?

Be sure that you have correctly run a scenery rebuild with the latest makerwys installed in your FS folder and available from http://forum.simflight.com/topic/66136-useful-additional-programs/. Also it is a good idea to have the latest fsuipc installed from http://forum.simflight.com/topic/66139-updated-modules/

 

Run RC to do a scenery rebuild and then restart it. Check the controller tab in RC to make sure the airports are properly identified.

 

At what point are you not getting instructions. You must have met your crossing restrictions at 40 nm out of KPHL at 11,000 or 12,000 feet and shortly thereafter approach should contact you assigning the runway. You then ack and vectors should start unless you request an IAP after the first vector assignment. If you miss an assigned waypoint prior to this RC will stall. An IAP means you will do your own nav without vectors for approach.

OK i followed your instructions to update and ran some tests.

IFR KJFK to CYUL RC did fine

I then thought it could be a KPHL problem, so ran KEWR to KPHL and directed all the way to Rwy 17. No problems.

Went back to KBUF again and same problem.

Perhaps I was not clear on original msg. Cleared for takeoff from KBUF and receive altitude advisories but never vestored on course. Takeoff from Rwy 5 and stay on that heading forever.

As I final test cancelled IFR with RC and filed my flight plan with FSX controller and immediately vectored on course - so it looks like not the flight plan either.

Out of ideas at this point.

If the first waypoint in your departure (sent to RC) falls within 30 nm of the airport RC assumes you are following your own departure procedure and you will not get vectors. This turns on one of the departure options as noted in the controller tab. The option for vectors (No Departure Procedure) will be unavailable. You will be responsible for crossing the waypoints within the airport area and lining up for the waypoints outside of that area.

 

When the first waypoint falls outside of 30 nm all departure options become available.

 

Please see page 107 of the rcv43 pdf manual.

 

Does this answer relate to your KBUF departure?

 

I auto generated a plan in FSBuild for KBUF to KPHL as KBUF BUF J95 CFB.SLATT3 KPHL. The first waypoint was the BUF VOR only three miles from take-off that would cause this behavior. The altitude restrictions is the default turned on in this case but you can also select No Altitude Restrictions option.

 

http://flightaware.c...KBUF/DP/all/pdf shows one departure. Now BUF is close to the end of runway 5 and if the aircraft turning radius is too tight to cross you could eliminate it and go to KELIE as your first waypoint on J95. That would also give you vectors if desired.

 

 

 

Depending on your planner you should be able to delete BUF from the expanded J95 waypoints. If you happen to use FSBuild there is a build option that lets you build directly from the grid table. To do that in this case just delete the BUF line and rebuild with export options as needed. Unless you are in a slow aircraft you might not be able to make that 60 degree turn from the runway heading for 5 to 110 degrees to cross BUF with three miles.

 

Also investigate the use of RC NOTAMS to increase tolerance if needed.

 

I also looked at some real world plans that were flown in turbo props or small regional jets and the plans were more South bound using V low altitude routes. They departed South:

KBUF VAIRS V33 BFD PSB BOJID1 KPHL

so the BUF VOR as a transition point was not used.

Deleted the Buffalo VOR from the flight plan and all works now.

Thanks for the help - I will have to watch for this circumstance in the future.