requiring people to literally teach these things is going to become a bottleneck quickly - what you could do instead is teaming up with the OpenRadar/ATCPie folks to implement support for integrated Tutorials - e.g. as per the FlightGear tutorial system (fully scriptable) so that "lessons" can be created by people who understand basic ATC concepts, which could be completed by novice users.
If the ATCPie/OpenRadar folks should not have enough time to help implement something like that, this could also be done using FlightGear's built-in Tutorial system:
http://wiki.flightgear.org/TutorialsBesides, note that FlightGear's very first ATC support was using built-in means, such as the Map dialog:
http://wiki.flightgear.org/ATC-aircrafthttp://wiki.flightgear.org/ATC-FSMeanwhile, it would be possible to recreate a virtual ATC environment solely in fgdata space, e.g. by using Nasal and Canvas - in fact, you can even create full-screen Canvas applications for FlightGear:
http://wiki.flightgear.org/Howto:Creati ... plicationsBesides, a few people (aircraft developers) are actually working on a full Nasal/Canvas based RADAR framework, which is intended to be sufficiently generic to be reusable for these purposes, including even ATC stations on AWACS-like aircraft:
http://wiki.flightgear.org/Canvas_RadarIn summary, there are a number of ways to provide "tutorials" using OpenRadar, ATC-Pie or even just Nasal/Canvas in FlightGear.
I definitely, would not make this a 1:1 setup, because at that point, people would be the bottleneck - whereas creating interactive lessons and tutorials scales, even beyond people's involvement in FlightGear (think years from now).
For example, it would only take ~50 lines of code added to the tutorial system to allow Canvas maps to be displayed as part of tutorials - in fact, we once implemented everything needed to display tutorial targets using a Canvas map:
http://wiki.flightgear.org/Canvas_MapSt ... _Layer_TUT