Yesterday I was dispatched a load with 230 empty miles to get it, and only 250 loaded miles, because it was tcalled on dispatch. I need miles and have hours, but yet they tcalled me in OKC, which is my home terminal, I get there and there is an unusual amount of trucks there. Now I get a dispatch out, but not untill monday midday. Trying to figure out why the tcall, and have me sit for a day and a half. It stinks because this will be a tiny payweek, but atleast it's happening at home and not at a far away terminal.
Where was the load going and when did it have to be there? Was it one of those copper loads going to the Carolinas? If so, you picked up a shuttle load. It will be t-called across the country until some poor sap has to deliver it with a couple hundred miles on it. BS, I know. I hate those loads. I had a 3-stopper I picked up in Sparks going all that long way to Sacramento...138 miles. You are allowed to call your weekend DM and find out if there is something moving sooner, stating you have hours and don't want to sit. Or, you can go home for the weekend and get a 34. Your choice.
copper load to indiana, I took the same load to sc, last week. I figure take the day at home with the wife, get a 34 and roll, this weeks pays is screwed anyway
When i was at swift i seen this happen alot to the OTR drivers but freight is slow this time of year and should be picking up soon... i ran dedicated accounts while i was there and never had this problem if i wanted to run i could
happens to those who dont have a good DM to back them up. I dont mind t-calling loads, but if it is such a time sensitive load, that is already running late, and i'm t-calling it for a team truck to haul it the rest of the way, they darn sure had better be sitting there with the truck running ready to hook to it as soon as i drop it. (well .... maybe not THAT extreme) But dont tell me its 'time sensitive', then i find it sitting there 12 hrs later when i wake up and go inside for my next load.
