Detroit’s Batted-Ball Readings Are Hot

Editors Note: Analysis in this article was conducted using Baseball Info Solutions Hard Hit batted ball data.

To be clear, this did not begin as an example of investigative journalism. While I do occasionally enjoy media pieces such as Spotlight and S-Town, my curiosity in this topic all began with the incredible amount of attention given to a seemingly mediocre player named Nick Castellanos. To give some examples, below are three popular FanGraphs/RotoGraphs articles written about Castellanos:

In theory, the hype surrounding Nick Castellanos makes sense. High hard-hit rate, few ground balls, sustainable HR/FB%, and a decent home ballpark. If only he could get those strikeouts down and avoid bad luck, he could turn into Kris Bryant or Nolan Arenado. The analytics community, who have been waiting for the Castellanos breakout for five years, is more divided than ever on the Tigers third baseman. Some continue to beat the drum while others are abandoning ship, arguing that the breakthrough will never happen.

This season, Castellanos is not the only Detroit Tigers player who has received love from the analytics community:

The claims brought up by all of these writers have one thing in common: high or increased hard-hit rate. As presented in Matthew Ludwig’s article The Value of Hitting the Ball Hard, hard-hit rate and wRC+ have a positive correlation. In general, a player who hits the ball harder would be expected to have more favorable results when they make contact.

This brings us to the question, is it possible for so many Detroit Tigers players to be underperforming their batted-ball profiles? In order to gauge exactly how much harder the Tigers are hitting the ball than their opponents this year, I took a look at the hard-hit rate for the Tigers as a team. The point that is colored “Tiger orange” represents the Detroit Tigers.

Screen Shot 2017-06-17 at 2.59.39 PM

It isn’t even close; the 2017 Detroit Tigers are currently the best team at making hard contact and the worst team at preventing hard contact. Thinking qualitatively, are the Tigers hitters really that much better at making hard contact than the hitters on the Astros, Nationals, or Diamondbacks? Are the pitchers really that much worse at preventing hard contact than the pitching on the Padres, Orioles, or Reds? If so, the results are not proving it. The Tigers currently rank ninth in runs scored and 20th in runs against. Park factors and other variables do apply, so it may be possible that the hitters are getting unluckier and the pitchers are getting luckier than the batted-ball data shows. Assuming that players’ abilities are transferable across stadiums, we should small differences in hard-hit rate for Tigers hitters and pitchers when looking at home/away splits.

Screen Shot 2017-06-18 at 9.18.25 PM

Quadrant I (x,y) represents the teams that have a higher hard-hit rate for both hitters and pitchers on the road than at home. Quadrant III (-x,-y) represents the teams that have a higher hard-hit rate for both hitters and pitchers at home than on the road. The Detroit Tigers (orange point) rank as the team with the largest negative difference for both hitters and pitchers. One thing to note about the data is that 22 out of the 30 points lie within either quadrant I or quadrant III. This could give some validity to the assumption that hard-hit rate is not consistently measured from park to park. There could be a variety of reasons for this (humidity, air density, etc.). For more on this, I would point to Andrew Perpetua’s article Home And Road Exit Velocity. If there was truly something unique about Detroit causing these balls to be measured harder, this trend would be seen over a wider time period. Let’s look at where the Tigers ranked for the years 2012-2016.

Screen Shot 2017-06-19 at 10.14.50 PM.png

See that orange circle almost directly in the middle of the chart? That is the Detroit Tigers. The only point that has a closer distance to the direct center is the Atlanta Braves, who now play in an entirely different city and stadium.

So what about all other stadiums? If hard-hit rate is being artificially increased at Comerica Park, it is likely that there are slight adjustments at all ballparks. Based on 2017 data, the difference for each stadium (hitters or pitchers) is listed below:

Screen Shot 2017-06-19 at 9.05.05 PM

Looking at an individual-player level (min. 50 AB home and away, min. 20 IP home and away), let’s see how many Tigers batters appear on the top 20 away-home hard-hit-rate difference leaderboard for hitters and pitchers. Detroit Tigers players are highlighted in orange.

Screen Shot 2017-06-19 at 9.37.18 PMScreen Shot 2017-06-19 at 10.31.05 PM.png

I can see four possible scenarios to explain why Detroit Tigers players may be experiencing this phenomenon:

  1. Tigers hitters and pitchers have actually experienced large splits between home/away hard-hit rate this year (with no other variables changing)
  2. Something about Comerica Park is causing increased error in the variables used for the quality of contact algorithm
  3. Changes are being made to the ball or environment at Comerica Park, making it act differently
  4. Small sample size bias is skewing the data

Unfortunately, this is about as far as I can take this piece. Something is going on in Detroit this year that is skewing the hard-hit-rate calculations. However, the whys and hows beyond the data are not clearly evident. Until then, I will continue to monitor this unintended project of investigative journalism from the sidelines.

Newest Most Voted
Inline Feedbacks
View all comments
5 years ago

Great article. I appreciate you laying out all the possible explanations instead of just picking one and trying to make it all fit.

I hope this gets some pub at the top of the new home page.

5 years ago

This is really good analysis. Can we get the good people at Baseball Savant to give their take on this?

5 years ago

Great article. It seems so abundantly clear that Comerica’s data is wrong after reading your argument. It would be great to have a regularly-running test to flag this type of issue in Statcast data (of course they should be doing this internally!).