Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

No take off clearance

Featured Replies

Hello,this always happens to Ataturk Istanbul runway 36R.A huge line of aircraft is formed but RC does not give any line-up and take off clearance although traffic is not so heavy.What could be the problem?

AI planes are stacked in front. FS is not offering clearances. RC merely echoes those controls.I suspect you have a fault in the runway/taxiway scenery layout. The ILS/universal hold short nodes may be too far from the runway, you might have a broken taxiway link to the center runway path, or other causes.The hold at K1 to 36L is a good example where AI might become stuck because of the taxiway angle and the placement of the hold short nodes. In your airport editor of choice, ADE9X is safe and universal for both sims, you need to see the hold short node boundary radius turned on in the view to see if it crosses into the runway. If not, FS will not let AI depart. In some instances it was found adding a normal taxiway node (where this radius limitation rule was not the cause) touching the hold short node on the runway side alleviated the problem. You might have to move the hold short nodes closer to the runway.In addition where no AI are in front of you you must be close enough to the runway edge of RC to give you clearance to line up on the runway. Typically in airliner views the high cockpit view distorts the perception of how close you are to the runway so keep that in mind. You'll probably have to get close to 36L past the hold short node for RC to release you.

  • Author

I tried to upload the AFCAD file ,if it is possible for you to check but I get a message that I am not permitted to upload this kind of file.Is it possible to upload the file so that it can be modified by you?

  • Author

I did it.It was easier than expected.Now it works fine.Thanks a lot for your help!!

  • Commercial Member
Hello,this always happens to Ataturk Istanbul runway 36R.A huge line of aircraft is formed but RC does not give any line-up and take off clearance although traffic is not so heavy.What could be the problem?
did you rebuild the rc scenery database after adding 3rd party scenery files?if you have more issues, make a log, duplicate the problem, and send me the log. how to make a log is pinned to the top of the forumjd
  • Author

Ok,I edited the AFCAD file, changed it and now it works ok.Thanks1!

I am running both FSX & FS9, separately of course. I recently corrected MS KCLT, using ADE, by adding the current RWY 18R-36L (changing the existing RWY to 18C-36C). In FSX on the new(er) RWY 36L, I have no takeoff clearance issue and RC controllers are just fine.With the exact same addition in FS9, as requested, I am directed by Ground to "taxi to 36L and hold short", on the way I am directed to monitor tower, and while on taxiway W and just prior to the "onramp" I am directed to "position and hold" onto 36L and after positioning on 36L, I get no takeoff clearance.I have checked the "data" files in RC and located 18R-36L, including the ILS file, both of which are correct. I have checked the hold short locations and these are the same in both FSX & FS9, as are the "starts". As I was using an A330-300, I have moved the "start" in FS9 to several locations to see if that was a problem, to no avail. If I push ahead and takeoff, at about 1,000 feet, sometimes I get a takeoff clearance and sometimes, at 1,500 feet or so, I only receive instruction to contact "Departure". I have not created a log yet, but will if you don't have something else for me to check first. John

First, I would compare the runway lines for KCLT from the FSX version and FS9 version from each version of r4.csv. They should be similar but probably not exact as scenery resolution is different between the two FS versions. What I am looking for is to insure that the correct r4.csv was created for your FS9 RC installed folder and you are not getting FSX data in there. I assume you have two RC folders, one for each version of FS and also you put in the correct path to FS9 after starting the scenery rebuild from the RC folder for FS9.Make sure you are running FSUIPC 3.98 or better. We need to figure out if RC see you on the runway pointed in the correct direction for take-off (within 25 degrees as I recall of runway heading) as calculated from your aircraft and the r4.csv data.I also suggest you get the free trafficlook.exe from the link in this thread:http://forums.simflight.com/viewtopic.php?f=54&t=81475&sid=15d9c915bd424dfa6bf5986752d64aa3Set that up in its own folder and use a shortcut property to run it as an admin. After you load your flight with RC running alt-tab to run the shortcut and a window will open showing AI activity in a spreadsheet type display. (This works in both FS versions by the way.)At the point where you get on the runway and seem stuck alt-tab to it and look at the nearby AI behavior to see if anything is stuck on the runway.Since you have both FS versions installed you need to check your registry settings with the free Registry Repair Tool from:http://www.flight1.com/view.asp?page=libraryto make sure each registry version is correct. Sometimes when incorrect you can be using the incorrect magnetic deviation data tables used to calculate mag. heading from true heading.If nothing shows up in your checks, then create a log file according to the instructions at the forum head quitting RC a few minutes after you are stuck (I recommend renaming it so it does not get overwritten with your next debug session) and jd can analyze it to see how RC sees your state sitting on the runway.

What I am looking for is to insure that the correct r4.csv was created for your FS9 RC installed folder and you are not getting FSX data in there. I assume you have two RC folders, one for each version of FS
Well, Ronzie, I am humbled in not being as savy as I thought I was <smile>. I am running the latest FSUIPC for both FS9 and FSX; The runway lines in both versions are exactly the same (ADE works very well at performing that); I use the traffic tool box to check on AI traffic and there are no AI's, except one coming on the taxiway behind me that I scheduled; My registry entries are correct for both versions.Guess what! During install of RC, I could find nowhere in the manual or instructions to create two separate RC folders for each version of FS and I was in such a hurry to get going with RC that my mind just didn't stop to fathom that such would have been a good idea <grin>. I am a programmer, but at 71 I guess I am losing my touch <grin>. The minute I read that you were looking for the correct r4.csv in FS9, I realized the problem and I am now receiving takeoff clearance in both versions at KCLT on the new(er) runway I added.The only reason I am running FS9 on this particular flight from KCLT to EDDF (which the wife and I actually use - she sleeps and I "assist" the bus drivers by flying the same route on my lappy) is that MegAirport Frankfurt had most of the moving visuals removed in FSX, due to complexity (and lack of will).I have "corrected" and "updated" a number of airports (particularly military ones) using both Google Earth and actual FAA charts, as the MS programmers were suposedly prohibited from using these tools, perhaps forgetting that lots of folks (former pilots, like me) see this hobby not as a "game", but a way of maintaining hard earned skills lost due to Flight Surgeons not renewing their certification <smile>. If you would like a copy of any that I have done, let me know.Thanks for the assist and thanks for assisting JD to keep this great program alive. Please update it to enable the correct taxiways to be identified. John

Taxiway idents and gates are pulled from your scenery and used in RC5. It knows where you are. As an "exercise" open runways.txt, a log of what makerwys does, located in your FS9 and FSX folders. Default airports have I recall one section and add-on airports have two sections per instance with the last pair of sections for a specific scenery having priority. You can look at the modified KCLT you created. Each section of a pair indicates the scenery path and file used. Be patient for this file to open as it is huge and can take some time.Hint:In your FS folders g5.csv and t5.csv are gate and taxiway data used in RCv5.Here's from FS9 is one identified short taxiway:KCLT,A3,36.58,35.210155,-80.946472,1,36.58,35.208588,-80.944916,1,0.00and a terminal gate:KCLT,B,1,35.220089,-80.945213,31.0,102.0,8Lot's of trig there :)

Please update it to enable the correct taxiways to be identified. John
Taxiway idents and gates are pulled from your scenery and used in RC5. Hint:In your FS folders g5.csv and t5.csv are gate and taxiway data used in RCv5.
OK Ronzie. How about getting me a copy of RC5, so I can check out g5.csv and t5.csv <smile> I'd be most pleased to buy a copy, if I could find one <grin> or even help BETAing it. <smile> John
OK Ronzie. How about getting me a copy of RC5, so I can check out g5.csv and t5.csv <smile> I'd be most pleased to buy a copy, if I could find one <grin> or even help BETAing it. <smile> John
These are the "W" taxiways (running alongside and onto the new(er) RWY 18R-36L) at KCLT that I located in FS. The other new taxiways are also listed, but guess that I will have to await RC5 for them to be recognized <smile> JohnKCLT,W,36.58,35.225079,-80.967392,1,36.58,35.225101,-80.966934,2,36.58,35.225109,-80.966835,4,36.58,35.225178,-80.965462,1,36.58,35.224281,-80.965378,1,36.58,35.223583,-80.965309,1,36.58,35.221729,-80.965141,1,36.58,35.206539,-80.963730,1,36.58,35.206089,-80.963684,1,36.58,35.202503,-80.963348,1,36.58,35.201740,-80.963280,1,36.58,35.200829,-80.963188,1,36.58,35.200756,-80.964684,4,36.58,35.200748,-80.964775,2,36.58,35.200718,-80.965317,1,0.00KCLT,W2,36.58,35.201633,-80.965393,1,36.58,35.201660,-80.964874,2,36.58,35.201664,-80.964775,4,36.58,35.201740,-80.963280,1,0.00KCLT,W3,36.58,35.204418,-80.965630,1,36.58,35.203911,-80.964989,2,36.58,35.203835,-80.964890,4,36.58,35.202503,-80.963348,1,0.00KCLT,W4,36.58,35.208012,-80.965935,1,36.58,35.207481,-80.965263,2,36.58,35.207409,-80.965187,4,36.58,35.206089,-80.963684,1,0.00KCLT,W7,36.58,35.219952,-80.966957,1,36.58,35.220440,-80.966385,2,36.58,35.220482,-80.966339,4,36.58,35.221729,-80.965141,1,0.00KCLT,W8,36.58,35.221828,-80.967117,1,36.58,35.222256,-80.966614,2,36.58,35.222321,-80.966537,4,36.58,35.223583,-80.965309,1,0.00KCLT,W9,45.72,35.224209,-80.966820,2,45.72,35.224213,-80.966728,4,45.72,35.224281,-80.965378,1,0.00

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.