* PilotEdge is what I thought VATSIM was going to be when I first started flying online. It's been a couple of years since I first started flying online and when I first found out that VATSIM existed (and read the website) I thought it was a serious place with all of the rules and such. It's not. I usually control Memphis Tower (KMEM) on Wednesday evenings and sometimes other people in my ARTCC join in on Ground or approach. While the sound and behavior is generally pretty professional, the details are always missing and my PE experience brings that into sharp relief. Ground controllers forget that tower owns the taxiways in certain parts of the airport. They rarely deal with VFR pilots and stumble inconsistently with clearances for someone that wants to fly in the Bravo. They don't enforce the SIDs based on the instructions (HOTRD not allowed during the day, only for the overnight). Overall, the people are fantastic, but I've learned something about myself - I want the realism that PE provides
* Flying on PE and listening to the constant traffic and instructions has made me a better controller. I did my third supervised Approach training session and my instructor was impressed. I was able to take immediate and confident control of the inbound and outbound aircraft because I'm so familiar with the calls from my time on PE. Being a VATSIM controller is like getting a tower tour and a chance to sit at console and observe in real life. While I wouldn't recommend it for everyone, VATSIM scratches an itch and contributes to everything I want to learn as a future pilot.
* PE's technology infrastructure is an underappreciated value. Stop and think about this for a moment:
- Automated AI traffic with realistic flight paths and density - someone had to fly those routes and record those drones right? But there are hundreds (thousands?) of routes and some piece of infrastructure injects that into the experience and "just works".
- Real world frequencies handled by magic -- I've figured out how it works from my own research but it's likely a trade secret so I won't mention it here. Based on what I know, it is half pixie dust and half staff skill. If you want to make your brain mush, try writing down a process of how you would build it and you'll quickly get lost.
- Sound quality stays good even under high system loads
- Regular shift changes are managed without drops in service - it's not like there's an office where everyone sits next to each other, so there has to be an extensive setup of interoffice comms to do controller turnovers and keep track of pilots.