this is what i have for kmciKMCI,0011,39.293800,-94.729187,1026,9,10801,110.50KMCI,0012,39.281914,-94.708870,1026,9,9500,110.75KMCI,0090,39.290806,-94.726006,1026,92,9500,109.70KMCI,0191,39.306400,-94.701614,1026,189,9500,109.55KMCI,0192,39.321770,-94.720901,1026,189,10801,109.10KMCI,0270,39.288124,-94.693810,1026,272,9500,109.701L/R, 9, 19L/R ,27is that the runways you have at kmci? do you have any special scenery?if you send me a .pln, i'll get a beta tester to fly it.

Yes those are the runways that I have. I'm using the default scenery for this airport. I really think RC is trying to send me to runway 27. Even though it tells me to expect vectors for runway 1L and it gives the proper frequency of 110.50. I just haven't flown away from the airport long enough to see what happens. I usually cancel RC and land myself on 1L at this point. I'm a little dense on sending you the .pln. You want me to email it to you? Bob

email is fine. [email protected] far (dme wise) are you from the airport, when you give up?jd

Regarding TO clearance, are you taxiing into position using the taxiway at the beginning of the runway? You must also be within a few degrees of the runway heading and stopped near the threshold. For a test, make sure your AI is turned down to zero and there are no aircraft preceeding you on the runway.JD: Does RC recognise intersection take-offs or must they be at the start location as shown in AFCAD. If the latter is required then I suspect the aircraft must be stopped within the start point radius. Also I'll throw in a version 4 request to be told to taxi into position and hold while an AI might still be on the roll out so I can go as soon as it clears - handy for dense situations.That being said I have not had any problems with KMCI take-offs or arrivals usually coming in from the northern boonies of KMSP. I originally used the default and later a downloaded AFCAD from flightsim that added gates and parking codes. I looked at the default and the downloaded AFCAD bgls.

Yes I'm entering the runway from the taxiway at the begining of the runway. RC is acting as if I have pulled onto the wrong runway. It is still waiting for me to pull onto the runway even though I have taxied into position and am holding on the proper runway. I have even inched down the runway a little bit hoping to be cleared by RC. I eventually just take off anyway and during climbout everyhing is fine with RC. I really think there is a mixup in the runways somewhere. Bob

as long as he is lined up on the runway heading, i'll clear him for takeoffjd

Usually I'm about 15 to 20 miles out from the airport before I give up and land by myself. I tried to draw a diagram of what's happening but when I posted it it was all messed up and didn't post like I had drawn it. Bob

I hope this comes out right. KMCI ! ! ! ! !______________________ < Runway 27 ! ! ! ! X ! ! X ! ! X ! ! ^ ^ ^ I give up here Runway 1L Runway 1R X

this is probably considered a straight in approach. you should fly 040 until intercepting the localizer. in your drawing, are you really that lined up with 1L or you more to the left of 1Lfor experimental purpose, ignore the fly heading 040, intercept the localizer, and go on in

Can anyone tell me if there is a fix for this problem? Every single time I try and fly into KMCI, Radar Contact will tell me to turn right to 040 and expect vectors for runway 1L. Ok so I comply and Radar Contact forgets me after this. Next thing I know I'm heading away from the airport. Usually I'm coming in from KDFW and I'm flying a heading of 009. I don't have this problem at any other airport, only KMCI. I have also noticed that when I try and depart KMCI I never get takeoff clearence. I get cleared to a runway and told to position and hold. But I never get takeoff clearence. I'm wondering if something in the RC program has the runways mixed up at KMCI. I'm thinking that RC thinks runway 27 is actually runway 1L. Is there anyway I can fix this short of going back to using default FS9 ATC? Thanks in advance. Oh let me add that the problem is not RC losing sync with FS9. I can still hear other chatter from RC and I can select numbers from the screen but they just forget I'm up there.I really think they are sending me to a wrong runway. Bob

A couple of clues:RC steps you down to an altitude suitable for each stage of arrival. You can estimate that stage by that. Also be sure you have reached the correct altitude. Is it possible you are getting delay vectors for altitude loss purposes?If AI is assumed, you could be being vectored around for a merge. It looks like you can almost do a straight in. For the fun of it, keep going until 30 nm out and see what happens. Also see if in the options tab you have Interact with AI checked so you'll receive some target call-outs. I also think there is an option for random holds somewhere that should be off.(From real world observation being located at work about 20 miles from the threshold of 12L at KMSP, in heavy traffic density on a clear night I can see patterns extending out to 25 nm estimated before turning to a 30 degree relavent intercept. Even those hedging closer (smaller jets) still run base about 20 nm out before turning to the intercept.)Anyway, allow up to 30 nm away from the sairport just in case.

I am lined up for 1L probably just a little to the right of centerline and flying 009 when I'm told to turn right to 040 and expect vectors for 1L. I have already descended to 4100ft which I was told to do. So RC turns me away from the assigned runway and then forgets about me. It makes no sense to me. Why doesn't RC just clear me for a straight in approach instead of turning me away from the runway? I'm going to try another flight tomorrow and when they tell me to expect vectors for 1L I'll ask for another runway. I don't have this problem at any other airport and I don't have the problem with default ATC. I still think it's a problem with RC. Bob

I don't think it's the altitude thing. I always make sure I'm at the proper altitude by the time I'm told to be there. I'll try your suggestion about continuing past 30 miles out and see what happens. Like I've said before though, this is the only airport I have this problem at. And with the problem of not being cleared for takeoff when I'm on the proper runway, I really think that for KMCI RC has some type of mixup with the runways. Did anyone at RC fly the flight plan yet that I sent you? If so did you get the same thing? Bob

one beta tester flew it with both 3.1 and 4.0, requesting 1L both times, without issuestill looking at it though....jd

Grasping at a straw here, but are you by any chance flying the JHAWK4 STAR on a flight plan generated by FSBuild? The coordinates for second to last checkpoint before the airport (JEWEL int) is incorrect in the FSBuild data, and the checkpoint it puts in the flight plan is actually 5700 miles away on the western coast of South Korea. The final checkpoint (NOAHS int) is 11 miles from KMCI. You might miss this if you didn't look at the flight plan closely. Given the apparent flight plan distance to KMCI I'm not sure if Approach would even be talking to you yet for another 10,000 nm past RUGBB int, so this may not be your problem, but I thought I'd throw it out anyway. I learned early on that some STARs have extra waypoints in them that result in getting some odd vectors to final from RC, but I've never had problems using RC with the JHAWK4 STAR after correcting the coordinates for JEWEL.Mark Kuebeler