Quote:
Originally posted by Carl Childress
Quote:
Originally posted by David Emerling
Is it just me, or are some of the rule references that support many example plays tenuous, at best?
You read the play ... you read the ruling ... then look up the cited reference and find NO BASIS for the suggested ruling based on the reading of the rule. I see this happen time and time again.
Here's an interpretation that I just read from the NFHS website:
SITUATION 10: With 1 out and R1 on first and a count of 2-1, B2 hits a bouncing ball along the first base foul line. U1 mistakenly declares Foul! as F1 picks up the ball in fair territory. RULING: The ball is dead immediately. R1 returns to first. B2 continues at bat with a count of 2-2. (5-1-1h)
Seems reasonable enough.
The ball instantly becoming dead seems reasonable and is supported by the cited rule.
|
David: I have an even stranger play, one given by Kyle McNeeley of the NFHS rules committee at the TASO state meeting.
B1 pops up in foul territory behind first base. The umpire calls "Foul ball." F3 catches the pop-up. And the answer is:
It's just a dead ball, and the batter stays at bat!
|
How about this. Home team trailing by 1 run, bottom of the 7th, two outs, runner on 2B. The batter hits a line drive that strikes the foul pole in flight in LF. PU calls "foul ball". What a sh*th**se that will be.
Based on this rule my future mechanic for FED games will be to keep my mouth shut unless I am absolutely positive the ball is FOUL. I may "signal" foul, which leaves me an out to change the call. But verbalizing FOUL is not changeable.
[Edited by DG on Jan 24th, 2005 at 12:12 AM]