The Crimson Tide was atrocious in the red zone in 2006, and no one needs any in-depth analysis to figure that one out. But exactly how bad were we, and how much did it hurt us?
Answering the first question, it was as bad as you think, and then probably worse.
After running the numbers, we made 53 visits to the red zone in 2006. Of those 53 visits, we scored on just over 75% of them (40), which is a good -- but certainly not great -- number. The major problem, of course, was being able to put the ball into the end zone. All told, we only scored 20 touchdowns in 53 trips to the red zone, thus putting it in the end zone on only 37.74% of red zone trips.
It gets worse.
When we look at the eight conference games the Tide played (which, of course, we went 2-6), we made 28 trips to the red zone. Of the 28 times that we got into the red zone in SEC play in 2006, we managed a mere 6 touchdowns. 6 touchdowns in 8 conference games. Long story short, we scored a touchdown on only about 20% of our red zone trips in conference play.
Now let's compare that to LSU, who led the conference in both total offense and scoring offense. Believe it or not, LSU had essentially the same number of red zone trips in conference play that we did (LSU had 30 red zone trips, we had 28). But, of course, they did much more with theirs. All told, LSU scored 22 touchdowns in their 30 trips, and, well, that was a big part of the reason why they led the conference in point production.
So exactly how much did the lack of productivity in the red zone hurt us in terms of wins and losses? Quite a bit, it would seem. With even half-way decent red zone production (say, just to quantify that, 14 touchdowns on 28 trips), our final win-loss record would have been drastically different, and the margin of victory in the games we did win would have gone up as well.
Against Hawai'i, despite us leading all night, it turned out to be a close game, with victory ensured only when a time-expiring Colt Brennan heave to the end zone was intercepted by Lionel Mitchell. We went to the red zone five times that night, and emerged with only one touchdown. With decent red zone production, that game never comes down to a last-second heave.
Against Vanderbilt, the following week, we narrowly edged out a 13-10 victory, at home, over the eventual 4-8 Commodores after Leigh Tiffin booted a 47-yard field goal late in the fourth quarter. During that game, we went to the red zone four times, scored no touchdowns, and came away with only six points. Again, with decent red zone production, that game is never that close; we would have by somewhere in the neighborhood of 14-20 points.
Against Arkansas, two weeks later, five trips to the red zone netted only one touchdown and ten points. Even with slightly better than atrocious red zone production, much less decent production, Alabama wins that game in Fayetteville. Instead, horrendous red zone production turns a sure-win into a one-point loss.
The following week against Florida, two red zone trips netted six points and no touchdowns. Decent red zone production might not have turned this game into a win, but it would have made it very close. Most people forget that this was a 14-13 game with under seven minutes to go in the fourth -- and Alabama having the ball. With decent red zone production, we likely have a 17-14 lead at that juncture, and instead of throwing the football -- which led to a Reggie Nelson interception returned for a touchdown that ultimately doomed us -- we are running out the clock. Again, Florida may still have won, but it would have been a much closer game.
Against Ole Miss -- big shock forthcoming -- we actually had solid red zone production. I've written before that it was probably our best offensive performance, and rightfully so. Four trips to the red zone resulted in 20 points (two touchdowns and two successful field goals). And -- big shock again -- we won this one, though one of the poorest defensive efforts of the year turned it into a very close game.
The following week in Knoxville, poor red zone production was largely responsible for a loss to the hated Volunteers. We had three trips to the red zone, and could muster only one touchdown. With just one more touchdown on the other two red zone trips (again, my definition of half-way decent red zone production), we win that game. Instead of leading 13-9 late, we would have been leading 17-9, and Tennessee would have not only needed to score a touchdown, but successfully complete the two-point conversion just to force overtime.
Against Mississippi State, it was more of the same. Four trips to the red zone netted zero touchdowns and only nine points. In a game ultimately decided by eight points, decent red zone production could have gotten us a win.
One week later against LSU, we played the Bayou Bengals surprisingly tough, but again... red zone woes. We made three trips to the red zone, which netted only ten points. Although this is most likely still a win for LSU with decent red zone production, it would have went right down to the wire in a close contest, particularly if Jamie Christensen could have connected on a first quarter field goal.
Against Auburn, in the Iron Bowl, red zone woes played another big role in our loss. Three red zone trips resulted in only one touchdown, and nine total points. Again, with decent red zone production, we may win that one.
At bottom, red zone woes really killed our 2006 team. It wasn't just that our problems in the red zone hurt us some, they have a drastic effect on our overall win-loss record. We finished the regular season at 6-6, but being quite objective about it, and decent red zone production would have probably given us an 8-4 or 9-3 regular season record, with those losses being very close losses at that. That would have put us, likely, in the Peach Bowl, and Mike Shula would still be the head coach of the Crimson Tide.
The good news though, I suppose, is that with nine starters returning on the offense for 2007, this group should be able to finally break through and translate all of that potential into points.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment