The Most Wrong Called Ball of June
Imagine, for a second, that Major League Baseball had an automated strike zone, and there weren’t any bugs in the system. Imagine that the zone were specifically defined, changing consistently for each hitter, such that there couldn’t ever be any dispute. The zone would be perfect, and any given pitch would be either a definite strike or a definite ball. What you have imagined doesn’t exist. Instead, we have human brains doing everything, and sometimes human brains fall for magic tricks and infomercials. Umpires make mistakes, and because of that, any pitch could conceivably be called either way. There’s always some probability, however small, that a bad pitch might be called a strike, or that a good pitch might be called a ball. This is the way it is, and for now the rate of mistakes is low enough that we haven’t had a bloody revolt.
Because there are mistakes, there is a spectrum of mistakes, with some being the most understandable and some being the most wrong. The most wrong strike-zone call would be a call with the greatest difference between the actual call and what the call should’ve been. Imagine a fastball down the middle. If it’s taken, and called a ball, that would be a big mistake on the umpire’s part. With all this in mind, the month of June is over, so I thought we’d take a look at the month’s most wrong ball call. In part out of curiosity; in part to see what we can learn. Get ready for a little Edwin Jackson.