"Last team with the ball wins" is a cliche, but sometimes cliches are the best way to get across the central narrative of an important game. If you like great quarterback play, you have to watch the NFC Championship Game.
07 Sep 2012
by Bill Connelly
In my second ever Varsity Numbers column in 2008, I discussed how I tend to view turnovers using the Equivalent Points measure:
In just about any football game, you'll see a reference to turnover margin, or maybe points off of turnovers. But it doesn't take in-depth thinking to realize that not all turnovers are created equal. If a running back fumbles on his opponent's 1-yard line, that's a huge turnover because his team had a high level of expected points, and he threw them away. And if he fumbles on his own 1, that's also huge because it hands his opponents a high level of expected points. And if he fumbles on his opponent's 1, and it's returned for a touchdown, that's doubly huge -- it cost his team quite a few points and handed his opponents a touchdown. But in turnover margin, all three of those fumbles count the same as if some backup quarterback fumbled at midfield on the last play of a 49-7 game.
It seems clear that, as FO has covered in the past, counting the significance of two values -- the team's field position when the turnover happened, and the opponent's resulting field position -- gives you a much better view of a turnover's true costliness. And that's what we're going to try to do.
Let's look at two turnovers:
* Turnover 1: Team A is about to score. Their running back carries the ball inside the 1, then fumbles. The ball bounces into the arms of a safety, who carries it 100 yards for a touchdown.
* Turnover 2: Team A's quarterback fumbles at his 45-yard line, and Team B recovers. Team B then immediately goes three-and-out and punts the ball back to Team A.
Using my numbers, Turnover 1 was worth 12.62 points (5.62 points for being at the opponent's 1, 7.00 points for being returned for a touchdown). Turnover 2 was worth 4.26 points (1.92 points lost/prevented, plus 2.34 points given/taken). Is that not a much more accurate read of which turnover truly impacted the result of the game and which did not?
I have used the Turnover Points concept frequently in my work at SB Nation, and it really does fill in quite a few gaps in terms of the difference between points scored, yards allowed, and huge special teams plays made. With Brian Fremeau revisiting the turnovers concept earlier this week, I thought it would be interesting to look at turnovers myself and see what we can glean from Week 1's action.
In all, Week 1 saw FBS teams play 76 games, 32 against FCS teams and 44 among each other. On average, the games saw 3.5 turnovers worth approximately 5.2 Turnover Points each. When you think about it, that is pretty staggering. For all the analysis we do about talent, matchups, etc., about 18 points per game (3.5 x 5.2) are determined simply by your ability to either force terrible mistakes, avoid them, or get lucky and fall on one when it hits the turf. No wonder football coaches often go gray faster than U.S. presidents.
In all, the results of 11 Week 1 games were decided almost entirely by turnovers. Below you will see those games broken out with the following columns: week, date, teams, score, turnovers committed, equivalent point value of those turnovers, scoring margin, turnover points margin, and "Non-TO Margin," which signifies the difference between the scoring margin and turnover points margin. For the 11 games below, the winning team had a positive turnover points margin and a negative "Non-TO Margin."
|Week 1||8/30/12||Kent State||41||0||0.0||+20||+27.1||-7.1|
|San Diego State||12||3||19.6|
|Week 1||8/30/12||McNeese State||27||0||0.0||+6||+9.9||-3.9|
|Week 1||9/1/12||Wake Forest||20||1||4.3||+3||+9.2||-6.2|
|San Jose State||17||2||9.9|
|Week 1||9/3/12||Virginia Tech||20||0||0.0||+3||+4.4||-1.4|
For a couple of these games, you could make the case that turnovers defined the game but didn't decide them. If Kent State and Illinois had not benefited so significantly from turnovers, they may not have taken the foot off of the accelerator, so to speak, and they may have done enough damage to win the game regardless. (Then again, Illinois quarterback Nathan Scheelhaase got hurt, so...)
For the other nine games, however, turnovers both defined and potentially decided the winner. Bounces ruled in the Ohio-Penn State game; not only did Ohio benefit significantly from turnovers, but they also benefited from a non-turnover. On their first touchdown, Ohio quarterback Tyler Tettleton saw a horrendous pass bounce off of the hands of a Penn State defender (said defender was actually stepping in front of another Penn State defender who might have picked the pass off) and into the hands of his intended receiver, who caught the pass and ran for an unlikely touchdown. Make no mistake: Ohio made the plays it needed to win the game late. But without turnovers, they don't win.
Turnovers made the difference in quite a few upset bids as well. Indiana and Wake Forest each avoided embarrassing losses to FCS teams that had otherwise potentially outplayed them (Liberty actually outgained Wake, 363 to 293), while Stanford narrowly avoided a loss in their first game post-Andrew Luck thanks to 10 turnover points. Washington escaped a bit of a stinker and held off San Diego State thanks to a 14-point turnover margin. UTSA and Northwestern each scored last-second road wins in part because turnovers kept them close enough through the game's first 59 minutes; meanwhile, Virginia Tech and Georgia Tech were in complete gridlock heading into overtime, but Tevin Washington's incredibly misguided overtime interception made the difference. And, finally, turnovers sealed an upset bid (if you can call it an upset) for McNeese State over poor Middle Tennessee, which has fallen off the map over the last couple of years.
So much of college football is determined not only by who can avoid throwing stupid passes, but who is lucky enough to intercept a given stupid pass (instead of simply breaking it up, or, in Penn State's case, batting it to an opposing receiver). It's determined not only by forcing or avoiding fumbles, but picking up the loose ball when it begins to bounce around in an abstract fashion. Turnovers obviously aren't based entirely on luck, but they are just random enough to drive you crazy. As much as or more than any other sport, college football allows fans of a given losing school to defiantly say "We gave them that game," or "They didn't beat us, we beat ourselves." It is oddly comforting to say such things, and as Week 1 proved, it isn't entirely inaccurate, either.
Week 2 F/+ rankings are now updated here. Obviously these are still based mostly on preseason projections, with a little bit of raw Week 1 data thrown into the mix. With no true opponent adjustments of which to speak, obviously the data is going to overreact to certain games (Alabama over Michigan, Duke over Florida International, or the S&P+-specific Random FBS Team who dominated Random FCS Team), but such is life. These kinks will work themselves out as the opponents adjustments take hold.
(Note: you can find updated S&P+ rankings at the same page. I was hoping to set up this year's S&P+ page this week but ran out of time. You can find the numbers there regardless.)
|F/+ Rk||Team||Record||F/+||Last Wk.||Change||S&P+||S&P+ Rk||FEI||FEI Rk|
|F/+ Rk||Team||Record||F/+||Last Wk.||Change||S&P+||S&P+ Rk||FEI||FEI Rk|
Once again, I will try to share with you some relevant pieces I wrote this week at SB Nation and elsewhere.
1 comment, Last at 07 Sep 2012, 5:03pm by Aaron Brooks Good Twin