OnCourse Software
http://www.ocs-support.co.uk/forums/

Being Told By Center To Contact Advisory On Current Frequency
http://www.ocs-support.co.uk/forums/viewtopic.php?t=2462		 Page 1 of 2
Author:  dtsakiris [ Thu Mar 16, 2017 11:11 am ]
Post subject:  Being Told By Center To Contact Advisory On Current Frequency
Hello everbody,

on my last flight (freeware EDMA to default LIPB), I think I stumbled across a problem.

The default LIPB has only one frequency, FSS on 120.600. After consulting the appropriate charts, I changed that in PF3 and set UNICOM to 120.600 and FSS to 124.150.

The approach was a handful, to say the least (and it also was my first flight in Carenado's C25A), but I'm pretty sure when Center cleared my approach and asked for 1200, he told me to contact advisory on his own frequency (124.450, if I recall correctly).

I noticed this also on an earlier flight, 2S1 to 7WA3, both from ORBX. Since 7WA3 is a private airport, it doesn't have a CTAF, and then I thought PF3 just can't handle this case. Has anyone else seen this?
Author:  Dave March [ Thu Mar 16, 2017 11:13 am ]
Post subject:  Re: Being Told By Center To Contact Advisory On Current Frequency
Please zip and attach the logs files from your PF3/Logs folder so we can take a look... without the logs we have no idea what happened
Author:  dtsakiris [ Thu Mar 16, 2017 1:48 pm ]
Post subject:  Re: Being Told By Center To Contact Advisory On Current Frequency
Of course, but that will be this evening. Thanks.
Author:  dtsakiris [ Thu Mar 16, 2017 7:04 pm ]
Post subject:  Re: Being Told By Center To Contact Advisory On Current Frequency
Here's the log!
Author:  Dave March [ Fri Mar 17, 2017 10:25 am ]
Post subject:  Re: Being Told By Center To Contact Advisory On Current Frequency
Quote:
The approach was a handful, to say the least (and it also was my first flight in Carenado's C25A), but I'm pretty sure when Center cleared my approach and asked for 1200, he told me to contact advisory on his own frequency (124.450, if I recall correctly).
No that didn't happen.

8:45 you were instructed to contact control on 125.45, which you did

8:52 you were instructed to contact control on 129.2, which you did

But then at 8:56 you changed back to 125.45

So yes there is an issue here but not what you thought... PF3, although recognising you changed frequency (it logged the event), it carried on but should really have gone quiet on you! Maybe in the future I'll just generate some static should this happen and emulate a dodgy squelch till you rectify it and retune to the correct frequency. :)
Author:  dtsakiris [ Fri Mar 17, 2017 11:49 am ]
Post subject:  Re: Being Told By Center To Contact Advisory On Current Frequency
dmarch wrote: *  Fri Mar 17, 2017 10:25 am
8:45 you were instructed to contact control on 125.45, which you did

8:52 you were instructed to contact control on 129.2, which you did

But then at 8:56 you changed back to 125.45
But that was enroute, or not? I'm pretty sure (and will check that later) that enroute, I had an event of "lost comms". I then had to check via PF3 Displayer and 125.45 was twice in the "Ctrl Freq" list, with another frequency in between (probably 129.2 then). That's why I changed back to 125.45.

Can you please paste the line from when PF3 clears me for approach?
Author:  vololiberista [ Fri Mar 17, 2017 1:58 pm ]
Post subject:  Re: Being Told By Center To Contact Advisory On Current Frequency
dtsakiris wrote: *  Fri Mar 17, 2017 11:49 am
dmarch wrote: *  Fri Mar 17, 2017 10:25 am
8:45 you were instructed to contact control on 125.45, which you did

8:52 you were instructed to contact control on 129.2, which you did

But then at 8:56 you changed back to 125.45
But that was enroute, or not? I'm pretty sure (and will check that later) that enroute, I had an event of "lost comms". I then had to check via PF3 Displayer and 125.45 was twice in the "Ctrl Freq" list, with another frequency in between (probably 129.2 then). That's why I changed back to 125.45.

Can you please paste the line from when PF3 clears me for approach?
Quote:
3/15/2017 8:52:01 PM: 170 - Transcript: ' Delta Charlie Alpha Mike Charlie Contact VIENNA RADAR on 129.2 '
3/15/2017 8:56:08 PM: 010 - Transcript: ' Delta Charlie Alpha Mike Charlie '
3/15/2017 8:56:19 PM: 900 - ****** FreqChange flag reset to ZERO
3/15/2017 8:56:20 PM: 900 - Not tuned to any 'active' ATC facility!
3/15/2017 8:57:56 PM: 220 - Transcript: ' Delta Charlie Alpha Mike Charlie 19 miles from Bravo Alpha Kilo Oscar Romeo at 1559 local '
3/15/2017 9:03:35 PM: 840 - Transcript: ' Delta Charlie Alpha Mike Charlie expect vectors for the ILS runway 01 '
3/15/2017 9:04:01 PM: 620 - Transcript: ' Delta Charlie Alpha Mike Charlie Turn right heading 300 '
3/15/2017 9:04:17 PM: 000 - Transcript: ' Delta Charlie Alpha Mike Charlie Descend and maintain 4 thousand on 1026 '
3/15/2017 9:04:31 PM: 500 - Transcript: ' Delta Charlie Alpha Mike Charlie Reduce speed to 150 '
3/15/2017 9:05:16 PM: 870 - Transcript: ' Delta Charlie Alpha Mike Charlie Turn right heading 340 '
3/15/2017 9:05:31 PM: 160 - Transcript: ' Delta Charlie Alpha Mike Charlie Cleared for the ILS runway 01 Approach Radar service terminated. Squawk 1200, change to advisory frequency approved on 129.2 descend on ILS '
You didn't change frequency.
Author:  dtsakiris [ Fri Mar 17, 2017 2:21 pm ]
Post subject:  Re: Being Told By Center To Contact Advisory On Current Frequency
Thanks. 129.2 isn't the right frequency, as far as I can tell. I explicitly entered (and double-checked) 120.600 as UNICOM. Does the log reflect this (and the other entry I made for FSS)?

P.S.: I wish the logs weren't "encrypted"... :cry:
Author:  vololiberista [ Fri Mar 17, 2017 2:22 pm ]
Post subject:  Re: Being Told By Center To Contact Advisory On Current Frequency
dtsakiris wrote: *  Fri Mar 17, 2017 2:21 pm
Thanks. 129.2 isn't the right frequency, as far as I can tell. I explicitly entered (and double-checked) 120.600 as UNICOM. Does the log reflect this (and the other entry I made for FSS)?

P.S.: I wish the logs weren't "encrypted"... :cry:
They have to be to protect them from nifty fingers!
Author:  dtsakiris [ Fri Mar 17, 2017 2:41 pm ]
Post subject:  Re: Being Told By Center To Contact Advisory On Current Frequency
vololiberista wrote: *  Fri Mar 17, 2017 1:58 pm
Quote:
3/15/2017 8:52:01 PM: 170 - Transcript: ' Delta Charlie Alpha Mike Charlie Contact VIENNA RADAR on 129.2 '
3/15/2017 8:56:08 PM: 010 - Transcript: ' Delta Charlie Alpha Mike Charlie '
3/15/2017 8:56:19 PM: 900 - ****** FreqChange flag reset to ZERO
3/15/2017 8:56:20 PM: 900 - Not tuned to any 'active' ATC facility!
3/15/2017 8:57:56 PM: 220 - Transcript: ' Delta Charlie Alpha Mike Charlie 19 miles from Bravo Alpha Kilo Oscar Romeo at 1559 local '
3/15/2017 9:03:35 PM: 840 - Transcript: ' Delta Charlie Alpha Mike Charlie expect vectors for the ILS runway 01 '
3/15/2017 9:04:01 PM: 620 - Transcript: ' Delta Charlie Alpha Mike Charlie Turn right heading 300 '
3/15/2017 9:04:17 PM: 000 - Transcript: ' Delta Charlie Alpha Mike Charlie Descend and maintain 4 thousand on 1026 '
3/15/2017 9:04:31 PM: 500 - Transcript: ' Delta Charlie Alpha Mike Charlie Reduce speed to 150 '
3/15/2017 9:05:16 PM: 870 - Transcript: ' Delta Charlie Alpha Mike Charlie Turn right heading 340 '
That was my "loss of communications". As far as I can recall, I tried to change from 125.45 to 129.2, but for some reason got no reply. It was then when I opened PF3 Displayer to check. I think I saw the next and last frequency was 125.45, so I went (back) to that one. But I then had trouble contacting control, which is why I also tried the position report.

Can someone please read out the sequence of control frequencies for the flight? Or maybe provide the decrypted log file...
vololiberista wrote: *  Fri Mar 17, 2017 1:58 pm
Quote:
3/15/2017 9:05:31 PM: 160 - Transcript: ' Delta Charlie Alpha Mike Charlie Cleared for the ILS runway 01 Approach Radar service terminated. Squawk 1200, change to advisory frequency approved on 129.2 descend on ILS '
You didn't change frequency.
No, at that moment in the approach I didn't change to 129.2, because I considered it to be the wrong frequency.
vololiberista wrote:
They have to be to protect them from nifty fingers!
Maybe two log files, one encrypted and one not? I'd love to be able to check these things myself before I bother you guys.
Page 1 of 2 All times are UTC+01:00
Powered by phpBB® Forum Software © phpBB Limited