JohnY wrote: * | Mon May 08, 2017 3:34 pm |
Yes, well, that didn't work either. I decided on runway 26 and asked for it. The acknowledgement was for runway zero.
Here is the corresponding log:
08/05/2017 14:18:21: 930 - Transcript: ' Juliet Charlie Yankee 633 at Hotel Lima Charlie Descend and maintain 7 thousand on 2989
Cleared to final for Sierra Tango Approach runway 17 at pilot's discretion Contact Tower on 119.1 when established. '
08/05/2017 14:18:38: 450 - Transcript: 'Roger Out of Flight Level 180 for 7 thousand at Hotel Lima Charlie until established on final for runway 17
Tower on 119.1 when established. Juliet Charlie Yankee 633 '
08/05/2017 14:18:57: 090 - Transcript: ' Juliet Charlie Yankee 633 Reduce speed to 300 '
08/05/2017 14:19:04: 360 - Transcript: '300 Juliet Charlie Yankee 633 '
08/05/2017 14:19:09: 490 - ****** HotKey #13 detected!
08/05/2017 14:19:12: 690 - FS Screen : Use runway 17 ? - C/S/Y for Yes, or C/S/N for No
08/05/2017 14:19:18: 810 - ****** HotKey #15 detected!
08/05/2017 14:19:32: 160 - ****** HotKey #13 detected!
08/05/2017 14:19:32: 180 - FS Screen : Closed Captioning OFF
08/05/2017 14:19:33: 240 - ****** HotKey #13 detected!
08/05/2017 14:19:36: 570 - FS Screen : Use runway 17 ? - C/S/Y for Yes, or C/S/N for No
08/05/2017 14:19:49: 720 - ****** HotKey #17 detected!
08/05/2017 14:19:49: 720 - FS Screen : Use runway 26L ? - C/S/Y for Yes, or C/S/N for No
08/05/2017 14:20:38: 320 - ****** HotKey #2 detected!
08/05/2017 14:20:43: 870 - ****** HotKey #2 detected!
08/05/2017 14:20:45: 140 - Transcript: 'Approach Juliet Charlie Yankee 633 request an instrument approach '
08/05/2017 14:20:52: 270 - Transcript: 'Stand by. We'll check '
08/05/2017 14:21:12: 080 - ****** HotKey #13 detected!
08/05/2017 14:21:12: 270 - FS Screen : Use runway 26R - ILS ? - C/S/Y for Yes, or C/S/N for No
08/05/2017 14:21:31: 820 - ****** HotKey #16 detected!
08/05/2017 14:21:31: 910 - Transcript: ' Juliet Charlie Yankee 633 request runway 0 '
08/05/2017 14:21:40: 110 - Transcript: 'Approach Juliet Charlie Yankee 633 request an instrument approach '
08/05/2017 14:21:47: 250 - Transcript: 'Stand by. We'll check '
08/05/2017 14:22:02: 430 - Transcript: ' Juliet Charlie Yankee 633 Runway change approved continue Approach runway 0 '
08/05/2017 14:27:10: 840 - ****** HotKey #13 detected!
08/05/2017 14:27:10: 980 - FS Screen : Use runway 26R - ILS ? - C/S/Y for Yes, or C/S/N for No
08/05/2017 14:27:35: 580 - ****** HotKey #16 detected!
08/05/2017 14:27:35: 720 - Transcript: ' Juliet Charlie Yankee 633 request runway 0 '
08/05/2017 14:27:44: 890 - Transcript: 'Approach Juliet Charlie Yankee 633 request an instrument approach '
08/05/2017 14:27:51: 020 - Transcript: 'Stand by. We'll check '
08/05/2017 14:28:06: 220 - Transcript: ' Juliet Charlie Yankee 633 Runway change approved continue Approach runway 0 '
|
HotKey #2 (during Approach) is Request an instrument approach
HotKey #13 (during Approach) is Select another runway for landing
HotKey #15 is Toggle Captions
HotKey #16 is Yes
HotKey #17 is No
You pressed HotKey #13, but during that pressed HotKey #15, then twice HotKey #13 again.
Before confirming a runway with HotKey #16 you asked for an instrument approach using HotKey #2 twice.
Before the second press of HotKey #2 was processed, you requested (#13) and confirmed (#16) a runway change.
At this point PF3 was confused enough to give you runway 0 and reply to the second request for an instrument approach.
Yes, this confusion is a bug, but I don't know if the time needed to fix this should be invested by Dave here, but of course this is his decision.
But he just wrote in the beta forum that he fixed the original issue that requesting an instrument approach does not come back to you
JohnY wrote: * | Mon May 08, 2017 3:34 pm |
A further thing I don't understand is that since the update I don't think I've once been given an instrument landing. Is this coincidence or has the update upset the apple cart somehow?
If it has. Is there a way I can disable the update and go back to what we had before?
Looks like coincidence to me. I did not check in this log (dinner time), but in the previous logs it was always the best runway for the current wind direction.
Rolling back to a previous release is possible, but complicated enough to not recommend it.