Quote:
Originally posted by bob jenkins
Quote:
Originally posted by bob jenkins
Quote:
Originally posted by Carl Childress
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!
|
That's completely inconsistent with last year's interp #14:
SITUATION 14: With R1 on first and one out, B2 hits a fly ball down the third-base line. U1 errs and announces Foul ball, but F5 catches the ball several feet in fair territory. RULING: B2 is out. R1 may tag and advance at his own risk. (Rule 5-1-1h does not apply on a caught fly ball.)
|
Last year's Interp #14 has been superceded by 2005 Interp #5.
|
Situation 3 is perhaps what you meant. Situation 3 and 4 really confuses this issue. For example, Situation 4 says we can correct an erroneous FOUL BALL call on a HR ball, but Situation 3 says the ball is dead because the umpire called FOUL BALL on one in LF. But foul balls can be caught for outs, so why not call this an out instead of a strike, and treat it like a FOUL BALL that was caught? I know, FOUL BALL means dead ball in FED, by rule. That's the answer to my own question. They really should look at changing the rule, instead of coming out with interps that just confuse things.
Fri Jan 28, 2005, 07:31pm
Threaded Mode
