Tuesday, September 9, 2008

What To Do Now That Your Number One Fantasy Football Player Tom Brady is Hurt?

GLENDALE, AZ - FEBRUARY 03:  Quarterback Tom B...Image by Getty Images via Daylife There were a couple of key injuries to some NFL players this past weekend. One is obvious, the other maybe not as much. The obvious key injury was to Tom Brady. The other player who was injured was Nate Burleson.
It looked like Nate Burleson was going to be Matt Hasselbeck’s number one receiver with Deion Branch and Bobby Engram out with injuries. The Seahawks ground game isn’t very impressive. The other concern for the Seahawks is who is Hasselbeck going to throw to?
You have to be suicidal if you took Tom Brady with your 1st or 2nd pick in your Fantasy Football draft this year. You got less than one quarter’s worth of action and he is done for the year.

You did have to wonder how much you would get out of Brady this year: he was hurt during the AFC Championship game last year and didn’t do much in the Super Bowl. He didn’t play during the pre-season because of another injury. So, you shouldn’t have expected him to put up numbers like last year. But, who would have expected a torn ACL? Did he just come back too early?

The only Patriots’ fantasy value this will help is Matt Cassell. Randy Moss is not going to get as many -touchdowns as last year and you have to wonder if he will have a meltdown with a non-Pro Bowl Quarterback. Wes Welker, Brady’s most consistent target, won’t see as many catches and yards as he has in the last couple of years. Maybe the Patriots’ running game will be used more. But, if other teams’ defenses are focusing on the running game, it might not work out so well for the Pats.

It will be interesting to see how the Patriots and Seahawks cope with the injuries and see how fantasy owners will deal with the loss of Brady. Hopefully they drafted a decent back-up quarterback, or they might have to make a costly trade.
One of the places you can check out football information is www.104football.com .
Reblog this post [with Zemanta]

No comments: