Hi Dave, I have a somewhat related question. I just completed an IFR flight to KMSP (Minneapolis). My initial flight plan called for an RNAV approach to RWY 04 on arrival to KMSP. However enroute wind and visibility conditions changed such that an ILS approach to RWY 12R was the better choice. After being handed off from Center to KMSP Approach, I issued a request for radar vectors to the ILS approach for RWY 12R. I received no response from P2A, and it continued to direct me on the RNAV approach to RWY 04. I issued the same request several times with no luck.
This may be a consequence of my ATC config. I think maybe most relevantly, under Flt Plan/ATC Options I have the following checked:
Force Pilot Runway Selection
Match SIM Runway if Known (this works great for matching what XP has marked as the active departure runway)
I am still on XP10, and near as I can tell there is really no way to confirm in the sim which runway(s) XP has designated as active (other than listening to an ATIS report). So perhaps in the case described above XP was insisting on RWY 04 and P2A would not allow a pilot override under these circumstances. Or???
(notice that I am not talking about configuring preferred runways).
Perhaps you could just outline the best procedure for forcing a pilot-requested change to an alternate destination runway. It would even be kinda' nice to have the ability to issue such request prior to the approach transition phase; while perhaps not common practice, this would reduce tension/work load during the approach. Better yet, I think it would be helpful to have something like a "Force Active Runway" box somewhere on the main panel that allows the user/pilot to simply type in a valid runway number, hit "Apply," and P2A would thereafter just treat this runway as the active destination runway (unless of course a different value is subsequently entered). Ideally, one could do the same for the departure runway (i.e., without having to wait to change runways until issuing a taxi request -- this, in my view, is a bit awkward).
Again general speaking, I find entering values in the middle panel of the "Say It" dialogue to be a bit clunky. As I understand, one must first click on a request (one that requires entering a value), enter a relevant value, then hit "Enter," and then press "Say It" (notice that I do not use PTT). I also notice that when a request which requires entering a value -- say for a runway -- the value box is auto-populated with the current active runway. So this requires first deleting that value, or highlighting and then over-typing the desired value. It would be helpful, in my view, to just leave the values box for such requests empty (unpopulated) -- that's why I am issuing the request -- to specify a different value. Anyway, just a friendly suggestion...
Hope that was all clear enough, and thanks in advance for your help,