Hi Dave

  Still seeing descent altitude problems with what p2a is calculating.  picture attached.  the route i was taking was: AKUNA7 MLC SGF J105 WELTS TRTLL4.

  You can it took me down to 11000 then the altitudes went up again.

  https://photos.app.goo.gl/dJ2UiDearS8VUBTU6

Joe

 

Oh, I just saw there was an R2 and R3 of 2.5.0.6 with altitude calculation fixes.  Let me try the latest with the same flight plan.

Joe

 

Whoa, 2.5.0.6R3 is worse.  same flight plan as above.  new screen shots below.  I had the altitude set to FL 350, but it put plan altitudes at FL 450., and the descent altitudes still go back up.  Not sure if this matters, but my waypoint input order was:  KDFW, KORD, SID, STAR, APPR, SGF, J105 to WELTS.

Let me know if you need the log.  

takeoff to TOD: https://photos.app.goo.gl/nBx6cjWdVqxt4wjN7

TOD to landing: https://photos.app.goo.gl/JzqAtXyiSR4UZNsXA

SID, Star, Appr: https://photos.app.goo.gl/Dn8yxBZ1WQ7mT4LF6

Thanks,

Joe

 

Edited November 10, 20187 yr by mihalich

Thanks Joe.

There will be some additional fixes in R4 that hopefully will fix the altitude issues.

The order of entry will affect the procedures selected by P2A.  The best order in this case would be 

KDFW, KORD, SGF, J105 to WELTS, SID, STAR, APPR

However, that is not what caused the altitude problem.

Cool, thanks.

Joe