Tony Moeaki: Updated Fantasy Outlook & Analysis for Chiefs TE

Thomas GaliciaFeatured Columnist IVNovember 12, 2012

PITTSBURGH, PA - NOVEMBER 12:  Tony Moeaki #81 of the Kansas City Chiefs runs for yards after the catch against Keenan Lewis #23 of the Pittsburgh Steelers at Heinz Field on November 12, 2012 in Pittsburgh, Pennsylvania.  (Photo by Gregory Shamus/Getty Images)
Gregory Shamus/Getty Images

The Kansas City Chiefs don't get much offense outside of running back Jamaal Charles and wide receiver Dwayne Bowe (and even Bowe isn't a given), so it wouldn't be a surprise if you overlooked tight end Tony Moeaki.

Moeaki's stats so far this season aren't much to look at either.

Coming into the game, Moeaki only had 14 receptions for 151 yards and still has had yet to score a touchdown. Against the Pittsburgh Steelers on Monday Night Football, Moeaki did have a slightly larger impact on the Chiefs offense, catching the ball three times for 68 yards.

This is not much of a surprise, as it fits the philosophy of Chiefs offensive coordinator Brian Daboll.

Daboll is known for using his tight ends mainly for blocking purposes, using a ground-and-pound philosophy. Last season when Daboll was in Miami, Anthony Fasano only had 35 receptions in 15 games for 451 yards. However, he did score five touchdowns, while this season Moeaki is still awaiting his first touchdown reception of the season.

This will likely continue to be the role that Moeaki is used in. He won't be Kansas City's top option and will likely only catch the ball whenever Matt Cassel has to check down. His touchdown numbers should increase just a tad, but the only way you will likely see him score is if he's open in the red zone.

According to, Moeaki is projected to finish with 28 receptions for 302 yards and no touchdowns.

It's highly doubtful that Moeaki won't score a touchdown considering that his 6'3", 251-lb size is a valuable asset to the Chiefs in short-yardage situations, but that size is also valuable when the Chiefs need someone to block for Charles when they attempt a run.

If Moeaki is available on your waiver wire (and he probably is), the only reason I'd grab him would be if your tight end is injured and there aren't any other options. Other than that, stay away. Kansas City's scheme is not conductive to using the tight end as a primary receiver, and if you have to start Moeaki, not only will he suffer from lack of scoring, but you will too.