Ground Can't Cause a Fumble

[jicecone]

Actually, when the DC went to my partner first as I called time and walked away to home plate. My partner sent him to me. R3 froze on third and afterwards my partner who was in the "B" position said that he did not realize the ball was first touched in foul territory anyway. Had I realized that I didn't make the correct call on the Fair/Foul then or was uncertain about it, I probably would have talked with my partner.

The coach did not discuss foul/fair, he wanted me to ask my partner if it was a catch or not. I told him that I was 100% sure that it was not, a catch and did not need to discuss it with my partner.

[Mrumpiresir]

I know you realize it, but I gotta emphasize your first responsibility is fair/foul. It's important. So many bad things can happen.

[jicecone]

Your absolutely correct, no excuse. As soon as the player hit the ground and dropped the ball I should have been all over it. Brain freeze, old age, no bearing on the outcome of the game, etc, etc, etc. Still not accepatable to me, for missing the call.

[Sco53]

Is it acceptable to point foul at the moment it is touched and then wait to see the result of the catch/no catch?

[bob jenkins]

Originally Posted by Sco53

Is it acceptable to point foul at the moment it is touched and then wait to see the result of the catch/no catch?

Not only acceptable, it's preferred (or required).

[Mrumpiresir]

Originally Posted by jicecone

Your absolutely correct, no excuse. As soon as the player hit the ground and dropped the ball I should have been all over it. Brain freeze, old age, no bearing on the outcome of the game, etc, etc, etc. Still not accepatable to me, for missing the call.

Don't beat yourself up about it. It happens to all of us.