WR Chris Horn - Free Agent

5-11, 195Born: 7-13-1977College: Rocky MountainDrafted: ---

Main      Career stats      Game Logs      Game Recaps      Split Stats      Play-by-play      Latest News

Game Recaps

2005 Week 2 vs OAK (2 / 2 / 25 / 0 rec)

Chris Horn ran sharp routes and was dependable as he caught both passes thrown to him.

2005 Week 3 vs DEN (0 / 0 / 0 / 0 rec)

Horn was not called on much during the game. He was not utilized very much and when he was in, Green did not have time to find him open before the Denver pass rush found Green.

2005 Week 7 vs MIA (2 / 1 / 50 / 0 rec)

Horn had one excellent catch where he gained separation from double coverage for a 50 yard over the shoulder completion from Trent Green. He made the catch with two defenders right on his heels. This was on the opening drive and helped open up all phases of the Chiefs' offense.

2005 Week 8 vs SD (8 / 7 / 58 / 0 rec)

Horn saw a ton of action in the game, and all of his production came after halftime. He was targeted seven times in the second half alone, and did a good job of getting open in the San Diego secondary. He wasn't exactly a playmaker, but he didn't drop anything and was a solid outlet for Green.

2005 Week 9 vs OAK (6 / 4 / 25 / 0 rec)

Horn was targeted in the end zone. He made the first reception of the game, a short one yard catch. Horn also made a 12 yard catch during the Chiefs' game winning drive.

2005 Week 10 vs BUF (6 / 2 / 15 / 0 rec)

Horn was not much of a factor in the game, catching two of his six targets. He dropped an easy pass when wide open as one drive ended in a missed field goal attempt.

2005 Week 15 vs NYG (4 / 0 / 0 / 0 rec)

Horn was targeted four times, but only one was catchable. He had a pass of about 30 yards skip off his fingers in the third quarter. Had he caught the ball it would have set up a first and goal for the Chiefs. Horn just happened to be the closest receiver on two other targets as QB Trent Green threw the ball away while scrambling. Another pass was in his general direction, and he may have been the intended receiver but just ran a very poor (or wrong) route.