August 7, 20205 yr My home airport is RPLL(Ninoy Aquino International Airport) in the Philippines Upon airborne 5nm away from the airport, ATC should hand me off to Departure(119.90) but this does not happen. What I expect to happen is "Contact departure on 119.90" and co-pilot replies and automatically switches to departure and makes an initial call. I have the use the co-pilot options checked(responds to radios and changes frequencies) Take note that this only happens at this specific airport. In all other airports I do not encounter this problem, ATC hands me off to departure. My workaround for this is I manually tune to Departure(119.90) when I am 5nm away from the airport and co-pilot reports "Deparute, Callsign Climbing to FLXXX" and flight proceeds normally. Edited August 7, 20205 yr by titofraginal
August 7, 20205 yr Commercial Member Please email the log file for that flight to me at [email protected]. P2A Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab. A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one. Thanks, Dave
Archived
This topic is now archived and is closed to further replies.