Fantasy Football Week 3 Projections: 3 QBs Who Will Disappoint
Quarterbacks have dominated the first two weeks of the season, and while I suspect that trend to continue, I would be wary of starting these three QB's in Week 3.
Cam Newton
Cam Newton has exceeded everyone's expectations in his first two NFL games, throwing for an absurd 854 yards and a respectable three touchdowns for the Carolina Panthers. He also has four interceptions but, obviously, that's to be expected with a rookie signal-caller.
TOP NEWS
.jpg)
Colts Release Kenny Moore

Projecting Every NFL Team's Starting Lineup 🔮

Rookie WRs Who Will Outplay Their Draft Value 📈
Despite his early success, I'm expecting Newton to come down to earth and it starts against a very solid Jacksonville Jaguars pass defense.
Newton has been brilliant thus far, but once defenses figure him out his numbers will drop. With two weeks of game film to study, Jacksonville has a great opportunity to remind the Heisman Trophy winner that he's not in the SEC anymore.
Michael Vick is expected to play against the New York Giants after suffering a concussion last week in Atlanta. However, I doubt he will be very effective in his first game back.
Giants defenders Justin Tuck and Mathias Kiwanuka will be chasing Vick around all day and one big hit could land the speedster back on the sidelines.
Vick is the most exciting player in the NFL because of his ability to scramble and improvise. But with lingering effects from the concussion, he'll be reluctant to make plays outside of the pocket—and that means less big plays from the star QB.
I wouldn't expect big numbers from Matt Ryan this week against the Tampa Bay Buccaneers; not because of any shortcomings on his part, but because the Bucs run defense is so awful Atlanta will likely primarily operate on the ground.
Tampa Bay is allowing 156 rushing yards a game, meaning the Falcons will be giving the ball to Michael Turner early and often.
Ryan will be solid but not spectacular this week. If you have a quarterback with a better matchup, I'd suggest starting the alternative.

.png)





