does this make sense?

Everybody has their own little twists to it, but in a nutshell, it's pretty much right-on to me.

I use the same numbers when I'm guesstimating ETDs and ETAs, only depending upon the route, I may even use 40mph for a portion of the route to be on the safe side (for example, pulling a heavy load out of rural PA, WV, or other such hilly area...weather conditions play into that as well).

But the slides keep it simple...you don't want to bog down newbies with every conceivable issue, because you can't, and the slides don't.

 

Seems like a pretty good explanation to me. That's how I learned, but without the fancy computer slide show. I usually take my driving time, add 10 hour break, then add 2 hours per day for each day of the trip (if it's a long trip) for bathroom break, fuel stop, lunch, etc. If you can read a map you should be able to figure out where you're going to stop for the night and then use reference materials to find a place to stay.

 

Simplest way I've found is to assume 10 mph below posted limits (or governor limits), and assume a 12 hour day (leaving an hour for breaks). It usually gets me there early, so I always have a buffer.

 

It's called Microsoft trips and streets, how do u know your routing doesn't take you down nightmare on Elm street, u don't till u get there, unless your me and you already been there, twice.