I have a 88 Mercury 35hp motor on a Bass Tracker Pro 17 that runs great but RPM's are only 4400 @ WOT. My father-in-law bought this boat new and we just picked it up from this past fall. I have only put abot 10 hours on the boat since I have had it (probably less than 35-40 hours total on the motor) and decided to change the prop to get the RPM's up where they should be running. The motor originally came with a 3 blade 13p and after talking to Mercury I picked up a used 4 blade 9p that has no visual damage from a local shop.
I put the prop on Friday and headed out to the lake for a test run that didn't end well. My wife backed me down the ramp and I had the boat idling probably 10 minutes waiting for her to get back to the boat, we idle out past the no wake zone and and as soon as the rpm's get up to around 4300 the motor starts clanking really loud so I shut the motor off. Thinking the used prop I had bought was spun I put the motor in neutral and started the motor, but the clanking was still there so I shut it down and used the trolling motor to get the boat back to the trailer.
I can grab the flywheel and rock it side to side quite a bit and there is also a slight up down play also. Is it normal for crank bearing to go bad without any warning or could there have been a issue with the prop that caused the problem?
I put the prop on Friday and headed out to the lake for a test run that didn't end well. My wife backed me down the ramp and I had the boat idling probably 10 minutes waiting for her to get back to the boat, we idle out past the no wake zone and and as soon as the rpm's get up to around 4300 the motor starts clanking really loud so I shut the motor off. Thinking the used prop I had bought was spun I put the motor in neutral and started the motor, but the clanking was still there so I shut it down and used the trolling motor to get the boat back to the trailer.
I can grab the flywheel and rock it side to side quite a bit and there is also a slight up down play also. Is it normal for crank bearing to go bad without any warning or could there have been a issue with the prop that caused the problem?