November 6, 200421 yr Ok. I flew the flight today once again. As I approached the airport I was told to expect vectors for 1L. Once again they turned me to 040 and away from the airport. I continued past the 30 mile mark, actually to 90 miles out and RC never contacted me. This is a really weird and confusing problem. I'll mess with it again tomorrow and will delete the flight plan and rebuild another. If that doesn't work I'll try and request 1L everytime they tell me to expect 1L. Maybe if I ask for it they will vector me properly or at least clear me for a straight in approach. This is one of those problems that will make one's hair turn grey or fall out. Actually I can't wait for version 4 to come out. Hopefully it will be out before FS2006. Bob
November 6, 200421 yr >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 No sir I'm not using the JHAWK4 STAR. And my flight plan was created using the default MS planner before I bought and installed RC. But I really appreciate the suggestion. Anything helps at this point.Bob
November 6, 200421 yr Author Commercial Member i looked at your flight plan, and there are no checkpoints.try rebuilding your flight plan, use low/high/vor routing, and see if it makes any differencei'm going to re do it with vor, and fly it, and see what happensjd JD Read my blog
November 7, 200421 yr It might be that the controller is giving you a vector and it's not coming across the radio. I am having trouble with the controller's voice disappearing...but since I use the RC copilot to answer calls, I can hear his readbacks even when the controller's clearances don't come through.RegardsBob ScottATP IMEL Gulfstream II-III-IV-V L-300Washington, DC Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
November 7, 200421 yr Author Commercial Member i flew this, and what i suspected was happening, is happening.the clearance is not simply fly heading 040it is fly heading 040 until established on the localizer. this is a near straight in approach, and you are a little to the left of 01L. you are also far enough out you are not registering the localizer.in this case, do the following. fly on your current heading until the localizer comes alive, then turn 040. as soon as the localizer starts zero'ing in, resume the 01L runway heading (008) until you are on the localizer.sorry for the delay in sorting this outjd JD Read my blog
Create an account or sign in to comment