The 2010 Arizona Cardinals And Offensive Formations Using TE
After the drafting of Robert Housler and the free agent signings of Jeff King and Todd Heap, the tight end position is in good shape. The Cardinals traditionally have not been a team to utilize the tight end much, either because of personnel or philosophy.
I hypothesized that with the addition of Heap and King that the 2011 season would feature greater use, with more formations with two tight ends, or with one and perhaps two backs. In my memory from 2010, it was not common to use those formations, even when almost half the season was played with rookie quarterbacks Max Hall and John Skelton.
I pulled up formation data for 2010 and was actually a little surprised.
The Cardinals had 1011 offensive plays in 2010. The tight end was used in the majority of plays. That surprised me. In "normal" formations, Arizona had at least one TE on the field 580 times, or 57 percent.
However, removing the three wide, one back, one TE formation (usually not a formation designed for protecting the quarterback), that percentage goes down to 36.6 percent.
There were 204 plays with two receivers and two tight ends. There were 166 with two receivers, two backs and one tight end.
Interestingly, the two games in which the team used the two back formations the most were when Max Hall started for the first time on the road in Seattle and John Skelton's first start against Denver.
While I was surprised that the tight end was used as much as it was, the most common formation was four receivers. They ran that formation 278 times, 27.5 percent of the time. With both Heap and Housler, I expect this year to see this formation diminish greatly, and of those formations, I would expect the majority of them to have either Heap or Housler lined up wide as a receiver.
This does not necessarily mean that the Cardinals will be a power running team. I just believe that the threat of balance will be greater and that it will give Kevin Kolb a little more protection, in addition to the fact that the second best receiver on the team is a tight end.
It would only make sense to have him on the field more that was the case for the Cardinals in 2010.
7 comments
|
0 recs |
Do you like this story?
Comments
Good number crunching. I wonder how many of the single TE formations turned into running plays and the TE being a blocker, and further how many the TE ran a route after chipping a DL.
Section 103, Row 19
I can probably find that in the chart.
I’ll check tonight if I have time tonight.
Like the Cardinals? Revenge of the Birds is where to go.
Like Arizona Sports in general? SB Nation Arizona is where you'll get it all.
Follow me on Twitter! @senorjessroot
come on Jess...
you’re better than that:)
jk, good stuff. Atleast now maybe Beanie can be on the field without the opponent knowing that he is definitely getting the ball… and going right up the middle.
+1
Gildo, we think alike in that respect. As soon as you said “knowing that he is definitely getting the ball” I thought “and going right up the middle” lol.
Hopefully we’ll use him on tosses to the right, and guard pulls to the right where are real big guys are.
Section 103, Row 19
Another interesting thing to point out in conjunction with these numbers is that Beanie has actually had more success thus far in his career running with 1 TE as opposed to two in there;
He averages 3.52 YPC with 2 TE’s in the game and 4.44 with just one TE in the game., However he also tend to run the ball marginally better as a lone back (4.26 YPC) as opposed to as part of the I-Form (4.18 YPC).
However, you get Beanie back to his 2009 form (The knee injury really seemed to hinder him the entire 2010 year) and you can run him in the 2 TE, 1 TE, I-Form, Singleback sets and he should have success.
Random note, Beanie Wells on first downs averages 4.62 YPC over 292 carries and has over 70% of his total yardage on 62.33% of his carries. In 2nd, 3rd and 4th downs her averages 3.17 YPC over 110 carries.
The tight ends are definitely going to add a wrinkle or two to our offense
Some complexity we could definitely use.
























