Bad Losses
As Texas Tech fans we constantly remind ourselves about the "bad game" that we tend to play under Captain Leach. Not wanting to discredit this thought, I couldn't help myself and look into the the past 7 seasons and figure out what was the cause of the "bad game". For what it's worth, I'll go ahead and define the bad game as being a game whereby Texas Tech loses to a supposedly inferior opponent or a game whereby it does not appear that Texas Tech was even remotely ready to play. With definitions out of the way, we move forward.
I know the season is almost upon us and I shouldn't be so negative heading into what we hope is a tremendous season, but those bad losses have bothered me for quite some time and I wanted to take a good look at each of those games. Not only that, the other reason why I'm doing this is to find out if there's any one clear cut reason why Texas Tech lost that game and see if there's some sort of general pattern as well.
Although I've certainly been around since 2000 I must admit that those games and situations are as clearly memorable as they used to be, so rather than rely on my memory to remember if a team was ranked lower than Texas Tech in any particular year, I'm just going to use the Congrove Final Rankings as my guide as to whether not a game was a bad game.

2000: In 2000, Texas Tech finished 7-6 and here are the losses:
At #36 TAMU (15-33)
#5 Nebraska (3-56)
At #8 Kansas State (23-28)
#14 Texas (17-29)
At #1 Oklahoma (13-27)
#29 East Carolina (27-40).
Now I'm tempted to give Leach a pass on this entire season. Texas Tech finished #51, no where really close to any of those teams and what a tough Big 12 slate. After it was all said and done, this being Captain Leach's first year, there's not too much to complain about with how things turned out.
2001: 2001 was marginally better as Texas Tech (#39) completed a 7-5 season and had losses to the following teams:
At #6 Texas (7-42)
#95 Kansas (31-34)
At #5 Nebraska (31-41)
#4 Oklahoma (13-30)
#41 Iowa (16-19)
Wow, a season ending #95 ranked Kansas gets a win, in Lubbock. Pretty amazing if you consider if this were to happen this year and perhaps speaks volumes about where Texas Tech has been. In any event, let's look at the game itself.
According to the game recap (boxscore) the defense gave up some late scores and Texas Tech was forced to play BJ Symons and Kingsbury injured his hand late in the game. Texas Tech turned the ball over 4 times (3 fumbles and 1 Kingsbury INT) while the Kansas offense rushed for 310 yards and had 18 of their 22 1st downs on the ground, including Reggie Duncan's 227 yards on 38 carries for a 6.0 average. The story of our lives, the Red Raiders couldn't stop the run.
Offensively, Kingsbury wasn't terribly effective, averaging only 6.3 yards per attempt, although he did manage 3 touchdowns (for comparison purposes, Harrell had 8.2 yards per attempt from last year). No one receiver really broke out during that game. The interesting item for me is that there were some long completions (Cole Roberts had a 33 yard catch, Ricky Williams 23 yards, Wes Welker 35 yards and Anton Page 31 yards) which accounted for 122 yards, which means that of the remaining 19 Kingsbury completions (he had 23 total) he only had 120 yards, which is only a 6.3 yards per completion. That's just not going to get it done. The rushing game was okay, at least by Texas Tech standards as Ricky Williams finished with 71 yards. When Symons came in, his longest completion went for 15 yards, threw a pick, and appeared to be a little overwhelmed.
Bullet-point Problems:
- Can't stop the run.
- Low yards per passing attempt.
- Too many turnovers.
2002: Things really turned around in 2002, an excellent season by the Captain, 9 wins capped by a nice win over Clemson in the Tangerine Bowl. Texas Tech (#26) finished 9-5 with the following losses:
At #1 Ohio State (21-45)
#20 North Carolina State (48-51)
At #63 Iowa State (17-31)
At #27 Colorado (13-37)
At #3 Oklahoma (15-60)
This one's pretty easy too, the loss to the hated Cyclones. So now we've got two bad losses in two seasons. One at home and one on the road. ISU wasn't quite as bad as Kansas, but still, Texas Tech finished the year appreciably better and Kingsbury was gunning for a Heisman trophy as well.
Here's the game recap (boxscore) and at first blush you scratch your head and try and figure out why Texas Tech lost with 23 first downs, 189 yards rushing and over 82 offensive plays (compared to 68 of ISU).
Many of the same problems that Texas Tech had against Kansas the year before, Texas Tech had against ISU. A paltry 5.3 yards per attempt plagued Kingsbury with the longest pass being a 22 yard catch from Wes Welker and other than Welker's 89 yards receiving, no other receiver had more than 46 yards receiving. The confusing part is that the attempts were certainly there with 51 total, but for whatever reason, there was some sort of disconnect and guys just couldn't catch the ball. I should also point out that Texas Tech had 4 turnovers again with 1 interception and 3 fumbles. Ouch.
The defense's biggest problem, again, was that the Red Raiders gave up 228 yards on the ground for a 5.0 average and Seneca Wallace was quietly efficient, completing 15 of 22 passes with no interceptions and 1 TD.
Bullet-point Problems:
- Can't stop the run.
- Too many turnovers.
- Low yards per passing attempt.
2003: The Red Raiders finished 8-5 (#31), which included a win over Eli Manning, but a few really bad losses. Let's go:
At #35 North Carolina State (21-49)
At #27 Oklahoma State (49-51)
At #38 Missouri (31-62)
At #8 Texas (40-43) #3 Oklahoma (25-56)
Yikes. I can understand the NC State loss, it was at the beginning of the year and NC State was at home. The OSU loss is self-explanatory, Texas Tech always seems to lose to the Cowboys on the road, much like the Longhorns. As far as the Sooners are concerned, ehh. That leaves us with the Missouri game where Texas Tech was absolutely blown out of the water 31-62 (boxscore). Just to recap, 2003 was the year that BJ Symons was leading the Red Raiders and had one of the more amazing quarterbacking seasons that I can recall. In any event, as the game recap mentions, the Texas Tech defense was one of the worst in the nation (113th out of 119 teams) and was giving up an average of 34 points a game, 37 points a game in conference).
So where to start? Missouri scored on their first 6 possessions, automatically putting Texas Tech in quite a hole. Texas Tech managed a field goal and a Symons-Peters touchdown in those 6 possessions. Texas Tech started a slight comeback in the 3rd quarter, scoring 2 TD's, and holding Missouri to no touchdowns, but the 4th quarter proved to be too much for Texas Tech as Missouri scored 4 touchdowns in the 4th quarter alone.
So where were the problems this game? How about quarterback Brad Smith running all over Texas Tech? Smith rushed 19 times for 291 yards and managed to pass for 128. That's not a bad day. Of course this doesn't account for Missouri's ability to rush for a total of 469 yards on the day, a ridiculous 55 rushes for an even more ridiculous 8.5 yards per average.
The other culprit, which again seems to be another theme, is 4 intereceptions and 1 lost fumble. It goes without saying that that's unacceptable.
Symons was actually okay as he completed 40 of 62 passes for 408 yards and 4 touchdowns, but he was responsible for 3 of those interceptions. Obviously, the offense stalled quite a bit in the second half, but without being able to look at how those possessions went, I'm assuming that Missouri running the heck out of the ball had something to do with Texas Tech not being able to do much.
Bullet-point Problems:
- Can't stop the run.
- Too many turnovers.
2004: Another 8 win season, as the Red Raiders go 8-4, but actually finish the season fairly highly ranked, #20, in large part due to the drubbing of #9 California in the Holiday Bowl. Let's get to the losses.
At #47 New Mexico (24-27)
At #2 Oklahoma (13-28)
#6 Texas (21-51)
At #41 Texas A&M (25-32)
The freaking Lobos? New Mexico kicked a field goal as time expired to beat Texas Tech to win 27-24 (boxscore). The Red Raiders and the Lobos came out guns-a-blazing in the first half as each team scored 3 times, but the second half was a struggle as both teams combined for 3 field goals.
Offensively, the Lobos didn't do any one particular thing well. They rushed the ball for 142 yards in 39 attempts (a 3.6 average) and threw for 173 yards. Not horrible by any means. On offense for Texas Tech, Sonny Cumbie threw the hell out of the ball. Cumbie completed 44 passes in 70 attempts for 449 yards . . . but, Cumbie only completed 1 touchdown to Jarrett Hicks. So what was the problem? Cumbie threw for a relatively low 6.41 yards per attempt, which means that he didn't stretch the field much. Granted, there were some long completions, but those completions didn't result in touchdowns. Let's take a look at the last drive for the Red Raiders, prior to New Mexico's game-winning field goal:
1st and 10 on the TexTc 2
TEXAS TECH drive start at 05:35 (4th).
1st and 10 on the TexTc 2
Sonny Cumbie pass incomplete to Bristol Olomua.
2nd and 10 on the TexTc 2
Sonny Cumbie pass incomplete to Joey Hawkins.
3rd and 10 on the TexTc 2
Clock 05:26.
3rd and 10 on the TexTc 2
Sonny Cumbie pass complete to Jarrett Hicks for 18 yards to the TexTc20, 1ST DOWN TexTc.
1st and 10 on the TexTc 20
Sonny Cumbie pass complete to Trey Haverty for 16 yards to the TexTc36, 1ST DOWN TexTc.
1st and 10 on the TexTc 36
Taure Henderson rush for loss of 2 yards to the TexTc34.
2nd and 12 on the TexTc 34
Sonny Cumbie pass incomplete to Taure Henderson.
3rd and 12 on the TexTc 34
Sonny Cumbie pass complete to Jarrett Hicks for 11 yards to the TexTc45.
4th and 1 on the TexTc 45
Sonny Cumbie rush for 7 yards to the NMex48, 1ST DOWN TexTc.
1st and 10 on the NMex 48
PENALTY - PENALTY NMex offside 5 yards to the NMex43.
1st and 5 on the NMex 43
Sonny Cumbie pass incomplete to Trey Haverty.
2nd and 5 on the NMex 43
Timeout TEXAS TECH, clock 02:03.
2nd and 5 on the NMex 43
Timeout TEXAS TECH, clock 02:03.
2nd and 5 on the NMex 43
Sonny Cumbie pass incomplete to Cody Fuller.
3rd and 5 on the NMex 43
PENALTY - PENALTY TexTc false start 5 yards to the NMex48.
3rd and 10 on the NMex 48
Sonny Cumbie pass incomplete.
4th and 10 on the NMex 48
PUNT - Alex Reyes punt 48 yards to the NMex0, touchback
Not real productive, right? There were a couple of decent sized plays with Hicks and with Haverty, but when it mattered the offense didn't deliver. Cumbie was 3 for 11 for 45 yards (4.09 yards per attempt). Couldn't get the ball into the endzone. If we took a look at the entire 3rd and 4th quarters I'm sure we'd see more of the same.
Defensively, the team did well to stop the bleeding in the second half and actually had 2 fumble recoveries (although Texas Tech did lose the turnover battle 2-3). The performance wasn't like the bad games in previous years where the defense struggled to stop the opponent in any meaningful way. The defense did stop New Mexico, but then we're talking about New Mexico, they should stop them.
If I have to pin this loss on anyone, it's the offense's inability to score in the second half.
Bullet-point Problems:
- Can't convert touchdowns in the second half.
- Low yards per passing attempt.
2005: The year of the Cotton Bowl. Not a bad year, all things considered. Texas Tech finished 9-3 (#15) and lost to Alabama in the Cotton Bowl in a personally frustrating game, especially after watching the offense play so well during the season. Here are the losses:
At #1 Texas (17-52)
At #90 Oklahoma State (17-24)
#9 Alabama (10-13)
The Texas Tech loss to Oklahoma State was bad (boxscore). Oklahoma State was a crappy team in 2005, going only 4-7 overall and 1-7 in the conference, Mike Gundy's first year as the head football coach, but I'll give you three guesses and the first two are wrong as to what happened this fateful day.
Couldn't stop the run.
OSU ran for 303 yards on 52 carries for a 5.82 yard per attempt average. OSU's final drive was just a kick in the teeth for Texas Tech and the Cowboys decided that they weren't going to pass at all, gaining only 94 yards through the air. Offensively for Texas Tech, the biggest problem was that the Red Raiders were 0-10 on third downs and rushed for 30 yards on the day . . . total.
Hodges did a pretty respectable job of getting the ball down the field, averaging 7.33 yards per attempt, but with Hodges also being the leading rusher with 36 yards (Henderson managed to lose 6 yards on 8 carries for the game), then things probably aren't going to go your way.
But I think the ultimate blame, again, falls on the defense. Giving up 303 yards is a ridiculous amount of yards and if we take a look at OSU's final drive, it's a testament to what happened pretty much the whole game:
O 1-10 O20 OKLAHOMA STATE drive start at 06:43 (4th).
O 1-10 O20 Hamilton, Mike rush for 1 yard to the OS21 (Saldi,John).
O 2-9 O21 Hamilton, Mike rush for 4 yards to the OS25 (Naziruddin,K.).
O 3-5 O25 Pena, Al pass complete to Pettigrew, Bran for 12 yards to the OS37,
1ST DOWN OS (Meeks,Vincent;Slay,Dwayne).
O 1-10 O37 Willis, Shawn rush for 2 yards to the OS39 (Dawson,Keyunta;Scott,Ken).
O 2-8 O39 Pena, Al rush for 13 yards to the TT48, 1ST DOWN OS
(Meeks,Vincent).
O 1-10 T48 Crosslin, Juliu rush for 11 yards to the TT37, 1ST DOWN OS
(Naziruddin,K.).
O 1-10 T37 Timeout Texas Tech, clock 03:53.
O 1-10 T37 Crosslin, Juliu rush for 9 yards to the TT28 (Session,F.).
O 2-1 T28 Crosslin, Juliu rush for 10 yards to the TT18, 1ST DOWN OS
(Slay,Dwayne;Meeks,Vincent).
O 1-10 T18 Crosslin, Juliu rush for 2 yards to the TT16 (Dawson,Keyunta).
O 2-8 T16 Crosslin, Juliu rush for 12 yards to the TT4, 1ST DOWN OS
(Garcia,Joe).
O 1-G T04 Crosslin, Juliu rush for 2 yards to the TT2 (Session,F.;Hudler,Chris).
O 2-G T02 Timeout Texas Tech, clock 01:08.
O 2-G T02 Timeout Oklahoma State, clock 01:08.
O 2-G T02 Pena, Al rush for 1 yard to the TT1.
O 3-G T01 Pena, Al rush for 1 yard to the TT0, TOUCHDOWN, clock 00:23.
Redden, Bruce kick attempt good.
That's an arse-whipping. Thirteen plays 80 yards and over 6 minutes of clock. Couple this with Texas Tech's final two drives, which consisted of Hodges going 1-6 for 9 yards and only Hodges able to gain positive yards (6) on two rushing plays. The Texas Tech drive before this was a Cody Hodges fumble which was recovered by OSU (Texas Tech lost the turnover battle 2-3).
Keep in mind that OSU was a truly awful team this year and Texas Tech was on its way to a 1 loss conference record (Texas Tech beat OU, I recall some sort of controversy, but I can't remember exactly what that was . . . Go Raiders . . . ). This was a really bad loss.
Bullet-point Problems:
- Can't stop the run.
- Can't convert 3rd downs.
2006: The Red Raiders finished 8-5 for the year and ranked #35 and had the following losses:
At #10 TCU (3-12)
#37 Missouri (21-38)
At #108 Colorado (6-30)
#13 Texas (31-35)
At #15 Oklahoma (24-34)
Colorado had lost 10 in a row before beating the Red Raiders 30-6 (boxscore) so I'm thinking that the Buffs qualify as the bad loss. Colorado finished the year 2-10 and this is as bad as any of the prior years' losses.
Turnovers, turnovers, turnovers. That was the name of the game on this Saturday. Harrell had 3 interceptions and 2 fumbles recovered by Colorado. There was another fumble in there as well, just for good measure. Harrell's 3 interceptions earned him a spot on the bench to be replaced by Chris Todd, fueling a quarterback controversy between the two. Harrell eventually settled down for the year and eventually led Texas Tech to one of the more dramatic bowl victories in the history of ever. Much like Harrell's predecessors, Harrell averaged only 6.05 yards per attempt, again, not enough to be effective in this offense, but his biggest problem was throwing really bad interceptions and being unable to hang onto the ball. That's why there's only 6 points on the board.
Here's how the offense ended each of their drives: punt, fumble, punt, punt, downs, interception, halftime, punt, punt, interception, fumble, touchdown, and interception. Doesn't take a genius to figure out what happened here.
When the quarterback doesn't tick, then it makes it hard on the entire offense. Nothing can really get done.
On the defensive side of the ball, Colorado rushed for 249 yards on 46 carries, a 5.41 average. Other than Colorado's quarterback getting sacked, the running backs only lost 2 yards for the entire day. The Buffalo offensive line was moving Texas Tech back all day. Jackson was never very competent throwing the ball, but he didn't need to be great during this game. He was certainly competent, that's all Colorado needed.
Bullet-point Problems:
- Can't stop the run.
- Turnovers.
- Low yards per passing attempt.
2007: Texas Tech finished 9-4 (#26) for the year and the losses are as follows:
At #48 Oklahoma State
At #6 Missouri
#71 Colorado
At #12 Texas
Although there are a couple of choices here (OSU and Colorado) I'm going to go with Colorado, two years in a row as the Buffs were able to beat the Red Raiders 31-26 (boxscore).
I think this one, again, begins and ends with the turnovers as Harrell threw 4 interceptions for the day, while Colorado had no turnovers. Harrell was efficient throwing the ball completing 74.1% of his passes, but as mentioned many times, had a relatively low yards per attempt average (6.9). Harrell finished with an 8.2 yards per attempt for the year. The running game was virtually non-existent as the team managed only 39 yards for the game, and if my memory is correct, this was the official introduction as Aaron Crawford as the starting running back for Texas Tech as Woods didn't see a down.
Texas Tech out-gained Colorado by quite a bit, but when you throw in those 4 turnovers. LaCour only had to punt the ball once that day and Trlica had only 1 missed field goal. It was a tough game to watch offensively because there wasn't much done on the offensive side of the ball.
Defensively, Texas Tech allowed 217 yards rushing on 44 carries for a 4.9 yard per carry average and Hawkins, although he wasn't great by any means was efficient, completing 15 of 26 for 123 yards and 2 touchdowns. I was at this game and it was incredibly frustrating to see Colorado run around the Texas Tech defenders often and with success.
Bah.
Bullet-point Problems:
- Can't stop the run.
- Turnovers.
- Low yards per passing attempt.
Here's a handy table of the major culprits of those bad losses. I've only used the causes that showed up more than once.
| Cause | 2001 | 2002 | 2003 | 2004 | 2005 | 2006 | 2007 |
| Can't Stop Run | * | * | * | - | * | * | * |
| Too Many Turnovers | * | * | * | - | - | * | * |
| Low Yards Per Passing Attempt | * | * | - | * | - | * | * |
Conclusions: I realize that the causes listed with each game are very general and there are more reasons than the ones listed with each team. These are generalizations, but I also feel that they also ring true with each of these games.
In any event, it looks pretty easy: stop the run, protect the ball and get the ball downfield. It sounds easy, but when you go back and really take a hard look at those game, it's pretty clear that the inability to stop the run and turning over the ball more than your opponent is the kiss of death. I'd imagine that just about any team that looks back could probably draw the same types of conclusions.
I also thought that the low yards per passing attempt was a telling statistic and at the very least should point out that the Air Raid works best when the ball is getting down the field, vertically.
Thoughts, comments, criticisms appreciated.
0 recs |
26
comments
Read Related
Comments
great analysis
this is prob my fav article you’ve done so far. we needed to air our dirty laundry to try and understand why the heck we always lose to a team that we should beat. nice work, great read.
by Ferret88 on Jul 28, 2008 12:27 PM CDT 0 recs
Thanks for the
nice words. It was tough spending 30 minutes or so looking at the boxscore for each game. Kind of a downer weekend.
Go Raiders . . .
by Seth C on
Jul 29, 2008 6:03 AM CDT
up
0 recs
This hurt to read….
After all is said and done, more is said than done.
by ayleein on Jul 28, 2008 12:31 PM CDT 0 recs
Yes, it’s incredibly tough to see some of those games, but there were some real bad games. I think OSU and the 2-10 Colorado teams hurt the worst.
Go Raiders . . .
by Seth C on
Jul 28, 2008 6:31 PM CDT
up
0 recs
i’d like to see a similar breakdown for the TCU 2006 and missouri 2007 games, though i can guess how those would turn out.
by kayakyakr on Jul 28, 2008 1:26 PM CDT 0 recs
I'll start working on those
soon. Those were bad losses, but at least those teams were talented. Some of those teams . . yeeeesh.
Go Raiders . . .
by Seth C on
Jul 28, 2008 6:29 PM CDT
up
0 recs
here ya go
The TCU game was the hardest game I ever had to watch. Frankly this is the only game I can ever remember the offense being the reason we lost rather then the defense. The final score was a Mike Leach low scoring 12-3. Can you imagine a Mike Leach team only scoring 3 points?! Only 38 yards of rushing and another Mike Leach low of 204 yards passing. Hodges was very inefficeint throwing 23 for 47 with no touchdowns obviously. To go with the theme that is a very low passing yards per attempt of only 4.3. However, no turnovers. TCU only rushed for 180 yards and passed for 101 yards. That is very good for a Tech defense. This was a game that the defense was the sole reason the Raiders were in this game.
Last years Missouri was probably the second hardest game to watch. We lost 41-10 and we got blown out in the second half. Harrell had his first of 4 interception games (the other being the next week against Colorado). (By the way could you imagine how good Harrell’s stats would have been without these two games). Ok back to the point. Tech did pretty much nothing right and both the defense and offense were turrible. Only 5.7 yrds per attempt and -9 yards rushing! Thats right negative yards. We gave up 210 yards of rushing so chalk that up on the list. So this game had all three pitfalls and boy did it show.
You could also extend the reason Tech loses every game is because of these three factors no matter good or bad team. This year though we should be better than every team we play except for maybe Oklahoma. I dont care what the Big 12 media says we are ahead of Texas this year!
"Once in awhile, a pirate can beat a soldier"
by crabtreeforheisman on
Jul 29, 2008 12:07 AM CDT
up
0 recs
I was also at that TCU
game and it was so frustrating to watch the offense that day. I also looked at yards rushing and that statistic seemed to fluctuate quite a bit so I didn’t consider it. However, recently, the rushing game has gone down quite a bit from years past.
Go Raiders . . .
by Seth C on
Jul 29, 2008 5:58 AM CDT
up
0 recs
You've used data to show
our weaknesses. As stated by others it was pretty obvious that we can’t stop the run. I’m not sure how much Lyle had to do with this, but it may be a dimension of the analysis too. I don’t think we even recruited well on defense during this period. That’s why we now have the national reputation of no defense. Now that those days are over I think the “no defense” reputation is good for us. It will make other teams complacent.
I also worry about the after Harrell leaves. With a new quarterback will we experience the turnover problem for the next 6 years? Trepidation abounds…
by CoachT on Jul 28, 2008 1:51 PM CDT 0 recs
I think a huge part of it
is that the defensive tackle position is one of the hardest to recruit in college football. Of course not every run-stopping team has recruited great DT’s, but I do think there’s something about commitment and working and developing guys.
Go Raiders . . .
by Seth C on
Jul 28, 2008 6:30 PM CDT
up
0 recs
Points
Looking at the losses, it’s too easy to pin those all on the defense. We didn’t exactly light up the scoreboard in many of those games, so the offense bears a lot of the blame. A majority of the games Tech lost they scored 24 or fewer points (23 of 37 losses (62%), not counting ‘07 where the scores weren’t listed), and in many of those Tech socred in the teens or fewer (16 of the losses).
That may be related to yards per attempt, I don’t know.
by Tech92 on Jul 28, 2008 6:47 PM CDT 0 recs
Those are
good points, and I think that a logical conclusion that greater yards per attempt = better offense. Offenses are intended to work vertically and not sideline to sideline.
Go Raiders . . .
by Seth C on
Jul 28, 2008 6:56 PM CDT
up
0 recs
True
I don’t disagree at all with that. Especially with Tech’s offense. We simply can’t grind out tough yards to sustain a drive if someone has our number or if the QB/WRs are off that day. That is the problem with being so one-dimensional.
My fear is this offense has about another two years of really active shelf-life before someone figures out how to stop it consistently. Not because Tech will get worse at executing it, but because darn near everyone runs a version of the spread and teams won’t be so dumbfounded when they see it from Tech. A massive number of high schools now play a spread, so kids are learning how to play defense against it early on. A lot of those kids hitting college now have never played D against anything but a spread offense, so it’s not as confusing to see for many of them.
But Leach is smart…he’ll figure something out, or adapt somehow.
by Tech92 on
Jul 28, 2008 9:57 PM CDT
up
0 recs
I've never ever thought about
how this offense has a shelf-life. If I had to wager a guess, I think that Leach would be so absolute that his offense is as unstoppable now as it ever was. He just seems like the kind of guy who isn’t going to change that much.
I would agree that defenders understand the spread much more, but I’ve always thought that the difficult thing to defend is that the offensive players are in space and defending players in space is difficult. If a team, like Missouri, bottles up those players so they can’t get into space then it’s much easier to defend. Again, make the offense go horizontal rather than vertical.
Go Raiders . . .
by Seth C on
Jul 29, 2008 6:02 AM CDT
up
0 recs
Yep
And like anything in sports, once something has been around a while, teams tend to adjust. Sometimes it seems Tech doesn’t always do a good job of working with what the defense is doing. It seems like Leach will be so sure of what he’s doing that he doesn’t alter it even when it’s obvious to everyone else something needs to be tweaked in-game. But maybe that’s part of his genious.
by Tech92 on
Jul 30, 2008 6:17 PM CDT
up
0 recs
Option
Maybe Leach will bring back the Wishbone option game hahaha.
by ST04 on
Jul 29, 2008 9:45 AM CDT
up
0 recs
2002 Loss to ISU
I’ll never forget this one because of how promising the team was; with Kinsbury in his third and final year as well as Ricky Williams and We Welker, two of the best we’ve ever had at their respective postions.
And to make matters worse, I’m often reminded of the loss becuause of that one Seneca Wallace play they always seem to replay on highlight shows. Anyone else remember it? He scrambles for all of like 23 seconds around the backfield (although it seemed like 23 minutes during the game), slips through tackle after tackle after tackle, giving a reciever decades to get open and run in for a touchdown. I most recently was reminded of it by a “50 greatest sports plays” edition of Best Damn Sports Show. I think it made the top 20. Still hurts to this day.
by 2001Raider on Jul 29, 2008 5:05 AM CDT 0 recs
I had completely
forgotten that play. Ughh.
Go Raiders . . .
by Seth C on
Jul 29, 2008 6:02 AM CDT
up
0 recs
How to contain a spread offense
One thing that occurs to me is that many of these things (low offensive production, turnovers) may be symptoms of the way teams chose to defend Tech rather than a bad game on behalf of Tech. If anything, Tech did not do a good job of recognizing the situation and adjusting.
I’ve thought about the comments about the "system" offense quite a bit. Let me say that I don’t agree with the people who say it’s a gimmick. I think Leech has realized something that football purists don’t like to admit. The team with the most points wins the game. The observations that you make stem from how the other team thinks they can beat the Tech offense. There are 2 things that teams have to do to, short of having significantly superior talent both ways, to beat the spread offense. If they don’t accomplish both, their odds of winning go way down.
1. Limit the number of possessions. Teams run against Tech to burn clock and keep the offense off the field, limiting the number of possessions. In football, both teams get roughly the same number of possessions. The Tech offense is designed to maximize the odds of scoring on any given possession by maximizing the number of players available to get the ball. Due to the clock rules, the fact that Tech accomplishes this by throwing the ball decreases the amount of game clock time per possession and therefore increases the number of possessions per game. A running game, on the other hand, decreases the number of possessions because it uses more of the game clock. Say Tech scores on 50% of its possessions. If an opponent can limit them to 2 possessions per quarter, they will likely only score 28 points. If Tech gets the ball just 1 more time per quarter, they score 42 points. So by limiting the number of possessions, an opponent that doesn’t run an offense capable of scoring 40+ points a game keeps the score within reach. It can also help keep the offense out of rhythm.
2. Once you limit the number of possessions, you have to force Tech to throw short and into traffic in the center of the field. I think that if you look at the low yards per attempt/high interception games, the opposing defense was successful in this. Passes to the center of the field are more likely to be tipped and/or intercepted, the throws are shorter and quicker (less time), and the receiver is more likely to be tackled quickly. If the receiver is tackled quickly (versus a long run or being forced out of bounds), the clock continues to run – further limiting the number of possessions. In this scheme deeper throws and throws to the sidelines are likely to be forced (how many times did Tech throw the wide receiver screen, the shuffle pass, or force the sideline fade in these losses??? Uggh.). While the offense may be able to move the ball down the field, this type of defensive scheme makes it especially difficult to score in the red zone where the field is compressed.
Stopping the run is obviously key. I am anxious to see if Tech can continue to step up in this area. Offensively, I think this year the receiving corps is capable of creating mismatches on the outside against most teams and is physical enough to fight through the first contact on the inside. Crabtree will almost always force a double team/cover 2 on the outside and deep routes, which should leave someone open. With a very experienced Harrell at quarterback, Tech should be able to do a better job of recognizing and adjusting to what the opposing defense is trying to do, so long as they avoid being too arrogant, thinking they don’t need to adjust.
by NM99 on Jul 30, 2008 3:54 PM CDT 3 recs
It's almost like the
Bible . . . _ who begot _, who begot , etc. One problem, leads to another, which potentially causes another. Excellent work.
Go Raiders . . .
by Seth C on
Jul 30, 2008 9:11 PM CDT
up
0 recs
Don't forget
Let’s not write off Graham Harrell’s nasty little habit of throwing INTs that are returned for touchdowns. That can’t continue for Tech to have that dream season. It absolutely killed us vs. Mizzou two years in a row. Not sure how many he’s had in his career, but if anyone does the research I would bet he’s near the top in that category.
I do like NM99’s points and they make a lot of sense.
by Tech92 on Jul 30, 2008 6:14 PM CDT 0 recs
DB's are fast
Offensive linemen are slow. Who’s going to catch that defensive back to keep him from scoring when all of the players fast enough to do it are spread abuot the field? One of the inherent risks of the system. That is one thing that has frustrated me about Harrell. At least the kicker tries to force the return man out of bounds…
by NM99 on
Jul 30, 2008 9:17 PM CDT
up
0 recs
Expanding on NM99's assessment
NM99 made a good assessment of what teams who have been successful stopping us in the past try to do. The Mizzou games the past few years are a perfect example. They create pressure by zone blitz keeping the OL guessing as to who to block, and Graham guessing about where the coverage weak points are. (MU also coaches up all lineman/blitzers to stop in place and jump/put arms up when the Graham prepares to throw to create tipped passes) This effectively takes away the deep ball because Graham never has time to wait for the deep throw. Feeling the pressure, he checks down to the inside rec’s who are being pressed and squeezed. (Some would argue during the MU game they were being pressed/squeezed before the ball arrived, ) This dramatically limits YAC, and creates more tipped passes. When we try to throw deep to stretch the defense, it’s usually a big gamble…We need to burn them to make them honest and back off. Frustration builds among observers and particpants. You can almost feel the difference in pressure and intensity when the opposing D is making life difficult for the offense…TCU game in Ft. Worth, both MU games. I think MU has done a better job of scheming and executing a gameplan against us than anyone. They pressure GH and take away the deep ball at the same time, which forces us to throw inside where they are already pressing. It compounds the problem when the opposing team has an offense which can 1) score like us or 2) pound the ball and run the clock . This puts more pressure on our offense by limiting the number of possessions our offense gets per game. We hope that a year of experience and overall improvement will increase our chance of burning teams who try to utilize this gameplan. An attacking defense that can create turnovers and stop the run every third series would be a substantial improvement. I hope Captain Cuckoo-Bananas has something up his sleeve to make teams pay who try to utilize this method against us.
by jdubmed on Jul 31, 2008 8:57 AM CDT 0 recs
On blitzin'
I remember all of the blitzing in the Mizzou games. Colorado did the same thing the following week last year. I think that is why they kept someone in the backfield with Harrell more after those games. An adjustment that should have been made during the games, but was not.
by NM99 on
Jul 31, 2008 9:50 AM CDT
up
0 recs
Expanding on NM99 nad jdubmed' comments - Defense
"Stopping the run is obviously key. I am anxious to see if Tech can continue to step up in this area " (NM99)
"An attacking defense that can create turnovers and stop the run every third series would be a substantial improvement." (Jdubmed)
I like the thread about the Raider defense plays a role in supporting the offensive scheme. The fact that our defense doesn’t (to date) force very many 3 and outs or for that matter 7 and outs i.e. 2 series – is a cause for worry. In this discussion it leaps at you. Examples: The OK state game – one more tackle on a tight end and maybe we run the clock out, the Mizzou game stop the second Tiger drive – we get shot at closing the gap to 10 points in the third period. The 2nd period in the Colorado game stuff the run just once for less than a 4.5 yard gain and maybe Alex Trlica doesn’t miss the FG. In the Texas game how about just one additional goal line stands in the 2nd or fourth periods forces Texas to kick the FG.. Whoa it’s a one score spread. (… doesn’t help on the 4th Quarter interception by Texas or the Replay refs in the booth high fiving the Texas Assistant coach…) Last example and good one for the defense – vs. Oklahoma our defense plays essentially the whole 4th quarter in our end of the field. But OK throws the ball repeatedly. Why ? They are down by 2 scores. Oh and by the way 2 earlier times the Raider defense stops the Sooners from getting a TD – they kick the FGs. A statistic which seems to be under reported is the defenses’ ability to get the opposing team off the field. Regain possession. Much has been said about the lack of a rush stuffing line and linebackers. This year’s depth at tackle and def. end looks to be better. But regaining possession now there is the rub. The 05 team was way ahead in turnovers forced and recovered. The 07 team forced a lot (30 plus? ) but they didn’t recover too many (16 ? Including the fatal one against Virginia by Henley). The defense’s mission is to force punts. Regain possession. Halt red zone possessions. The combination of a defense which forces punts and denies red zone chances – even if they kick field goals gives the offense another opportunity to test the opposition’s defense. I agree a modest increase in three and outs series is the goal for this defensive squad. This equates to putting the opposing offense in a 3rd and 5 (+) routinely – a situation which can translate into a scheme which denies an opponent the ability to play ball control offense. The opposing Coaches want to impose an offensive game plan counter to what Leach likes to do. Allowing 4.7 plus yards per carry by Big 12 opponents is going to sink us. Don’t forget the new NCAA clock rule is going to make our defensive coordinator react to a lot more no huddle offensive series. We will need to rapidly get the right package in place to impose our attacking defensive scheme. So we begin to see folks adopting the same tactics the Raiders use i.e. offense up on the ball before a defensive substitution can get on the field. I am optimistic the Tech defense can increase their productivity by regaining possession. Further I believe it’s going to come from the defensive line play. I wouldn’t be surprised to see – as a result of the defensive play – a jump in Raider punt returns .
by centexraider on Aug 5, 2008 2:34 PM CDT 0 recs
Centex's two cents...
I’m right with you in terms of just a few more stops being the key for our year. I think we all hope that our added depth and talent at D-Line will allow us to create more disruption up front, create better down and distance scenarios….We can’t have 2nd and 3, 3rd and 1 all year against good teams. Spot on…we’ll find out if our D can tip us over. I actually feel excited about watching theis D unleashed on folks…hope our hopes are realized.
by jdubmed on
Aug 6, 2008 8:39 PM CDT
up
0 recs












