Two nights ago, I twice tried to land at John Wayne. Both times, shortly after initiating contact with Socal approach, Xplane crashed and dumped me back at the desktop. (This is, I suspect, because I am running the 32-bit version of Xplane on OSX and ran out of memory, so I anxiously await the availability of the 64-bit plugin on the 17th.)
I don't want to seem rude or inconsiderate in any way to the controllers, and I'm sure it's a little frustrating to have them start working with an aircraft only to have it disappear with no explanation. Is there anything I can or should do in this case to contact the controllers (maybe offline?) to let them know "hey, I was not being rude or stupid, I just had a computer software malfunction"? (Sorry to whomever was working two nights ago, around 11:00 EST!)
Similarly, is there a protocol one should use if they're in the middle of working with ATC on Pilot Edge and some real-life urgency arises and we need to go suddenly?
Thanks,
Protocol if real-life causes communication break?
-
- Posts: 19
- Joined: Mon Jun 02, 2014 6:55 am
-
- Posts: 5716
- Joined: Tue Oct 12, 2010 3:21 pm
Re: Protocol if real-life causes communication break?
Hello,
To answer your questions.
We do ask if you disconnect and reconnect more then a few seconds later you give us a call when you get back (otherwise we will quickly forget about you and may not notice you're back).
Let me know if you have any other questions.
To answer your questions.
We are used to sudden disconnections (I see several a day), we know they happen, and we know it's not you being rude or anything like that. So in simple terms don't worry about it. There is no need to apologize for it.I don't want to seem rude or inconsiderate in any way to the controllers, and I'm sure it's a little frustrating to have them start working with an aircraft only to have it disappear with no explanation. Is there anything I can or should do in this case to contact the controllers (maybe offline?) to let them know "hey, I was not being rude or stupid, I just had a computer software malfunction"? (Sorry to whomever was working two nights ago, around 11:00 EST!)
We do ask if you disconnect and reconnect more then a few seconds later you give us a call when you get back (otherwise we will quickly forget about you and may not notice you're back).
Just a quick "Center/Approach/Tower something has come up and I'll have to disconnect at this time" works just fine.Similarly, is there a protocol one should use if they're in the middle of working with ATC on Pilot Edge and some real-life urgency arises and we need to go suddenly?
Let me know if you have any other questions.
-
- Posts: 19
- Joined: Mon Jun 02, 2014 6:55 am
Re: Protocol if real-life causes communication break?
Thanks Peter!
-
- Posts: 17
- Joined: Thu Sep 22, 2011 8:21 am
Re: Protocol if real-life causes communication break?
I know I've asked for a couple of minutes "off the flight deck" on occasion. It's always been graciously granted, just "report when back". Is that ok or would you prefer we disconnect and then reconnect when back.
Dave
Dave
Dave Paige
Private Pilot
Instrument Airplane; ASEL
Private Pilot
Instrument Airplane; ASEL
-
- Posts: 5716
- Joined: Tue Oct 12, 2010 3:21 pm
Re: Protocol if real-life causes communication break?
Stay connected, that way we know where you are. If you disconnect and reconnect we won't know exactly where you are reappearing.I know I've asked for a couple of minutes "off the flight deck" on occasion. It's always been graciously granted, just "report when back". Is that ok or would you prefer we disconnect and then reconnect when back.