Dropped third

Welcome to Discuss Fastpitch

Your FREE Account is waiting to the Best Softball Community on the Web.

Mar 13, 2010
957
0
Columbus, Ohio
I'm not going to quote the whole rule, but it states that interference should be called when...obstructs,impedes,hinders, or confuses fielder attempting to make a play. A batter running to first after a strikeout has to be by definition an attempt to confuse team. Are we talking semantics, I don't understand what I'm missing here it seems cut and dry to me.

The only thing you're missing is that there is another rule that specifically says this is not interference!

It's a common mistake, and one that's caused many an argument on a softball field: Sometimes, you can't read just one tiny snipet of the rule book from a single rule and assume it applies equally in all situations. Quite often there will be another rule that makes an exception to or conflicts with the other rule. You really have to take the rule book into account as a whole, not as a collection of dozens of unrelated rules.

Why is there an exception to this rule? A couple of reasons.

First, the play you describe does not really meet the definition of interference. Maybe this defensive player was "confused", which is part of the definition. But the "confusion" did not prevent the defense from "making a play", which is another part of the definition that you are overlooking.

This is another case where you need to read more than one little snipet of the rule book to fully understand the ruling. There is a definition for what "making a play" means! "A play" is an attempt by a defensive player to retire an offensive player (ie: an attempt to record an out).

On your play, the batter was already out. A throw to first base cannot possibly "retire her again". The throw to first base was not part of an attempt to record an out, because there was no out to be gained there. Thus, a play was not interfered with and it's not interference.

As for the other two runners, the batter didn't prevent the catcher from throwing the ball to second or third. Those options were still there and the catcher could have made those plays unimpeded. The catcher's ignorance of the rule and unecessary throw are on her and you don't penalize the offensive team for that.

I believe that the exception is in there just to clarify a play that is fairly common in fastpitch. Batters are usually coached to start running to first on any third strike that isn't cleanly caught, even when not entitled to advance. This being interference or not was such a commonly debated point that the exception was added to clarify that it is not.
 
Last edited:

djraidah

Coach DJ
Mar 7, 2012
7
3
Arizona
An umpire's interference call yesterday during a high school softball game has me a bit frustrated. In my 14 years of coaching the game, I have never experienced this: My team had one out, base runners on 1B and 2B. A drop third strike occurred, the batter took off for 1st. The catcher made an overthrow to first and my runner on second scored & the runner on 1B advanced to 3B. The umpire called interference & along with calling-out the batter who struck out (which obviously was the correct call), he called-out my base runner who was originally on 2B. Again, right call if this was was a true interference call. The rationale the umpire gave me was "since first base was occupied and only one out, the batter should not have attempted to run to 1B. By doing so, her action 'confused' the catcher into throwing the ball to 1B." Let me paraphrase ... because my batter confused the catcher into throwing. Really??? Shouldn't the catcher know the rule? Am I missing something? Should I no longer continue to tell my players to head to 1B on a 3rd strike regardless of the situation? We have another game tonight. Need to get this right. Spent last night practically memorizing the rule book. Can't find this anywhere. Any help will be greatly appreciated.
 

MTR

Jun 22, 2008
3,438
48
An umpire's interference call yesterday during a high school softball game has me a bit frustrated. In my 14 years of coaching the game, I have never experienced this: My team had one out, base runners on 1B and 2B. A drop third strike occurred, the batter took off for 1st. The catcher made an overthrow to first and my runner on second scored & the runner on 1B advanced to 3B. The umpire called interference & along with calling-out the batter who struck out (which obviously was the correct call), he called-out my base runner who was originally on 2B. Again, right call if this was was a true interference call. The rationale the umpire gave me was "since first base was occupied and only one out, the batter should not have attempted to run to 1B. By doing so, her action 'confused' the catcher into throwing the ball to 1B." Let me paraphrase ... because my batter confused the catcher into throwing. Really??? Shouldn't the catcher know the rule? Am I missing something? Should I no longer continue to tell my players to head to 1B on a 3rd strike regardless of the situation? We have another game tonight. Need to get this right. Spent last night practically memorizing the rule book. Can't find this anywhere. Any help will be greatly appreciated.


NFHS Rule 8.6, Art 16.c. Page 68 in the 2012 Rules Book

BTW, when reading that rule, take a pen and strike out the word "intentionally"
 
Apr 4, 2012
45
0
Just in case I missed it I would like to clarify something.

With the example of the ball hitting before the plate and the batter takes a swing. If the catcher manages to catch the ball after the bounce is it then an out, or does the tag still need to be applied.

I have been trying to get our catchers to just tag the batter after every third strike just to make sure but they don't like to. They call it annoying when another team does it so they don't want to.

Gotta love rec ball.
 
Jun 22, 2008
3,756
113
If a pitched ball, called a strike, or swung at touches the ground at any point between the pitchers release and the catcher cleanly catching the ball, it is considered a dropped third strike.
 
Jan 15, 2009
683
18
Midwest
Just in case I missed it I would like to clarify something.

With the example of the ball hitting before the plate and the batter takes a swing. If the catcher manages to catch the ball after the bounce is it then an out, or does the tag still need to be applied.

I have been trying to get our catchers to just tag the batter after every third strike just to make sure but they don't like to. They call it annoying when another team does it so they don't want to.

Gotta love rec ball.

Yes, the tag/throw to first still needs to be done.

Teach them the rule instead. Do not tag every batter after every strikeout. It is annoying. :cool:
 
Feb 3, 2011
1,880
48
Then I was thinking more about it, considering this is more than just a “dropped third rule” , it is an “uncaught rule” , theoretically a wild pitch could occur, missing the catcher altogether while the “inexperienced” batter at the beginner level could actually swing at the uncatchable ball. With two outs and two strikes, bases loaded, it would seem plausible that all advancing runners could be safe on the play……
I just never considered the various scenarios of why this rule would be applied that way.
Weird stuff happens at the rec ball level!

Would the average coach be upset if a speedster deliberately swung at a WP on 1-2 count?
 

Forum statistics

Threads
42,862
Messages
680,273
Members
21,517
Latest member
coopdog
Top