Fantasy Football Week 6: Start’em / Sit’em

Use your ← → (arrows) to browse



Kirby Lee-USA TODAY Sports

Philip Rivers IND (50%, 19): I’m not 100% on board the Philip Rivers revival bus. He has had some cushy match-ups (Oak, Phi, Dal) and has been held under 200 yards by the two good defenses he has faced (Ten & Hou). I think the bus crashes this week against an Indy D that has played better than expected all season and is giving up the 9th least amount of fantasy points to QBs.

Colin Kaepernick AZ (61%, 17): I’m going to keep putting Kaep on this list until I’m wrong. The Cards D looked rejuvenated last week by the return of MLB Daryl Washington and they absolutely destroyed Cam Newton. I’d feel more comfortable starting Luck, RG3, or Cutler who are all currently being started in less leagues.


Chris Johnson @SEA (68%, 11): CJ3 finally found the end zone last week, but it will be a different story against Seattle. Johnson isn’t getting red zone carries, so basically the only way he’s going to score is on a long run. With the Seahawks boasting one of the fastest defenses in the league, I just don’t see that happening.

Darren McFadden @KC (22%, 11): DMC practiced for the 2nd straight day (Thurs) so it looks like he will be good to go on Sunday. Who cares? I wouldn’t start McFadden this week unless I had absolutely no one else. He’s playing against a stingy Chiefs D (8th fewest RB fantasy points allowed) and if you have any history with McFadden you know you can’t rely on him to play hurt. He’s heading to the bench the first time he feels a twinge in his hamstring. Just trust me and stay away this week.

Steven Ridley NO (25%, 8): Another guy who is back at practice this week and likely to suit up on Sunday that I don’t trust at all. In this instance, it’s not Ridley’s fault as much as it is Bill Belichick’s who has installed a RBC in NE and wrecked the fantasy value of all RBs involved. Ridley is riding my bench until I see him get 20 carries in a game. Sadly, I don’t think it’s happening this year.


Kevin Hoffman-USA TODAY Sports

Danny Amendola NO (60%,13): With Gronk back this week there are a lot of mouths to feed in New England and I’m not sure Amendola gets enough targets to meet his projected total. I want to see what the distribution looks like with all of their receiving options healthy before I count on any of them. The Saints were very tough against the underneath routes last week and those are Amedola’s bread and butter. I think he will get you close to 10 points, but his upside is limited.

Golden Tate TEN (34%,10): Why are people still starting this guy? He’s had exactly 1 decent game this year. Stop.

Tavon Austin @HOU (24%, 7): I’m hoping the old reverse jinx will spark Austin into doing something this week. I own him in so many leagues and he’s been pretty much worthless. Part of the blame is on Jeff Fisher; Why use the 8th pick on a WR if you aren’t going to put him in position to succeed (short passing game)? Part of it is on Austin as well; He just doesn’t look as explosive as he did in college and he is running sideways too often. Houston is giving up the least amount of fantasy points to WRs so this is a pretty brutal match-up for Austin who has struggled against just about everyone this year.


Antonio Gates IND (76%,12): I don’t feel good about this one, but had to pick somebody so here we are. Indy has been tough on opposing TEs (24th in points allowed) and I already predicted a regression game from Rivers, so I guess Gates suffers by extension. If you have two TEs on your roster, I would rather start the following players who are currently being started in less leagues: Cameron (71%), Olsen (62%), Bennett (56%), G Graham (39%)


Larry Fitzgerald @SF (81%,11 ): Sorry Larry, you’re one of my favorite players, but with the way Carson Palmer is throwing the ball I just don’t feel confident in your fantasy viability right now. Plus, you are playing the Niners in SF, which sucks for your whole team. Maybe you will prove me wrong like you did in week 1 (24 points)? I hope so, but I’m not betting on it.

Twitter: @MikeFlannery_



Use your ← → (arrows) to browse

comments powered by Disqus