Sorry, we don't support your browser.  Install a modern browser

Please add an OPTION to override BATC's ATIS runway restriction#1329

N

I see using Simbrief’s choice of departure runways over BATC”s ATIS’ runway restriction was voted on 45 times now and no change. And I see overriding BATC’s ATIS was rejected. PLEASE reconsider the OPTION to override this and here are two fresh examples:

  1. After ample pre-flight work, I learn Rwy 3 is the only runway at KBJC’s airport I can depart on. Problem is this short strip is too short for the Longitude I’m in. Please appreciate this is a simulator, not the real world. So I have to abort, or change the load, or use the appropriate runway from Simbrief which was 12L, much longer and always used for commericial aviation. Again, this is a simulator for the enjoyment of users, it’s not the real world. Make it an option so that those who wish to simulate RW operations can go there as desired.

  2. Far worse than #1 was the landing at KSBA the other day, in the Longitude. BATC ATIS says only Rwy15L in use and yet that runway is only used in the RW for T&G’s in light planes, or departures only over the Pacific. I was coming in from KRNO and this routes me directly over the mountains north of Santa Barbara with a 4500’ descent in few miles to land on Rwy15L. Clearly BATC’s ATIS does not consider everything, and ATC in the RW does, has to! And there was zero regional traffic then to boot.

And just now, scheduled KTEX to KGSU, BATC givees me Rwy 9, yet once again no traffic in the area of this 9000’ elevation airport and a 5kt wind from 60 degrees. Rwy 9 is used FOR LANDINGS, and 27 for TAKEOFFS. Any pilot in his right would never use 9 here so I guess what BATC devs are expecting is users to just ignore its instruction? WE NEED THE OPTION TO OVERRIDE BATC ATIS which appears to only look at ONE ELEMENT: wind. Not good!

a year ago
Changed the status to
Rejected
20 days ago