Hello fellow community!
After finding some feature requests for unable, I thought of a well solution to reduce miscommunication between pilots and controllers, especially on approach.
Having the use of an expandable ‘Unable’ command would really help controllers manage a situation. This would reduce the amount of possible level 3 Violations and pilots unable to tell controllers what their issue is.
What I propose is adding the feature of multiple options for ‘the Pilot has control’ theory, to manage themselves in a well packed airspace, or preventing them from imminent danger. Linked below are many features that would utilize this. Some have already made this idea, but these would fall under the ‘sub-category’ of this request.
|ATC tab||In-game coms||ATC response||Description of use|
|Terrain||“Unable, terrain, EC-123”||“EC-123, copy terrain”||To be used when you are approaching terrain that you are too close to. This command is to be used to warn controllers of your danger.|
|Traffic||“Unable, Traffic alert, EC-123”||“EC-123, copy traffic”||To be used when you are certain you will exceed 3nm, and/or 1000ft between another aircraft on your new vector given.|
|Stall||“Unable, Stall imminent, EC-123”||“EC-123, copy stall alert, please maintain a manageable speed”||To only be used when you are being told say, in windy conditions, when you are being given a speed command, or when you are heavy, to prevent a stall from occurring.|
|Request Divert*||“Unable, requesting divert to nearest suitable airport, EC-123”||“EC-123, divert to nearest suitable airport”, or “EC-123, divert unable, please follow vectors.”||To be used as a last resort. Made for pilots who don’t believe they will make it to the airport, or for denied aircraft when they are being vectored.|
*Requesting a divert means there would have to be the controller replying with 'divert to nearest suitable airport added to this as a response, as well as the option of “EC-123, divert unable, please follow vectors.”
Pretty simple. The Unable prompt opens up a new tab where you select the option, and have to confirm it with the standard ‘send’ before sending it live onto the frequency.
More will be edited in once created suggested and approved by the community as part of the request. Screenshot was taken on 20/05/2020 in Toronto airspace, shortly after Approach had closed.
This means that the pilot would be able to potentially ‘deviate’ from the control, to get themselves to a safe path. This would reduce pilot-controller confusion, and would reduce Level 3 violations.
The controller would be able to acknowledge these unable commands. This would allow the controller to be aware of the pilot’s position if it does deviate from it’s vectored location. The controller would respond with a vector command after acknowledging the unable request, to give them a new heading and/or altitude to clear them of the danger they were previously unaware of.
I hope you can drop a vote to these, or one of the votes within the sub-categories of this command. If you have any more ideas that would be used for the pilot to not be able to follow the controllers command, then please go ahead and ask! I don’t bite.
Please do note I cannot physically vote for my request at this time, since I have about 5 over my normal amount as a Member from when I was a Regular.