The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Baseball (https://forum.officiating.com/baseball/)
-   -   Missed Third Strike & Abandonment (https://forum.officiating.com/baseball/34463-missed-third-strike-abandonment.html)

tibear Thu May 10, 2007 11:34am

Missed Third Strike & Abandonment
 
Situation: R3, 1 Out. Left handed batter swings and misses third strike, catcher misses the ball and the ball go to the backstop. I make the call, "Strike Three, no catch".

R3 is stealing home on the play, the batter, rather then running for first takes about 5 or 6 steps backwards towards the dugout and watches the play at the plate. After a second or two he finally realizes he is able to steal first and then runs safely to first. There is no "home plate circle".

Once the play ends the defensive manager questions why the batter wasn't automatically out because he had no intention of running to first immediately after the thrid strike and in fact had backed towards his dugout so this should be interpreted as abandonement.

I said that I didn't see the batter as abandoning the stealing apportunity but rather was vacating home plate area and then realized he was entitled to steal first.

With no home plate circle, did I make the right call or should the batter have been out.

LMan Thu May 10, 2007 12:19pm

OBR, its now 'dirt circle.' In your case I'd say this was a judgment call on your part, since there was no circle marked.

FED, the batter's still OK until he enters the dugout/DBT.

Why didn't F2 throw to 1B when the batter eventually started that way?

And, ST is right. You can't steal first. Unless it's not bolted down.

BigGuy Thu May 10, 2007 12:26pm

Quote:

Originally Posted by tibear
Situation: R3, 1 Out. Left handed batter swings and misses third strike, catcher misses the ball and the ball go to the backstop. I make the call, "Strike Three, no catch".

R3 is stealing home on the play, the batter, rather then running for first takes about 5 or 6 steps backwards towards the dugout and watches the play at the plate. After a second or two he finally realizes he is able to steal first and then runs safely to first. There is no "home plate circle".

Once the play ends the defensive manager questions why the batter wasn't automatically out because he had no intention of running to first immediately after the thrid strike and in fact had backed towards his dugout so this should be interpreted as abandonement.

I said that I didn't see the batter as abandoning the stealing apportunity but rather was vacating home plate area and then realized he was entitled to steal first.

With no home plate circle, did I make the right call or should the batter have been out.

You got the call right. The only thing you did wrong was use the words "no catch". It's up to the offensive team to figure out that the ball wasn't caught and the defensive team to figure a play needs to be made at first. If the ball is caught, you can say "strike three, batter's out". Saying "no catch" is coaching the offensive team.

UmpJM Thu May 10, 2007 12:33pm

BigGuy,

I beg to differ on the "no catch".

Remember, it's not whether the catcher caught the pitch - it's whether the umpire judged he did. How's anyone supposed to know if the umpire doesn't tell them.

Since the Eddings fiasco in the ALCS, the "no catch" verbalization is being taught.

JM

blueump Thu May 10, 2007 12:46pm

Quote:

Originally Posted by Steven Tyler
I've never heard of a steal of first, but if in your judgment the batter didn't abandon his right to run on the play, the coach was crying over spilled milk.

"Judgment" and "abandoning his effort" has nothing to do with it in FED ball. The batter has the right to make his attempt for first base at anytime before he enters dead ball territory.

tibear Thu May 10, 2007 01:08pm

Quote:

Originally Posted by blueump
"Judgment" and "abandoning his effort" has nothing to do with it in FED ball. The batter has the right to make his attempt for first base at anytime before he enters dead ball territory.

Not sure about FED, we only use OBR in Canada.

bob jenkins Thu May 10, 2007 01:14pm

Quote:

Originally Posted by BigGuy
You got the call right. The only thing you did wrong was use the words "no catch". It's up to the offensive team to figure out that the ball wasn't caught and the defensive team to figure a play needs to be made at first. If the ball is caught, you can say "strike three, batter's out". Saying "no catch" is coaching the offensive team.

Actually, it's just the opposite. Although I'd be likely to assume the "no catch" (and thus not verbalize it) was obvious if the ball went to the backstop. And, of course, I do call the batter out if he starts to run when he's not legally allowed to.

BigGuy Thu May 10, 2007 01:18pm

Quote:

Originally Posted by CoachJM
BigGuy,

I beg to differ on the "no catch".

Remember, it's not whether the catcher caught the pitch - it's whether the umpire judged he did. How's anyone supposed to know if the umpire doesn't tell them.

Since the Eddings fiasco in the ALCS, the "no catch" verbalization is being taught.

JM

If the catcher is not sure, he tags - that is taught. If the umpire is sure, he says "batter's out!" Batters are taught to run. It is not up to the umpire to signal "no catch", and thus tell the batter "run". Let them figure it out for themselves.

The issue with the ALCS debacle is whether or not Eddings actually called Pierzynski "OUT" he appeared to give the "out" signal but then later on says no. There is no way whatsoever that he could be sure the ball was caught. The Angels catcher screwed up by not tagging just to make sure. Everybody assumed something. We all know where that gets us. I think Pierzynski also reacted to the fact there was NO CALL. All this means is that he reacted the way he was supposed to. Whatever you want to call it it was still smart baserunning on his part.

LMan Thu May 10, 2007 01:21pm

Quote:

Originally Posted by BigGuy
If the catcher is not sure, he tags - that is taught. If the umpire is sure, he says "batter's out!" Batters are taught to run. It is not up to the umpire to signal "no catch", and thus tell the batter "run". Let them figure it out for themselves.

Heh, heh, heh.

BigGuy Thu May 10, 2007 01:22pm

Quote:

Originally Posted by bob jenkins
Actually, it's just the opposite. Although I'd be likely to assume the "no catch" (and thus not verbalize it) was obvious if the ball went to the backstop. And, of course, I do call the batter out if he starts to run when he's not legally allowed to.

I think we mean the same thing, our perspectives are different. I could have just as easily said it the other way. I do call "batter's out". I don't say no catch.

blueump Thu May 10, 2007 01:30pm

Quote:

Originally Posted by Steven Tyler
You are correct, Sir. However in perusing the post and knowing our original poster is from north of the border, I didn't believe a FED ruling to be necessary as they are an OBR country.

I caught that after the fact:cool:

I usually don't frequent enough to know where everyone is from yet...:D I thought that "north of the border" meant Michigan!:p

tibear Thu May 10, 2007 01:43pm

Everyone is right, I probably didn't have to say the no catch with the ball being at the backstop. But with the age of the players I felt it necessary for both the defense and offense to remind them of the situation.(12-13 year olds playing their first or second game of the year)

I always thought that the dropped third strike was to be treated like a missed base while baserunning. Something we take note of but don't verbalize. However, I thought the thinking had changed on that situation because of the MLB incident of a couple of years ago.

Does anyone have any authoritative sources which mandate either verbalizing or non-verbalizing this situation??

LMan Thu May 10, 2007 01:51pm

This might help:


http://forum.officiating.com/showthread.php?t=24238

tibear Thu May 10, 2007 02:11pm

Thanks, it seems to indicate that a verbalization is preferred.

LMan Thu May 10, 2007 02:25pm

Quote:

Originally Posted by tibear
Thanks, it seems to indicate that a verbalization is preferred.

That seems to be the trend in this case. I confess that I have not yet gotten to the verbalization point - after the Eddings stuff, I 'evolved' into making several emphatic 'safe' signals upon a D3K, but Im still working on opening my mouth about it :D

As far as calling 'batters out' when he cannot advance, I dont have a choice - our state manual specifies that we will do this. So we do.

bob jenkins Thu May 10, 2007 02:32pm

Quote:

Originally Posted by BigGuy
I think we mean the same thing, our perspectives are different. I could have just as easily said it the other way. I do call "batter's out". I don't say no catch.

No. Our perspecives are the opposite.

LMan Thu May 10, 2007 03:02pm

http://www.firedougeddings.com/

BigGuy Thu May 10, 2007 03:58pm

Quote:

Originally Posted by bob jenkins
No. Our perspecives are the opposite.

I guess my perspective is this - I don't verbalize information that could potentially be perceived as coaching/aiding one team or the other. If I say no catch, I'm essentially telling the runner to run. Depending on the batter, that could mean an additional 1 or 2 seconds between me saying it and they noticing it and possibly the difference between safe and out at 1B.

If I say batter's out, I am making a statement of fact to prevent the batter from causing a state of confusion he does not have the right to do.

We don't tell coaches when to bunt or what pitch to throw, so why should we tell batters when there is a D3K?

Arnold A. Thu May 10, 2007 04:17pm

Quote:

Originally Posted by BigGuy
We don't tell coaches when to bunt or what pitch to throw, so why should we tell batters when there is a D3K?

Because this has become the universal teaching at clinics and schools since the Eddings "situation".

This has been clearly stated in previous posts.

UmpJM Thu May 10, 2007 04:18pm

BigGuy,

Quote:

...so why should we tell batters when there is a D3K?
Because sometimes the umpire is the ONLY one who knows whether the pitch (in his judgement) was "legally caught" or not and it is the umpire's job to make those judgements and communicate his decision to the participants.

This is NOT coaching. You are equally informing the Batter(/Runner?) and the Catcher of your ruling.

No different than a fly ball that a fielder may or may not have caught. The umpire makes his ruling and announces it so all the players know what the situation is and have the opportunity to react accordingly.

JM

GarthB Thu May 10, 2007 04:22pm

Quote:

Originally Posted by Arnold A.
Because this has become the universal teaching at clinics and schools since the Eddings "situation".

This has been clearly stated in previous posts.

The approved mechanic is to give a strike signal to the side (no hammer) and then give the safe sign and say "No catch."

Arnold A. Thu May 10, 2007 04:37pm

Quote:

Originally Posted by GarthB
The approved mechanic is to give a strike signal to the side (no hammer) and then give the safe sign and say "No catch."

Garth,

Thank you for filling in the numerous blanks I left.

3appleshigh Thu May 10, 2007 05:27pm

Quote:

Originally Posted by BigGuy
I guess my perspective is this - I don't verbalize information that could potentially be perceived as coaching/aiding one team or the other. If I say no catch, I'm essentially telling the runner to run. Depending on the batter, that could mean an additional 1 or 2 seconds between me saying it and they noticing it and possibly the difference between safe and out at 1B.

If I say batter's out, I am making a statement of fact to prevent the batter from causing a state of confusion he does not have the right to do.

We don't tell coaches when to bunt or what pitch to throw, so why should we tell batters when there is a D3K?


If you get into the habit of verbalizing this on any and all D3K. It would be better then. Just adding the Batter's out to the end when needed. Then when you say it, it will simply mean the catcher didn't catch the ball, nothing else. Doesn't tell anyone to run.

umpduck11 Thu May 10, 2007 06:16pm

Quote:

Originally Posted by LMan
As far as calling 'batters out' when he cannot advance, I dont have a choice - our state manual specifies that we will do this.

In its' lovely mauve cover........ :D

bob jenkins Fri May 11, 2007 07:20am

Quote:

Originally Posted by BigGuy
I guess my perspective is this - I don't verbalize information that could potentially be perceived as coaching/aiding one team or the other.

Saying "run" or "tag him" is coaching. Saying "no catch" is giving facts about the status. Again, only used when there might be some doubt.

You are correct that saying "Out" is also giving the status. My point on this is that it should no be used routinely -- use it when F2 catches the pitch that's near the dirt, or when BR runs when he's not legally allowed to.


All times are GMT -5. The time now is 02:30pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1