Thread: Unsafe catcher
View Single Post
  #14 (permalink)  
Old Wed Apr 20, 2011, 06:43am
MikeStrybel MikeStrybel is offline
Official Forum Member
 
Join Date: Feb 2011
Location: Northwest suburbs of Chicago
Posts: 645
Quote:
Originally Posted by ozzy6900 View Post
Totally disagree here. We are not coaches, we apply rules. If F2 is where he should not be, call the offense as it occurs. If you tell F2 "Don't stand there" and he moves to a worse position and gets nailed, you are responsible. Keep your mouth shut and take care of business when it happens,. You can't be held responsible for stupidity.
Ozzy, thanks.

Preventive officiating does not involve telling a catcher to move because he MAY be in the way. That is being an Overly Officious Official and an invitation for fallout when your meddling is ignored or causes a more serious scenario.

I recall a discussion a while ago about another OOO. With R3 he told the batter to move far away if the ball gets away from the catcher. The batter didn't move and he ejected him, citing the player's lack of respect for his authority. Telling a catcher or scored runner to remove a bat is another example that some think is fine but others whince at. I have seen what happens when a partner tells a catcher to "Get the bat out of the way." One involved the on deck batter having a bat sail his way and the other had the catcher try to kick the bat with his foot, fall and miss the catch. When his coach learned that the umpire told him to do it, the coach was justifiably upset. The umpire felt justified that he was trying to make the play safer but forgot to simply call the play. One of the first things I tell new umpires is to be Harry Carey out there - see the play and tell everyone what happened. I have heard other instructors preach the same thing - watch and report, but never coach. Call the game.
Reply With Quote