Hi,Long time user of RC but I'm having major issues at Oakland airport. I'm wondering if somebody could fly this short route from KLAX to KOAK using the following route:KLAX.VNY.GMN.PXN.KARNN.BORED.BUSHY.SUNOL.KOAK Fly at FL280. Force RC to land at rwy 29.I've flown this route 5 times in the past 2 days and have yet to be vetored to the ILS. I will be told by approach to descend to 4000 expect rwy 29, no problem. Then almost there controller tells me to fly a heading 310 then I never hear again from the controller until finally I ask for Missed approach. 310 heading takes you compeletely away from 29.Just for grins I changed routing to VNY.GMN.PXN.OAK and it worked. Is there something wrong with my route or what. I've flown thousands of hours without an issue until this airport and that runway. All default FS9 installation, no addon scenery only default. I've even d/l latest makerwy and rebuilt database but no avail. I originally built the plan in FSBUILD so I then built compeletley in FS flight planner to see if something was awry in FSBUILD but it still didn't help.I appreciate any help on this matter.Sean

Try this. Look at your screen in the upper LH corner. You will see KOAK and 29 with the heading for both. When the KOAK heading lines up with the 29 heading then put that heading in you HDG in your A/C. That should take you to 29 then you can tweak your heading for your ILS approach on the localizer.

I understand that, the point is ATC is vectoring me away from the runway after having me descend to the proper alititude. Then I never hear from them again. Today I just let the plane fly on a heading of 310 for and hour and almost 100 miles away before i just closed out the program.The point is RC4 is supposed to vector you to within 30 degrees of the ILS localizer for capture and then you land; but in this instance for some reason RC vectors me away from the runway and never speaks again until I request Missed Approach. The first time I flew this route Saturday night I was at 4000 feet right over the threshold of the runway and was finally told to approach 1 mile from the marker. The other times I just vectored away never to be heard from again. Altimeter is set right, navigation is performed by FMC, I didn't miss any points, I've flown this route 4 times today from dawn till my eyes hurt and it just doesn't want to vector me to the runway. I understand its just a computer program but I'm trying to understand where I'm going wrong with the first route and why the second route works. Thanks for your help, hopefully somebody understands the situation.Sean

Ok I flew your flight plan. When I got around the BORED intersection the ATC had be to fly a HDG of 295. I flew this at FL30. I noticed that I had passed up my HDG to the runway after abt 20 miles out. Thats when I went miss. My intentions was the vector and was put on a vector heading. After I came back to the airport approach gave me rwy 19 or something. I requested rwy 29 and they gave me the vector to rwy29. Anyway I did land on rwy 29 no problem. You may want to send jd a file of your flight so he can look at it and see where you miss the approach. IF I had been watching my HDG and the KOAK had lined up close to the RWY29 then I would had put my HGD on that heading.

FL30? i don't think so.did you set your altimeter to local pressure below FL180? did you reach your crossing restriction prior to the 40 mile dme from KOAK.i think you missed your crossing restriction, probably because you were at the wrong altitude, because your altimeter wasn't at the local pressure.if you can correct these little things, and still have a problem, follow the directions pinned at the top of the forum, and send me the .logjd

I suspect vectoring starts just after BUSHY before SUNOL. What headings are you commanded to take. Did you miss 4,000 by the required position? Did you ack all commands? Were there any missed outstanding waypoints in the RC window status portion?I'm attaching an FSB generated navlog for others to look at.Fly it again and generate a log for jd to look at if you don't come up with anything. The procedure is in a link at the head of the forum.

After you are on vectors you do NOT use the FMC but use your MCP controls to comply with ATC commands using FLCHG and and HDG and SPEED as necessary. Vectors may take you away from the FMC path and you must be at any crossing restriction.Put a range ring of 40 nm using your FMC fix page (FIX KOAK then /40 for the distance) around KOAK and insure your descent arcs indicate you'll reach the altitude by then.

When I flew the FP I got my descent before the PXN waypoint. I began the vector after the BORED intersection. I never hit the BUSHY or the SUNOL waypoint. Also I flew at 3,000 ft and not FL30. The only thing I can figure out is when I was not watching the HDG screen and when the HDG lined up I didn't come off the 295 HDG and go toward the rwy 29. Also the other flights I fly I always get vectored before I hit all my waypoints.

Thanks for the respone, I'm relieved somewhat somebody else experienced the exact same issue I did.JD I did meet my crossing restriction, usually if you don't the controller will have you turn away until you do. I made sure I was down to level and speed 5-10 nm before. I constantly hit "B" key to make sure alitimeter was correct. The fourth time flying the route I made sure everything was perfect.I had a log and deleted it DOH when I'm back in town I'll refly and send you the log. If you fly the other flight plan it works which is wierd.Thanks,Sean

I believe your correct, vectoring starts just after BUSHY. I'm told to decend to 11,000 and be at 250 within 30 nm of KOAK. I follow orders. At 30 nm for KOAK I'm handed off to approach who reaffirms rwy 29. A minute or so later I'm told to descent to 4000. On my way down to 4000 I recieve a message out of the blue that once again, as if I missed initial instructions, to fly heading 310. Well this heading with that route takes me completely away from KOAK and localizer which at the time rwy 29 is less than 20 miles away. After a heading of 310 I never hear from controller again until I request MA just as expressjet experienced.I'm out of town for work so when back in town I'll fly route again with log.I also go off FMC route when given vectors.Sean

When you fly this next time just as a position guide, when RC starts vectoring you and you navigating with the MCP, on your LEGS page puch the LLSK next to the destination to get it in the scratchpad. Then punch LSK1 at the top and EXE. The heading to the airport will now show on LEGS line 1. If you want to see the path to this destination on your ND from your present position just "double-punch" LSK1L and exe and you'll see the line on your ND At the time you get the 310 degree course, see if you are south of the extended localizer heading. If so, that 310 should work.In the RC window it also should show the heading to the runway as you move along.The question is (and the log will show it) what heading were you given prior to the 310 vector, was that vector command acked, and where were you when the 310 heading was given.One thing I do to help (but not as I previously described) once vectors start and I am on MCP control, is to go to the FMC DEPAPP page and just LSKR the ILS for the runway (not the STAR). I then on the LEGS page close the discontinuity and then place the first ILS waypoint on the top and EXE. The ND now shows the extended ILS path and you can tell if you are going to merge with it. If the FMC ILS APP has the right data, it should show the 294 inbound path from JENFR about 15 nm from the threshold on your ND, useful for guidance.This is especially helpful (not in this case) if you going outbound on a downwind and getting turned to base and then turned for merging. It just gives a better picture.

I'm going to ask a stupid question. What FMC are you refering to? I use FSNavigator and I have a FMC there but all it shows is the time, distance ect from waypoint to waypoint and the ETA to destination.

I'm flying the CRJ-200 by Wilcopub which has a very basic FMS that I basically import the flightplan into due to lack of fuctionality. I may try this route with my PMDG bird or LDS one later but I doubt it has to do with the airplane.Sorry didn't answer your question you asked. At a heading of 310 I'm north of the localizer heading away. I have the localizer tuned and see it pegged to the right with the glideslope already coming down. The reason I don't turn to intercept is I've not been cleared for the approach and if I try to turn to intercept I'm scolded for not flying heading 310. I'll try the route again and make notes of direction etc.I'll try your tips Ronzie as I just got home so I'm going to try the route again.I'll also get a log created and send to JD.Thanks,Sean

Just flew the flight again and was looking at the log file it created and I may know whats going on I think.I'm flying with the FMC controlling lateral navigation. The fs9 flightplan STAR ends at SUNOL then proceeds onto KOAK direct.KLAX VNY GMN PXN KARNN BORED BUSHY SUNOL KOAKWell by the time I reach SUNOL I'm in contact with APPR and d/m 4000 with no other HDG changes yet issued by APPR. After SUNOL I fly 279 per the FMC becuase I have not had any vectors from APPR only altitude constraints (d/m 4000).Very soon after the plane turns to the last waypoint which happens to be KOAK (HDG 279 which is more than 15 degress out from what RC is expecting) I am reprimanded for not flying 300 which was approximately what I was flying before passing SUNOL. According to the log file APPR expects me to stay on a 300 course but I'm never told that, OTTO has comms, so after SUNOL I'm flying 279. After the reprimand I change course to 3000 and never hear from approach again until I decide to file MISSED APPR.Should you fly to your last waypoint if it is the AIRPORT of destination or should you continue on past your last waypoint holding that heading going off of LNAV. I usually only go off LNAV when I'm given a heading vector during appraoch. When told to d/m 4000 there was no command to fly a HDG. I'm flipping through the log and see nothing until RC notices I'm not at a HDG of 300 that it wants me at but never metioned.The point is should I fly HDG mode at the last heading I'm on once I'm in contact with APPROACH or should I continue to fly the flightplan until told otherwise? I've always flown the flightplan until given a heading vector from approach.I will fly again and try my theory, got nothing better to do.Sean

Well I tried again and did not get reprimanded for course correction but was told to d/m 4000 and thats the last I heard from approach.Sent JD log of previous flight, maybe you can make sense out of whats happening here.I'm out of ideas.Sean