Navy QB out for game
(no message)
Replies to: Navy QB out for game
Shouldn’t be a problem for us then.
(no message)
Beat me to it...
The injury is only expected to keep him out for this week, and it was a game time decision.
When you lose a guy who has rushed for almost 1000 yards and 13 TD's, and has proven to be at least a reasonable passing threat, that will certainly shift the last second odds.
Link: https://x.com/PeteThamel/status/1987302065882996939
That’s not good - Historically, ND has a penchant allowing 1st time QB starters….
……play out of their socks. Remember Ryan Mallett at scUM in 2007? He beat ND 38 - 0!!
True, but a lot of people had field days against us that year
That 2007 Michigan team was a very well developed, veteran team that year, and by all rights, should have been a BCS Bowl team if it weren't for a couple of fluke losses (App State, Wisconsin).
Mallett was already a very polished passer coming out of high school, and had a very good offensive line protecting him, along with Mike Hart there as a safety blanket.
We, on the other hand, were working with a bare cupboard, no true junior or senior depth (thanks to Lionel Tyrone Willingam's inept recruiting for the 2004 and 2005 classes).
In the weeks before, Tashard Choice (Georgia Tech's RB) ran wildly over us, and Penn State took us to the woodshed.
What's ironic, though, is that 2008's Michigan team was the equivalent of our 2007 team, once Rich Rodriguez tried to turn them into a finesse-based spread option team.
Re: That’s not good - Historically, ND has a penchant allowing 1st time QB starters….
He’s not a first time starter so maybe not
ND D = too big + fast
(no message)
I'm guessing the Navy back up is bad.
(no message)
I know it’s ECU but he tore them up last year in a bowl game
(no message)
I'm pretty sure ND is a tad better than ECU.
(no message)
Just saying he’s not terrible
(no message)