<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Fantasy Guru Blog</title>
	<atom:link href="http://www.fantasyguru.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fantasyguru.com/blog</link>
	<description>In it&#039;s 4th year, FantasyGuru.com&#039;s John Hansen&#039;s Fantasy Football Blog</description>
	<lastBuildDate>Sun, 02 Jun 2013 16:33:36 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<copyright>Copyright &#xA9; Fantasy Guru Blog 2010 </copyright>
	<managingEditor>gurureport@aol.com (Fantasy Guru Blog)</managingEditor>
	<webMaster>gurureport@aol.com (Fantasy Guru Blog)</webMaster>
	<image>
		<url>http://www.fantasyguru.com/blog/wp-content/plugins/podpress/images/powered_by_podpress.jpg</url>
		<title>Fantasy Guru Blog</title>
		<link>http://www.fantasyguru.com/blog</link>
		<width>144</width>
		<height>144</height>
	</image>
	<itunes:subtitle></itunes:subtitle>
	<itunes:summary>In it's 3rd year, FantasyGuru.com's John Hansen's Fantasy Football Blog</itunes:summary>
	<itunes:keywords></itunes:keywords>
	<itunes:category text="Society &#38; Culture" />
	<itunes:author>Fantasy Guru Blog</itunes:author>
	<itunes:owner>
		<itunes:name>Fantasy Guru Blog</itunes:name>
		<itunes:email>gurureport@aol.com</itunes:email>
	</itunes:owner>
	<itunes:block>no</itunes:block>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://www.fantasyguru.com/blog/wp-content/plugins/podpress/images/powered_by_podpress_large.jpg" />
		<item>
		<title>Sleeper alert: Bilal Powell</title>
		<link>http://www.fantasyguru.com/blog/2013/06/02/sleeper-alert-bilal-powell/</link>
		<comments>http://www.fantasyguru.com/blog/2013/06/02/sleeper-alert-bilal-powell/#comments</comments>
		<pubDate>Sun, 02 Jun 2013 16:33:36 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>
		<category><![CDATA[Bilal Powell]]></category>
		<category><![CDATA[Chris Ivory]]></category>
		<category><![CDATA[Mike Goodson]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1237</guid>
		<description><![CDATA[<p>After closely studying the initial ADPs this year for the ADP article we posted on Friday and seeing how fantasy owners are scarfing up RBs like it’s going out of style, one of my main missions this year is to find some RBs who have a chance to be impactful but aren’t getting any love, and I have one in AFC East.</p>
<p>With veteran Mike Goodson having an ugly off-season that includes a May 17 arrest in New Jersey on drug and weapons charges, which could result in prison time, and a new paternity suit being filed this week (and he has others), it’s time to start talking about a potential sleeper RB for the Jets: Bilal Powell.</p>
<p>Goodson is still on the roster and has the speed they need in their backfield, but between his off-field issues and injury history, he’s very hard to count on. They obviously brought former Saint Chris Ivory in to be their lead back, and Ivory does run very hard and has good explosiveness for power back. But he’s also dealt with a multitude of injuries, despite never coming close to carrying the load for a rushing attack.</p>
<p class="wp-caption-text">Bilal Powell was a solid goal line back [...]]]></description>
				<content:encoded><![CDATA[<p>After closely studying the initial ADPs this year for the ADP article we posted on Friday and seeing how fantasy owners are scarfing up RBs like it’s going out of style, one of my main missions this year is to find some RBs who have a chance to be impactful but aren’t getting any love, and I have one in AFC East.</p>
<p>With veteran <b>Mike Goodson</b> having an ugly off-season that includes a May 17 arrest in New Jersey on drug and weapons charges, which could result in prison time, and a new paternity suit being filed this week (and he has others), it’s time to start talking about a potential sleeper RB for the Jets: <b>Bilal Powell</b>.</p>
<p>Goodson is still on the roster and has the speed they need in their backfield, but between his off-field issues and injury history, he’s very hard to count on. They obviously brought former Saint <b>Chris Ivory</b> in to be their lead back, and Ivory does run very hard and has good explosiveness for power back. But he’s also dealt with a multitude of injuries, despite never coming close to carrying the load for a rushing attack.</p>
<div class="wp-caption alignright" style="width: 453px"><img alt="" src="http://www.fantasyguru.com/football/subscribers/images/powell.jpg" width="443" height="325" /><p class="wp-caption-text">Bilal Powell was a solid goal line back in 2012, but he can also catch the ball and produce in the passing game.</p></div>
<p>At 5&#8217;10, 204 pounds, Powell is the incumbent here, and while his career hasn’t blown anyone away thus far, he’s not a bad player. In 2012, he emerged as an effective goal line back, and for a time in the second half of the season last year, he emerged as the goal line back over <b>Shonn Greene</b>. Powell had five carries inside the 10 yard line last year, and he scored on three of those carries. If he got the ball inside the 5 in 2012, he scored a TD. He had six games last year in which he had double-digit carries, and he averaged a solid 4.2 yards per carry in those games. In addition, Powell can catch the ball and pose a threat in the passing game. Although his catch rate for the season was a miserable 47.2% (keep in mind the Jets were horrendous on offense), he did improve greatly in the second half of the season and posted a solid 68.4% catch rate. He was able to average a very serviceable 8.2 yards per catch on his 17 grabs in 2012.</p>
<p>Powell hasn’t proven to be an iron man thus far, so injuries are slight concern (he missed two games last year), but they’re a greater concern for Ivory. If Goodson isn’t in the mix this year for the Jets, I have to think Powell will be a large factor in this offense, especially since Ivory has only 3 career receptions in 24 career games. Keep in mind former Eagle coach <b>Marty Mornhinweg</b> is the new OC for the Jets, so they should be throwing the ball to their backs. Even if Goodson is on the roster, Powell has better size for short-yardage work, and Goodson himself also has durability issues. I’m sure Ivory will be the main guy, and I’m sure he’ll be on the field running violently come September. But will he be able to hold up in the process? That is a major question.</p>
<p>I’m not saying Powell is a great breakout candidate, but especially for those in larger and deeper leagues, it’s time to put him on the radar as a legitimate deep sleeper and a guy who could easily be very handy for fantasy in 2013.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2013/06/02/sleeper-alert-bilal-powell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>10 Draft Tips for 2013</title>
		<link>http://www.fantasyguru.com/blog/2013/05/21/10-draft-tips-for-2013/</link>
		<comments>http://www.fantasyguru.com/blog/2013/05/21/10-draft-tips-for-2013/#comments</comments>
		<pubDate>Tue, 21 May 2013 16:35:28 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>
		<category><![CDATA[Aaron Rodgers]]></category>
		<category><![CDATA[Alfred Morris]]></category>
		<category><![CDATA[Andrew Luck]]></category>
		<category><![CDATA[Ben Tate]]></category>
		<category><![CDATA[Calvin Johnson]]></category>
		<category><![CDATA[Cam Newton]]></category>
		<category><![CDATA[Colin Kaepernick]]></category>
		<category><![CDATA[Darren McFadden]]></category>
		<category><![CDATA[David Wilson]]></category>
		<category><![CDATA[Demaryius Thomas]]></category>
		<category><![CDATA[Dennis Pitta]]></category>
		<category><![CDATA[Drew Brees]]></category>
		<category><![CDATA[Jimmy Graham]]></category>
		<category><![CDATA[LeSean McCoy]]></category>
		<category><![CDATA[Marshawn Lynch]]></category>
		<category><![CDATA[Matt Forte]]></category>
		<category><![CDATA[Rob Gronkowski]]></category>
		<category><![CDATA[Russell Wilson]]></category>
		<category><![CDATA[Tony Romo]]></category>
		<category><![CDATA[Vick Ballard]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1229</guid>
		<description><![CDATA[<p>The NFL and fantasy landscapes change quickly these days, so if you have a draft strategy, it had better be year-specific. I have already done several mock and real drafts for various publications, and the 2013 trends are pretty clear – so they dominate the following 10 draft tips.</p>

Try to hold off a little before drafting a QB – To summarize the best 2013 draft approach in a word, it’s “patience,” and that specifically applies to the QB position. Just 2-3 years ago, I was all about getting as many impact players as possible, regardless of position, and QB was a big part of that approach. After the passing game bonanza that we saw in 2011, you’d think that I’d be all over the signal-callers as rock-solid early picks. I do still believe in the BPA approach (best player available), and the top QBs are almost always safe and extremely productive options. But in 2013, it doesn’t make nearly as much sense taking a QB early as it did even just one year ago. There are many paths to a championship, and there’s nothing wrong with using a No.1 pick on Aaron Rodgers, or a 2nd-round snag of Drew Brees. [...]]]></description>
				<content:encoded><![CDATA[<p>The NFL and fantasy landscapes change quickly these days, so if you have a draft strategy, it had better be year-specific. I have already done several mock and real drafts for various publications, and the 2013 trends are pretty clear – so they dominate the following 10 draft tips.</p>
<ol start="1">
<li><b>Try to hold off a little before drafting a QB</b> – To summarize the best 2013 draft approach in a word, it’s “patience,” and that specifically applies to the QB position. Just 2-3 years ago, I was all about getting as many impact players as possible, regardless of position, and QB was a big part of that approach. After the passing game bonanza that we saw in 2011, you’d think that I’d be all over the signal-callers as rock-solid early picks. I do still believe in the BPA approach (best player available), and the top QBs are almost always safe and extremely productive options. But in 2013, it doesn’t make nearly as much sense taking a QB early as it did even just one year ago. There are many paths to a championship, and there’s nothing <i>wrong</i> with using a No.1 pick on <b>Aaron Rodgers</b>, or a 2<sup>nd</sup>-round snag of <b>Drew Brees</b>. But obviously, there’s no <i>value</i> in it, either. I’ve seen <b>Cam Newton</b> slip to the 7<sup>th</sup> round of a 10-team draft this year, for example, which is outrageous. And great options like <b>Colin Kaepernick</b>, <b>Andrew Luck</b>, <b>Tony Romo</b>, and <b>Russell Wilson</b> will cost much less than the top dogs. Ultimately, your best chance for domination is clearly holding off a bit on drafting a QB while loading up on talent at the other skill positions. If you hit on those picks and slam it out of the park with a guy like Luck or Kaepernick, then you’ll have formed a fantasy all-star team.</li>
</ol>
<ol start="2">
<li><b>Going RB-RB with your first two picks is more viable than it’s been in quite some time</b> – The key, of course, is picking the right two players – two options who are very deserving of such a high pick. That might not be viable for those who draft near the top of Round One, since the talent level at the RB position does dry up considerably after the first 13-15 backs are off the board. But for those drafting near the end of the first round, kickin’ it old school and going RB-RB looks like a great play this year. Again, that is due in large part to the outstanding depth at QB and WR, but also due to the quality at the top of the RB position. It’s entirely possible, for example, to grab a <b>Marshawn Lynch</b> and an <b>Alfred Morris</b> with your first two picks this year, or a <b>LeSean McCoy</b> and a <b>Matt Forte</b>, and both would be great starts to a draft. There’s almost always a hole left at RB or WR if you take a QB or TE very early, so the best plan is to not do that, especially since QB is so deep and WR is deep enough to still get at least two excellent options in the 3<sup>rd</sup>-5<sup>th</sup> rounds.</li>
</ol>
<ol start="3">
<li><b>TE is not a position to invest heavily in</b> – Ironically, the lone exception is New Orleans’ <b>Jimmy Graham</b>, who I think is worth a top-15 pick this year. I do because the number of high-end options at this position in 2012 has fallen off, due in large part to the questionable status of Patriot <b>Rob Gronkowski</b>. An advantage can be gained this year if you dominate TE production with a stud like
<div class="wp-caption alignright" style="width: 381px"><img class=" " alt="" src="http://www.fantasyguru.com/football/subscribers/images/jgraham.jpg" width="371" height="381" /><p class="wp-caption-text">Investing in TE Jimmy Graham early could pay off big in 2013, but you will have to make up for it by drafting well in the middle rounds to make sure you&#8217;re strong at RB-WR.</p></div>
<p>Graham, but you do have to make up for using a high pick on a TE while others are loading up on stud RBs and WRs. If you do by drafting well in the middle rounds, then your team just might be devastating with a major positional edge at TE. If you fail to hit on 1-2 mid-round picks, however, drafting Graham could leave you with a fairly significant hole on your roster. And since there are some appealing TE options who should be available in the middle rounds (I really like <b>Dennis Pitta</b> as one of them), holding off on TE is just as viable as drafting Graham early and is probably a little safer.</li>
</ol>
<ol start="4">
<li><b>Reaching for players is not advisable</b> – An overriding theme of this article is the ridiculous depth available at all skill positions other than TE. Whenever the viable player pool is larger than we’re used to, that makes reaching for a player with some issues – durability, inexperience, etc. – even riskier. With great depth at QB, RB, and WR, fantasy players have options and can be flexible. Although it pains me to write this because I’m an aggressive player, they can also be conservative.  So that means trying to be a hero by drafting Giant RB <b>David Wilson</b>, who still has to earn the trust of the coaches, in the 3<sup>rd</sup> round is not advisable. With so much talent to be had, the best plan is to sit back and let the draft – and hopefully some values – come to you.</li>
</ol>
<ol start="5">
<li><b>Remember the outstanding depth at WR</b> – Again, I focus on depth, and this time it’s the WRs. It’s a deep group this year, so while you might be feeling slick taking three stud wideouts in the first 4-5 rounds, you might feel like a fool when there are still some really nice WRs available in the 6<sup>th</sup> and 7<sup>th</sup>, and you’re looking at <b>Vick Ballard</b> as your #2 RB. <b>Calvin Johnson</b> is in a class by himself and is comparable to most RBs, but otherwise there are plenty of strong options – roughly 40 of them this year plus sleepers – so it’s not a position one needs to be overinvested in.</li>
</ol>
<ol start="6">
<li><b>Durability is more important than ever</b> – I believe there are more viable fantasy options at the skill positions in 2013 than ever before. That might mean you’ll be able to overcome a key injury or two, but more likely it means you took an unnecessary risk by selecting <b>Darren McFadden</b> in the 3<sup>rd</sup> round when you could have had a reliable stud in <b>Demaryius Thomas</b> instead. With more desirable options to choose from than usual, players with serious durability issues have to be downgraded, plain and simple.</li>
</ol>
<ol start="7">
<li><b>Strength of schedule isn’t as critical as it used to be</b> – Each year I do a very extensive SOS analysis and 2012’s wasn’t nearly as accurate as it’s been in years past. This is likely due to the decrease in shut-down defenses in the league, but also a slight decrease in “get-well” defenses that are easy matchups. There is more “sameness” when it comes to NFL defenses these days, so it’s harder than usual right now to handicap a team’s schedule. In short, strength of schedule is still a factor to consider, but it’s only one of many factors and shouldn’t be given too much weight.</li>
</ol>
<ol start="8">
<li><b>Handcuffing your studs isn’t as practical as it used to be</b> – For one, due to the great depth at RB and WR, you might be passing on a productive player in favor of a guy who’s a backup for a reason (he’s not starter material). Furthermore, it’s just harder than ever to find a must-have handcuff. The top one last year was <b>Ben Tate</b>, and he was being selected as high as the top-75 in drafts in 2012. He ended up being completely worthless. At this point, handcuffing your studs appears to be more of an unneeded luxury than a necessity.</li>
</ol>
<ol start="9">
<li><b>Forget about drafting a defense until one of the final rounds</b> – At this juncture, most fantasy players know the defenses have been an absolute farce and have been impossible to handicap on a year-to-year basis, so this tip isn’t very profound. But just in case you’re tempted to grab the Bear D a few rounds from the end of your draft based on last year, give it up. You certainly do want to get one of the more appealing options with one of your final picks, but let’s not forget that more than half of last year’s top-12 finishers at DT were Waiver Wire pickups, so you’re more likely to fetch a solid unit off the scrap heap than you are to draft one.</li>
<li><b>Prepare for an active Waiver Wire</b> – And finally, with all this great depth at most key positions, we should prepare for a WW that is very fruitful in 2013. There are many jobs and roles up for grabs in training camps this year, but most likely a lot of those situations will still be fairly fluid come Week One, so fantasy owners will probably leave a lot of viable options undrafted this year. That’s also true simply because there are more viable options than usual. So in the final rounds of your draft, you should be able to focus a little more on upside potential and not worry too much about drafting a player who’ll be an obvious cut after a couple of weeks. In fact, you might prefer having a player or two to release with no worries because appealing options will be emerging on the wire.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2013/05/21/10-draft-tips-for-2013/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>12-team Non-PPR mock draft review</title>
		<link>http://www.fantasyguru.com/blog/2013/05/09/12-team-non-ppr-mock-draft-review/</link>
		<comments>http://www.fantasyguru.com/blog/2013/05/09/12-team-non-ppr-mock-draft-review/#comments</comments>
		<pubDate>Thu, 09 May 2013 20:52:51 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>
		<category><![CDATA[Ahmad Bradshaw]]></category>
		<category><![CDATA[Colin Kaepernick]]></category>
		<category><![CDATA[Danario Alexander]]></category>
		<category><![CDATA[Dez Bryant]]></category>
		<category><![CDATA[Doug Martin]]></category>
		<category><![CDATA[Dwayne Bowe]]></category>
		<category><![CDATA[Green Bay Packers]]></category>
		<category><![CDATA[Greg Jennings]]></category>
		<category><![CDATA[Johnathan Franklin]]></category>
		<category><![CDATA[Justin Blackmon]]></category>
		<category><![CDATA[Kyle Rudolph]]></category>
		<category><![CDATA[Michael Floyd]]></category>
		<category><![CDATA[Mike Gillislee]]></category>
		<category><![CDATA[Phil Dawson]]></category>
		<category><![CDATA[Stevan Ridley]]></category>
		<category><![CDATA[Vick Ballard]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1222</guid>
		<description><![CDATA[<p>In about a month, I will be whipping up my initial and early Draft Plan, which will simply cover all the positions and how to approach them. In the summer, I’ll tweak that and quadruple the size of the article, as I always do in the summer. That will cover a plan of action by position, go pick-by-pick through the first 10 rounds, and much more.</p>
<p>But in order to formulate my Draft Plan, I have to actually draft, and I have been doing that this month. Today I did my second mock draft for a magazine, this one for USA Today’s fantasy magazine. I can’t share all the results, but I can share my picks and some general thoughts.</p>
<p>As you may recall, I thought last year a good way to zig when everyone zagged in a draft was to, as I put it, “kick it old school” and go RB-RB. That actually might have been bad advice, thanks to some RB injuries/poor play from namely Darren McFadden and DeMarco Murray. But I always try to be ahead of the curve, and it appears I was because going old school looks like a great way to go this year, since QB [...]]]></description>
				<content:encoded><![CDATA[<p>In about a month, I will be whipping up my initial and early Draft Plan, which will simply cover all the positions and how to approach them. In the summer, I’ll tweak that and quadruple the size of the article, as I always do in the summer. That will cover a plan of action by position, go pick-by-pick through the first 10 rounds, and much more.</p>
<p>But in order to formulate my Draft Plan, I have to actually draft, and I have been doing that this month. Today I did my second mock draft for a magazine, this one for<strong> USA Today’s fantasy magazine</strong>. I can’t share all the results, but I can share my picks and some general thoughts.</p>
<p>As you may recall, I thought last year a good way to zig when everyone zagged in a draft was to, as I put it, “kick it old school” and go RB-RB. That actually might have been bad advice, thanks to some RB injuries/poor play from namely <b>Darren McFadden</b> and <b>DeMarco Murray</b>. But I always try to be ahead of the curve, and it appears I was because going old school looks like a great way to go this year, since QB and WR are so deep. RB is pretty deep, too, but the quality falls off considerably after the top-15 or so RBs.</p>
<p>So knowing that I had to try my best to hold off on QB at least a little and focus on RB if at all possible, this draft went pretty well for me. Here’s a quick review:</p>
<p>Round 1</p>
<p><b> 4. Fantasy Guru &#8211; Doug Martin RB, TAM</b></p>
<p>Young back who proved a lot last year and is not sharing the ball, plus his OL should be much better with those two starting guards back. So I obviously liked the pick.</p>
<p>Round 2</p>
<p><b> 9. Fantasy Guru &#8211; Dez Bryant WR, DAL</b></p>
<p>Little risky taking him over a Demaryius Thomas and a Larry Fitzgerald, but I’m usually all about juice and upside.</p>
<p>Round 3</p>
<p><b> 4. Fantasy Guru &#8211; Stevan Ridley RB, NWE</b></p>
<p>I have to have two high-end RBs, and Ridley was top-10 in a non-PPR last year. He’s a borderline stud, so I’m not worried about <b>Leg Blount</b> at all, because Blount stinks.</p>
<p>Round 4</p>
<p><b> 9. Fantasy Guru &#8211; Dwayne Bowe WR, KAN</b></p>
<p>Not a sexy pick, but Bowe is rock solid and will get much better QB play this year, plus Andt Reid certainly helps.</p>
<p>Round 5</p>
<p><b> 4. Fantasy Guru &#8211; Colin Kaepernick QB, SFO</b></p>
<div class="wp-caption alignright" style="width: 422px"><img alt="" src="http://www.fantasyguru.com/football/subscribers/images/ckaepernick.jpg" width="412" height="423" /><p class="wp-caption-text">I was at this playoff game and saw first-hand how deadly Colin Kaepernick can be.</p></div>
<p>I couldn’t hold out any longer on a QB and got my guy Kaepernick. This was a very good spot for him and I got the best of both worlds holding off a little, but still getting someone with top-3 potential</p>
<p>Round 6</p>
<p><b> 9. Fantasy Guru &#8211; Vick Ballard RB, IND</b></p>
<p>Another non-sexy pick, but Ballard should be reliable as the main guy in what should be a good offense. I had to get some stability there for my third RB spot and he was the final stable option available.</p>
<p>Round 7</p>
<p><b> 4. Fantasy Guru &#8211; Greg Jennings WR, MIN</b></p>
<p>I considered <b>Danario Alexander</b> here, but that knee still scares me. Jennings should be fine as the clear #1 WR here. If <b>Christian Ponder</b> flops, they at least have <b>Matt Cassel</b>, who threw 15 TD passes to Bowe a few years ago.</p>
<p>Round 8</p>
<p><b> 9. Fantasy Guru &#8211; Kyle Rudolph TE, MIN</b></p>
<p>In a non-PPR, I feel okay about Rudolph and have to think he will have more consistency this year – or at least fewer goose eggs. He did score 9 TDs last year.</p>
<p>Round 9</p>
<p><b> 4. Fantasy Guru &#8211; Danario Alexander WR, SDG</b></p>
<p>Whenever someone is available two rounds after you seriously considered him, you take him.</p>
<p>Round 10</p>
<p><b> 9. Fantasy Guru &#8211; Justin Blackmon WR, JAC</b></p>
<p>Starting to get a little lazy, but Blackmon is going to get the ball when he returns and he knows one more strike and he’s out. Worthy gamble this late as my 5<sup>th</sup> WR.</p>
<p>Round 11</p>
<p><b> 4. Fantasy Guru &#8211; Ahmad Bradshaw RB, NYG</b></p>
<p>Not a bad sneaky option for some RB depth. He’s going to play somewhere, that’s for sure.</p>
<p>Round 12</p>
<p><b> 9. Fantasy Guru &#8211; Johnathan Franklin RB, GNB</b></p>
<p>I was still looking for RB depth, and some upside, so he made sense.</p>
<p>Round 13</p>
<p><b> 4. Fantasy Guru &#8211; Green Bay Packers Def/ST, GNB</b></p>
<p>I actually thought the draft was 14 rounds (long story), so I took a DT. Believe it or not, there was already a little run on defenses. Green Bay is usually decent.</p>
<p>Round 14</p>
<p><b> 9. Fantasy Guru &#8211; Phil Dawson K, SFO</b></p>
<p>Again, I thought this was my last pick, and I was glad to get a guy who could easily boot 35 FGs in this great situation. In fact, at his 2012 clip and if he was on the 49ers, he would have approached 50 FGs in 2012 if you can believe that.</p>
<p>Round 15</p>
<p><b> 4. Fantasy Guru &#8211; Mike Gillislee, RB, Mia</b></p>
<p>Now that I see I have two more picks, I’m all about upside. In Miami, this rookie might actually have to only beat out a guy who has 50 career carries in Lamar Miller, so he’s worth a look.</p>
<p>Round 16</p>
<p><b> 9. Fantasy Guru &#8211; Michael Floyd, WR, ARI </b></p>
<p>Not a bad depth pick in the final round, since he’s a 1<sup>st</sup> round talent whose QB situation just got a lot better.</p>
<p><b>Starting lineup</b>:<br />
<b>QB</b> &#8211; Kaepernick, Colin QB (SFO 9)<br />
<b>RB</b> &#8211; Martin, Doug RB (TAM 5)<br />
<b>RB</b> &#8211; Ridley, Stevan RB (NWE 10)<br />
<b>WR</b> &#8211; Bryant, Dez WR (DAL 11)<br />
<b>WR</b> &#8211; Bowe, Dwayne WR (KAN 10)<br />
<b>TE</b> &#8211; Rudolph, Kyle TE (MIN 5)<br />
<b>K</b> &#8211; Dawson, Phil K (SFO 9)<br />
<b>D/ST</b> &#8211; Packers, Green Bay D/ST (GNB 4)<br />
<b>Flex</b> &#8211; Ballard, Vick RB (IND 8)</p>
<p><b>Bench</b><br />
Jennings, Greg WR (MIN 5)<br />
Alexander, Danario WR (SDG 8)<br />
Blackmon, Justin WR (JAC 9)<br />
Bradshaw, Ahmad RB (NYG 9)<br />
Franklin, Johnathan RB (GNB 4)<br />
Mike Gillislee, RB, Mia<br />
Michael Floyd, WR, ARI</p>
<p>I wasn’t watching this mock draft like a hawk, but overall I felt this was a good draft and that my team includes a lot of young players who are proven and in good situations. It’s not a completely accurate look at how I would draft in real life because I have no backup QB or TE, but it’s a good exercise. 1-2 more of these and I should be ready to formulate my initial 2013 Draft Plan.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2013/05/09/12-team-non-ppr-mock-draft-review/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Very, very, very, early rookie keeper rankings</title>
		<link>http://www.fantasyguru.com/blog/2013/04/28/very-very-very-early-rookie-keeper-rankings/</link>
		<comments>http://www.fantasyguru.com/blog/2013/04/28/very-very-very-early-rookie-keeper-rankings/#comments</comments>
		<pubDate>Sun, 28 Apr 2013 19:23:13 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1213</guid>
		<description><![CDATA[<p>5/1 Edit: I have made a few small but key changes to the early rankings, as expected, so I&#8217;ve removed them in case someone stops by here and thinks these are the latest and (at least for now) final rankings. You can find our updated keeper rankings, including all the rookies, here:</p>
<p>http://www.fantasyguru.com/football/subscribers/ftdb.php?page=keepers&#38;position=QB&#38;print=N</p>
<p>&#160;</p>
]]></description>
				<content:encoded><![CDATA[<p>5/1 Edit: I have made a few small but key changes to the early rankings, as expected, so I&#8217;ve removed them in case someone stops by here and thinks these are the latest and (at least for now) final rankings. You can find our updated keeper rankings, including all the rookies, here:</p>
<p><a href="http://www.fantasyguru.com/football/subscribers/ftdb.php?page=keepers&amp;position=QB&amp;print=N">http://www.fantasyguru.com/football/subscribers/ftdb.php?page=keepers&amp;position=QB&amp;print=N</a></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2013/04/28/very-very-very-early-rookie-keeper-rankings/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Quick thoughts on the 2013 schedule</title>
		<link>http://www.fantasyguru.com/blog/2013/04/19/quick-thoughts-on-the-2013-schedule/</link>
		<comments>http://www.fantasyguru.com/blog/2013/04/19/quick-thoughts-on-the-2013-schedule/#comments</comments>
		<pubDate>Fri, 19 Apr 2013 21:43:18 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1210</guid>
		<description><![CDATA[<p>There have been years in the recent past when our SOS analysis has been really strong and looking at strength of schedule has been very useful for fantasy purposes. This is always an element to inspect closely, but I have to say that looking back at least year’s coverage, the impact of SOS in 2012 was negligible. I’d say in terms of accuracy that it leaned to the positive, but overall the schedule’s impact was minor last year.</p>
<p>But certainly, inspecting each team’s schedule is something that absolutely has to be done, especially the key playoff weeks, when 1-2 good or bad matchups can mean the difference between merely making the fantasy playoffs and winning it all.</p>
<p>As we always do, we project the upcoming season’s SOS by assigning a number grade for each defense against the run and the pass. We then compare those grades for all 32 teams’ 16 matchups and attempt to predict SOS rather than go strictly off of 2012’s numbers.</p>
<p>We’ll do that after the draft, when we can properly grade each defense against the run and the pass, but for now here are some quick thoughts on the 2013 schedule.</p>
<p>Arizona – Their SOS will be tougher simply due [...]]]></description>
				<content:encoded><![CDATA[<p>There have been years in the recent past when our SOS analysis has been really strong and looking at strength of schedule has been very useful for fantasy purposes. This is always an element to inspect closely, but I have to say that looking back at least year’s coverage, the impact of SOS in 2012 was negligible. I’d say in terms of accuracy that it leaned to the positive, but overall the schedule’s impact was minor last year.</p>
<p>But certainly, inspecting each team’s schedule is something that absolutely has to be done, especially the key playoff weeks, when 1-2 good or bad matchups can mean the difference between merely making the fantasy playoffs and winning it all.</p>
<p>As we always do, we <i>project</i> the upcoming season’s SOS by assigning a number grade for each defense against the run and the pass. We then compare those grades for all 32 teams’ 16 matchups and attempt to predict SOS rather than go strictly off of 2012’s numbers.</p>
<p>We’ll do that after the draft, when we can properly grade each defense against the run and the pass, but for now here are some quick thoughts on the 2013 schedule.</p>
<p><b>Arizona</b> – Their SOS will be tougher simply due to their four games against SF/Sea so it won’t rank high, but otherwise there are a number of favorable matchups, especially against the pass, which could be good news for <b>Carson Palmer</b> and their receivers.<br />
<b>Weeks 13-16</b>: A mixed bag against Phi, Stl, Ten, and SF.</p>
<p><b>Atlanta</b> – The Falcons have had a good schedule the last couple of years, but it will check in as one of the hardest this year, most likely due to four tough matchups. The good news is I see eight good matchups for the pass, so <b>Matt Ryan</b> should be helped by the schedule (and his division).<br />
<b>Weeks 13-16</b>: Pretty solid against Buf, GB, Was, and SF<b><br />
</b></p>
<p><b>Baltimore</b> – Their schedule won’t rank as being particularly favorable, but it doesn’t look particularly prohibitive and looks more favorable against the pass than not.<br />
<b>Weeks 13-16</b>: Pretty good against Pit, Min, Det, and NE</p>
<p><b>Buffalo</b> – The schedule looked tough for the Bills last year, but it definitely looks better this year and should rank in the top 50% for both the run and the pass. That should help, since they need assistance in their first year in a new system and with a new coaching staff.<br />
<b>Weeks 13-16</b>: Pretty darn good against Atl, TB, Jac, and Mia</p>
<p><b>Carolina</b> – They have four tough matchups against the run and zero favorable ones (as of now), but it does look better against the pass. I see <b>Cam Newton</b> as going up against eight weak pass defenses this year, which could definitely help.<br />
<b>Weeks 13-16</b>: Overall, pretty good against TB, NO, NYJ, and NO</p>
<p><b>Chicago</b> – The Bear schedule looks very favorable overall. They have only one tough matchup against the run (Pit) and that might not be as tough as it’s been. They also have what I view as seven favorable matchups against the pass.<br />
<b>Weeks 13-16</b>: Nothing scary against Min, Dal, Cle, and Phi</p>
<p><b>Cincinnati</b> – The Bengal schedule looks unusually easy this year, thanks to some hits the Steelers and Ravens have taken on defense (although Balt could still be very good). They rank in the top 50% against the run and pass.<br />
<b>Weeks 13-16</b>: It could be particularly good against the pass versus SD, Ind, Pit, and Min</p>
<p><b>Cleveland</b> – The Brown schedule also looks easier than usual with only one tougher matchup against the run (Pit, but they also get Pit again Week 17) and one against the pass (NYJ Week 16). But that matchup will look better if CB Revis is no longer a Jet.<br />
<b>Weeks 13-16</b>: About average against Jac, NE, Chi, and NYJ</p>
<p><b>Dallas</b> – I actually do not see a single tough matchup for them against the run or the pass, so that’s good news for their players. It’s especially good for the passing game, as I see nine favorable matchups for <b>Tony Romo</b>.<br />
<b>Weeks 13-16</b>: Pretty darn good against Oak, Chi, GB, and Was</p>
<p><b>Denver </b>– Thanks to their weaker division and some luck, the Bronco schedule looks fantastic. I don’t see a tough matchup on the schedule for run or pass, and I see <b>Peyton Manning</b> with a whopping 10 favorable matchups.<br />
<b>Weeks 13-16</b>: It’s good overall against KC, Ten, SD, and Hou</p>
<p><b>Detroit</b> – Nothing particularly scary here, but it is a little tougher against the run than the pass due to a couple of tough matchups against the run.<br />
<b>Weeks 13-16</b>: Average or even slightly above average against GB, Phi, Bal, and NYG</p>
<p><b>Green Bay</b> – They have two tough matchups against the run, but otherwise the schedule looks pretty good and it’s a little easier overall against the pass. In other words, the schedule looks negligible.<br />
<b>Weeks 13-16</b>: Nothing concerning against Det, Atl, Dal, and Pit</p>
<p><b>Houston</b> – The Texans usually have a good schedule in recent years, and 2013 is no exception. It’s particularly favorable against the pass, which will help because they need all the support they can get throwing the ball.<br />
<b>Weeks 13-16</b>: Well above average against NE, Jac, Ind, and Den</p>
<p><b>Indianapolis</b> – The Colts will likely come in below average against the run and the pass when we do our numbers, but overall their schedule doesn’t look very prohibitive. It’s going to be skewed a bit due to matchups against SF and Sea.<br />
<b>Weeks 13-16</b>: About middle-of-the-road against Ten, Cin, Hou, and KC</p>
<p><b>Jacksonville</b> – Their schedule is probably below-average against the run and the pass, but overall it doesn’t look too bad. We’ll have a better idea about their opponents after the draft, of course.<br />
<b>Weeks 13-16</b>: Looks pretty good against Cle, Hou, Buf, and Ten</p>
<p><b>Kansas City</b> – They have several matchups in the NFC East that could be tougher, but given the 2012 state of the Eagle, Giant, and Redskin defense, it does look very good for the run and the pass – and playing the Raiders twice a year doesn’t hurt.<br />
<b>Weeks 13-16</b>: Nothing scary at all overall against Den, Was, Oak, and In</p>
<p><b>Miami</b> – There are definitely some problem areas, but the schedule looks at worst above average against the run and the pass. It looks particularly favorable against the pass.<br />
<b>Weeks 13-16</b>: Pretty decent against NYJ, Pit, NE, and Buf</p>
<p><b>Minnesota</b> – Playing against Pit, Bal, and Sea doesn’t help and knocks them down in the bottom half against the run and the pass.<br />
<b>Weeks 13-16</b>: Not that great against Chi, Bal, Phi, and Cin</p>
<p><b>New England </b>– They have had some great schedules in the past, but this year’s looks below average, thanks to several matchups against top-10 NFL defenses. It looks little harder for the run than the pass.<br />
<b>Weeks 13-16</b>: Not that great on paper against Hou, Cle, Mia, and Bal</p>
<p><b>New Orleans</b> – They will likely rank low against the run and the pass due to a certain few matchups, but overall things don’t look overly prohibitive.<br />
<b>Weeks 13-16</b>: About average against Sea, Car, Stl, and Car</p>
<p><b>NY Giants</b> – Playing the AFC West and in a weaker (for now) NFC East should mean the Giants will land in the top-10 in terms of ease of schedule against the run and the pass.<br />
<b>Weeks 13-16</b>: Not bad at all against Was, SD, Sea, and Det</p>
<p><b>NY Jets </b>– Their schedule looks average or even a little worse against the run, but it’s one of the easiest schedules against the pass I can recall in recent years. Of course, that’s kind of a moot point for this team.<br />
<b>Weeks 13-16</b>: Very favorable against Mia, Oak, Car, and Cle<b><br />
</b></p>
<p><b>Oakland</b> – They will likely land around the middle of the pack in our projected 2013 SOS, but other than a couple of problematic matchups, the schedule looks pretty good for the Raiders, especially against the pass.<br />
<b>Weeks 13-16</b>: Nothing scary against Dal, NYJ, KC, and SD<b><br />
</b></p>
<p><b>Philadelphia</b> – Playing in a shakier NFC East and against the AFC West helps, and overall the Eagle schedule looks favorable against the run and especially the pass.<br />
<b>Weeks 13-16</b>: Favorable overall against Ari, Det, Min, and Chi</p>
<p><b>Pittsburgh</b> – The Steelers usually have a very favorable schedule, and that should be the case this year, especially if they can avoid <b>Darrelle Revis</b> playing for the Jets this year.<br />
<b>Weeks 13-16</b>: Not wonderful against Bal, Mia, Cin, and GB but nothing to panic about<b><br />
</b></p>
<p><b>San Diego</b> – The Chargers haven’t finished high in the standings for a while and playing in a weaker division, so their schedule has been pretty good the last few years. That is definitely the case this year, and they should wind up in our top-12 against the run and the pass this year.<br />
<b>Weeks 13-16</b>: Could possibly be a little tough against Cin, NYG, Den, and Oak<b><br />
</b></p>
<p><b>San Francisco</b> – It looks like they will be middle-of-the-pack or worse against the run and the pass, with the run matchups looking a little tougher.<br />
<b>Weeks 13-16</b>: Not too bad against Stl, Sea, TB, and Atl</p>
<p><b>Seattle</b> – It looks pretty tough against the run (SF twice doesn’t help) and below average against the pass.<br />
<b>Weeks 13-16</b>: Could be below-average overall against NO, SF, NYG, and Ari<b><br />
</b></p>
<p><b>St. Louis</b> – The Rams had a really tough schedule last year, thanks mainly to their division, and they are certainly looking at a tough schedule on paper this year. It’s a little tougher against the run and could wind up being the hardest run schedule in the league.<br />
<b>Weeks 13-16</b>:<b> </b>Probably leans to the tougher side against SF, Ari, NO, and TB<b><br />
</b></p>
<p><b>Tampa Bay</b> – It’s about average against the run and could be a little easier and overall favorable against the pass.<br />
<b>Weeks 13-16</b>: Probably below-average against Car, Buf, SF, and Stl</p>
<p><b>Tennessee</b> – Despite playing four games against the Colts and Jags, the Titans had a tougher schedule in 2012, and it looks like they do again. It looks a little tougher against the pass.<br />
<b>Weeks 13-16</b>: Not too bad against Ind, Den, Ar, and Jac<b></p>
<p>Washington</b> – Overall, the Redskins schedule looks above average, and it looks easier against the pass than the run.<br />
<b>Weeks 13-16</b>: Nothing too scary against NYG, KC, Atl, and Dal</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2013/04/19/quick-thoughts-on-the-2013-schedule/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>For Fitzgerald, the cavalry has arrived</title>
		<link>http://www.fantasyguru.com/blog/2013/04/05/for-fitzgerald-the-cavalry-has-arrived/</link>
		<comments>http://www.fantasyguru.com/blog/2013/04/05/for-fitzgerald-the-cavalry-has-arrived/#comments</comments>
		<pubDate>Fri, 05 Apr 2013 18:26:09 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>
		<category><![CDATA[Andre Roberts]]></category>
		<category><![CDATA[Bruce Arians]]></category>
		<category><![CDATA[Carson Palmer]]></category>
		<category><![CDATA[Larry Fitzgerald]]></category>
		<category><![CDATA[Michael Floyd]]></category>
		<category><![CDATA[Rashard Mendenhall]]></category>
		<category><![CDATA[Rob Housler]]></category>
		<category><![CDATA[Ryan Williams]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1199</guid>
		<description><![CDATA[<p>It is amazing how quickly fantasy fortunes can change for those in keeper or dynasty leagues. Just a few days ago, those who owned wideout Larry Fitzgerald really did not know what they had in the future Hall of Famer, which was a sad statement because he is still in his prime and is, you know, a future Hall of Famer.</p>
<p>I’m not saying his new QB Carson Palmer is unquestionably a savior, but Palmer landing in Arizona is pretty news for this offense. Yes, the OL is a major concern, but let’s keep in mind it was pretty bad in Oakland, too, and Palmer managed to throw for over 4000 yards with a lesser receiving corps and a crappy running game.</p>
<p>I particularly like the fit with Bruce Arians, who is as proven an offensive coordinator as there is in the league. Arians has had particular success with big, strong-armed QBs like Palmer in Ben Roethlisberger and Andrew Luck. Palmer doesn’t move as well as those two, but he’s not a total statue in the pocket, either. And I LOVED what Arians did last year with Reggie Wayne, particularly how he moved him around to find good matchups. I said on [...]]]></description>
				<content:encoded><![CDATA[<p>It is amazing how quickly fantasy fortunes can change for those in keeper or dynasty leagues. Just a few days ago, those who owned wideout <strong>Larry Fitzgerald</strong> really did not know what they had in the future Hall of Famer, which was a sad statement because he is still in his prime and is, you know, a future Hall of Famer.</p>
<p>I’m not saying his new QB <strong>Carson Palmer</strong> is unquestionably a savior, but Palmer landing in Arizona is pretty news for this offense. Yes, the OL is a major concern, but let’s keep in mind it was pretty bad in Oakland, too, and Palmer managed to throw for over 4000 yards with a lesser receiving corps and a crappy running game.</p>
<p>I particularly like the fit with <strong>Bruce Arians</strong>, who is as proven an offensive coordinator as there is in the league. Arians has had particular success with big, strong-armed QBs like Palmer in <strong>Ben Roethlisberger</strong> and <strong>Andrew Luck</strong>. Palmer doesn’t move as well as those two, but he’s not a total statue in the pocket, either. And I LOVED what Arians did last year with <strong>Reggie Wayne</strong>, particularly how he moved him around to find good matchups. I said on the radio last summer that Wayne could catch 100 balls, but I was still a little surprised that he actually did it (106). Luck was obviously quite good, but Wayne in 2012 was brilliant with Arians pulling the strings, and there’s reason to believe Fitzgerald can quickly turn his shaky fantasy status around with Arians and Palmer in the fold. I also think it’s a case of addition by subtraction with <strong>Ken Whisenhunt</strong> out of Arizona. He’s a good coach who got them to the Super Bowl, but let’s be honest: Whisenhunt is not exactly known as a creative or particularly effective offensive guy, and it was <strong>Kurt Warner</strong> and OC <strong>Todd Haley</strong> who should have been given the most credit for the team’s success early in Wiz’s career in the desert.</p>
<div class="wp-caption alignright" style="width: 422px"><img src="http://www.fantasyguru.com/football/subscribers/images/lfitzgerald.jpg" alt="" width="412" height="423" /><p class="wp-caption-text">If you&#8217;re a Larry Fitzgerald owner, you&#8217;re feeling a lot better about your guy this week</p></div>
<p>You can certainly make some pretty strong arguments against Palmer this year, but you can say that about roughly two-thirds of the players drafted in fantasy football. Overall, Palmer’s numbers were merely solid last year, but for fantasy purposes, I usually look at completion percentage and yards per attempt, and Palmer’s in 2012 (61.1 and 7.1, respectively) were, again, solid. Palmer back in 2010 looked like a player who might be slipping quickly, but I felt he has thrown the ball well the last two years; it’s come out of his hand well and with good velocity. He <em>has</em> fallen into the trap of trying to do too much, which tends to lead to some bad decisions, but that might not be a huge problem with a stud like Fitzgerald and a great offensive coach like Arians supporting him.</p>
<p>The Raider receiving corps last year, while talented on paper, was shaky. <strong>Denarius Moore</strong> is a player I like a lot, and we’ve pushed him pretty hard, but he lost his way last year. Clearly, he was not on the same page as Palmer, and most disconcerting was how that was case as the season wore on. I don’t know the real story there, but Palmer has been a big Moore supporter, so I have to assume most of the blame should go to the young wideout, and not the veteran QB. Again, I know the OL is a problem, but if they can give him a semblance of protection (keep in mind former #1 pick <strong>Levi Brown</strong> will be back this year at LT, and he missed all of 2012), there is really nice potential with this passing game, much like there was in Indy last year with Arians running the offense. It could very well be a complete passing game with last year’s #1 pick <strong>Michael Floyd</strong> – who Arians told me at the combine he thinks is a rising star – and <strong>Andre Roberts</strong>. This looks perfect because Roberts is probably best cast as a slot receiver, yet his versatility and production last year (64/759/5) was excellent, considering the circumstances. And the icing on the cake could be TE <strong>Rob Housler</strong>. We’ve pushed Housler pretty hard the last two years as a great sleeper candidate, almost entirely because of his high-end speed and athleticism. He caught a sneaky 45 passes last year, but his YPC average of 9.3 was bad (he tied fossil <strong>Dallas Clark</strong> and was around 45<sup>th</sup> at the position among all TEs with 20 or more grabs last year). He also has yet to score a TD in the NFL. That’s disconcerting, but I specifically remember <strong>Kevin Kolb</strong> missing him running wide-ass open down the seam for two potential scores in 2011, and I’m pretty sure Kolb (or someone else) missed him on one in 2012. Granted, a lot of Palmer’s production with TE <strong>Brandon Myers</strong> last year was in garbage time, but Palmer is clearly a big upgrade at QB, and in his “magical” third season, Housler could be poised for a coming out party. The Cardinal defense is top-12 in the league, so Palmer might not pad his stats with GTP this year, but let’s not forget that Arians loves to throw the ball. This guy’s never seen a passing play he didn’t like. I can still see Palmer throwing it about 550 times this year, and I see his completion percentage sticking in the 61-62% range, with 63-64 a possibility. Palmer back in 2011 actually averaged 8.4 yards per attempt, so I can see him bumping his 2012 number of 7.1 up to about 7.5, which would give him 4,125 yards. New RB <strong>Rashard Mendenhall</strong> isn’t a great goal line back, so when they are in tight, I can see them looking to throw plenty, so 25 TDs should be attainable for Palmer, and there’s upside if – all goes perfectly well for him – to hit 30 in this passing league. 25 TDs with that yardage would give Palmer about 310-315 fantasy points (I’m giving him 10 points for rushing, and he has scored 1 TD on the ground the last two years). Back in 2005, that would have netted Palmer a top-3 finish at QB, but things have changed considerably in the NFL and in fantasy. These days, around 300 points is usually a top-12-14 finish, which is around where he finished in 2012.</p>
<p>But unlike 2011 and 2012 in Oakland, there’s upside for more in Arizona with what could be a surprisingly-strong receiving corps. The backfield isn’t exactly set, but there’s talent here for sure with Mendenhall and <strong>Ryan Williams</strong> on the roster, and <strong>William Powell</strong> showed some promise last year as a changeup and potential 3<sup>rd</sup> down back (he had a 6-catch game last year). Palmer won’t command a lot of respect in fantasy drafts, so he should be a nice choice as a backup due to value and potential. As for Fitzgerald, he’s obviously back in the conversation as a top-5 wideout. Although the Cards have other options, he’s still one of the few true #1 WRs – a guy Arians will gameplan to get the ball to a TON, and he will do so EVERY WEEK.</p>
<p>Again, it’s easy to find warts with almost any player who’ll be taken outside of the top-25 in a typical fantasy draft. Palmer will be 34 in December, the shabby OL is a problem, and this is a very tough division, one with three good secondaries. But when I add up and compare the positives and negatives, I really like Palmer in Arizona, and with Arians. The cavalry has arrived finally for Fitzgerald, and with a true pro at QB who can actually play, we should see significant development from their young receivers, specifically Floyd and Housler.</p>
<p><strong>Projected 2013 rankings</strong>:</p>
<p>Carson Palmer – 13-15 at QB<br />
Larry Fitzgerald – 6-10 at WR<br />
Michael Floyd – 45-50 at WR<br />
Rob Housler – 20-25 at TE</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2013/04/05/for-fitzgerald-the-cavalry-has-arrived/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Vikings had to trade Percy Harvin</title>
		<link>http://www.fantasyguru.com/blog/2013/03/11/vikings-had-to-trade-percy-harvin/</link>
		<comments>http://www.fantasyguru.com/blog/2013/03/11/vikings-had-to-trade-percy-harvin/#comments</comments>
		<pubDate>Mon, 11 Mar 2013 21:54:42 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>
		<category><![CDATA[Christian Ponder]]></category>
		<category><![CDATA[Minnesota Vikings]]></category>
		<category><![CDATA[Percy Harvin]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1196</guid>
		<description><![CDATA[<p>This past Friday night, I hosted a special off-season addition of SiriusXM Fantasy Football, and my FB question of the night asked if the Vikings should try to stick with Percy Harvin or go another route with a marquee free agent receiver like Mike Wallace or Greg Jennings. Of course, most people said “both,” but that was not an option given to readers/listeners because I didn’t see Minnesota retaining Harvin and signing a top free agent at his position as being possible.</p>
<p>And apparently, it wasn’t an option for the Vikings, who will (as soon as tomorrow) officially trade Harvin to Seattle for the 25th overall pick in this year’s draft plus a 7th-round selection this year and a mid-round pick in 2014.</p>
<p class="wp-caption-text">Percy Harvin is a flat-out stud, but the Vikings had to move him now</p>
<p>We all know Harvin is a unique and versatile athlete who can produce for a team in three ways: as a receiver, a runner, and a return man. The running is the least important element to his game, but the former high school tailback is certainly capable of helping an offense by rushing the ball. He’s a stud; we all know this. But he’s also [...]]]></description>
				<content:encoded><![CDATA[<p>This past Friday night, I hosted a special off-season addition of SiriusXM Fantasy Football, and my FB question of the night asked if the Vikings should try to stick with <strong>Percy Harvin</strong> or go another route with a marquee free agent receiver like <strong>Mike Wallace</strong> or <strong>Greg Jennings</strong>. Of course, most people said “both,” but that was not an option given to readers/listeners because I didn’t see Minnesota retaining Harvin and signing a top free agent at his position as being possible.</p>
<p>And apparently, it wasn’t an option for the Vikings, who will (as soon as tomorrow) officially trade Harvin to Seattle for the 25<sup>th</sup> overall pick in this year’s draft plus a 7<sup>th</sup>-round selection this year and a mid-round pick in 2014.</p>
<div class="wp-caption alignright" style="width: 422px"><img src="http://www.fantasyguru.com/football/subscribers/images/pharvin.jpg" alt="" width="412" height="423" /><p class="wp-caption-text">Percy Harvin is a flat-out stud, but the Vikings had to move him now</p></div>
<p>We all know Harvin is a unique and versatile athlete who can produce for a team in three ways: as a receiver, a runner, and a return man. The running is the least important element to his game, but the former high school tailback is certainly capable of helping an offense by rushing the ball. He’s a stud; we all know this. But he’s also been a pain in the ass for the Vikings who, keep in mind, took a bit of a chance on him with the 22<sup>nd</sup> overall pick of the 2009 draft. Harvin played well for Minnesota, but ultimately he did little to pay back the franchise for believing in him when some NFL teams were scared away due to his maturity issues. It’s rare we see a team give up on a young and elite talent like Harvin, but I don’t think the Vikings had a choice.</p>
<p>&nbsp;</p>
<p>Asking how Harvin can help the Seahawk offense is like asking what kind of scoring system one can implement in his or her fantasy football league; the main limitation is ones imagination. Obviously, he’s a dynamic (and vertical) threat inside, so he’s primarily a slot receiver. But he can also certainly line up and make plays (and vertical plays) outside.  There is definitely some familiarity here, since Harvin played under Seahawk OC <strong>Darrell Bevell</strong> for two seasons from 2009-2010.</p>
<p>Although he had missed only three games in three years going into 2012 (he missed 7 games this past year), Harvin’s availability had been in doubt from time-to-time over the years with the Vikings. Fortunately for Harvin, the situation with his migraines seems to have improved considerably. You would think that once he signs his new contract with the Seahawks, Harvin will be able to focus only on football, and if so Seattle’s offense just got a whole lot better. Even if Harvin still has some issues on and off the field, it’s impossible to be critical of Seattle for acquiring such a difference maker. Harvin’s versatility will work extremely well with QB <strong>Russell Wilson’s</strong> game, which includes the read-option. Harvin will make defending this offense – Wilson and the running game with <strong>Marshawn Lynch</strong> – a lot harder, so the move is at least good news for Wilson’s fantasy value. If there was still doubt as to whether or not Wilson was a viable fantasy starter in a 12-team league, that doubt should be gone now. Clearly, despite his lack of ideal height, Wilson will be able to get Harvin the ball all over the field due to his movement and ability to see the whole field. I’d have to also believe the presence of Harvin will help Lynch as well. The only real issue I have with this move is that I’m not sure there’s an active enough role now for all their other weapons. Harvin has played with veteran <strong>Sidney Rice</strong>, and with Rice being a tall receiver who can stretch the field from the outside, it’s a good pairing. But I don’t see much left over for guys like <strong>Doug Baldwin</strong> (who could be traded) and <strong>Golden Tate</strong>, and we might have to forget about the playoff emergence of TE <strong>Zach Miller</strong>, who finally came on late in 2012 and was the team’s leading receiver in both playoff games this past season.  Miller is a volume type of player at the TE position, but it’s hard to envision a huge role for him every week with Harvin around. Still, it’s not like anyone’s fantasy fortunes are going to be tied to Baldwin, Tate, or Miller.</p>
<p>Harvin will also help Seattle’s fantasy defense, since he’s a deadly return man and should be a good bet to take 1-2 kicks back for scores every year.</p>
<p>As for Harvin’s fantasy value, I think it’s fair to keep expectations at least a little tempered. He is moving on to a new team, but most importantly he’s on a team that attempted the fewest passes in the league in 2012. Yes, they were breaking in a new rookie QB, but they were only 22<sup>nd</sup> in pass attempts the year before. This has been <strong>Marshawn Lynch’s</strong> offense, and he will continue to handle a large workload. Harvin had a similar situation with the Vikings and <strong>Adrian Peterson</strong>, but Minnesota had literally nothing other than Harvin. In Seattle, they do have some other solid players on offense. This is also a team that has a darn good defense, and I don’t see them pushing the envelope too much by throwing the ball all over the field if they are holding a lead in the second half of their games. Again, I can’t really be too critical of such a dangerous player, but between his new environment, his previous issues on and off the field, and the run-heavy approach we’ve seen in Seattle the last two years, I’d prefer to consider Harvin as a #2 fantasy wideout in 2013. Calling Harvin a top-10 or top-12 fantasy WR, even in a PPR, seems to be pushing it, at least for this year.</p>
<p>Obviously, this move makes the Vikings major players in the wide receiver market both in free agency and in the draft. I can see them using significant resources for a wideout for both. For example, I can see them signing either <strong>Mike Wallace</strong> or <strong>Greg Jennings</strong> and also using one of their two #1 picks on a wideout. They do have 2012 rookie <strong>Jarius Wright</strong>, whose emergence I’m sure helped the team make the decision to move Harvin, at least a tiny bit. Wright is no Harvin, but he’s a natural slot receiver whose value is about to rise because he should replace Harvin in several ways, mainly as their top inside receiver (but we’ll see who else they bring in). Losing Harvin is a shame for QB <strong>Christian Ponder</strong>, who clicked well with Harvin this year, but this move had to be done, and the Vikings deserve credit for getting so much for a player who was likely gone after 2013, anyway (and Harvin in Minnesota in 2013 could have been ugly). Ponder wasn’t going to be a hot fantasy pick with Harvin, so it’s not really worth delving into the ramifications for Ponder, or for that matter, Peterson.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2013/03/11/vikings-had-to-trade-percy-harvin/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Alex Smith an upgrade for Chiefs, but hardly a slam dunk</title>
		<link>http://www.fantasyguru.com/blog/2013/02/27/alex-smith-an-upgrade-for-chiefs-but-hardly-a-slam-dunk/</link>
		<comments>http://www.fantasyguru.com/blog/2013/02/27/alex-smith-an-upgrade-for-chiefs-but-hardly-a-slam-dunk/#comments</comments>
		<pubDate>Wed, 27 Feb 2013 18:50:21 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1191</guid>
		<description><![CDATA[<p>With the news coming down today that the Chiefs have agreed to a deal to acquire QB Alex Smith from the 49ers, and confirmed by two reporters who seemingly never get a story wrong (Adam Schefter and Jay Glazer), I thought this would make for a good first blog post of the 2013 season, even though the deal won’t be official for about two weeks, when the league year officially begins on March 12th.</p>
<p>New head coach Andy Reid is high on Smith, and I get it – to a point. Reid certainly knows a lot more about football than I do, but a Smith-Reid marriage does seem a little odd.</p>
<p class="wp-caption-text">Alex Smith is an upgrade for the Chiefs at QB, but he doesn&#8217;t exactly appear to be an Andy Reid QB</p>
<p>Let me first focus on the positives with Smith. Clearly, he’s a “professional” QB, and a guy a team can win with if the pieces around him are in place. He’s shown he can play well in big games. He’s mobile and fairly athletic, very efficient and doesn’t turn the ball over, and he has experience in the west coast offense.  He’s a veteran, a good leader, he’s tough, he’s [...]]]></description>
				<content:encoded><![CDATA[<p>With the news coming down today that the Chiefs have agreed to a deal to acquire QB <strong>Alex Smith</strong> from the 49ers, and confirmed by two reporters who seemingly never get a story wrong (Adam Schefter and Jay Glazer), I thought this would make for a good first blog post of the 2013 season, even though the deal won’t be official for about two weeks, when the league year officially begins on March 12<sup>th</sup>.</p>
<p>New head coach <strong>Andy Reid</strong> is high on Smith, and I get it – to a point. Reid certainly knows a lot more about football than I do, but a Smith-Reid marriage does seem a little odd.</p>
<div class="wp-caption alignright" style="width: 394px"><img class="   " src="http://www.fantasyguru.com/football/subscribers/images/alexsmith.jpg" alt="" width="384" height="505" /><p class="wp-caption-text">Alex Smith is an upgrade for the Chiefs at QB, but he doesn&#8217;t exactly appear to be an Andy Reid QB</p></div>
<p>Let me first focus on the positives with Smith. Clearly, he’s a “professional” QB, and a guy a team can win with if the pieces around him are in place. He’s shown he can play well in big games. He’s mobile and fairly athletic, very efficient and doesn’t turn the ball over, and he has experience in the west coast offense.  He’s a veteran, a good leader, he’s tough, he’s a gamer, etc.</p>
<p>The Chiefs reportedly gave up the 34<sup>th</sup> overall pick in the 2013 draft for Smith, plus a later pick (possibly a conditional pick). That seems high to me, since I do see a potential identity crisis with this pairing. We all know that Reid loves the forward pass, yet Smith is a guy who’s at his best when he’s being limited in an offense. Back in 2011, by far his best season, Smith for example averaged only 27.8 pass attempts per game, which was the second-lowest number for QBs who played every week that year. Smith isn’t a game-manager per se (whatever that is), but he’s at his best when he’s in an offense that focusses on the running game. San Fran was perfect for him in ’11 because of their extremely active running game but also their great defense. The Chiefs do have some promising players on defense, but unless Reid’s offense is going to undergo a seismic shift, asking Smith to drop back 35+ times per game seems like a shaky proposition. In 2012, Reid’s offense averaged 38.6 pass attempts per game, and that seems high for Smith. Smith’s arm isn’t very strong, and while he’s made some nice throws for the 49ers under <strong>Jim Harbaugh</strong>, a lot of them came on designed big plays against defenses that were more so gearing up to stop the run. He’s also in the past been considered a bit of a slow-blinker, and if you’re going to throw the ball 35+ times a game, a QB must have a great clock in his head and be able to process information quickly. Smith has improved in this area, but I’m not sure he’s a great fit for a pass-happy system.</p>
<p>The other element that seems odd here is how we know Reid loves the deep ball, and Smith clearly has a mediocre arm. Now, I’ve always felt that Reid adapted his offense to the strengths (and weaknesses) of his QBs, namely <strong>Donovan McNabb</strong> and <strong>Michael Vick</strong>, by implementing more of a deep ball passing game. Smith should be a good fit in a traditional WCO, but I do still think Reid loves the deep ball, and I don’t see Smith have a lot of success throwing the ball 30-40+ yards down the field. In fact, I can count on one hand the number of Smith completions in 2011 that traveled more than 35 yards in the air.</p>
<p>The conservative nature of the 2011 49er offense is shown by Smith’s ultra-low INT rate (1.1%, best in the league) and high sack rate (9.0%, worst among the QBs who played every game). Clearly, he was coached to minimize turnovers and eat the ball if necessary – the sack rate was his worst since his rookie year and his INT rate was a career best. That really doesn’t seem like a Reid QB. He also in 2011 registered a career best in completion percentage, 61.4%, and YPA 7.1, which were nothing special. Typically, Reid QBs are at about 8.0 yards per attempt, and I really don’t see Smith in that territory.</p>
<p>So again, I understand the move to upgrade the QB position, and Smith definitely represents one over the sluggish <strong>Matt Cassel</strong>, who will likely get cut. But you’ll have to excuse me for not getting too excited. Also, other than 2011, let’s be honest: Smith’s body of work in the NFL has been shaky.</p>
<p>However, I am excited for <strong>Jamaal Charles</strong>. I actually had a chance to ask Reid about Charles and how he fits into his offense at the combine last week. Reid gave a fairly generic answer and basically said Charles can fit into any system. But the look on his face clearly told me that he feels very fortunate to have the electrifying Charles on his side and that he’s going to give him the ball and let him loose. The acquisition of Smith clearly helps that cause and improves Charles’ value. With the efficient Smith at the helm, the coaches should not only be more consistently committed to the running game, but they should be able to run off more plays, since Smith rarely turns the ball over.</p>
<p>We’ll see about the UFA <strong>Dwayne Bowe</strong>, but this could also help in terms of his return. Reid was high on him when he came out of LSU six years ago, and Bowe could feel more inclined to stick with Reid in town and a QB upgrade in place in Smith. Also, with KC acquiring Smith it definitely means that QB <strong>Geno Smith</strong> is off the board for KC with the 1<sup>st</sup> overall pick. I would be shocked if Smith made it past Oak, Cle, Ari, and Buf, so Smith should still be a top-8 pick, so it’s not a tragedy for him. And finally, this move doesn’t help <strong>Nick Foles’</strong> future fortunes. Another team could step in and trade for Foles, but Foles doesn’t appear to be a major player in <strong>Chip Kelly’s</strong> future plans, and the thought was that Reid could look to acquire him.</p>
<p>So to summarize the implications of Alex Smith the Chiefs, here’s a quick fantasy stock watch for their key players, including Smith:</p>
<p><strong>Alex Smith</strong> – Upgrade, but still a lower-end backup<br />
<strong>Matt Cassel</strong> – Downgrade; you can cut him now in your keeper league<br />
<strong>Jamaal Charles</strong> – Definite upgrade<br />
<strong>Dwayne Bowe</strong> – TBD, but slight upgrade if he sticks in KC<br />
<strong>Tony Moeaki</strong> – Holding steady at worst<br />
<strong>Jonathan Baldwin</strong> – Holding steady at worst</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2013/02/27/alex-smith-an-upgrade-for-chiefs-but-hardly-a-slam-dunk/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Just missed it: Week Ten</title>
		<link>http://www.fantasyguru.com/blog/2012/11/15/just-missed-it-week-ten/</link>
		<comments>http://www.fantasyguru.com/blog/2012/11/15/just-missed-it-week-ten/#comments</comments>
		<pubDate>Thu, 15 Nov 2012 22:26:39 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1188</guid>
		<description><![CDATA[<p></p>
<p></p>
<p class="MsoNormal">Here are more close calls for big plays and TDs from Week Ten. Again, I think this stuff is valuable if you are not able to watch the games because almost scoring or making a big play is a lot better than not even coming close to doing so. As always, these are fairly random in order and not exactly crafted like a wordsmith would. This is merely an FYI.</p>

QB Tom Brady had WR Wes Welker for a sure TD, but Welker dropped it running toward the endzone.
Pass to Patriot TE Rob Gronkowski in the endzone, and PI on the defense was called on the play.
Pass to WR Brandon Lloyd in the endzone, but it was broken up. Later, he had a pass thrown to him deep in the endzone, and defensive PI was called.
Pass to Torrey Smith in the endzone, could have had it, but incomplete. Later, he had another ball thrown to him in the endzone that was very close to a score, but it was incomplete. He did eventually score 2 TDs.
Pass to TE Brandon Myers in the endzone; he was wide open for the TD but it was too high and offensive PI was called [...]]]></description>
				<content:encoded><![CDATA[<p><!--[if gte mso 9]><xml><br />
 <o:OfficeDocumentSettings><br />
  <o:AllowPNG/><br />
 </o:OfficeDocumentSettings><br />
</xml><![endif]--></p>
<p><!--[if gte mso 9]><xml><br />
 <w:WordDocument><br />
  <w:View>Normal</w:View><br />
  <w:Zoom>0</w:Zoom><br />
  <w:TrackMoves/><br />
  <w:TrackFormatting/><br />
  <w:PunctuationKerning/><br />
  <w:ValidateAgainstSchemas/><br />
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
  <w:DoNotPromoteQF/><br />
  <w:LidThemeOther>EN-US</w:LidThemeOther><br />
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian><br />
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript><br />
  <w:Compatibility><br />
   <w:BreakWrappedTables/><br />
   <w:SnapToGridInCell/><br />
   <w:WrapTextWithPunct/><br />
   <w:UseAsianBreakRules/><br />
   <w:DontGrowAutofit/><br />
   <w:SplitPgBreakAndParaMark/><br />
   <w:EnableOpenTypeKerning/><br />
   <w:DontFlipMirrorIndents/><br />
   <w:OverrideTableStyleHps/><br />
  </w:Compatibility><br />
  <m:mathPr><br />
   <m:mathFont m:val="Cambria Math"/><br />
   <m:brkBin m:val="before"/><br />
   <m:brkBinSub m:val="&#45;-"/><br />
   <m:smallFrac m:val="off"/><br />
   <m:dispDef/><br />
   <m:lMargin m:val="0"/><br />
   <m:rMargin m:val="0"/><br />
   <m:defJc m:val="centerGroup"/><br />
   <m:wrapIndent m:val="1440"/><br />
   <m:intLim m:val="subSup"/><br />
   <m:naryLim m:val="undOvr"/><br />
  </m:mathPr></w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"<br />
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"<br />
  LatentStyleCount="267"><br />
  <w:LsdException Locked="false" Priority="0" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/><br />
  <w:LsdException Locked="false" Priority="9" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/><br />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/><br />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/><br />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/><br />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/><br />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/><br />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/><br />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/><br />
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/><br />
  <w:LsdException Locked="false" Priority="39" Name="toc 1"/><br />
  <w:LsdException Locked="false" Priority="39" Name="toc 2"/><br />
  <w:LsdException Locked="false" Priority="39" Name="toc 3"/><br />
  <w:LsdException Locked="false" Priority="39" Name="toc 4"/><br />
  <w:LsdException Locked="false" Priority="39" Name="toc 5"/><br />
  <w:LsdException Locked="false" Priority="39" Name="toc 6"/><br />
  <w:LsdException Locked="false" Priority="39" Name="toc 7"/><br />
  <w:LsdException Locked="false" Priority="39" Name="toc 8"/><br />
  <w:LsdException Locked="false" Priority="39" Name="toc 9"/><br />
  <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/><br />
  <w:LsdException Locked="false" Priority="10" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Title"/><br />
  <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/><br />
  <w:LsdException Locked="false" Priority="11" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/><br />
  <w:LsdException Locked="false" Priority="22" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/><br />
  <w:LsdException Locked="false" Priority="20" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/><br />
  <w:LsdException Locked="false" Priority="59" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Table Grid"/><br />
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/><br />
  <w:LsdException Locked="false" Priority="1" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/><br />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Shading"/><br />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light List"/><br />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Grid"/><br />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 1"/><br />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 2"/><br />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 1"/><br />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 2"/><br />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 1"/><br />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 2"/><br />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 3"/><br />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Dark List"/><br />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Shading"/><br />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful List"/><br />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Grid"/><br />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/><br />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light List Accent 1"/><br />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/><br />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/><br />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/><br />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/><br />
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/><br />
  <w:LsdException Locked="false" Priority="34" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/><br />
  <w:LsdException Locked="false" Priority="29" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/><br />
  <w:LsdException Locked="false" Priority="30" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/><br />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/><br />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/><br />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/><br />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/><br />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Dark List Accent 1"/><br />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/><br />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/><br />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/><br />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/><br />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light List Accent 2"/><br />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/><br />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/><br />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/><br />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/><br />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/><br />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/><br />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/><br />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/><br />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Dark List Accent 2"/><br />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/><br />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/><br />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/><br />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/><br />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light List Accent 3"/><br />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/><br />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/><br />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/><br />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/><br />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/><br />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/><br />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/><br />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/><br />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Dark List Accent 3"/><br />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/><br />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/><br />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/><br />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/><br />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light List Accent 4"/><br />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/><br />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/><br />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/><br />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/><br />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/><br />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/><br />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/><br />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/><br />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Dark List Accent 4"/><br />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/><br />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/><br />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/><br />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/><br />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light List Accent 5"/><br />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/><br />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/><br />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/><br />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/><br />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/><br />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/><br />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/><br />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/><br />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Dark List Accent 5"/><br />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/><br />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/><br />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/><br />
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/><br />
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light List Accent 6"/><br />
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/><br />
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/><br />
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/><br />
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/><br />
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/><br />
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/><br />
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/><br />
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/><br />
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Dark List Accent 6"/><br />
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/><br />
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/><br />
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/><br />
  <w:LsdException Locked="false" Priority="19" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/><br />
  <w:LsdException Locked="false" Priority="21" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/><br />
  <w:LsdException Locked="false" Priority="31" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/><br />
  <w:LsdException Locked="false" Priority="32" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/><br />
  <w:LsdException Locked="false" Priority="33" SemiHidden="false"<br />
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/><br />
  <w:LsdException Locked="false" Priority="37" Name="Bibliography"/><br />
  <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/><br />
 </w:LatentStyles><br />
</xml><![endif]--><!--[if gte mso 10]></p>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Verdana","sans-serif";}
</style>
<p><![endif]--></p>
<p class="MsoNormal">Here are more close calls for big plays and TDs from Week Ten. Again, I think this stuff is valuable if you are not able to watch the games because almost scoring or making a big play is a lot better than not even coming close to doing so. As always, these are fairly random in order and not exactly crafted like a wordsmith would. This is merely an FYI.</p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">QB <strong style="mso-bidi-font-weight: normal;">Tom Brady</strong> had WR <strong style="mso-bidi-font-weight: normal;">Wes Welker</strong> for a sure TD, but Welker dropped it running toward the endzone.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to Patriot TE <strong style="mso-bidi-font-weight: normal;">Rob Gronkowski</strong> in the endzone, and PI on the defense was called on the play.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to WR <strong style="mso-bidi-font-weight: normal;">Brandon Lloyd</strong> in the endzone, but it was broken up. Later, he had a pass thrown to him deep in the endzone, and defensive PI was called.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to <strong style="mso-bidi-font-weight: normal;">Torrey Smith</strong> in the endzone, could have had it, but incomplete. Later, he had another ball thrown to him in the endzone that was very close to a score, but it was incomplete. He did eventually score 2 TDs.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to TE <strong style="mso-bidi-font-weight: normal;">Brandon Myers</strong> in the endzone; he was wide open for the TD but it was too high and offensive PI was called on the play, anyway.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to <strong style="mso-bidi-font-weight: normal;">Tony Gonzalez</strong> in the endzone, but Gonzo unable to haul it in. He obviously scored 2 TDs in the game.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">WR <strong style="mso-bidi-font-weight: normal;">Andrew Hawkins</strong> just missed a second TD on endzone catch, but he caught the ball out of bounds.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">TE <strong style="mso-bidi-font-weight: normal;">Martellus Bennett</strong> caught a pass in the endzone, but he didn&#8217;t get both feel in for the score.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to WR <strong style="mso-bidi-font-weight: normal;">Steve Johnson</strong> in the endzone just before the half, but it was incomplete. He later had two passes in the endzone on a drive, one pass he caught but he was out of bounds, but it was very close to a TD.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Giant WR <strong style="mso-bidi-font-weight: normal;">Victor Cruz</strong> dropped a sure TD running into the endzone.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">RB <strong style="mso-bidi-font-weight: normal;">C.J. Spiller</strong> just missed a TD on a play in which he stepped out inside the five streaking into the endzone.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">RB <strong style="mso-bidi-font-weight: normal;">Michael Turner</strong> got stuffed late in the game on carry right on top of the goal.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to WR <strong style="mso-bidi-font-weight: normal;">Deion Branch</strong> in the endzone late, but it was incomplete.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">TE <strong style="mso-bidi-font-weight: normal;">Scott Chandler</strong> almost made a great one-handed catch to potentially win the game, but it was a no go.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Cowboy CB <strong style="mso-bidi-font-weight: normal;">Orlando Scandrick</strong> just missed a pick-6 against QB <strong style="mso-bidi-font-weight: normal;">Nick Foles</strong>. Of course, they did score two defensive TDs.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass down the field to WR <strong style="mso-bidi-font-weight: normal;">Brandon Marshall</strong> in the endzone, was a sure TD, but he couldn&#8217;t hold on.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Deep pass to WR <strong style="mso-bidi-font-weight: normal;">Mike Wallace</strong> streaking into the endzone, and he couldn&#8217;t haul it in. He did score on the drive.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">WR <strong style="mso-bidi-font-weight: normal;">Dwayne Bowe</strong> had a nice little TD catch that was called back for holding.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to WR <strong style="mso-bidi-font-weight: normal;">Emmanuel Sanders</strong> in front of the endzone, but it really didn&#8217;t have a chance.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Steeler S <strong style="mso-bidi-font-weight: normal;">Ryan Clark</strong> failed to catch a sure INT that he probably would have taken to the house in the 4th quarter.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">RB <strong style="mso-bidi-font-weight: normal;">Jonathan Stewart</strong> had a 62-yard catch and run called back.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to TE <strong style="mso-bidi-font-weight: normal;">Jacob Tamme&#8217;s</strong> direction in front of the endzone, but <strong style="mso-bidi-font-weight: normal;">Peyton Manning</strong> was hit as he threw it and it was incomplete.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Deep pass to <strong style="mso-bidi-font-weight: normal;">Demaryius Thomas</strong> on the right side, it was a little overthrown or it might have been a long TD. Thomas later caught a long pass running to the endzone but was knocked out at the 4.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Deeper pass in the endzone to Panther WR <strong style="mso-bidi-font-weight: normal;">Armanti Edwards</strong>, was incomplete.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to WR <strong style="mso-bidi-font-weight: normal;">Kenny Britt</strong> in the endzone, but he was double covered</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to WR <strong style="mso-bidi-font-weight: normal;">Brian Hartline</strong> in the endzone, but good covered and broken up.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">WR <strong style="mso-bidi-font-weight: normal;">Donald Jones</strong> caught a pass inside the 5 and almost rolled into the endzone, but was down inside the 1. <strong style="mso-bidi-font-weight: normal;">Fred Jackson</strong> scored on the drive.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">RB <strong style="mso-bidi-font-weight: normal;">Fred Jackson</strong> fumbled on a run inside the 1 late in the game.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to WR <strong style="mso-bidi-font-weight: normal;">TJ Graham</strong> in the endzone at the end of the game was picked to ice the win for the Patriots.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Deep ball to WR <strong style="mso-bidi-font-weight: normal;">Denarius Moore</strong> early in the game streaking into the endzone, but incomplete and well covered.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">RB <strong style="mso-bidi-font-weight: normal;">Ray Rice</strong> missed a TD by about a foot early in the game on a run, and <strong style="mso-bidi-font-weight: normal;">Joe Flacco</strong> snuck it in on the next play.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to WR <strong style="mso-bidi-font-weight: normal;">Anquan Boldin</strong> in the endzone, incomplete. They faked a FG for a TD on the next play.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Deep pass in the endzone to Raider WR <strong style="mso-bidi-font-weight: normal;">Derek Hagan</strong>, but off his fingertips.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">WR <strong style="mso-bidi-font-weight: normal;">AJ Green</strong> just missed a jump-ball in the endzone for what would have been his second TD in the first quarter. He had another pass thrown to him in the endzone on the next play.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">WR <strong style="mso-bidi-font-weight: normal;">Roddy White</strong> on their first drive caught a long pass and was knocked down at the 1, pretty close to a score. He also had a goal line pass thrown to him in the endzone late in the game that was broken up. At the end of the game, Roddy has some space for game-winning TD, but he seemed to stop too soon and/or wasn’t on the same page at the QB.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Short pass to <strong style="mso-bidi-font-weight: normal;">Julio Jones</strong> in the endzone in the 4<sup>th</sup> quarter; he got his hands on it, but it was incomplete.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Pass to WR <strong style="mso-bidi-font-weight: normal;">Marques Colston</strong> in the endzone was broken up; this was after his early TD.</li>
<li class="MsoNormal" style="mso-list: l0 level1 lfo1;">Viking Rookie <strong style="mso-bidi-font-weight: normal;">Jarius Wright</strong> came very close to scoring on a deep ball, one he caught was came down with at about the 1. He scored on that drive.</li>
</ul>
<p><a style="color: #000000; outline: none; text-decoration: initial; display: block; font-family: arial, verdana, sans-serif; font-size: 19px; font-style: normal; font-variant: normal; font-weight: bold; letter-spacing: normal; line-height: 23.03333282470703px; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: #ffffff;" title="Just missed it: Week Nine" href="http://www.fantasyguru.com/blog/2012/11/08/just-missed-it-week-nine/">Just missed it: Week Nine</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2012/11/15/just-missed-it-week-ten/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Just missed it: Week Nine</title>
		<link>http://www.fantasyguru.com/blog/2012/11/08/just-missed-it-week-nine/</link>
		<comments>http://www.fantasyguru.com/blog/2012/11/08/just-missed-it-week-nine/#comments</comments>
		<pubDate>Thu, 08 Nov 2012 22:38:31 +0000</pubDate>
		<dc:creator>John Hansen</dc:creator>
				<category><![CDATA[Fantasy Football]]></category>

		<guid isPermaLink="false">http://www.fantasyguru.com/blog/?p=1185</guid>
		<description><![CDATA[<p>I may have missed a few more near TDs than usual this week, but here is what I got from Week Nine in terms of passes in the endzone, near scores, and more.</p>

Pass to WR Dwayne Bowe running to the endzone, was incomplete. On the same drive, he was open for a TD but it didn’t happen.
Pass to TE Dante Rosario in the endzone, but it was incomplete.
WR Calvin Johnson just missed the endzone on a 38-yard catch, but he was once again down at the one. Pass to Calvin later near the endzone, but it was incomplete.
Pass to WR TY Hilton in the endzone, but it was broken up. He also had a long TD, but he couldn&#8217;t hang on to it. He did eventually score, of course.
Pass to TE Jared Cook in the endzone was caught, but he was out of bounds.
Pass to WR Kenny Britt in the endzone, incomplete, this was before he scored.
Pass to Kendall Wright in the endzone, incomplete.
QB Peyton Manning’s endzone INT was intended for Eric Decker in the endzone; looked like the throw was slightly off.
Pass to WR James Jones in the endzone after his TD, but it was incomplete.
Pass to Bengal WR [...]]]></description>
				<content:encoded><![CDATA[<p>I may have missed a few more near TDs than usual this week, but here is what I got from Week Nine in terms of passes in the endzone, near scores, and more.</p>
<ul>
<li>Pass to WR <strong>Dwayne Bowe</strong> running to the endzone, was incomplete. On the same drive, he was open for a TD but it didn’t happen.</li>
<li>Pass to TE <strong>Dante Rosario</strong> in the endzone, but it was incomplete.</li>
<li>WR <strong>Calvin Johnson</strong> just missed the endzone on a 38-yard catch, but he was once again down at the one. Pass to Calvin later near the endzone, but it was incomplete.</li>
<li>Pass to WR <strong>TY Hilton</strong> in the endzone, but it was broken up. He also had a long TD, but he couldn&#8217;t hang on to it. He did eventually score, of course.</li>
<li>Pass to TE <strong>Jared Cook</strong> in the endzone was caught, but he was out of bounds.</li>
<li>Pass to WR <strong>Kenny Britt</strong> in the endzone, incomplete, this was before he scored.</li>
<li>Pass to <strong>Kendall Wright</strong> in the endzone, incomplete.</li>
<li>QB <strong>Peyton Manning’s</strong> endzone INT was intended for Eric Decker in the endzone; looked like the throw was slightly off.</li>
<li>Pass to WR <strong>James Jones</strong> in the endzone after his TD, but it was incomplete.</li>
<li>Pass to Bengal WR <strong>Muhammad Sanu</strong> in the endzone, but it was incomplete.</li>
<li>Pass to Panther WR <strong>Steve Smith</strong> in the endzone, incomplete but defensive pass interference on the play.</li>
<li>Brown WR <strong>Josh Gordon</strong> had a TD taken off the board, and it was actually a shorter slant pass, not down the field.</li>
<li>WR <strong>Andre Johnson</strong> caught a pass running to the endzone, but he was brought down inside the 5 and Foster scored on the next play. He later had a nice pass thrown to him for what would have been a TD but it was overthrown, he was open.</li>
<li>QB <strong>Robert Griffin III</strong> had a TD run taken off the board and on the same drive he had a TD pass to Leonard Hankerson taken off the board.</li>
<li>WR <strong>Leonard Hankerson</strong> also had a deep pass thrown to him in the endzone, but it was incomplete.</li>
<li>Pass to WR <strong>Roddy White</strong> in the endzone late in the game, but it was incomplete.</li>
<li>Pass to Eagle WR <strong>Jeremy Maclin</strong> in the endzone late in the game, but it was too high.</li>
<li>WR <strong>Josh Morgan</strong> had a pass thrown to him in the endzone, but it was broken up.</li>
<li>WR <strong>Armanti Edwards&#8217;</strong> 82 yard TD could have easily been a 92 YD TD, but he was caught and brought down by the 1 defender who had a prayer.</li>
<li>WR <strong>Steve Smith</strong> had a 40-yard bomb thrown to him in the endzone; he almost caught it, but he had a defender on him and it was incomplete.</li>
<li>Pass to WR <strong>Michael Floyd</strong> in the endzone, but it was too high.</li>
<li>RB <strong>LaRod Stephens-Howling</strong> had a carry inside the 3 late in the game, but he was stopped</li>
<li>QB <strong>Matt Stafford</strong> had WR <strong>Titus Young</strong> wide open in the endzone for TD in the endzone, but it was slightly overthrown</li>
<li>Pass to Jaguar WR <strong>Laurent Robinson</strong> in the endzone late, but it was incomplete.</li>
<li>Pass to TE <strong>Marcedes Lewis</strong> in endzone late, but it was too high.</li>
<li>Bear WR<strong> Devin Hester</strong> came very close to returning punt for TD.</li>
<li>CB <strong>Charles Tillman</strong> was 3-4 yards away from giving the Bears their third defensive TD against the Titans.</li>
<li>WR <strong>AJ Green</strong> came close to a second TD on a catch-and-run, but was down at the 3. QB <strong>Andy Dalton</strong> also had AJ Green for a possible 70-yard TD, but there was defensive holding.</li>
<li>Pass to WR <strong>Demaryius Thomas</strong> in the endzone, incomplete. Dreessen scored on that drive.</li>
<li>Pass to TE <strong>Anthony Fasano</strong> at about the 2, probably would not have scored, but it would have been close as he was open.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.fantasyguru.com/blog/2012/11/08/just-missed-it-week-nine/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
