December 7, 20205 yr Have an ongoing issue (tried a couple of times) with the flight plan shown below using cruise altitude of FL300. Using version 2.16.1.3_x64 on Window 10 and using "Co-Pilot Responds" option enabled. Also using the latest Navigraph data. The initial flight is fine up to the point that ATC should give a decent command with P2A Map shows proper decent point and the plan detail in P2A also showing the decent point. Howver instead of giving the command, nothing happens for a little while past that point and then it gives a "Cleared for ILS runway 28R" while I am still at FL 300! So decided to go ahead and descend on my own and follow the flight route and was not alterted by ATC about altitude or anyting else. After passing over the airport (approach was opposite direction from current flight path), was contacted by ATC to call the tower which Co-Pilot did. It then cleared me for landing runway 10! I went ahead and finished following my flight plane landing on Runway 28R which once done, the normal exit runway when able was given followed later by taxi to parking. Barton Whisler ====================== Flight Plan ================== 1100 version CYCLE 2013 ADEP KPIE DEPRWY RW36 SID PIE9 SIDTRANS PIE ADES KFLL DESRWY RW28R STAR FORTL7 STARTRANS PIE APP I28R NUMENR 2 1 KPIE ADEP 11 27.9087 -82.6865 1 KFLL ADES 65 26.07167 -80.1497
December 8, 20205 yr Commercial Member If you can email the log file for this flight to [email protected], I can have a look. 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. Dave
December 9, 20205 yr Commercial Member Thanks for the log. Just to follow up for others experiencing a similar issue. The flight plan needs to ensure that the beginning of the STAR is far enough away from the departure airport that you can get to cruise altitude before you enter the STAR or hit the TOD. In this case, the STAR began right at the departure airport so many of the "triggers" used by P2A could not be fired, so the flight didn't work. Dave
Archived
This topic is now archived and is closed to further replies.