Trip Planning "Coefficients?"

Throw Garmin out the window and get an atlas

 

you are wanting a mathmatical formula that is virtually impossible due to variables. the 21 mph avg on the garmin is entirely misleading.

one guy gave you the best way take total miles divide by 50 that gives driving hours then from driving hours figure the number of breaks but figure them as 12 hour breaks , that will get you close . and do your eating on your 10 hour break

and if the preplan doesnt work out , so what?/ let know you will be late. unless you are hauling a heart for a transplant , dont sweat it.

go to love how the megas drive new guys nuts about a "preplan" like its the end all be all.

fact is a mega carrier dm should have each drivers avail hours on his qualcomm and in 30 seconds tell if a guy can make delivery, but then that would require common sense would it not.

in a perfect world where we all got loading in 30 minutes, no one wrecked, it never snows , and unloaded in 30 minutes you could do that. but frankly if you insist on a benchmark. use 25 mph and go from there.

 

That's how I ran 32 days straight without a reset. The Load planners knew exactly what my hours were.

sent from Droid RAZR. DrtyDiesel

 

I noticed this low mph average too, but I've never considered it. Because I know those numbers take into account a lot of down-time that is not relevant when I'm running. And when I have a load... I'm running.

If I have a load that is 769 miles. I think, uihh.. 500-600 miles a day easy, 10 hrs or less. That leaves 3-4 hours for the next day... 10 hour break between. so... 24 hours tops. Done.

I'll go into a bit more detail besides the above, because I like to be precise. I'm always on my ETA unless something falls apart on the way.

 

My last trip was 32 days. I ran 11,465 miles. That's the miles from odometer/elogs. Divided by 672. Got just a tad over 17.

I don't get where your going with this.

sent from Droid RAZR. DrtyDiesel

 

You are WAAAYYY over thinking this...

 

What's wrong with using both? They do have useful benefits if you gave it a chance. You can make a GPS do what you want it to do. Not what it wants you to do. Those wrong routes and low bridges are just excuses for someone who doesn't know how to use a GPS properly in conjunction with a Rand McNally. Too many have the concept you use one or the other. Nope, you can use both and make both agree.

I like having accurate ETA's, the ability to see customer parking lots and buildings, to see curves coming at night or bad weather, to know when a left exit is coming up, to know where and how far a truck stop or Walmart is at the touch of your finger.

There's even more benefits.