There was a grave error made by the Timekeeper in the Kent Game that is getting no play, and I can't figure out why.
At 12.12 left in the 2nd half with Kent up 46-45, Kent starts their possession.
At 11.45 in the same possession, Rod Sherman tosses up a 3 pointer that hits the backboard padding - NO RIM.
There is a scrum for several seconds, and Kent kicks the ball out to the top of the key to re-start their possession.
Luckily for them, our OHIO timekeeper reset the shot clock with approximately 2 seconds left so that they could setup a new possession even though the ball hadn't touched iron.
Vis a vis, there was a media timeout called...Kent got the ball with a new 35 and ended up taking a 47-45 lead via a Sayles foul and 1/2 of FT's by Justin Manns.
We get the ball back at 11.01 left in the game...which is 1m 11s after we gave it to Kent. Certainly worth 2 more possessions for us.
By the way, when Manns missed his 2nd FT, there was another offensive rebound on a FT for Kent. How does this happen where nobody blocks out on FT's??? It happens every single game now!
I'm sorry, but this is not the first time this season that we have had timekeeper issues. Against Oakland, it seemed like we had a 4 year old pushing the buttons as the refs continuously had to come to the scorers table to figure out what in the world was happening.
It's clear this '10-'11 edition of the Bobcats is going to be playing a lot of games that come down to inches, and the Timekeeper not knowing the rules or applying the rules or pushing the right buttons is unacceptable in the scope of these wins and losses. There has to be an immediate remedy, b/c as correctly stated by Jason Arkley on twitter - neither of us can remember a season with this many timekeeper issues.
This is not even something we should ever be discussing, as that's a function that should take place in the background with ease.
Edit - I did see Dustin Ford talking to the Ref during the media timeout...but I was standing there pointing at the shot clock demanding that we get the ball back. Just because the timekeeper resets the shot clock does not mean Kent touched iron in 35 seconds...it should have been our ball, not a reset shot clock. The refs looked at the monitor and made the call to give Kent a new 35, but it either should have been Ohio ball or Kent ball with 1 second left on the shot clock. There is no way you can tell me Sherman's shot touched iron - it wasn't even close.
Last Edited: 1/18/2011 9:52:29 AM by Bobcat Love