November 13, 20187 yr Hi Dave, Running 2.5.0.6 R5, and getting a message saying can't calculate TOD as shown in the screen shot. My flight plan is: KTPA SYKES7 SIMMR REMIS Y280 LEV LINKK1 KIAH. I put in altitude of 32000, which should be attainable. screen shot: https://photos.app.goo.gl/essKAHDrkGSt21Ct7 Thanks, Joe
November 13, 20187 yr Author Hmm, i changed the descent rate to 2200, and that fixed it. You'd think it would have been able to calculate the TOD with 2000, and have it just pushed back a little. Joe Edited November 13, 20187 yr by mihalich
November 13, 20187 yr Commercial Member I just tried it and it worked at 1500, 1800 and 2000 FPM. Did you press the Validate button? Let me know if it happens again. Thanks, Dave
November 14, 20187 yr I don't get this message but the TOD Dist and TOD ETE are both blank even though a TOD marker is onscreen.
November 14, 20187 yr Commercial Member Usually pressing Validate button will remedy this. If not, there could be an issue with the combination of route length, Climb Rate, GS, Cruise altitude and Descent rate. For example, TOD might occur before the plane reaches Cruise altitude. Dave Edited November 14, 20187 yr by Dave-Pilot2ATC
Archived
This topic is now archived and is closed to further replies.