The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Baseball (https://forum.officiating.com/baseball/)
-   -   Infield fly not called (https://forum.officiating.com/baseball/49598-infield-fly-not-called.html)

johnnyg08 Thu Oct 30, 2008 01:50pm

you're right griff...my bad...did realize you were replying to a previous post.

bob jenkins Thu Oct 30, 2008 01:57pm

Quote:

Originally Posted by griff901c (Post 547261)
It's IFF.." if fair"..meaning in fair territory..right? Landing foul ( no IFF) and rolling fair...no IFF

griff

Until the ball is touched, or comes to rest, or goes beyond 1st/3rd, it's neither fair nor foul.

Landing foul and rolling fair (and then being touched...) will still result in an infield fly (if the other conditions are met).

griff901c Thu Oct 30, 2008 02:12pm

Quote:

Originally Posted by bob jenkins (Post 547277)
Until the ball is touched, or comes to rest, or goes beyond 1st/3rd, it's neither fair nor foul.

Landing foul and rolling fair (and then being touched...) will still result in an infield fly (if the other conditions are met).

I hate being wrong.....by my own verbage no less...

thanks

johnnyg08 Thu Oct 30, 2008 03:26pm

Quote:

Originally Posted by bob jenkins (Post 547277)
Until the ball is touched, or comes to rest, or goes beyond 1st/3rd, it's neither fair nor foul.

Landing foul and rolling fair (and then being touched...) will still result in an infield fly (if the other conditions are met).

I got that one wrong too. Bob, can you explain that a bit further? I guess I don't understand how (assuming all other fair ball conditions are met) a ball that lands foul, legally rolls fair can still be ruled infield fly when touched. Where does that end? At some point, defense is going to have to "touch" the ball.

SethPDX Thu Oct 30, 2008 03:42pm

Quote:

Originally Posted by johnnyg08 (Post 547325)
I got that one wrong too. Bob, can you explain that a bit further? I guess I don't understand how (assuming all other fair ball conditions are met) a ball that lands foul, legally rolls fair can still be ruled infield fly when touched. Where does that end? At some point, defense is going to have to "touch" the ball.

Consider a fly ball hit between the plate and 1B or 3B. Let's say an infielder was under the ball, ready to make a play on it, but misjudges it and it drops in foul territory without him touching it (And wind, weather, etc. was not a factor).

The ball then rolls into fair territory where he picks it up, making it a fair ball. Because it is a fair ball that could have been caught with ordinary effort, we have an infield fly.

DG Thu Oct 30, 2008 10:52pm

Quote:

Originally Posted by bobbybanaduck (Post 546776)
sun could absolutely be a factor. take the same situation as in game 5, but make it a day game with a bright sun. ball goes up above F4's position and should be a "routine" catch, but he looks up and right into the sun, causing him to move his head away and put his arms up over his head for protection. reading this reaction of the fielder, you no longer have a catch that is about to be made with ordinary effort, you have a fielder that doesn't know where the ball is. you're telling me you're going to call infield fly on that?

I played 2B when I played and never dropped an easily catchable ball due to the sun. I also can't remember the last time I saw this happen in a major league game. The sun is not a factor, or should not be a factor in judging IFF on ordinary effort.

SanDiegoSteve Thu Oct 30, 2008 11:07pm

Quote:

Originally Posted by DG (Post 547448)
I played 2B when I played and never dropped an easily catchable ball due to the sun. I also can't remember the last time I saw this happen in a major league game. The sun is not a factor, or should not be a factor in judging IFF on ordinary effort.

I agree, and the infield fly is traditionally called at the apex of the ball's upward flight anyway, so the fielder's late reaction to the sun would be after the IFF was called.

johnnyg08 Fri Oct 31, 2008 07:47am

that makes perfect sense...thanks Seth

D-Man Fri Oct 31, 2008 11:57am

Sure Am!
 
Quote:

Originally Posted by bobbybanaduck (Post 546776)
sun could absolutely be a factor. take the same situation as in game 5, but make it a day game with a bright sun. ball goes up above F4's position and should be a "routine" catch, but he looks up and right into the sun, causing him to move his head away and put his arms up over his head for protection. reading this reaction of the fielder, you no longer have a catch that is about to be made with ordinary effort, you have a fielder that doesn't know where the ball is. you're telling me you're going to call infield fly on that?

The fielder can protect his eyes from the sun. How are you going to guage the integrity of a player who learns he can just fake the sun in his eyes to get an easy double play?

The characteristics of the batted ball are what I consider when calling an infield fly (along with conforming to the rule, of course). The wind is a physical factor acting on the batted ball, making it move laterally in an unpredictable fashion. A fielder can't be expected to catch a wind deviated fly ball with ordinary effort. His integrity does not matter because we can see the affect the wind is having on the batted ball.

As an aside, the rule is all about protecting the offense.

D

UMP25 Sun Nov 02, 2008 11:17am

Quote:

Originally Posted by bobbybanaduck (Post 546779)
Never read it, and 100% disagree. So a guy hits a popup in the infield and the second baseman sees it on the way up but loses it because it's getting dark out, and you're going to call infield fly?

Absolutely! Why? Because, simply put, it's a ball that can be caught with ordinary effort. Period. Considering the decision will be made by me once the ball has reached its peak of begun its descent, the fielder's inability to cope with the sun is irrelevant and not considered "unordinary" effort.

UMP25 Sun Nov 02, 2008 11:21am

Quote:

Originally Posted by bob jenkins (Post 547249)
"You're right. It was poor mechanics. But, it was the right call."

And I might add a comment that simply explained, "The rule is there to protect the offense. I cannot let the defense gain an advantage in this situation; therefore, I must call the Infield Fly."

I once had the offensive manager come out to argue this very play. When I politely explained to him that I was making the ruling to protect his runner(s), he commented, "Oh," and walked away.

DG Sun Nov 02, 2008 10:09pm

Quote:

Originally Posted by midtnblu (Post 546885)
I think this was another error on the part of this crew. The IFF is designed to protect the offense in this situation, and by not calling it, they failed to protect the offensive team. You can't "not protect" them just because it's raining.

Wind made the play not one that could be made with ordinary effort, not rain. If he was camped under a fly ball in the rain, then IFF would be the correct call.

Fan10 Mon Nov 03, 2008 12:34am

Quote:

Originally Posted by UMP25 (Post 548034)
And I might add a comment that simply explained, "The rule is there to protect the offense. I cannot let the defense gain an advantage in this situation; therefore, I must call the Infield Fly."

I once had the offensive manager come out to argue this very play. When I politely explained to him that I was making the ruling to protect his runner(s), he commented, "Oh," and walked away.

Ironically, I saw the infield fly rule screw the offense in an NCAA game last year. Runners at 1st/2nd, 1 out. Batter hits a pop up to 1B. Should be an easy out. The ball hit off the side of the first baseman's glove and rolled all the way into foul territory between third and home. Both runners advanced, and the batter was called out on the infield fly. However, had there been no infield fly, the batter would have easily reached 1st, and it would have been bases loaded.

It was the right call, and nobody argued. But, as a fan who was sitting in the stands rooting for the offense, I was upset (not upset with the umps, just upset in general) that a rule designed to protect the offense actually screwed my team. :eek:

dash_riprock Mon Nov 03, 2008 08:43am

Quote:

Originally Posted by Fan10 (Post 548147)

...I was upset (not upset with the umps, just upset in general) that a rule designed to protect the offense actually screwed my team.

The rule didn't pop up to first with two on and one out, the batter did.

justanotherblue Mon Nov 03, 2008 09:47pm

Throughout this thread several poster's keep coming back to it was a ball that should have been caught with ordinary effort....maybe so...,or I would call it at it's apex. What seems to be left out is the judgement portion of the rule, as well as the judgement of the umpires on the field fighting the elements, living it, not sitting home with a cold one watching the game. So what I gather from some, is that simply because the ball was in the infield, it should have been caught with ordinary effort. That's wrong. Take this play.....bases loaded, one out, high fly ball is hit near the first base line, 20 feet up the line from the plate. Catcher can't find it, as the ball hits it's apex, it's spotted and F1, 2, and 3, rush in, with the first baseman diving unsucessfully. The ball lands and stops in fair territory. All runners advanced one base, with R3 scoring. If you employ the addage of it should have been caught, so it's an IFF your wrong. There is clearly no ordinary effort in this play. Something some need to add into their thought process, when calling an IFF is, is there a fielder comfortably under the ball to make that catch? If not, you very well may not have an IFF. Weather can and does very often come into play when deciding to call an IFF or not. Including the sun.


All times are GMT -5. The time now is 10:20am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1