![]() |
Runs Scored
NFHS / ASA Rules...
R1 on third, R2 on second, R3 on first and 1 out. B5 hits safely to right field. R1 scores, R2 misses third base and scores. R3 is thrown out at third. Playing action ends defensive team makes a dead ball appeal R2 missed third on her way home. Umpire declares R2 out. How many runs score? |
R1 scores. The out on R2 is not a force out, as a trailing runner (R3) had already been declared out.
You can never, ever have a force out on a runner when a runner who's trailing them has already been declared out. |
ASA RS#1.J Last Sentence......
"On an appeal play, the force out is determined by when the appeal is made, not when the infraction occurred." |
Quote:
|
Quote:
|
Quote:
|
Then the call is the same for ASA and NFHS?
|
Quote:
Bases loaded, one out. Ground ball to F6... she throws to F5 for the force on R2. F5 sees R3 making it to 2nd, so tries to make a play on B/R at first. B/R is safe and F3 throws back to F5 who tags R3 trying to steal. There's still three outs and R1 still scores. So why does the timing matter (in the OP)? What am I missing? |
Quote:
Quote:
Quote:
Make sense? |
Quote:
OK, that sentence doesn't make total sense, but I think I understand. |
Quote:
Here's what I confirmed/learned. Check your 2004 ASA rule book, if you still have one laying around. ASA changed their interpretation of the definition of a force as it pertained to an appeal play. Another person already quoted it as follows: "On an appeal play, the force out is determined when the appeal is made, not when the infraction occurred." Prior to 2004, that was not ASA's rule/interpretation. Only ASA (among all softball codes) has adopted this definition/interpretation. Consequently, in ASA, the run does score. However, in all other codes, including NFHS and NCAA, the run does NOT score. They keep the "retroactive" force play. I'm sure this will create some controversy, but that's the interpretation. MLB is currently discussing possibly changing their interpretation as well. There are some case plays that illustrate why ASA has gone with this interpretation, but I'll leave them out for now. Fire away :p |
Quote:
ASA waits until the defense appeals and makes the ruling from that point in time. So the run scores from third. NFHS Keep the "retroactive" force play. So the run from third does not score. |
There are some case plays that illustrate why ASA has gone with this interpretation, but I'll leave them out for now.
I for one would like to see a list of them. |
Quote:
Would it be logical to apply a "retroactive" force out in the following play. R3 on 3rd. R1 on 1st. 1 out. Ball hit to right field. R3 scores (nothing else going on her R3). R1 misses 2nd and starts to 3rd base. Meanwhile, F9 fires the ball in and guns out BR going for a double. BR is out #2. Now that BR is out of the picture, there is no preceding runner holding R1 back. How can R1 logically be prevented from returning all the way to 1st base? That isn't to say it would be rational for R1 to go back to 1st base. Rather, the argument is used to justifying the rule. The only way to keep her back from 1st is to have a runner "force" her from it. That doesn't exist here. That's one example. I have a few more after my conversation tonight. I might be able to add to that number if the double jacks are-a-flow'n when we meet up tomorrow night for a state meeting. Stay tuned. |
Quote:
Looking forward to more examples. Also wonder if the original comments / thoughts, etc are available somewhere? Also have a cold one for me. |
All times are GMT -5. The time now is 04:12pm. |