Most of the Airports in Austria have no Ground-Controller but Tower is handling Taxi etc.How can I disable Ground. If I uncheck it in "Controller info" also Tower gets unchecked.When I fly an approach (e.g. to LOWK) arriving from e.g. Rijeka via VOR DOL - VOR KFT I get handed over to Approach (126.82) allready when passing VOR DOL which is far to far away from the point where you normally get handed over. This point in real life is BERTA which is the border between Slovenia and Austria.The approach-controller then vectors me to intercept the ILS in 7000 feet while normally (in real life) he would vector me to the VOR KFT in 4000 feet.Can I somehow change the behaviour of the controller?If I fly useing IAP he directs me not to descend below 7000 feet bevore established on the ILS. As he then does not interfere when I descend below 7000 feet this is okay but it is not verry real.RegardsKlaus [email protected]

Hi Klaus,RC is set up so that you either have both tower and ground or neither. They may be on the same frequency.You will be handed to approach 40 miles from your destination. There is no local variation in this. Partly this is to ensure RC provides consistent, reliable vectoring in approach airspace.The altitude you are told to join the localiser is based on the msa for the airport to avoid RC vectoring you into a mountain.As I remember if you choose an iap you can descend below the assigned altitude when you consider appropriate without being warned by the controller. We assume you know what you are doing. Perhaps we could improve the phraseology here to find something which would actually clear you to do that.The controllers on the team will have to decide that one.All the best,John

>>As I remember if you choose an iap you can descend below theassigned altitude when you consider appropriate without being warned by the controller. Perhaps we could improve the phraseology here to find something which would actually clear you to do that. The controllers on the team will have to decide that one.<

RC samples the quadrature MSA published for those areas for quite a relatively wide radius around your projected path. It looks like those quad MSAs on VFR and low level IFR charts.If you are approaching an area surrounded on the sides by higher terrain within this radius RC will not bring you down far enough in some cases especially on those that lie near and parallel to the circumference of hilly/mountainous terrain. RC looks on both sides of your path, not one.The best way to use RC is to have plates of your departure and destination airport so you are situationally aware and can fly DP and IAP if required using the NOTAMS option or IAP.The standard .pln format of FS that RC uses does not include any altitude information other than cruise.I see but have not examined the option of FSBuild, a payware flight planner, to export in some formats altitude information. I also see that some IAP databases have the approach altitudes included as indicated on FMC displayed approaches. FS does not give much of a clue regarding terrain height on the approach path.Perhaps at some time in the future RC will have the option of using the advanced features of these databases and flight planners. It sounds great and feasible but then there is another problem to consider:How are these advanced databases synchronized to your loaded scenery? True, the earth doesn't change too much except in earthquake areas or volcano type elevation changes so perhaps discrete elevation points can be taken for approach paths. For now RC extracts runway data and certain info from your existing scenery, a big step forward in sychronization.When RC looked at the narrow path apparently there were some CFIT (controlled flight into terrain) instances. It was improved to consider the quadrant MSAs.