Titans RB Chris Johnson Named AFC Offensive Player Of The Week

Rams Rookie QB Sam Bradford Signs Deal That Includes $50 Of His $78 Million Guaranteed

The St. Louis Rams and former Oklahoma quarterback Sam Bradford agreed to terms on a record setting six-year, $78 million deal Friday night. For Bradford, it gets better. The d.

Cowboys Rookie WR Dez Bryant Out 4-6 Weeks With A High Ankle Sprain

Dallas Cowboys rookie wide receiver Dez Bryant was helped off the field on Friday after suffering a sprained ankle late in the team’s afternoon practice. The team announced.

Broncos Sign First-Round Pick QB Tim Tebow To A Five-Year Deal

Former Florida Gators quarterback Tim Tebow agreed to a contract with the Denver Broncos on Thursday. The deal for the 25th overall draft pick is for five years with $8.7 milli.

Steelers Sign Former Cowboys T Flozell Adams To A Two-Year Deal

ESPN’s Adam Schefter reports that former Dallas Cowboys left tackle Flozell Adams has signed a two-year deal with the Pittsburgh Steelers. It’s unknown whether Adams .

Browse: Home → AFC → Titans RB Chris Johnson Named AFC Offensive Player Of The Week

Titans RB Chris Johnson Named AFC Offensive Player Of The Week

05 November 2009
AFC
147900 Comment2009-11-05+15%3A00%3A50MKRob

chrisjohnson

Tennessee Titans running back Chris Johnson was named AFC Offensive Player Of The Week after he set a franchise record in rushing yards in a single game, with 228 in a 30-13 win over the Jacksonville Jaguars.

He carried the ball 24 times and had touchdown runs of 52 and 89 yards to help the Titans (1-6) to their first win of the season.

Johnson’s counterpart on Jacksonville, Maurice Jones-Drew, had touchdown runs of 80 and 79 yards, making it the first time in NFL history that there were four rushing touchdowns of at least 50 yards in a single game.

In his second season out of East Carolina, Johnson earned his first weekly award.

Share

This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.