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.

Feature Suggestions

Featured Replies

Hi JD & Co.I came up with a few enhancement ideas for RC, some of which I hope are implementable.1) Spontaneous directsAt least in Europe, to maintain an orderly, expeditious flow of traffic, ATC issues so-called spontaneous directs, which means that ATC gives clearance direct to a waypoint without pilot request.In RC, these could be random2) Change of assigned runway in approach sequenceThis means that Approach would change the pilot's landing runway in the midst of a radar-vectored approach. My uncle, who flies the MD-11 for Finnair, told me that a while ago, ATC had to change their landing runway 3 times (KJFK, rush hour) during the approach. Certainly not a normal approach that one =)These could somehow depend on airport size, time-of-day, and random factors3) Denial of runway requestsI understand RC is supposed to be flexible, but it would be a nice touch if RC occasionally denied pilot requests for arrival/departure runways (e.g. for traffic)4) Step-over clearances to parallel runwaysSometimes at busy airports, ATC has to instruct a pilot to step over to a parallel runway (e.g from 22L to 22R) while on short final. It would be nice to have this in RC too.5) Instructions to expidite climb/descentFor example, "Fastair three four five, descend and maintain 8000, expidite descent until passing one zero thousand"/"expedite through niner thousand" etc.In addition, you could look at these possibilities:* Detailed taxi instructions (Taxi to runway 22 via alpha, bravo etc..)* Less predictable approach vectors* "Instructor mode" which could be switched on on any flight. This would mean that the co-pilot/instructor would during the flight explain the ATC clearances to the pilot and how to fly them. A bit like the flight lessons that come with FS.. dunno, just an idea...

Everything except detailed taxi info and instructor mode could be done.Detailed Taxi - no way to get taxiway info. Would be nice if MS put out an ATC SDK.Instructor - too many wavs for the crew to record and way too much programming.Otherwise, everything else you list is done in the US as well, and would be nice.

One more thing: Could place name pronounciations (like in default MS ATC) be done for at least some airfields (e.g. "New York Approach, Fastair 345 with you") I know it will mean more wav files, but it would be very nice...P.S If you need manual translations, I'm ready to help -- I'm fluent in Finnish, English, Swedish, German & Spanish.

I'm not sure if this is relevent or not but in reference to getting taxiway info there's a gentleman who has written a program called "Airport Chart Viewer" who has managed to extract taxiway and gate info for all airports in FS2002. Here's the URL:http://www.joenetwork.de/manuel/chart_viewer.htmRegards,Nick Anzelino

Getting the information isn't the problem. It's getting it on the fly quickly that is. FS has its own internal method to determine which taxiways to use based on where you are and the AFD files. If RC could access the AFD files quickly then it would be able to do the same. Basically, AFCAD does it fairly quickly and a similar method may be able to be used in RC. It would just be easier if there were a map of how to tap into that info.Then there's the problem of airports with no taxiway designations in the AFD files. RC will just not be able to give you taziways. However, FS won't give you any instructions at those at all.

How about making the access to the AFD files a function of the Controller window for the departure, destination, and alternates before the flight starts. A default "gate" or area would be assumed if a destination gate is not specified. The resulting data could be extracted and buffered either in its own area of RAM or in a temp file nicely decoded for RC easy digestion when it is required during the landing taxiing process. At complex runways with many turn-offs it could be a large matrix but maybe an autoroute algorithm can be performed once the aircraft has exited the runway and contacted ground. I realise this all gets hosed if you while enroute request a different destination but at least you are covered for alternates.For large airports perhaps it would be sufficient just to get taxied to the general area for that airlines gates at which point a non-RC airline dedicated ground controller would handle the task. I noticed in the real KMSP small towers located on top of the areas for each airline where I imagine "local" taxi logistics are carried out. Don't know for sure.

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.