With the introduction of ATIS, I am proposing a simple change to the menu system to hide the “Remaining in the Pattern” option from pilots where particular conditions are met.
What am I asking for?
I am asking to do not display the “Remaining in the Pattern” option if any of the conditions are met:
The controller has selected “No Pattern Work” in the ATIS remarks.
The visibility in the airport METAR is below 3SM.
What does this add to the sim?
Realism!
Assists controllers who constantly have to give the “no pattern work” reply because people did not read the ATIS.
Fine Print…
Not asking for changes to unicom
Not asking for changes to ATC menus, just the pilot menu
Voted for this, as it reinforces the (real-world) decisions made by tower controllers. Wouldn’t this make the “No Pattern Work Allowed” command obsolete though? Or maybe that’s the point…
I meant more along the lines of no need to have it if they don’t need to select it. I think I’m getting at the wrong side of this request. Forget I said anything.
“Realism” (insert TimB trademark symbol here) would be the ‘expert’ pilot understanding/using the METAR and ATIS and knowing from those two sources that pattern work is not accepted in the first place.
Seems maybe a little excessive on the hand holding, but I’m all for making life easier on the controller side of things.
It should be a ghost if they request pattern work with the ATIS restricting it, but I guess this is in some cases restricts pilots who don’t actually read the ATIS, from requesting pattern work. $10 someone makes a support topic why they can’t request pattern work… If this were to be added :)
It should also be hid if they have a flight plan filed and they plan on departing the airspace. I get tired of them using that command then requesting departure or frequency change. It gets very annoying!
After global was released I have seen many pilots will file a flight plan, do a pattern or two, and then depart the airspace. You get a landing or three in and then continue on your 15 hour flight.
As Chris mentioned, I tend to do that before a long haul to ensure my device doesn’t crash. I think just hiding the feature during pattern work before departing the airspace wouldn’t be nessacary
This sort of cange is a slippery slope. You make one change and then every button gets a workover and tried to over automate it. I was just trying to fix a specific issue at hand.
I understand that and that doesn’t bother me. It only annoys me when they say remaining in the pattern and they never do touch and go’s. That’s all I was trying to say. I completely understand doing pattern work then departing out.