Register free!
Search
 
     

The Green Industry's Resource Center


Click for Weather
Reply
 
Thread Tools Display Modes
  #1  
Old 09-21-2013, 01:08 PM
Ormond32176 Ormond32176 is offline
LawnSite Member
 
Join Date: Jul 2013
Location: Daytona, FL
Posts: 200
Belt Lifespan?

Just bought a 36" Gravely walkbehind. The belt that runs around the deck just broke with 8.5 total hours on the mower. Probably 6 hours or so of actual cutting, and never used it in anything more testing than St. Augustine.

Is this normal? I would think I could get a lot longer than that out of one. Anyone know of a reason why it might go?

Here is a picture if it helps:
Reply With Quote
  #2  
Old 09-21-2013, 02:00 PM
jsslawncare's Avatar
jsslawncare jsslawncare is offline
LawnSite Bronze Member
 
Join Date: Feb 2011
Location: North Georgia
Posts: 1,658
Belt Lifespan?

I'd say its not normal, but how old is the belt?
__________________
All equipment is wore out. <- Never mind. All equipment has been repainted and with new decals. It's like I have new mower's again!
48" Ferris WB
36" Ferris WB
All Echo hand helds
<- That's how I feel at the end of the day.
Reply With Quote
  #3  
Old 09-21-2013, 02:02 PM
Ormond32176 Ormond32176 is offline
LawnSite Member
 
Join Date: Jul 2013
Location: Daytona, FL
Posts: 200
Quote:
Originally Posted by jsslawncare View Post
I'd say its not normal, but how old is the belt?
Idk it's a 2013 mower, with less than 10 hours.
Posted via Mobile Device
Reply With Quote
  #4  
Old 09-21-2013, 02:21 PM
Sharpcut 1's Avatar
Sharpcut 1 Sharpcut 1 is offline
LawnSite Senior Member
 
Join Date: Sep 2006
Location: Roseville, MI
Posts: 450
From the picture, that's a clean break, meaning you fot something binding somewhere. It does'nt look shreaded, which would indicate more of a pulley problem. I do see a line in the v portion of the belt, so there may also be a pulley with a groove in it somewhere, or mis-aligned.
Reply With Quote
  #5  
Old 09-21-2013, 03:08 PM
Oldtimer Oldtimer is offline
LawnSite Bronze Member
 
Join Date: Apr 2000
Location: Pensacola, Florida
Posts: 1,386
Looks like someone turned the blades on while in the grass.


Oldtimer
Reply With Quote
  #6  
Old 09-22-2013, 06:19 AM
123hotdog's Avatar
123hotdog 123hotdog is offline
LawnSite Senior Member
 
Join Date: Aug 2012
Location: Bristol TN
Posts: 444
I don't have your answer but a friend of mine bought a brand new Scag walk behind last year. He used it a week or two and the deck belt broke. They would not warranty it at the dealer. It never happened again. The dealer told him that any kind of debris coulda got lodged anywhere and done it???
__________________
Licensed and Insured
Operating since 2007
1993 Isuzu NPR dove tail open bed 4cyl diesel
1978 F-350 Dump Truck
1988 Z-71 Chevy 4x4 Meyers Plow
2005 Chevy HD 2500 6.0
2013 61" Bad Boy Outlaw XP 36 Vanguard
2013 54" Bad Boy Outlaw Stander Kawasaki
2014 48" Wright Walk Behind
1995 36" Scag Walk Behind
Reply With Quote
  #7  
Old 09-23-2013, 01:33 AM
herler herler is offline
LawnSite Gold Member
 
Join Date: Apr 2012
Posts: 3,347
Sometimes you get a belt that's defective off the shelf, too.

I would just install a new one, make sure it's routed proper and that the tension is about right and let it fly.

On that note order up two.
Reply With Quote
  #8  
Old 09-24-2013, 08:47 PM
Patriot Services's Avatar
Patriot Services Patriot Services is offline
LawnSite Fanatic
 
Join Date: Jul 2006
Location: Tampa FL
Posts: 8,321
Either adjusted to tight or idler pulley binding or as mentioned it was started after stalling out in the grass.
Posted via Mobile Device
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump





Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright ©1998 - 2012, LawnSite.comô - Moose River Media
All times are GMT -4. The time now is 08:37 AM.

Page generated in 0.07668 seconds with 9 queries