Not wanting to pile on (or off) without some perspective, I dusted off my VATSIM credentials and flew some basic VFR flights on the free-as-in-beer network. My flight tonight was a V2 rating style VFR flight from John Wayne to Ontario. The controller was a C1 sitting as SoCal Approach and had 5 airplanes. The experience was so obviously different:
East ramp taxi instructions: 20R via Alpha, Lima
Departure instructions: "Fly heading 080, (winds) clear for take off" No "left or right" just up to me.
Once I checked in out of habit at "1200 for 5500 VFR" I got told to resume own nav which took me across the approach corridor for KSNA at 3500FT.
The rest was mostly basic but "lacking". If you haven't heard VATSIM audio in awhile, you'll wonder why you even ask Keith for "VHF realism". Oh gawd it's awful and hard to hear.
Why do I even mention this?
The controllers get pissed off or sound that way because of amateur behavior in a professional environment. I heard a discussion recently between a controller and a pilot. Pilot told to taxi to runway at an intersection. Pilot ignored the taxiway intersection he was given and went full length, crossing another runway. When the controller called him out (with a tone and timber similar to a real-world astounded ATC would) the pilot wanted to contend that since he was not told to hold short, he did nothing wrong.
I like that the controllers get pissed off at the pilots sometimes, but they never make it personal. I should get yelled at if I call Riverside Tower, get pattern entry instructions, then proceed to enter the pattern at CHINO and bust that charlie all because I misidentify landmarks and fly over the wrong area. Now, if the controller had name-called or worse, sure that's not cool.
As far as I'm concerned, a pissed of controller means he cares about his job, the service he/she provides and cares about me learning something. Just don't be personal about it.
