Some more observations in Martin's last log:
01/04/2016 16:40:44: 850 - -----------------------------
01/04/2016 16:40:44: 850 - Step Climbs for Waypoint: 3
01/04/2016 16:40:44: 850 - -----------------------------
01/04/2016 16:40:44: 850 - 34000'
01/04/2016 16:40:44: 850 - -----------------------------
01/04/2016 16:42:39: 880 - Checking compliance - Alt: 33660 sWPAlt: 34000 FlightType: 1 ATC_Timer: 0 AltTimer: 0 FSTime: 60159 AptSighted: 0 Handoff: 0
01/04/2016 16:42:39: 900 - TOD recalculated now distance is set to 232 NM
01/04/2016 16:42:39: 920 - ****** Reached TOD ******
01/04/2016 16:42:39: 920 - BPT: 0
01/04/2016 16:42:39: 920 - -----------------------------
01/04/2016 16:42:39: 920 - Step Climbs for Waypoint: 3
01/04/2016 16:42:39: 920 - -----------------------------
01/04/2016 16:42:39: 920 - 15000'
01/04/2016 16:42:39: 920 - -----------------------------
01/04/2016 16:42:43: 700 - Checking compliance - Alt: 33768 sWPAlt: 15000 FlightType: 1 ATC_Timer: 0 AltTimer: 0 FSTime: 60163 AptSighted: 0 Handoff: 0
01/04/2016 17:01:32: 110 - -----------------------------
01/04/2016 17:01:32: 110 - Step Descents for Waypoint: 5
01/04/2016 17:01:32: 110 - -----------------------------
01/04/2016 17:01:32: 110 - 24000'
01/04/2016 17:01:32: 110 - 10000'
01/04/2016 17:01:32: 110 - 8000'
01/04/2016 17:01:32: 110 - -----------------------------
01/04/2016 17:01:35: 860 - Transcript: 'Air India 3205 Descend and maintain Flight Level 240 '
|
So you reached the TOD calculated by PF3 at 208 NM from the destination (not the 232 NM shown above), but this was before you reached the cruising altitude.
Some things in PF3 are only triggered after the cruising altitude is reached and I think some only at waypoints. It seems PF3 was heavily confused by this situation.
If you could do the climb a little bit faster, or set the cruise altitude a little bit lower, or maybe add some waypoints for PF3 to work with, or maybe fly in an area where PF3 inserts XXX waypoints for control center boundaries, this should already work with the current version of PF3.
Wow, these are many if, ors and maybes, but I assume Dave can find a solution (or at least a workaround) for such situations. But as it is important to not break other parts of PF3 while fixing this, we should let him take the time he needs to make a good decision on how to solve this predicament.