FBG Mobile Home

Week 1 vs. TEN

Receiving: 1 / 11 / 0 on 2 targets

Heyward-Bey's first target came late in the third quarter, and he had no chance on a tipped pass. Later, he made an 11-yard reception that took him to the 5-yard line.


Week 2 vs. STL

Receiving: 6 / 80 / 0 on 13 targets

Heyward-Bey, like McFadden, played up to the level at which he was drafted. He made himself available for his quarterback and made plays when given the chances. Murphy is clearly this team's number-one, but if Heyward-Bey can build on this performance and continue to perform, he can become a viable number-two. Everyone knows he has the physical tools to do so. Heyward-Bey outfought defensive players for extra yardage and had the best game of his career by far.


Week 3 vs. ARI

Receiving: 3 / 49 / 0 on 11 targets

Heyward-Bey did not make a big impact on the stat sheet, but he drew multiple pass interference penalties, including the one that set up what should have been the game-winning field goal. Gradkowski missed Heyward-Bey when he was open downfield early, and the two's timing was off on another early throw, but the combo started hooking up as the game went on and Heyward-Bey showed off his excellent run after catch instincts. Heyward-Bey got numerous end zone targets in the fourth quarter, but couldn't convert any of them, although one drew a pass interference. The terrible rookie season seems to be completely behind DHB.


Week 4 vs. HOU

Receiving: 1 / 2 / 0 on 5 targets

Heyward-Bey was once again inconsistent as a receiver against the Texans on Sunday. He was targeted deep downfield twice, once resulting in an incompletion and once resulting in an interception off a deflection. He also was targeted on four short passes but was only able to catch one at which point he was immediately wrapped up for a two yard gain. As the game wore on, it was clear that quarterback Bruce Gradkowski was targeting Zack Miller and his running backs much more then Heyward-Bey. On most routes after the first quarter, Heyward-Bey was sent on short crossing patterns or hooks and was ignored almost completely as the Raiders offense went to other parts of the field.


Week 5 vs. SD

Receiving: 0 / 0 / 0 on 2 targets

Heyward Bey suffered from Jason Campbell syndrome today. He had no catches, which is not atypical for a boom or bust WR of his calibre. He just did not get enough looks downfield from Campbell, and is perhaps lacking his trust to put the ball out there for Heyward Bey to catch.


Week 6 vs. SF

Receiving: 3 / 19 / 0 on 4 targets

The effectiveness of Darrius Heyward-Bey was limited due to the poor play of the Raiders offensive line, which didn't afford Campbell time to get the ball to his receivers downfield. Heyward-Bey made a nice catch early in the game as he caught a pass along the sideline and absorbed a wicked hit, but impressively maintained possession. The 49ers only gave up yards in small chunks to the Raiders passing game, and Heyward-Bey couldn't get into his stride.


Week 8 vs. SEA

Rushing: 1 / 30 / 0
Receiving: 5 / 105 / 1 on 9 targets

Thrust into the number one role, Heyward-Bey looked like a legitimate NFL starter. He showed that he's more than a one-trick pony, as he burned the defense on short comeback patterns when they over respected his speed, burned them deep when their coverage lapsed, and even started out the game with a 30 yard gain on the ground. His touchdown was gorgeous: he stopped his man with a turn-around move, then zoomed upfield and caught it as the safety was bearing down on him. He then took advantage of the safety over-committing, and made his way easily into the end zone. He still had rough patches (unable to bring his body to the ball on one long would-be catch, for example, and instead reached out and bobbled it awkwardly) so he probably shouldn't be counted on yet from week to week, but is definitely heading in the right direction.


Week 9 vs. KC

Receiving: 0 / 0 / 0 on 5 targets

Heyward-Bey had an ugly game, characterize by multiple drops, including one in the end zone, and errant passes from Campbell when he did get open. DHB's thunder from last week was stolen by Jacoby Ford in this game, so it's questionable whether he is worth holding through his bye next week.


Week 12 vs. MIA

Rushing: 1 / 2 / 0

Had 1 carry in the game and that was it. No factor in the passing game at all.


Week 13 vs. SD

Rushing: 1 / 14 / 0

Heyward-Bey didn't record a single reception in the game, and was limited to a ten yard rush on a reverse on the play that Jason Campbell had to leave the game briefly due to injury.


Week 14 vs. JAX

Receiving: 2 / 40 / 0 on 3 targets

DHB looked good catching the ball on a comeback route, getting excellent separation from his DB and showing reliable hands that have been questioned many times so far in his short career. DHB also was able to get inside on a mis match vs. a Safety and exploited this after play action for another big pass. DHB has not become the go to guy however and his involvement and presence on the field was still spotty at infrequent at best.


Week 15 vs. DEN

Receiving: 1 / 20 / 0 on 2 targets

Darrius Heyward-Bey only made one catch but it was an impressive 20 yard grab along the sideline as Campbell put it up high and DHB attacked it in the air. He did well to come down with it.


Week 16 vs. IND

Receiving: 4 / 40 / 0 on 6 targets

DHB had a few short passes, and was able to probably the most consistent receiver for Campbell. However, Heyward-Bay wasn't brought to the Raiders to be a possession receiver, and at no time was he able to get deep down the field and stretch the defense.


Week 17 vs. KC

Rushing: 1 / 2 / 0
Receiving: 0 / 0 / 0 on 3 targets

DHB fumbled early on an end around and despite being targeted a couple of times, he failed to make any catches in this one. What he lacks is that polish that receivers need to succeed at the pro level. He fails to grasp the little things like coming back to the football to help your quarterback and general field awareness. In time, he can become better but I wonder just how good DHB can be if his career continues on this conspicuously unproductive path.