OnCourse Software

Dave, I had reported part of this issue in a different thread related to ATC not recognizing that I was at the correct flight level when cruising, but I also ran into a second issue during the flight so I figured I would create my own thread.

Here are the two issues I had during my flight from KJFK to KCLT.

1. When I entered the cruise phase of my flight I settled in at FL260 (with Std QOH), but ATC kept nagging me to maintain FL260. I eventually changed my altitude to 26500 and then the nagging stopped. This reminded me of the issue that had been reported previous to your 3.15.0 release and you had fixed it in that release, but perhaps it's something entirely different.

2. As I continued with this flight, ATC handed me off to approach, and assigned me to ILS approach 18L (going from memory here), and said to report back when I was established on final. As soon as I was established, I tuned to the tower frequency (118.1 I believe), and then hit Hotkey 1 to report in. I heard the "hotkey sound" letting me know the hotkey was registered, but that was it. From that point on PF3 seemed to be in a stuck state and I never heard anything back. I tried switching back to approach, then back to tower, tried different hotkeys, but I never got anything back from ATC. I eventually just finished up the landing without ATC and then ended the flight.

I've attached all of my logs that I collected after I ended the flight and disconnected PF3 from FS2020. Appreciate you taking a look whenever you have a chance. I'm not in a big hurry though. I mainly just reported this in case it helps you find any issues that might improve PF3 overall.

Thanks again for your outstanding support!

Dave, I just saw your reply in that other thread about my using an old version of FSUIPC. I'll update that and will start using it to see if it corrects these issues.

FWIW, followup flight with latest FSUIPC worked perfectly. I'll keep an eye on it. Consider this one closed though. Thanks.

Thanks for the feedback