J Maverick 16 wrote:It's difficult to coordinate with people who just don't care about ATC... anyway, all we want at FGUK is stated here:
[snip]
Thanks! I'll mark the restricted area in OR.
sanhozay wrote:Surely it's up to the pilot to contact ATC, not the other way around? I've never completely understood why this non-standard phraseology is built into OpenRadar.
Yes, it's (theoretically) up to the pilot to contact ATC, but sometimes players are not aware of this rule and wait to be contacted by a controller first. Furthermore, there's the airspace issue IAHM-COL mentioned.
jwocky wrote:On another unrelated question: Elgaton wrote about GND controllers. Now as far as I understand it, and correct me if I am wrong, GND brings the planes from the terminals to the runways respectively vice versa and makes sure, they don't crash into each other on the way? So, are there ATC procedure for that too, do you need groundnet with OpenRadar, or how does that work?
The ground chart from the eAIP is usually enough (although it is preferable to convert WED taxiways to lines in the OpenRadar file - there's an old script by VaLeO on the main forum which does the trick). Also, the ground controller should clear the departing planes to their destinations, assigning the SIDs (in coordination with the tower); however, since we've always included departure and arrival procedures in the OR files, nothing else should be done for this purpose.
Ground networks are used only to provide parking positions to pilots (as well as taxi networks for AI planes, but they don't matter here, since they are usually disabled when FG is connected to the multiplayer network).
---
I'll update the thread on the main forum tomorrow morning.