Dealing with a game changing call

[johnnyg08]

I never worry about ball/strike calls.  If it's close enough for me to call a strike, the kid should be swinging.  HS on down - SWING THE BAT!

 

Had one the other day - called a ball on a pitch maybe a ball/ball and 1/2 off the plate.  Immendiately knew I should have called it a striike.  Oh well.  Next pitch  - EXACT same place.  Ball two.  At least I'm consistent.  Pitch #3 - same place again!  Jeszum Crow!  Now I'm begging the catcher to set up somewhere else. 

 

Kid got a free BB becasue I missed the first pitch.  Big deal.  It was a HS baseball game.  The sun rose the next day.  And we all had lunch (obscure Red Sox quote)

 

 

If you miss a pitch...don't miss more pitches because you missed one before.  Think of the slippery slope that creates.  

 

So if you miss a pitch right down the middle, are you going to ball it for the rest of the game?  

 

What if you call a strike at the guys neck...do you now have to call that a strike for the rest of the game in the name of consistency?  

 

None of us are perfect, but I would challenge you to reconsider your approach following a missed pitch.

[bam]

So are you saying you intentionally missed 2 more pitches in the name of consistency???

 

 

So are you saying you intentionally missed 2 more pitches in the name of consistency???

 I got stuck.  So yes - They were pitches I would have called ordinarily, even though they were off the plate.  It's not as if they were dead red.  They were borderline.  I've done the Ball/Strike call when the pitch is in the same location in the past - at least I didn't miss them both is what I tell the coach.  But since these were ACTUALLY outside, and I called the first one a ball, I had to stick with it.  And yes, in the name of consistency.  I let the catcher know after the at-bat those were going to be strikes going forward.  Plus it was a scrimmage. 

 

In hindsight, I probabaly should have told F2 I missed it, sorry.  Just one of those things.  Couple lessons here.  DON'T miss the first dman strike.  Let F2 know immediately, don't wait. 

[Moriarty_45]

With R2 only, I was on the line. That is the mechanic. We do use go opposite of that with 2 outs though. U1 on the line, U3 in the middle.

R-2 only in a bunt situation with a tie game you can stay on the line and bring U-1 into the B position. U-3 stays on the line and is in a much better position to rule on a play at 3rd base. Some crews are inflexible and will not try this. We're you in "short C" ? Situational umpiring. Set yourself up for success

[Stan W.]

I've never met an umpire that wanted to be wrong.....I have met a few that didnt do enough to prevent it though......over the years I've worked with the "anguish over every call" guys and the "when in doubt call 'em out, it dont bother me" types ......... The extremes in both cases are wrong.....

 

On the whole I'd rather work with the guys who anguish......I know they wanted to get it right and for the most part will be open to advice or training to not let it happen again.......or they can be reassured by support that they did the best that could be done.... 

[noumpere]

 I got stuck.  So yes - They were pitches I would have called ordinarily, even though they were off the plate.  It's not as if they were dead red.  They were borderline.  I've done the Ball/Strike call when the pitch is in the same location in the past - at least I didn't miss them both is what I tell the coach.  But since these were ACTUALLY outside, and I called the first one a ball, I had to stick with it.  And yes, in the name of consistency.  I let the catcher know after the at-bat those were going to be strikes going forward.  Plus it was a scrimmage. 

 

 

In hindsight, I probabaly should have told F2 I missed it, sorry.  Just one of those things.  Couple lessons here.  DON'T miss the first dman strike.  Let F2 know immediately, don't wait. 

 

I think calling 3 one way and then changing is worse than calling 1 one way and then changing.

[bam]

 I got stuck.  So yes - They were pitches I would have called ordinarily, even though they were off the plate.  It's not as if they were dead red.  They were borderline.  I've done the Ball/Strike call when the pitch is in the same location in the past - at least I didn't miss them both is what I tell the coach.  But since these were ACTUALLY outside, and I called the first one a ball, I had to stick with it.  And yes, in the name of consistency.  I let the catcher know after the at-bat those were going to be strikes going forward.  Plus it was a scrimmage. 

 

 

In hindsight, I probabaly should have told F2 I missed it, sorry.  Just one of those things.  Couple lessons here.  DON'T miss the first dman strike.  Let F2 know immediately, don't wait. 

 

I think calling 3 one way and then changing is worse than calling 1 one way and then changing.

It's a LOT more noticeable when it's on the same batter. 

[MidAmUmp]

We all miss pitches.  If you know you missed one, lean in on the catcher and tell him "I missed that one.  I'll stay with it and get it next time."  Hell, if it's bad enough, I'll even tell the batter - "I missed that, I won't miss it again."

 

If he throws it in the same spot on the next pitch, get it.  If you ball pitches in the same spot one inning because you missed a pitch, then change your zone the next inning, now you're inconsistent.  Just admit you kicked the pitch and move on.

[Jocko]

Agreed. Fix it immediately.

[Maineac]

We all miss pitches.  If you know you missed one, lean in on the catcher and tell him "I missed that one.  I'll stay with it and get it next time."

^ ^ ^ This is great. ^ ^ ^

 

As a former catcher, this gave the umpire instant credibility in my eyes. A great habit I learned when I was playing that I use now as an umpire.

[NFUA_44]

I can see where Bam is coming from when the pitch is a stretch to begin with.  Anything where they are old enough to understand how to catch I would fix it immediately though.  I will tell F2, so that the batter can hear, that I missed that one and won't miss it again so everyone is aware, and move on from there.