Nelson L. wrote:Agreed on both points - just to clarify (is it just me or have I been using that phrase a lot?) -
If your radio has actually failed, I wouldn't classify it as disconnect-worthy unless your in the middle of a fly-in (provided your wing hasn't fallen off - i.e. you can safely keep going). Lost-comms situations can be great training for both pilots and controllers.
I'm thinking of this as stuff you want to know when starting out, not the PE Bible. That's a separate post.
Nelson L. wrote:Speaking of that, Keith, Peter, Tim, or "other", are the controller-induced failures still in consideration with the network growing at such a rapid pace? If so, if Peter or Keith is controlling, and the network is quiet, would you guys be OK with us putting in the remarks "feel free to fail radio" or "feel free to fail___"? It would add another dimension to the "training" aspect of the service, although I imagine its a lot of work to train controllers and implement such a system.
Good stuff, outside the scope of this post. Might be worth a new thread of your own.
Nelson L. wrote:Edit - Actually, I dispute the first claim - controllers can get very frustrated, especially if its busy. You can usually tell though; great incentive to not mess up...
I agree with you in general, but again, keeping with the spirit of the intended audience, I wouldn't want someone to get in over their head, think the controllers are jerks, then quit the service. Yes, the might be frustrated, but there's a real world simulation or standard to be met. In the real world, a controller would get frustrated with you but since PE is a learning environment too, there should be a relief valve of some type. It should be known it's OK to throw up your hands and say "I need to disconnect" instead of plowing along into chaos. It was one of the things I was most nervous about when I started.