I’ve been using planner.flightsimulator.com to do my route planning, but have been having a hard time reading the Briefing / Nav Log page. I think I understand the formatting, but all of the ETE and ETO entries seem to be scrambled? Am I missing something? If you switch the view to OFP mode they all make sense, but it’s overall a bit harder to read.
I’ve included a screenshot below of a VFR route with multiple legs. Second screenshot is of the relevant section of the OFP printout.
ETE is the estimated time for that leg calculated approximately from groundspeed and distance.
ETO is estimated total time for the flight. Calculated using the previous ETO and adding the current ETE.
Same for ATE and ATO except these are the actual times that should be recorded. If there is a difference between ETE and ATE, try to determine why. If ATE is significantly greater than ETE, make sure there is enough fuel remaining.
That’s what I thought, but it doesn’t explain why the Nav Log above shows a 14.5nm leg taking 12min 12sec, then a 10.1nm leg taking 33 seconds, then a 9.7nm leg taking 12min 27sec, and then a 32nm leg taking 8min 27sec. Not to mention the ETO times are all over the place for sequential waypoints. I’m guessing this is just a weird bug with the web page after all.
I took another look at your flight plan. Disregard what I said earlier as my abbreviations were incorrect. ETE is Estimated Time Enroute. ETO is Estimated Time Over (waypoint) in UTC, that is clock time, not elapsed time.
Everything else looks good!
