This Game-Ending Called Strike Defied All Reason And Logic

Marty Foster admits he blew the call, but that still doesn't explain how it happened.

Angel Hernandez's strike call in the 2013 World Baseball Classic, below, was pretty horrendous.

buzzfeed.com

But we've found one that's worse. Much worse. Here's Marty Foster's version of a "strike," one that ended the Rays-Rangers game last night.

img.gawkerassets.com

The batter, Ben Zobrist, was rather upset by the call.

Rays manager Joe Maddon? Pretty livid.

James Loney? STUNNED DISBELIEF.

PITCHf/x said it was about half of a foot from being on the edge of the zone.

baseballprospectus.com

Here are the TV and radio calls for each club. Not one person on either side of the game could believe that Foster called it a strike.

Via mlb.mlb.com

After the game, Foster said, "had I had a chance to do it again, I wouldn't call that pitch a strike." Because, really, look at this.

What's odd, though, is Foster called this other, closer pitch to Zobrist a ball in the same at-bat. It's not like he just got momentarily crossed up by an unexpected pitch motion.

So why did he call the last one a strike? ESPN's Keith Law dubbed it a classic "ump show" moment, especially given Zobrist's move toward first before the call was made.

Here's what Zobrist did, which is only what any ballplayer with decent judgment of balls and strikes might do.

Then again, there's no recourse to be had, so there's little sense in getting upset about the whole thing.

But let's review, one more time. This is not a strike:

But this is a strike:

After the game, Zobrist was rather philosophical regarding the whole debacle: "Everybody makes mistakes. What are you going to do?"

i.imgur.com

As for Rangers pitcher Joe Nathan, he knew he'd gotten away with one. When even the pitcher is suppressing a smile at your call, you've really gotten it wrong.

baseballprospectus.com