View Single Post
  #14 (permalink)  
Old Tue Oct 07, 2008, 01:04am
SanDiegoSteve SanDiegoSteve is offline
Senior Member
 
Join Date: Oct 2005
Location: Lakeside, California
Posts: 6,724
if you watch the play in regular speed, not super slow-mo, I don't think the correct call was made. The ball most certainly didn't meet the "long enough" standard. I've seen outfielders catch balls and then run five or six steps into the wall and lose possession, and these have been emphatically called, "no catch." Varitek did nothing to demonstrate either control or voluntary release as well. It is my opinion that if Varitek had held the ball after colliding with the ground, then as he was showing the ball it fell out, it would be an out, and he would have had it long enough. But to tag the runner then hit the ground in the same motion dropping the ball on impact, that's stretching it a little.

Varitek tagged the runner and in the same motion his mitt slammed into the ground dislodging the ball. In the meantime, Tim Welke was already signaling and calling the out before the ball even popped out. He called the out the nanosecond the tag was applied and did not even see the ball pop out. Absolutlely terrible timing on his part. I know that he was trained as we all were to see the entire play through until the action stops before making his call. He most definitely did not do that on this play.

If I were making the call, I would have waited until action had ceased, while keeping my eyes everalastingly on the baseball (as the rules instruct). I would have seen the ball rolling away and called the runner safe. This isn't football...the ground certainly can cause a fumble.
__________________
Matthew 15:14, 1 Corinthians 1:23-25