“An error is a statistic charged against a fielder whose action has
assisted the team on offense, as set forth in this Rule 9.12.”
– MLB Rule book, 2023
These questions seem natural:
1) Are the number of fielding errors correlated with a team’s winning percentage? If so, how were are they correlated?
2) Are errors uniformly distributed? That is, given the frequency of the 24 game states (as described in the game states post), do errors occur in the same rough frequency?
In the case of the 2nd question, the states with bases empty (0, 1, or 2 outs) are the most commonly occurring states, followed by the states with a runner on 1st (only). For a randomly selected game from the 81 home games of a given MLB team in a given season, are the proportions
“plays with bases empty (batter up, pitcher about to throw first pitch)”: “plays with runner on 1st (only)”
and
“plays with bases empty that have an error”: “plays with runner on 1st (only) that have an error”
roughly equal? (Short answer: I doubt it.)
To these and related questions, we use Retrosheet to compile data. The plays below use the Retrosheet event file notation, as explained in the Retrosheet documentation.
For example, what we examine these questions in the case where the team is the Baltimore Orioles and the (regular) season is 2019? The O’s had a low winning percentage that year: 33.3% in 2019 (the year Brandon Hyde was hired as the Orioles’ manager).
The Orioles finished the 2019 season with 54 wins and 108 losses. The team was also below the league average in offensive categories runs scored, batting average, on-base percentage, and slugging percentage. In the 81 home games, 111 errors were committed, 59 by a visiting team and 52 by the Orioles. The Os played 12 games with at least 3 errors (by both sides), and 6 games with 2 errors. A significant proportion of the errors were in those 12 games: about 15% of the games had over 1/3rd the total number of errors.
Here are three particularly interesting plays from that season of Orioles home games. Back-to-back errors that occur for consecutive batters, such as Alberto–Mancini below, are relatively uncommon. But so are put outs with an error modifier that didn’t get negated by that error, as in the 3rd play below.
- During the game TBA (Tampa Bay Rays) vs BAL (Baltimore Orioles) on 2019-08-22, the state before was (0,0,0,0,1,0,0,1). The batter came up to the play and a simple type of error occurred:
play,1,1,albeh001,01,CX,E6/TH/G. The state after was (0,1,0,0,1,0,0,1).
Summary: In the bottom of the 1st inning with bases empty, BAL batter Hanser Alberto hit a ground ball to short. A throwing error by the shortstop allowed the batter to reach 1st. - Trey Mancini is next in the batting line-up. The state before is, as we know, (0, 1, 0, 0, 1, 0, 0, 1), where the runner on 1st is Alberto. Mancini’s play is:
play,1,1,manct001,00,X,D7/G+.1-H(UR);B-H(TH)(E6/TH)(NR). The state after is (0, 0, 0, 0, 1, 0, 2, 1).
Summary: In the bottom of the 1st inning with a runner on 1st, BAL batter Trey Mancini hit a hard ground ball double to left field. The runner on 1st base scored (1 RBI). A throwing error by the shortstop allowed the batter to stretch the double into a home run (no RBI).
[Video showed more details of this unusual play: the left fielder attempted to throw out Alberto at home, but the throw was to the shortstop, not the 3rd baseman who could have held Mancini at 2nd. This is not an error. However, the shortstop’s errant throw home, hoping to stop Alberto form scoring, went into the camera well, so by MLB Rule 5.06(b)(4)(A), the Umpire awarded Mancini an extra base.] - During the game SDN (San Diego Padres) vs BAL on 2019-06-25, the state before was (2, 1, 0, 0, 3, 5, 1, 1). The batter came up to the play and a simple type of error occurred:
play,3,1,smitd007,00,X,D9/G+.1-H;BX3(95)(E9). The state after was (0, 0, 0, 0, 4, 5, 2, 0).
Summary: In the bottom of the 3rd inning, BAL batter Dwight Smith hit a ground-rule double to right field. The runner on 1st base scored (1 RBI). The batter stretched the hit into a triple, due to an error by the right fielder. Here, the error (E9) does not negate the tag (BX3) in this case but the explanation is complicated: The runner reached 3rd but then (mistakenly?) stepped off and was tagged out. It was ruled that the error by the center fielder allowing the batter to reach 3rd was unrelated to the put out at 3rd. The batter was tagged out at 3rd base by the third baseman after safely reaching the bag. This out was the 3rd out, ending the half-inning.
There are 108 others described in the full report “Game states via Retrosheet: Errors in BAL 2019 home games”. It’s available as a (approx 40-50 page) pdf for anyone who wants it. Just email me at wdjoyner@gmail.com.