The Jets and the Odd Use of the Wildcat

Use your ← → (arrows) to browse

Sep 16, 2012; Pittsburgh , PA, USA; New York Jets quarterback Tim Tebow (15) runs the ball past Pittsburgh Steelers defensive end Ziggy Hood (96) during the second half of the game at Heinz Field. The Steelers won the game, 27-10. Mandatory Credit: Jason Bridge-US PRESSWIRE


We have been over the result, no need to rehash it at this point. Needless to say, aside from early in the game, the offense looked lost. Mark Sanchez was inconsistent at best, and had no help from his wide receivers. All of that flow that the Jets had in the win over Buffalo, that was the lack of flow they had against the Steelers. The offense needed a change of pace, clearly.

The Wildcat? A whopping 3 snaps. The first of those snaps yielded the top running play for either team all game long, when Tim Tebow ran for 22 yards. His emotion coming off of that play was palpable. They ran two more plays, Sanchez was back, and we never saw the Wildcat again on the day. Very odd.

Also, did the Jets forget about the performance Tim Tebow had against the Steelers, in that building in the playoffs? He threw for 316 yards, 2 scores, and ran for 50 and a score. He has been a success against that team. If you were ever going to let the package loose, this past Sunday would have been the day to do it.

The common denominator in both games, has been the fact that Tebow hasn’t thrown a pass yet. We can argue about his fundamentals, not the point here. The point is, Tim can get the ball downfield with the pass out of this package. If you don’t ever try it, you are saying that the only thing they are going to do out of the Wildcat is run the football. Eventually that will be figured out.

Are the Jets still feeling their way with the Wildcat package? Sure. Figuring out where to use it and not to use it? Definitely. Are they holding some of it back? Probably. But they had better figure this thing out. If the Wildcat doesn’t serve a defined purpose, it won’t work out.

Use your ← → (arrows) to browse

comments powered by Disqus