Lorenzo Stobbione 1368867 Posted December 30, 2016 at 04:32 PM Posted December 30, 2016 at 04:32 PM Hi all! I'm opening this topic to ask what is the best Vatsim behavior in case of any issues during landing/takeoff procedures not directly connected with simulation itself but connected with PC, hardware and other issues which are not part of the simulation. I am not speaking of errors like Missed approach, or rejected takeoff but issues like controller frozen, graphic card drivers no more working... so things which typically do not have anything connected with simulation. For example: due to an hardware driver issues I discovered after having just touched down that my brakes were simply not working even if they had been [Mod - Happy Thoughts]igned to a button. Due to this "small" issue I had to manage all the deceleration with thrust reversers with the result that the aircraft did not stop in time. Since it was a busy day I disconnected immediately in order to avoid issues for other pilots... but my question is: in a situation like this what is the Vatsim recommended behaviour? If for any external reason (like mine, controller not fully working due to driver conflict, PC issues or so) the takeoff/landing process becomes unmanageable it is correct to disconnect and disappear in order not to impact others? Thank you!! PS: I have a "PC checklist" which I execute before taxing in order to be sure everything is ok but sometimes windows is... unpredictable! Lorenzo Stobbione P1 Rating - VATSIM Online Pilot P2 Rating - VATSIM Flight Fundamentals Link to comment Share on other sites More sharing options...
Robert Shearman Jr Posted December 30, 2016 at 05:18 PM Posted December 30, 2016 at 05:18 PM I discovered after having just touched down that my brakes were simply not working even if they had been [Mod - Happy Thoughts]igned to a button. Due to this "small" issue I had to manage all the deceleration with thrust reversers with the result that the aircraft did not stop in time. Since it was a busy day I disconnected immediately in order to avoid issues for other pilots. {...} it is correct to disconnect and disappear in order not to impact others? It's never wrong to disconnect if you feel you're potentially impeding others' enjoyment of the network. Depending on exactly what failed, you could try to remain online and cope with it, treating it as a simulation of real-world control failure. If your situation requires special handling from ATC, you can request it, and the worst you'll hear is "unable, please disconnect to continue simulating your emergency." But in some cases, particularly if it's not busy, the controller will be able and willing to do what they can to accommodate, so you can both enjoy the challenge of trying to save your life and your equipment as if it had happened in the real world. (Fortunately, in this case, you get to walk away unscathed regardless of success or failure!) But certainly in your example, where you pointed out that it was a busy day, getting out of everyone's way was certainly not a bad course of action. sometimes windows is... unpredictable! Yeah, that was the nice way to say it, LOL... Cheers, -R. Link to comment Share on other sites More sharing options...
Lorenzo Stobbione 1368867 Posted December 30, 2016 at 05:46 PM Author Posted December 30, 2016 at 05:46 PM Well, it's good to know that the choice of disconnecting does not create issues with the controller Theoretically I also had the occasion of engaging TOGA button as soon I discovered brakes were not working and performing a touch and go but I am not so sure to know how to handle the aftermath (in terms of communication ) Yes... Windows is an unpredictable resource eater.. I calculated that if Win could free as many resources as Linux while executing XPlan I could comfortably hit the ceiling of Vsync with details maxed out... But that's the way it is.. Lorenzo Stobbione P1 Rating - VATSIM Online Pilot P2 Rating - VATSIM Flight Fundamentals Link to comment Share on other sites More sharing options...
Robert Shearman Jr Posted January 2, 2017 at 03:10 AM Posted January 2, 2017 at 03:10 AM Theoretically I also had the occasion of engaging TOGA button as soon I discovered brakes were not working and performing a touch and go but I am not so sure to know how to handle the aftermath (in terms of communication) No different than calling a Missed Approach for any other reason. It's not common to go Missed after making contact with pavement, but I'm sure it does happen (VATSIM and real world) from time to time and the considerations for ATC would be the same as going missed after Decision Height. Start executing the published missed, inform ATC when able, and either continue to fly the procedure or follow whatever overriding instructions they give you. Cheers, -R. Link to comment Share on other sites More sharing options...
Lorenzo Stobbione 1368867 Posted January 2, 2017 at 10:11 AM Author Posted January 2, 2017 at 10:11 AM Thank you Rob for the answer, I'm still learning how to handle communications since I began flying with voice only after I began rating cl[Mod - Happy Thoughts]es with italian division. So, as the golden rule says, in a complex situation like that I should: 1) Fly the plane 2) Contact ATC as soon as I will have the control Thank you Lorenzo Lorenzo Stobbione P1 Rating - VATSIM Online Pilot P2 Rating - VATSIM Flight Fundamentals Link to comment Share on other sites More sharing options...
Recommended Posts