Jered Weaver threw a no-hitter on Wednesday night. Weaver has been a really good pitcher for the past several seasons, so the fact that he threw a no-hitter, against the Minnesota Twins, is not too surprising (although still an incredible accomplishment). During his no-hitter, Kevin Goldstein tweeted the following “Jered Weaver's ability to manipulate a baseball is remarkable. Guys with that stuff and that arm angle should not be THIS good.” This re-invigorated me to research something that I have wondered about for a long time – what impact does a pitcher’s height, release point, and ability to hide the ball have on the hitter’s chances for success?
The underlying impact of all three of these variables is the change in a hitter’s reaction time. You’ll see some times later in this post, but MLB hitters have an otherworldly small amount of time to see a pitch, start their swing, and make solid connection using a round bat moving approximately 72 mph on a round ball moving in the opposite direction at approximately 90 mph. If a pitcher can manipulate a hitter’s reaction time to be even shorter by taking advantage of height or pitching delivery, the impact is far-reaching on every one of that pitcher’s pitches, not just the fastball. The hitter has precious fractions of a second to attempt to hit a pitcher, and if a pitcher can steal even a few of those milliseconds from the hitter, the pitcher’s chance of success can only increase.
Let me begin my detailing some assumptions that I have made. First, it is difficult for me to provide a precisely accurate release point for a pitcher based on his height. I have made an estimation for release point in the following manner: I have assumed that the length of a man’s leg is 53% of his height (I’m 73 inches tall, my inseam from floor to crotch – I really wish there was another word for crotch - is 39 inches long, and I feel I’m proportionally representative of an average person, #humblebrag). Next, I have assumed that at release, a pitcher’s plant leg is bent to be half the height of his leg when fully extended. Using these two pieces of information, and the Pythagorean theorem (look, Mom, I’m using trigonometry!), we can determine an approximate distance from the pitching rubber that a pitcher releases the ball. See the below picture for the illustration:
I created these tables with three variables that can be changed to generate different results: Pitcher height, ball hiding (using a -6 to +6 in. scale), and pitch speed. In this first table, I have held pitch speed constant at 90-mph, and ball hiding constant at 0 (average), and have adjusted the pitcher’s height by 1 in., starting at 5’10”, and increasing to 6’10”.
Now, look at the change in reaction time based on a pitcher’s height. Adding one inch to a pitcher’s height changes the time a ball is visible by 0.0003 seconds. While you don’t yet know how this compares relative to the other variables, I can assure you that this isn’t very much, unless you look at the difference between the 6’10” pitcher and the 5’10” pitcher, in which case the visible time is 0.0035 seconds less. This is more significant.
In the next table, pitch speed is held constant at 90-mph and the pitcher’s height is held constant at 6’4”, which seems about right for the average MLB pitcher. The only variable is the change in when a ball becomes visible to the hitter.
There are so many variables to pitching, and just isolating these three doesn’t paint the whole picture. The movement on pitches, the sequence in which they are thrown, the hitter’s preference to a pitcher’s style, and the platoon matchup are all extremely significant. But this at least gives you a taste of the impact of a pitcher’s size, mechanics, and pitch speed on the hitter. One last table for you, which shows what I estimate Weaver’s three inputs for these variables are. Weaver is 6’7”, averages a 90-mph velocity on his fastball, and I am giving him the best rating for release point.
Peter Ellwood is a Senior Staff Writer for Shutdown Inning. You can email him at Peter.Ellwood@shutdowninning.com or reach him on Twitter @Peter_Ellwood