January 20, 20197 yr Since some time I noticed ATC is very strict with assigning higher altitudes during departure climb. For example, my last flight took me out of ENBR via the REKL1C departure. I filed a Cruise Alt of 280 and the departure part of the flight plan looked like this: ENBR RW17 UNPUT (5000ft) BR521 (FL075) GISUK (FL120) REKLI (FL240) VALDI (FL280) ... I was cleared to 4000 ft initially, then i was cleared to FL100, which i reached after UNPUT. I had to level off as I didn't receive a higher clearance. At waypoint BR521 I was cleared to FL120 which i reached shortly after just to level off again. At GISUK I was given FL240, had to level off again for 20 nm until i finally was cleared to FL280 when passing REKLI. So it looks like ATC will strictly stick to the altitudes which where calculated in my flight plan, even if I clearly could climb much faster. This was not the case previously, I think it started with one of the last versions of P2ATC. Another thing I noticed is that P2ATC seems not to allow to change the altitudes for waypoints, it would always revert back to the automatically calculated altitudes after I press validate. Did somebody notice same behavior recently?
January 20, 20197 yr Commercial Member Please email me ([email protected]) the P2A log file so I can see if this is a bug. 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, so if you take the most recent one when you have the error, you should have the correct one. Thanks, Dave
Archived
This topic is now archived and is closed to further replies.