
Cut block consequences...
Seriously, every single year before the Air Force game I get nervous that someone will get injured, whether it be a high ankle sprain, a torn ACL or whatever the case is. It is just commonplace when playing them that someone will inevitably get caught flat-footed and rolled up on. Last year we suffered a very, very substantial injury to the defensive line due to the Air Force cut block, breaking the ankle of 4 year starting DT Kelly Griffin and keeping him out until the Rose Bowl. Oddly enough, TCU was lucky enough to have sophomore Jeremy Coleman and D.J. Yendrey step in and fill his void nicely. I'd like to see more out of the same from those two this year, although Coleman is most certainly M.I.A. so far this fall. Former standout cornerback Drew Coleman also was injured during his TCU days due to an Air Force cut block. Coleman hurt his knee, and fortunately for him it wasn't very severe because now he's found a good home in the NFL spending the past several seasons as the Jets nickel back before coming over to Jacksonville this season.
I'd say our players need to be alert and on their toes, looking out for cut blocks and avoiding injury, but from everything I read and see there's really no way to avoid it. Plain and simple- you will be cut blocked and we just have to hope we don't sustain any injuries because of it. Our depth on the DL isn't exactly stellar, and we have a lot of young guys getting serious playing time at that spot and I hope they aren't forced into permanent action. As evidenced by the Drew Coleman injury a few years back, defensive backs aren't out of the woods either, and we can ill afford to lose any DB's, because as we saw against Baylor, that is an area where we need to grow up fast and get stronger. Let's all hope that week 2 goes a lot better than week 1, and we make it back for the home opener in good health and are ready to roll with a 1-1 record.
7 comments:
a chop block is not what our RB did in the third qt. (the rediculous penalty that stopped us from being 1st and goal on the 4)
Yeah I worded that poorly. What I was saying is that a "chop block" is legal unless the defender is engaged with another blocker, which is the penalty we got called for- engaging a defender who is already being blocked. Didn't mean to say we chop blocked.
I think I worded that poorly too. Oh well.
oh i didnt realize that aspect of the penalty. i dont remember the play exactly, but that could give it some validity. personally i thought it was a lame call given the frogs predicament
any idea when we play baylor next?
whenever they get a handle on their future Sun Belt schedule and need to fill in the gaps.
The Frogs will be fine.
haha yes - the Sun Belt. i've heard OU and grambling state (really) are our non-conferencers for 2012.
Post a Comment