Around the League

Presented By

Nate Burleson 'not shocked' Detroit Lions cut him

It wasn't a surprise when the Detroit Lions cut Nate Burleson on Thursday. Fans weren't surprised, we weren't surprised and the wide receiver wasn't surprised.

The 11-year-pro told NFL Network's "NFL AM" on Friday that he knew it was "50-50" whether he'd stay in Detroit or be cut.

"I'm lucky. I've been in the league for over 10 years so I wasn't too shocked," Burleson said. "It was a move they had to make. I was a little disappointed that I wasn't able to retire a Lion, but I understand the business side of things."

Burleson's first two seasons in Detroit were highly productive. In 2011, he was part of the reason Matthew Stafford threw for 5,038 yards. His 757-yard season helped the Lions return to the playoffs for the first time in 12 years.

"In my own career there I just wish I wasn't injured as much," said the man who missed 17 games the past two seasons. "When I was on the field I felt like I was very productive, a great piece to the team, a complement to Calvin (Johnson). In retrospect I had a great time here."

The media-savvy veteran said he understood the Lions' position. The team saved $5.5 million on the cap by cutting the receiver. Burleson said the Lions did discuss the possibility of bringing him back down the line (at a low salary), but he plans to be playing in another jersey by that point.

"I'd just like to go to a team that's got an established No. 1 (receiver) and work the slot," he said. "I've been able to show my versatility -- play outside, play inside -- and I can go somewhere and be a tall, strong slot receiver, chain-moving slot receiver. (I'm) talking about an offense that is productive and a team that can make it to the postseason. At this point I'm not playing for the dollars; I think it's very obvious."

On the latest edition of the "Around The League Podcast," the guys huddle with Seahawks trio Michael Robinson, Brandon Mebane and Red Bryant before unpacking Cleveland's week of chaos.

This article has been reproduced in a new format and may be missing content or contain faulty links. Please use the Contact Us link in our site footer to report an issue.

Related Content